YOUR ACCOUNT

meyendlesss
???????????

Posts: 395
Filters: 32
I noticed something weird while plugging a Free Gradient into a Divide component...
What's causing the line to show up?

  Details E-Mail
meyendlesss
???????????

Posts: 395
Filters: 32
Invert the gradient and the line is gone...

  Details E-Mail
meyendlesss
???????????

Posts: 395
Filters: 32
Rotating also gets rid of it...

  Details E-Mail
meyendlesss
???????????

Posts: 395
Filters: 32
This time I typed in 0.50000000000001 (which showed still as 0.5) for the 'start X' and got a single pixel in the corner...

  Details E-Mail
meyendlesss
???????????

Posts: 395
Filters: 32
Is this some kind of bug in the gradient or divide components?
Or is it something that I just don't understand?
  Details E-Mail
Totte
Übernerd

Posts: 1460
Filters: 107
Isn't that divide by zero or something?
- I never expected the Spanish inquisition
  Details E-Mail
Vladimir Golovin
Administrator
Posts: 3446
Filters: 55
Pink is error color (see the inputs of the Divide component). If you see pink in the output of Divide, it means you're dividing by zero in that region.
  Details E-Mail
meyendlesss
???????????

Posts: 395
Filters: 32
I kind of asked the original question in a hurry...
I understand what the error color is.
I'm still curious why it's not there if I invert or rotate the gradient.
Wouldn't it still be dividing by 0 and still show the error color?
  Details E-Mail
tigerAspect
Posts: 222
Filters: 9
This could be a symptom of the weird gradient bug where white is black. I know it exists in Free Gradient, so I don't see why it wouldn't show up in an Angular one. Granted, it could be in Elevation gradient, so this may be unrelated.
  Details E-Mail
Sphinx.
Filter Optimizer

Posts: 1750
Filters: 39
It is due to floating point precision and the way floating point values are represented bitwise (approximations).

In your first example, the lowest value is 0, but the highest is 0.9992274. If you invert this, you will not get an exact zero, but something close to.

Small changes (like rotate) can change the exact representation slightly which is why you see different results.

Perhaps it traces back to the precision of the internal angular gradient function, dunno.
  Details E-Mail

Join Our Community!

Filter Forge has a thriving, vibrant, knowledgeable user community. Feel free to join us and have fun!

33,712 Registered Users
+19 new in 30 days!

153,534 Posts
+27 new in 30 days!

15,348 Topics
+72 new in year!

Create an Account

Online Users Last minute:

31 unregistered users.