Shanks16

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 FPS GPU frametime CPU frametime GPU Usage CPU Usage Average 36.09 20.06 27.03 59.56 22.64 10% Lows 31.33 26.67 41.05 1% Lows 27.62 29.69 45.11 Fenix A321 FPS GPU frametime CPU frametime GPU Usage CPU Usage Average 39.89187 17.00659 14.73645 68.16993 26.24062 10% Lows 38.9 19.33 22.8 1% Lows 36.9 22.24 34.57 MSFS 2024 Beta SU3 with mostly Medium and High settings TLOD 120 OLOD 100 CPU: AMD 7950X3D GPU: RTX 4800 driver 566.36 RAM: 64GB 6000 CL32 Hardrive: 1TB NVME dedicated for MSFS VR: Valve Index; tracking via FPSVR Fenix A321 MSFS2024.xlsx ini A350 MSFS2024.xlsx

I've just tested the new update (v1.1.2) and I wanted to follow up on my post to report back findings. This update is night and day different from the one before. Of course, MSFS still stutters at the odd occasional time, but I'm not sure anyone can get rid of that entirely. The performance is somewhere along the lines of the Fenix for me at this point, so I have to say job well done ini team! I hope everyone else sees this performance uplift as well, and I'm back to enjoying my A300 and looking forward to the A350 even more now 🙂

Thanks @richboy2307 It's nice to hear about the upcoming update with the performance improvements! I'll be eager and glad to retest. 🤞 that I'll have excellent results to share with the update as well. It's tough to balance the VR performance/quality in MSFS with how demanding the sim is on one single core of the CPU, and sometimes it doesn't even appear that any core is throttled at 100%. Sometimes it's maddening 🤣

Hello, ini! I'd like to start this post by saying I'm not bashing and I truly hope this data can help in some way. I know that performance has come up in many different threads, but I wanted to provide solid examples and data points in the hope that they help. The test conditions were the A300RF and Fenix A320 at KATL runway 27R with clear skies and no traffic to remove as much skew as possible in testing. The test was a short sit in the cockpit to ensure I was ready for the takeoff, then a takeoff roll, followed by rotation, and climb to approximately 3000 agl. I compared it against the Fenix A320 because outside the ini lineup (ini A320, ini A310, and ini A300) the Fenix A320 is the hardest-hitting performance-wise. I gathered this data using FPSVR which is a great tool that allows exporting of all the performance-related data from VR play. The specs and VR headset for my computer and setup are below as well. My overall impression is that on the ground it is stuttery and not a pleasant VR experience at all. I love the systems, modeling, and hand feel that the A300 has, and the performance has been the only thing that has kept it in the hanger when I'd love to be flying the plane. In the attached frametime excel files, I did some conditional formatting to highlight where the performance dipped, but more importantly when CPU or GPU frametimes dipped. The goal for me in my VR experience is to stay under 25ms with CPU and GPU frametimes as that will net me 40 fps. 40fps allows me to use Motion Reprojection to achieve 80 fps to the eyes and the overall experience is nice while flying airliners. CPU frametime is the culprit to my eyes at the moment. It is a repetitive and dependable spike in CPU frametime every 5ish seconds that causes the domino effect and terrible performance. The spikes become more prominent and dependable when the aircraft is rolling which is also kind of odd, and those are rows ~1500 through ~2800 in the spreadsheet. The A300 spent ~11% of my short playtime above 25ms CPU frametime which was certainly the cause of the stutters and drop in performance. The crazy thing is once the aircraft is off the ground, the massive CPU frametimes spikes smooth out as evidenced by the last 1000 or so rows which was the climb. All aircraft do have certain spikes of course, and that will be seen in the Fenix spreadsheet, but the ini lineup is where I see these very dependable spikes. The averages don't do justice to the truth which is why I'm hoping the frametime spikes shown will help. Hopefully, this helps narrow the field in some way, but please let me know if you need any follow up information. I do want to see the performance improve so I can enjoy these great aircraft! ini A300RF FPS GPU frame CPU frame Average 35.09 14.18 15.82 1% Low 27.3 19.5 35.7 .01% Low 26 22.8 38.4 11% of time lower than 25ms cpu Fenix A320 CFM FPS GPU frame CPU frame Average 39.14 18.53 12.90 1% Low 28.4 22.9 25 .01% Low 27.3 26.7 38.7 1% of time lower than 25ms cpu VR using Valve Index running SteamVR AMD 7950X3D CPU RTX 4080 GPU 32gb 6000Mhz RAM 1TB NVME SSD PS: Sorry for such a long post, but feel free to allow me to beta test these numbers on that A350 which is my favorite airliner haha 😅 Frametimes_iniA300RF_KATL_clear.xlsx Frametimes_FenixA320_KATL_clear.xlsx

Excellent to hear it will be supported in a future update, and great to hear the plane plays nice with pausing already! I use TOD Calculator when an airplane doesn’t have a native feature, but the built in option is always more accurate 🙂.

Hello ini! I've been tuning into the streams and youtube videos and so far have not seen this feature. Could you please add a pause at top of descent feature as an option? For many like myself, life sometimes has to get in the way of my wonderful flight sim passion 😁, so this is a big deal on long haul aircraft like the A300 and the very exciting upcoming A350. Or if this isn't in the works, then can we just be sure that the aircraft won't do strange things when paused so outside applications can pause the sim? Looking forward to both the A300 and even more so the A350!!!

I just wanted to bump this as well. I love the plane, but even with the newest Beta 13 that actually has the A310 mentioned in the changelog there are still issues coming out of pause. For me while in pause, it appears the trim continues to trim the plane up to its max setting which results in the airplane violently climbing until I can regain some control. I'm not sure why the aircraft would continue to trim while in a paused state at all? Also, since I'm in VR, I can look down at the center pedestal while paused, and the trim will indicate a normal reading. But once unpaused, the trim is immediately 15 degrees nose up and crazy. I love the A310 and want to fly it more often, but I fly in VR and work while flying so I pause a lot. AFAIK the A310 is the only one that suffers from pause issues anymore, including Fenix, PMDG, JustFlight, SWS, etc. I'm not bashing at all, just trying to help by pointing it out so I can enjoy the lovely bird to its fullest 🙂