The remap node is what creates the thickness of the sine wave. There are other nodes for noise, speed etc.
I have noticed this poor quality in other shaders I am trying to create, including one where I am using a texture of a sine wave and then colouring it for use in a Line Render. Even though the texture is 1024 when it is applied to a material and added to the line, it looks like a resized 32 pixel image stretched out.
Looks like floating point precision problem, but can you show us the whole graph?
It’s hard to guess what exactly caused this from these 3 nodes - waves on the left already look off, so maybe there is big number coming from time node or something similar.
The time node gives you constantly growing time value, but float loses precision with high numbers, so it can produce jumps, gaps, pixelization and similar stuff depending on what you do.
To be more precise, when time goes above 30.000s (in your graph) you can notice quality is significantly dropping and above certain threshold it starts to chunkify your wave - you can test it by adding some big number to time value.
You may say that your editor is not running for such a long time, but you multiply your input by speed and perform some other calculations, so it can become distorted even after 1-2 hours.
I know two ways to fix that, you either provide your custom time to shader with “looping” to reset it when scene is loaded or other event happens (bug). Or the other way is to put modulo to make time loop in shader, but the obvious downside is that at some point in time there will be “jump” to 0.
It was running overnight again and when I looked at it the sine wave had completely broken down into a few blocks! This is quite an interesting problem. Would the Modulo work if you also added 0.01 so it was never zero?
