Ramlyn
![]() |
||
Posted: February 16, 2020 5:54 am | ||
Ramlyn
![]() |
The Switch has all sources originally set to transparent (white).
The picture shows two examples. The first example, the polygon should disappear if Scale goes to 0, instead it becomes something like many stripes. The second case there are 4 inputs, none of them should generate anything of that color, but with Scale to 0, ... you can see the result. Is it only my computer? I attach the filter. Error Test.ffxml |
|
Posted: February 16, 2020 5:59 am | ||
Sphinx.
![]() |
I can reproduce this. The pink is the default error color in other components, like when you divide by zero. Normally we have a dedicated input for that case (e.g. see Divide). However I've never seen this with the Scale component before, even with Scale = 0, so something else is going on here.
It seems to be related to the Blur component (and probably any other Bitmap based component). It probably reduces the floating point bit depth to single precision, which causes zero checks to fail somewhere down the line.. |
|
Posted: February 16, 2020 8:01 am | ||
GMM
Moderator
Posts: 3491 |
Sphinx is correct: you have stumbled into the precision threshold. Try changing the scale value from 0 to 0.00001.
|
|
Posted: February 18, 2020 9:20 am | ||
Ramlyn
![]() |
Thanks GMM.
Yes, in the filter that I was making it was easy to solve. I didn't need negative or exactly 0 values, then I selected as minimum value 0.0001. But I think it would be useful to solve it in the component structure too, because sometimes the controls don't allow us to avoid to pass through zero. |
|
Posted: February 24, 2020 12:45 am |
Filter Forge has a thriving, vibrant, knowledgeable user community. Feel free to join us and have fun!
33,711 Registered Users
+18 new in 30 days!
153,531 Posts
+39 new in 30 days!
15,347 Topics
+72 new in year!
17 unregistered users.