Hey Real Time! I’ve been working on a pixel / dot style water shader, but ran into a bit of a problem. Essentially, the shader is set-up to create a eroding caustic effect through panning textures, but when the textures interact they smoothly pan over each other, causing the resultant caustic texture to not have discrete “pixelated” (1x1) edges.
Is there some form of texture compression or panning option that would make the pixels “step” discretely to get a proper pixelated erosion? The textures being used have been converted to paper 2D to alias properly at low resolutions, and are the same resolution.
Sorry if the explanation is a bit confusing, I’m having trouble describing the issue specifically!
@Lush That link was exactly what I was looking for! I would never have thought to ceil time to get discrete stepping, it makes so much sense. There’s a bit of artifacting happening when I “re-pixelate” my already low-res textures, but I think that can be fixed by just re-exporting them to be higher res first before pixelating them in the shader.
@Niels Thanks for the advice! Right now the resultant masks are clamped into discrete ranges using a ceil so we can get a bit of range with the colours, but we’re workshopping the look of water as whole right now and might try going for complete binary in the future!
I was working on similar like this too. It’s always efficient to pix-elate a high quality textures procedurally in engine (Which was already mentioned here haha).
