Z
zoltna67
Guest
At sim rate 16 above 20,000 feet the plain starts rocking up and down!
Anybody with some help please!
Anybody with some help please!
-
There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.
If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.
Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.
The Staff of SOH
W
wildcat400
Guest
At sim rate 16 above 20,000 feet the plain starts rocking up and down!
Anybody with some help please!
How many knots per hour are the winds?
Regardless of windspeed or cloud conditions, that much time acceleration will always cause instability.
As an example, say that the autopilot looks at the vertical speed 10x a second, and adjusts appropriately to stay at a set altitude. If you move through an area of turbulence where the vertical air movement changes strength every 1.6 seconds, the autopilot has 16 cycles to correct for the movement. If you speed the sim up to 16x, the autopilot is still scanning at 10 scans per second, but you're now moving through those air pockets every .16 of a second, so every time the autopilot looks at the vertical speed of the aircraft and the altitude, the two variables are different. The autopilot will still attempt to correct, but it has no time to do so, therefore the error gets worse and worse the longer you leave the sim at 16x time acceleration.
Another way of looking at it is that if, say, you are running your sim at 32fps, if you see a tiny change, you can correct for it. If, however, you are running at 16x, those "slight" changes happen 16x as fast, so you react 16x as slowly. You'll end up with 16x the error that you would have if you were running it at 1x and might as well be flying at 2fps - by the time you've seen the change and tried to correct for it, it's too late and you're making the wrong correction.
Basically, there's no way you will ever keep a flight model stable at that speed. Even a microscopic trimming error or a tiny area of turbulence will throw you miles out of balance.
Ian P.
As an example, say that the autopilot looks at the vertical speed 10x a second, and adjusts appropriately to stay at a set altitude. If you move through an area of turbulence where the vertical air movement changes strength every 1.6 seconds, the autopilot has 16 cycles to correct for the movement. If you speed the sim up to 16x, the autopilot is still scanning at 10 scans per second, but you're now moving through those air pockets every .16 of a second, so every time the autopilot looks at the vertical speed of the aircraft and the altitude, the two variables are different. The autopilot will still attempt to correct, but it has no time to do so, therefore the error gets worse and worse the longer you leave the sim at 16x time acceleration.
Another way of looking at it is that if, say, you are running your sim at 32fps, if you see a tiny change, you can correct for it. If, however, you are running at 16x, those "slight" changes happen 16x as fast, so you react 16x as slowly. You'll end up with 16x the error that you would have if you were running it at 1x and might as well be flying at 2fps - by the time you've seen the change and tried to correct for it, it's too late and you're making the wrong correction.
Basically, there's no way you will ever keep a flight model stable at that speed. Even a microscopic trimming error or a tiny area of turbulence will throw you miles out of balance.
Ian P.