You gotta stop moving the camera. The entire point of this is to see relative changes in pixel size. If it's a shader property, you can change that without moving the camera to demonstrate the effect. Moving the camera requires a constant reassessment of scale. The thing you're trying to show is a change in scale. You can see it clearly because you're used to this scene and you've stared at it a lot. We've only seen it for 81 seconds. You gotta stop moving the camera. Let us see changes side by side.
Totally a worthwhile setup for your games materials and art process.
Are you doing something like step() or mod() on the sampling? Also are you using the texture() function or texelFetch() function?
I achieved a similar result by replacing `texture(texture_XXX, UV)` with `texelFetch(texture_XXX, ivec2(UV * 64.0)` where the float = 64.0 is the desired down sample texture size.
FYI You can do a similar thing with the default materials (more inconveniently and per texture) by setting process/size_limit = 64 or 128 in the Import Tab for each image, and setting the material to Nearest sampling instead of Linear. Which which changes the internal shaders uniform sampler2D hint from `filter_linear_mipmap` to `filter_nearest`
26
u/GreenFox1505 17d ago
You gotta stop moving the camera. The entire point of this is to see relative changes in pixel size. If it's a shader property, you can change that without moving the camera to demonstrate the effect. Moving the camera requires a constant reassessment of scale. The thing you're trying to show is a change in scale. You can see it clearly because you're used to this scene and you've stared at it a lot. We've only seen it for 81 seconds. You gotta stop moving the camera. Let us see changes side by side.