Reproduction Step: Go into my place file and test the viewmodel with the model at the distant position and you will see the viewmodel jittering and struggling to render
The video contains the instructions on what I think should be done to fix the bug.
Expected Behavior: Viewmodel has no jittering or issues rendering(which in a place where your character is not inside a distant map it does
Actual Behavior: Viewmodel has jittering and issues rendering when character is inside of a distant map
Please follow How to post a Bug Report when making reports; this at least needs repro instructions in the post. It is difficult to get the right eyes on bug reports when they only link to a 12 minute video.
As I can see that’s a floating point rendering error, I don’t think they can fix this, otherwise it would’ve been fixed long ago.
Search “floating point errors roblox” on google and you’ll find lots of videos about it, the further away you are from 0, bigger the problem is. What you can do is just, try to not go too far away from 0
Very refreshing to hear a reply from such a famous developer. Thank you I greatly appreciate this information. I was aware of floating point errors because I have encountered them previously, but not on a large scale like this.
I did not know anything about what it actually is either, I only assumed what it could be. I hope they will file this to internal database because it is a pretty big issue but thank you for your input it means a lot to me
I’ve seen a lot of your feedbacks and they’re usually pretty spot on. I’m surprised you don’t see this as game breaking but it definitely is and any FPS game would pretty much lose their player base entirely if this bug were occurring in their game…
Hopefully my insight helps you understand this more clearly! Thank you for the feedback though. No hard feelings
We understand that this jittering issue with viewmodels at distant positions is confusing and definitely not the desired behavior. We appreciate you bringing it to our attention and providing such a clear reproduction case.
We’ve had internal discussions about how to address floating-point errors, which are the underlying cause of this problem, and we recognize the impact they can have. Unfortunately, addressing these fundamental floating-point limitations is a complex undertaking and not something we are actively working on at this time. It’s a significant engineering challenge.
To help bring more visibility to this specific problem and potentially prioritize it for future development, we highly recommend submitting a formal feature request. A well-written proposal with clear examples (like the one you’ve already provided here) and community support in the form of comments and upvotes will greatly increase its chances of being considered in our future planning. This will allow us to gauge the community’s demand for this type of improvement and factor it into our roadmap.
