Okay this has bothered me for a LONG time.
I showed it to sim0nsays/Gemlocker and he acknowledged it and pretty much ignored it.
Basically bricks flicker at far distances. Example, (15000,1000,15000). Many airlines have issues with this. I’ll demonstrate why.
Here is a video showing this “flickering” that happens. Note: This flickering doesn’t happen at 0,0,0. No bricks are at the same position. FULLSCREEN IT IN HD.
[video]http://www.youtube.com/watch?v=v1NGNhjQrj0[/video]
Thanks,
Rukiryo
Happens to me too. Guess ROBLOX isn’t unlimited afterall, even with perfect and unlimited CPU and memory.
Floating-point precision depends on the magnitude of the number - so we get precision issues far from the origin.
We have tentative plans to improve this but no ETA.
Okay it also happens in studio, not just a playerbug.
Yea can you guys fix this?
Increasing the precision of floats would mean even a lot more memory consumed per CFrame coordinate.
Problem isn’t really in CFrame, but in values that are passed to shader, or calculated within it.
Exactly. And this ruins many games.
Please don’t bump really old bug reports
@zaydoudou File a feature request with proper format if you are having severe issues with Z-fighting that you can’t reasonably solve yourself by offsetting geometry.