Unexplained Frame Time Spikes - Only in FBW Aircraft

User Support Hub Aircraft & Systems
, ,
1

Going a little crazy now. The FBW a320 would run smooth and for some reason, every few seconds, it will freeze for a second, then a spike is displayed in the dev mode tools. This will then happen for as long as i keep flying.

Low and behold the a380 acts the same way.

Clean community folder. Clean installs of a320 stable. Clean install of Windows and Sim. No DLSS, Frame Gen, just TAA - 7800x3d, 3080, 64gb ram.

I cannot figure out what is happening. Posted on the a320 discord too but they are swamped by a380 questions understandably.

Anyone else seeing this type of behavior. I may need to record a video.

2

Moved to User Support Hub User Support Hub > Aircraft & Systems that is more appropriate for community support.

3

I do observe the same behavior, but only when activating Pimax VR. Unfortunately this issue keeps on even after switching of Pimax VR and even killing the process

4

I have a Reverb G2 but this is occurring for me in 2d mode.

5

If it’s only the FBW aircraft, are you running their Simbridge companion utility? I don’t know if that’s it, but it is something unique. If you’re not running Simbridge, then you can probably assume that’s not it :slight_smile:

6

It’s occurs with or without simbridge running. Opening and closing simbridge doesn’t make any difference sadly.

I agree it’s something unique, a binding issue perhaps. Going to start removing all my equipment next time it happens and see if it stops.

Pmdg, mad dog, salty are all fine even on long flights. Fbw goes from normal to unusable either before I program the mcdu or by cruise.

7

Same here with 380 but didn’t have issue with the 320. Crazy back and forth stuttering even while frame rate says locked steady 30 /60.
The salty 747 and pmdg 737 smooth as butter. Same route conditions everything.

8

RESOLVED

I was able to solve and reproduce the error by unplugging and reconnecting my honeycomb bravo throttle. At that point I knew it was a bad key bind.

Created a new profile for the a380 with the bare essentials. Did not bind the rotary ap dials or trim wheel, deleted the analog flap lever bind, etc.

Now the a380 is a dream. (At least as good as it can be right now, vs my bravo getting in the way) I’m confident the a320 will be the same. I will make a second profile for it with only two engines.

Good luck!!

9

Thank you so much Jonny5Alive6618!
Now I had my first stutter-free flight in VR onboard a Lufthansa A380!

10

Glad it helped! Any idea what the binding causing the issue was?

I’ve been loving the a380. Katl to ksfo earlier. Smooth as could be!

11

I enjoyed a smooth and impressive ride from LEMG to EDDM (Malaga Spain to Munich Germany).
I assume it was an autopilot binding, but no idea which one.

12

Just to add to this topic: I also removed all the autopilot, nav, comm, transponder, etc settings from my honeycomb bravo and it seems like the FBW A380 has about 10FPS better in cruise than before. Definitely weird behaviour.

13

I did the same but I assume it’s just one binding causing the issue.

Spread the word. I feel a lot of people have the bravo and won’t be able to figure this out.

14

Just some random keybind causing it without even using the bind?

15

Just some random keybind causing it without even using the bind? I have currently this problem

16

Yes appears to be so. The honeycomb switches are a little weird, when they are on or off I think they are constantly pulling their position (the set on and set off binding options). I think this normally isn’t an issue but for the A380 it seems to cause an fps drop.

I just completely unbound the trim wheel, the autopilot settings knob, the increase decrease knob, and the switches that are above the throttles. It improved the fps.

17

Ok thanks for answer. Too bad this didnt fix my random stutters with fbwa320, which doesnt happen with any other planes.

18

You were right ! And for my case, I found which bind was causing the saccades.

It’s in the Autopilot section “SET AP SPEED SLOT INDEX”, which was binded on my Honeycomb Bravo.

Thank you so much !

19

You were right ! And for my case, I found which bind was causing the saccades.

It’s in the Autopilot section “SET AP SPEED SLOT INDEX”, which was binded on my Honeycomb Bravo.

Thank you so much !

Actually it was not necessary because of the “SET AP SPEED SLOT INDEX”, but it’s definitly related to a AP bind.