A350 MSFS 2024 VR Performance Comparison (Bad CPU Frametimes)

Shanks16 · Wednesday at 06:31 PM

Hello iniBuilds Team,

I performed a test like this with your A300 when performance wasn't great, and I was delighted when that was remedied and gladly reported back when you all took care of it. I'm hoping the same will happen with your A350. I'll start by saying I love the modeling, flight dynamics, features, etc., and the only problem now is performance. My hope is that this data helps your team, or better yet, someone can give me some feedback to figure out why I'm experiencing this poor performance with my favorite airliner. This is only data to show what is happening on my system.

Most people judge by FPS alone, but in VR frametimes are king. CPU and GPU frametimes tell the whole story and show more of the performance than average fps does. The average FPS was down from the Fenix A321 by about 9.5% in my testing, but the real problem is the constant stutters in the CPU frametimes that make the plane feel awful in VR comparatively. Aiming for 40 fps to hit 1/2 of my Valve Index's 80hz refresh rate, requires cpu and gpu frametimes of <25ms. The average CPU frametime for the A350 was 27.03 which misses the mark on the average. Worse was the 10% low which was 41.05ms. To put this into more perspective, only 2 frames of my Fenix A321 run dipped below that 41.05ms mark which helps explain why the A350 feels so much worse in the headset. Again, this isn't a slam, and my hope is there is a fix for this.

Below will be some graphs showing the CPU frametimes, and it appears to be constantly stairstepping on cpu frametimes. The CPU frametimes are constantly spiking, and this doesn't happen for me on any other payware or default aircraft. All aircraft stutter at points, and I show this fairly with the Fenix A321, but the problem is the A350 does this constantly and never recovers. Below are the numbers and graphs, and I've attached the spreadsheets themselves for transparency. I'd love some help or feedback on how to make this better!

Sorry for the long post, but just trying to give as many details as possible 🙂

Test Methodology

EGKK runway 26R with clear skies and no traffic to remove as many variables as possible. A350 was completely uninstalled, and the local cache was deleted as well before a complete reinstall of the plane. I loaded the plane to let the WASM generate, then exited MSFS 2024 before conducting the test.

Test Results

iniA350