You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current range node doesn't use same conditions for all boundary values. I think that the following conditions should be applied for all boundary values.
Minimum boundary condition: Minimum value and more than minimum value
Maximum boundary condition: Less than maximum value
But in some cases, range node uses the following conditions.
Minimum boundary condition: More than minimum value
Maximum boundary condition: Less than maximum value and maximum value
For example, a user selects "Scale and wrap within the target range" as Action in the property of range node. After that, the user sets 0-10 as input values and 0-360 as output values.
The following graph is output when range node processes values between -30 and 30 as input.
As the graph result, range node uses incorrect boundary conditions (red circle) when input values are between -30 and -10.
The text was updated successfully, but these errors were encountered:
Current range node doesn't use same conditions for all boundary values. I think that the following conditions should be applied for all boundary values.
But in some cases, range node uses the following conditions.
For example, a user selects "Scale and wrap within the target range" as Action in the property of range node. After that, the user sets 0-10 as input values and 0-360 as output values.
The following graph is output when range node processes values between -30 and 30 as input.
As the graph result, range node uses incorrect boundary conditions (red circle) when input values are between -30 and -10.
The text was updated successfully, but these errors were encountered: