July 16, 20232 yr Anyone know how to disable? I have my fps locked at 62 (could go much higher) but I can't even do 2x speed. It won't let me even though my fps are at least 62. This seems to vary by development version update. Some updates I can increase sim to 4x and others I can't even do 2x. Edited July 16, 20232 yr by knich
July 16, 20232 yr I didn't even know they have one. Was it introduced recently? Intel i9-13900K | Gigabyte Z790 Aorus Master | RTX4090 | 2x16GB Corsair Vengeance DDR5-6000 | Be quiet! Pure Loop 2 FX AiO | Win 11
July 16, 20232 yr Author 25 minutes ago, ThomseN_inc said: I didn't even know they have one. Was it introduced recently? It's built in to the FBW A320. There is a line they have somewhere in its programming that restricts the simrate. I can't recall where it is.
July 16, 20232 yr 3 minutes ago, knich said: It's built in to the FBW A320. There is a line they have somewhere in its programming that restricts the simrate. I can't recall where it is. lol my bad. For some reason i misread and was thinking of a FPS Limiter. So disregard. 🙂 Intel i9-13900K | Gigabyte Z790 Aorus Master | RTX4090 | 2x16GB Corsair Vengeance DDR5-6000 | Be quiet! Pure Loop 2 FX AiO | Win 11
July 16, 20232 yr Author 4 minutes ago, ThomseN_inc said: lol my bad. For some reason i misread and was thinking of a FPS Limiter. So disregard. 🙂 I corrected topic name so hopefully it is more clear. 🙂
July 16, 20232 yr There's no hardcoded figure programmed in the A32NX to limit simrate, it's wholly based on your real time FPS as the autopilot logic requires a certain FPS to receive enough data between frametimes to output some kind of data the the Fly-By-Wire computers. Quote The Simulation Rate is limited by the FlyByWire A32NX to protect and guarantee the Autopilot is able to work reliably. The Autopilot needs the equivalent of about 17 or more frames per second (FPS) in a real time simulation. This is needed for the Autopilot to be able to do enough calculations for each real time second. The required FPS for a specific simulation rate can be calculated using <sim rate> * 17. Another way of calculating the simulation rate your system can support is by using <FPS at sim rate 1> / 17. Example: 1) If your FPS at simulation rate 1 is 60, you can support a simulation rate up to 3.5 (60/17=3.5). At simulation rate 2, the Autopilot would be able to use 30 FPS for its calculations (60/2=30). At simulation rate 3, it would be able to use 20 FPS (60/3=20) 2) If you would like to enable a simulation rate of 4, you need at least 68 FPS (4*17=68), so that the Autopilot still has 17 FPS available for its calculations for each real time second.
July 16, 20232 yr Author 3 hours ago, Lucky38i said: There's no hardcoded figure programmed in the A32NX to limit simrate, it's wholly based on your real time FPS as the autopilot logic requires a certain FPS to receive enough data between frametimes to output some kind of data the the Fly-By-Wire computers. Hi....thanks for the explanation. I completed a flight from KTPA to KLGA and my framerate the entire flight until I hit KLGA was 62. I have my fps locked at 62. If it was unlocked it would have been much higher. So...not sure why it would not allow me to increase my framerate?
Archived
This topic is now archived and is closed to further replies.