Microsoft Flight Simulator crashes with "!status && "vkAcquireNextImageKHR"" while loading on Wayland since 555

Graphics / Linux Linux
1

Screenshot_20240902_155120
Screenshot_20240902_1551201920×1046 232 KB

nvidia-bug-report.log.gz (662.9 KB)

Attempting to play Microsoft Flight Simulator 2020 on Steam (Tried both steam-native and steam-runtime) with any version of Proton (Tried 8, 9, experimental, -GE, etc) crashes about half way through the initial loading screen before it reaches the main menu.

Screenshot_20240807_121431

The error reads

Assertion failed!

Program: Z:\media\Erend\Games\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
File: …/src-wine/dlls/winevulkan/loader_thunks.c
Line: 39

Expression: “!status && “vkAcquireNextImageKHR””

Press OK to exit the program, or Cancel to start the Wine debugger.

Clicking either button closes the game.

  • Affects all versions of Proton
  • Affects Wayland (Game still loads on X11)
  • Affects driver versions 555 and 560
  • Affects proprietary and open drivers

System Info

Motherboard: ASUS ROG CROSSHAIR VIII DARK HERO
CPU: AMD Ryzen 9 5950X (32) @ 3.40 GHz
GPU: EVGA NVIDIA GeForce RTX 3090 Ti
Driver: nvidia-open-dkms 560.35.03
EGL Wayland: egl-wayland-git 1.1.16.r7.g2d5ecff-1
RAM: 64GB DDR4
Distribution/Kernel: Arch Linux 6.10.7-arch1-1
Desktop Environment: KDE Plasma 6.1.4
Window Manager: KWin (Wayland)
GRUB_CMDLINE_LINUX_DEFAULT=“loglevel=3 nvidia_drm.modeset=1 nvidia_drm.fbdev=1 nvidia.NVreg_EnableGpuFirmware=0”

1 Like
2

Hi have encountered the same issue on a different game (Catherine: Classic). But, on my case the crash happens on X11 too.

Driver Version: 560.35.03

System Info

Motherboard: X470 AORUS GAMING 5 WIFI
CPU: AMD Ryzen 7 5800X
Kernel: Fedora 40 6.10.8-200.fc40.x86_64
Desktop Enviroment: KDE Plasma 6.1.4
Window Manager : KWin (Wayland)
GPU: Gigabyte Windforce RTX 2080
RAM: 64GB DDR4

2 Likes
3

Just confirming this is still an issue. Now on nvidia-open-dkms 560.35.03-9 and linux 6.11.1-arch1-1

Would be nice if nvidia could acknowledge this - Haven’t been able to play this game for ~3 months now.

nvidia-bug-report.log.gz (830.9 KB)

Screenshot_20241001_103432
Screenshot_20241001_1034321920×1046 232 KB

2 Likes
4

Confirm same issue. On nvdia-dkms 560.35.03-3 and linux 6.8 lts on ArchLinux. RTX 3060 Desktop

1 Like
5

This continues to be an issue on 565.57.01

5 Likes
6

Running Arch Zen - with Hyprland and the dkms 565.57.01. Still having this issue inside of any Wayland environment with the later versions of the Nvidia driver. Getting a little sick of the fact that Nvidia has not put out any update to address this. The introduction of explicit sync has been a nightmare for a lot of the software I use. Sure would be nice to get a reply on this post to show that someone is addressing this at least.

Motherboard: X570 Taichi
CPU : AMD Ryzen 5900X
Kernel : 6.12.1-arch1-1
Desktop Enviroment: Hyprland 0.45.2
Window Manager : Wayland
GPU : Gigabyte RTX 3090
RAM: 128 GB DDR4 @ 3000Mhz

1 Like
7

Hi All,
I have filed a bug [4978267] internally for tracking purpose.
Shall try to reproduce issue locally and will get back if needed any additional information for the same.

4 Likes
8

can confirm similar crashes occur on Forza Horizon 4 (VKD3D) and Satisfactory (Select vulkan backend). Errors are very slightly different, one is vkWaitForFences and the other is vkCreateGraphicsPipelines

I shared some more info of those crashes and repro steps here:

9

This also happens with the latest version of Hoyoverse’s unified game launcher (HoyoPlay).

I think this is related to some new version of the CEF having beef with WINE/Proton and nVidia cards while under Wayland somehow.

Motherboard: ASrock X870 Steel Legend
CPU : AMD Ryzen 7 9800X3D
Kernel : 6.12.1-pikaos
Desktop Enviroment: KDE 6.x
Window Manager : Wayland
GPU : Gigabyte RTX 3080
nVidia Driver: 565.57.01
RAM: 64 GB DDR5 @ 6000Mhz
WINE/Proton: GE 9-20

10

Using the latest Proton Experimental (9.0-20241223), MSFS seems to be loading now on Wayland.

This is on Gentoo Linux 6.6.62-gentoo-dist, nvidia-drivers-565.77

Screenshot_20241227_231321
Screenshot_20241227_2313211920×1080 246 KB

11

I think 565.77 actually fixed this. I know other games thet had the same error message and those games work now

1 Like
12

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.

13

Thank you, I will archive the nvidia bug internally as issue no longer persists.