Parts don't render correctly the higher you build

Just discovered this bug. Parts flicker and wiggle around (even appear to move out of their place) the higher you build. The below demo is at 20,000 Studs high. The higher you get, the worse it appears to get.

I know 20,000 sounds like an insane height for a build to be at, but if you were to build a Universe for example, expanding in all directions, the assets high up in the level are going to move around and wiggle on their own.

Really hoping this can be fixed.

3 Likes

http://developer.roblox.com/forum/bug-reports/113-rendering-bug-my-most-hated-bug

Interesting, they acknowledged it with a response that sounded like it wasn’t a priority. It really should be though. I’ve always thought of Roblox as unlimited and now I can’t think that anymore.

This is a serious set back, and I’m glad I brought it up, even though it was already posted months ago. This should be a #1 priority in terms of bugs to fix.

3 Likes

Hey! I have a solution! Use Lua instead of C++ for rendering code! I had issues with floating point precision so I ported over some code into Lua and it ran fine!

Mmmmm…

Kitteh6660 made a test place for camera issues and other glitches.

The place is basically a spawn with 4 teleporter bricks for various distances. The farthest teleporter was something like 1M studs. At that location, the camera would lag horribly and your clothing and gear would appear glitched. Chat’s appear glitchy too.
Give that a try. It doesn’t help you out, but shows some of ROBLOX’s limitations.

Plz, that’s not even a C++ code. Those are shaders that can cause wibbly wobbly stuff, thus it has something to do with them.

Example:

Plz, that’s not even a C++ code. Those are shaders that can cause wibbly wobbly stuff, thus it has something to do with them.
[/quote]
My computer cannot see shaders. So, I can say it’s not 100% Shaders. The bug has been like this for as-long as I know. I remember first seeing it about 3 years ago.

Plz, that’s not even a C++ code. Those are shaders that can cause wibbly wobbly stuff, thus it has something to do with them.
[/quote]
My computer cannot see shaders. So, I can say it’s not 100% Shaders. The bug has been like this for as-long as I know. I remember first seeing it about 3 years ago.[/quote]

I am 90% sure that you do see shaders. You couldn’t see them, if you had no GPU or suuuuper super old GPU without shader models(that’s like real old, older than old laptop GPUs).

Plz, that’s not even a C++ code. Those are shaders that can cause wibbly wobbly stuff, thus it has something to do with them.

Example:

–snip–[/quote]

hoyt wat
is that an actual screenshot?

We can build levels at 20,000 studs and set players a-trippin.

Yeah I made that thread a while ago and they still don’t care. It makes games look hideous and makes ROBLOX look like it was coded in a day.

[video width=425 height=344 type=]www.youtube.com/watch?v=v

Plz, that’s not even a C++ code. Those are shaders that can cause wibbly wobbly stuff, thus it has something to do with them.
[/quote]
My computer cannot see shaders. So, I can say it’s not 100% Shaders. The bug has been like this for as-long as I know. I remember first seeing it about 3 years ago.[/quote]

I am 90% sure that you do see shaders. You couldn’t see them, if you had no GPU or suuuuper super old GPU without shader models(that’s like real old, older than old laptop GPUs).[/quote]
It’s so bad that I cannot see part outlines or the water terrain block (It’s completely invisible).

I have this issue on my infinite randomly generated games, physics also gets buggy (notably Velocity) :dry:

That’s what causes the jittering when you’re flung at insane speeds.

I think that stuff doesn’t get rendered, when quality level is 1. Try setting it to max. Also what GPU does your computer have?

[video width=425 height=344 type=]www.youtube.com/watch?v=v[/video][/quote]

uhm. video, where are you pls?

The joys of floating point…