Unexpected behavior: Sin(time) seems to be "invisibly" remapped
Hi, there! This is a quick, and maybe pedantic question about the Sin and Time nodes in Unreal, but I'm experiencing some odd behavior that I'd like to better understand.
In this screen recording, I have a simple material set up with sin(time) going into the opacity channel (after being remapped from
In my mind, the expected behavior would be a period of 2π, or 6.28 seconds, because the sin node receives an input in radians and the default period of a sin operation is 2π. Meanwhile, when I try to multiply the Time node output by
So, what's going on here? Does the sin node somehow "know" that it's receiving a time input and trigger some special remapping behavior? Is my time input just operating on a 2π-multiplied scale? This isn't necessarily a blocker, but if there's some predetermined behavior I'd like to know how it works and be able to work around it
Much thanks! Brendan
asked Sep 11 '17 at 10:40 PM in Rendering
This is definitely an intended behavior.
answered Sep 11 '17 at 10:59 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here