02-27-2023, 07:13 PM
Ah interesting...
So basically what's happening is this:
Terrain colors in tyFlow are all stored as 3 1-byte integers (R/G/B)...this gives a channel precision of 0-255 for each channel, which is pretty standard for colors in various image formats.
However, for something like this that requires more precision - a precise falloff value - that level of precision isn't enough, and the original float values (4-bytes) are being clamped to fit inside the color channel (1-byte G channel)...so that's where the banding is coming from.
What's the solution? Well currently there isn't one...although I could see maybe adding a blur/smoothing parameter in the future, in that interpolation rollout, so that when you use color values for interpolation you can smooth out the stepping that isn't perceptible when the value is used for color information but is perceptible when used as height information.
So basically what's happening is this:
Terrain colors in tyFlow are all stored as 3 1-byte integers (R/G/B)...this gives a channel precision of 0-255 for each channel, which is pretty standard for colors in various image formats.
However, for something like this that requires more precision - a precise falloff value - that level of precision isn't enough, and the original float values (4-bytes) are being clamped to fit inside the color channel (1-byte G channel)...so that's where the banding is coming from.
What's the solution? Well currently there isn't one...although I could see maybe adding a blur/smoothing parameter in the future, in that interpolation rollout, so that when you use color values for interpolation you can smooth out the stepping that isn't perceptible when the value is used for color information but is perceptible when used as height information.