Hello FloB,

 

thanks for your answer. I will ask Ben Supnik about this bug and the 10.30.

 

Here are my videos I sent to Austin:

 

https://www.youtube.com/watch?v=_v6_6nsJ4a0

https://www.youtube.com/watch?v=Yc89IqiegK8

 

Greetings.

PilotX777

This is a common problem that needs to be fixed.

This is a mathematical limitation of computers and partly the way X-Plane was coded. What you are seeing is floating point rounding errors. The computer is trying to compute the accuracy of the position of the spot you are on and is having some major rounding issues. If you are not familiar with floating point calculation errors, i recommend you Google it.

 

I use to be worse, if that is any consolation, and looks the worst when looking at the ground.

This is a mathematical limitation of computers and partly the way X-Plane was coded. What you are seeing is floating point rounding errors. The computer is trying to compute the accuracy of the position of the spot you are on and is having some major rounding issues. If you are not familiar with floating point calculation errors, i recommend you Google it.

 

I use to be worse, if that is any consolation, and looks the worst when looking at the ground.

I really only notice it in GA aircraft and helicopters, or if there is a jetway next to the cockpit. It used to drive me mad, but now I'm used to it and it rarely bothers me. The explanation is much appreciated Jack, thanks

Ah interesting, I also get this, but shrugged it off as something weird on my computer or something to do with my texture settings and have simply learned to ignore it. In fact, it wasn't until seeing the posted videos above that I realized it's a common problem and reminded me again it was there

This is a mathematical limitation of computers and partly the way X-Plane was coded. What you are seeing is floating point rounding errors. The computer is trying to compute the accuracy of the position of the spot you are on and is having some major rounding issues. If you are not familiar with floating point calculation errors, i recommend you Google it.

 

I use to be worse, if that is any consolation, and looks the worst when looking at the ground.

Hello,

 

thanks for the explanation. I am a bit familiar with floating point calculation errors. But I think this is no excuse :huh: , because other simulators don`t have this problem. I love my X-Plane 10 :wub: , but I don`t want to have a shaking ground :mad: .

 

Greetings  B)

Perhaps we can use this time to gather information on this for laminar to use.

 

Question that I have wondered about for a while are:

• Does this happen on all operating systems? (is this happening only on windows?)
• Does this happen more or less at varying latitudes? (some land data is larger then others)
• Does this happen more frequently with GA planes then airliners? (Is it depending on your distance to the ground or is that just an illusion)
• Does this happen more so at airports then out in the middle of nowhere? (is something with the positioning of the airport doing this and not the land data)
• Does this happen near or far from the Origin of the DSF file that makes up the ground plane you are on right now? (is it more or less based on the DSF and the positioning of the aircraft on that spot. Remember it may not be the ground shaking but rather the aircraft.)

 

 

 

Something to think about with regards to floating point errors is. The reason they exists is more or less a huge limiting point on large game worlds. You can really only work withing an X sized game world grid. If you are to far out from the origin you start getting more rounding errors, until you get to such a point the world starts jittery way to much. Most large game worlds box you in so you cannot go out to far form origin. But others don't, for example, Kerbal Space Program. In that game you can travel very far away from the Origin, and you will experience some interesting side effects. 

 

There are ways around this, like nesting grid systems withing grid systems. I am not 100% sure how x-plane was built, or how it handles the entire world. I can only assume this or that.

 

I can pass on whatever you guys find onto laminar for us. When they look into this at some point, I'm sure having some base to help find the issue will help.

Hi Jack,

as Laminar knows about this "issue", and probably knows for a long time, it would be helpful to have a "official" statement if such information is needed or not. I don't mind to collect information, not at all, but I'd like to know if it is really helpful or a waste of time.

 

Cheers

Flo