[1.4.7.0] SU2 Beta Survey - Performance (PC)

Please indicate your playability of the sim with the following statement - PC performance (frames per second) in this build is generally:
  • Great
  • Good
  • Acceptable
  • Poor
0 voters

To report a bug, please use a sub-category of Sim Update 2.

:arrow_down: Please provide additional information in the comment section below :arrow_down:

:warning: Reminder:

Friendly reminder: performance in this beta build is expected to be reduced slightly because of enhanced telemetry data collection being enabled during public testing. Please keep this in mind when voting in this survey.

Memory Logging in the Sim Update 2 Beta

Memory logging will be enabled in the first Sim Update 2 Beta build, which will cause a small decrease to performance (in particular during menu transitions). The telemetry we receive from this memory logging will aid our investigations into stability improvements. This memory logging will be removed from the Sim Update 2 Beta before release, or as soon as we have enough data.

On Xbox console, you can help ensure we receive your data by following the below instructions:

  1. Navigate to Settings > System.
  2. Now select Console info.
  3. Check ‘Allow optional data collection’

Thanks,
MSFS Team

Performance seems to be really good and reasonable considering the graphic fidelity improved a lot in SU2.

1 Like

Seems to be better optimized for my setup than retal…Higher FPS all over

1 Like

My first flight was a positive delight - mostly super smooth with just the occasional hint of a stutter and the visuals looked markedly better. VRAM usage was very much under control too.

There is a significant improvement in FPS and the game feels much smoother both inside and outside the cockpit, definitely a step in the right direction. However, I’m experiencing frequent CTDs after playing for about 5-10 minutes.

Faulting application name: FlightSimulator2024.exe, version: 1.4.7.0, time stamp: 0x00000000
Faulting module name: nvwgf2umx.dll, version: 32.0.15.7283, time stamp: 0x67d4654a
Exception code: 0xc0000409
Fault offset: 0x0000000000f65401
Faulting process id: 0x0x4B24
Faulting application start time: 0x0x1DB9EBE75E4ADD9
Faulting application path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.4.7.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe
Faulting module path: C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_9d15b9aa9e1c885b\nvwgf2umx.dll
Report Id: 11369acb-595d-460b-b379-d18445c3b8a1
Faulting package full name: Microsoft.Limitless_1.4.7.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
1 Like

I picked poor because most of the time I get the “takes a very long time to start a free flight” issue. I usually give up after 10 minutes. When it does start a flight (from 1 to 5 minutes) - I get good performance in the flight.

1 Like

Hi there, I googled your report and it turned out the faulting .dll file is nviidea related. Try to reinstall the driver with DDU, lower graphic settings… and so on.

Good luck
Mick

I’ve run a DDU, reinstalled the latest GPU drivers, and adjusted the settings. This issue only occurs in the SU2 beta.

SU1 still runs without any CTDs. It seems like part of the beta may not be compatible with my GPU driver, or vice versa.

1 Like

My FPS are up by 30 fps. The balance between cpu and gpu are much more equal. I’m very happy with SU2 Beta except for a couple regressions (bugs).

Good overall performance, (once you can get into a flight).
Though im confused what my true framerates are.
In game fps says 60 in VR. And openxr counter says 37.

Same, performance is good, in between the CTD’s.

Same here, didn’t work. Still lots of CTD’s caused by that same dll.

System i9 13900K, 64GB RAM, RTX3090 driver 572.83, Pimax Crystal Light. Good performance and able to complete flights without CTDs using FS24 aircraft only. However, PC24 CTD on selecting. ATC worked briefly then fails to work even after restarts (and even tried Repairing sim.) EFB fails to load logical flight plans but only tried in Vision Jet so far.
Fist time startup took a long time to load, then subsequent starts much faster.
Map textures are much better, and in some places, nearly as good as FS20.
In 2D, initial FPS=68-70 external, 63-65 internal using DLSS3, preset J (default settings). Tried preset K with DLSS 3.1 and FPS dropped to 29-30. Back to J and FPS stayed at 28-30?? Swapped to DLSS 3.2.1, preset K same FPS 29-30. DLSS4 only marginally increased FPS. Can’t explain the huge decline in 2D FPS although I did update the SDK after first start of SU2 Beta.
In VR, using OpenXR Toolkit as I can improve sharpness over the PimaxPlay software and FFR. Also using the OXRTK resolution override to reduce the vertical (to 90%) and horizontal (to 96%). FPS consistent at 30-32 for both presets J and K in both DLSS3.1.0 and 3.2.1.
Flying Kodiak 100 in VR with DLSS4 re-introduces blur in the cockpit, in both eyes but is near the edges so not so intrusive. Does not occur in DLSS3.
Tried the Foveated Rendering in the sim (turned it off in OXRTK) but with DLSS4 there was a distinct vertical boundary displayed left eye only (this might have been associated with resolution constraints?
At this stage staying with DLSS3.2.1

There’s another thread around for this issue, might be worth to keep an eye on…:

1 Like

Thanks for the link!

It seems like Asobo is aware of the issue and are trying to fix it with the next update.

Where did you see that? Have a link?