- User Since
- Jul 29 2008, 1:46 AM (593 w, 2 d)
Tue, Dec 10
Mon, Dec 9
Keep patch updated with master.
Code changed quite a bit, I think I caught everything.
Keep patch updated to master.
Keep patch updated with master
Sat, Dec 7
This adds label support to sockets much like nodes. This is a proof of concept to see if this approach is acceptable as changing socket name is complicated and hints at future nodes refactor.
Resolved by updating cmake. I had an old version that did not support the touch command on Windows.
Fri, Dec 6
Hi @Brecht Van Lommel (brecht) I've got dynamic labels working in the math node update function that also hides sockets when not required.
After making changes to D5827 I realised that it would make sense to add lerp, inverse_lerp and smoothstep to this patch. Is that a reasonable thing to do now while waiting for approval? I think that would complete my work on the maths node. I've already got the code prepared and ready here: P1180
The original code for map range was as follows:
Thu, Dec 5
Address comments including a change to the step behaviour to relate to input range rather than [0-1].
Refactor and add Interpolation modes to Map Range node
I've rewritten the patch so that it incorporates the different interpolations into the map range node. This works by applying the interpolation option to the from values and then mapping to the to values.
Wed, Dec 4
@Brecht Van Lommel (brecht) @Jacques Lucke (JacquesLucke) After taking a looking at the Map Range code, I think combining these functions into the Map Range node is not such a good fit. The inputs To Min and To Max are misleading and do not work for these interpolation functions. The inputs From Min and From Max are not required for these functions. This would mean additional sockets, ambiguous variable names and introducing more complexity into the map range code to account for the different functions.
Tue, Dec 3
Remove node labels for Interpolate node. Clearer to just show Interpolate.
Fix unused variable warning.
Split into two nodes, Interpolate and Smoothstep.
I think splitting the node into two as suggested by @Bartosz Moniewski (monio) is best and makes it less ambiguous. This way, the commonly used smoothstep has it's own node. I think map range node is well defined already and it's already used for the compositor too. I'll also remove the smooth mode as this can be recreated using a smoothstep node when they are split.
Mon, Dec 2
I've renamed Stepped to Linear Stepped and Smooth to Linear Smooth. This avoids confusion with the Smoothstep function.
Address comments and rename 'smooth' to 'linear smooth' and 'stepped' to 'linear stepped'.
Fri, Nov 29
Wed, Nov 13
Nov 6 2019
Quick fix: https://developer.blender.org/P1153
@Antonio Vazquez (antoniov) I'll take a look. Fix straight into 2.81 or master?
Nov 5 2019
Oct 30 2019
Oct 26 2019
Oct 23 2019
These are keys that work with guides in GP draw mode.
@Antonio Vazquez (antoniov) Yes, looks like it. I'll add descriptions to these.
Oct 20 2019
Oct 19 2019
Add back ESC key to cancel
Add back FKEY for brush size
Oct 18 2019
Add back mousewheel support to increase number of points per line
Add back control point to show last pivot point
When features get deprecated or refactored the DNA remains in Blender files. The only other suggestion is to reintroduce the switch statement for supported DNA values.
Checking the count does not work here as the array length and key values may not be in sync in the future. What needs testing is if the custom1 value is a known field otherwise assume it is unknown. The way it is now means that 2.81 will crash when opening files with unknown values. Unknown values always need to be handled.
@Brecht Van Lommel (brecht) @Omar Emara (OmarSquircleArt) @Jacques Lucke (JacquesLucke)
node_shader_math.c and other refactored nodes
There is a crashing issue with the way that the GPU functions are called. I encountered this when opening a file from a test build which was saved with a newer option added.
Blender builds prior to this commit used a case statement which allowed for unknown values.
Current builds crash when opening this file.