@nalyDylan that VVL error should be gone now, could you try again and see if that resolved the issue?
@nalyDylan that VVL error should be gone now, could you try again and see if that resolved the issue?
Looks like one of the errors dropped off with doitsujin's latest commit, but the others remain. Progress!
steam-1250410.log
Fixed the crash in the linked PR, but the actual FPS on amdgpu is unusable as is due some unfortunate host memory imports. You can try VKD3D_CONFIG=host_import_fallback and see if the game is still running correctly after that.
I can't really test the game since I get blocked on login by a broken webview ...
Hey again @HansKristian-Work ,
I tried with the latest build of master and the flag you suggested this morning and still get the same crash on startup.
Any ideas what may be different between our setups? I tried switching to Experimental also and same result
steam-1250410.log
Did you update submodules? The build id suggests you have a botched build.
I just double checked but yah, I'm using the vkd3d-proton-mingw-git AUR package that does do submodule upgrade.
Is the build id the id on this line? If so, that looks like the correct commit hash of the latest commit to master to me
712.209:012c:0130:info:vkd3d-proton:vkd3d_instance_init: vkd3d-proton - build: 4f8d7917efeafc8+.
The + means it's a build that isn't clean. What does git status say?
You could just use the dlls from the CI build: https://github.com/HansKristian-Work/vkd3d-proton/actions/runs/19106018337/job/54589989674 Those should be fine.
If there are still problems, make sure you actually run with proper debug logs, you've removed all information about the crash in your log.
Oh, got it working 🤦
I started looking at those command line options after your comment about it hiding errors and the vulkan validation layer one was causing the issue. It was just something I grabbed from another issue to make logs so I hadn't really read it much.
Thanks for the help and the quick turnaround on the fixes!
proton 9.0-4x1 2025-11proton experimentalx1 2025-11VKD3D_CONFIG=host_import_fallbackx1 2025-11MESA_LOG_LEVEL=debugx1 2025-11PROTON_LOG=1x1 2025-11VKD3D_CONFIG=vk_debugx1 2025-11VKD3D_DEBUG=debugx1 2025-11WINEDEBUG="+timestamp,+pid,+tid,-all,+err"x1 2025-11
Software information
Microsoft Flight Simulator (2020) crashes on startup after switching to DX12.
DX11 works, but I'd like to be able to use FSR and the other graphical goodies if possible.
The report below uses a CachyOS-proton package, but I did also try Proton Experimental and Proton 9.0-4 to check if it was an issue with the package or one of the new wine 10.0 features like Wayland support. Same error with the buffer shows on all three versions
System information
Log files
Launched from steam using:
VKD3D_CONFIG=vk_debug VK_INSTANCE_LAYERS=VK_LAYER_KHRONOS_validation VKD3D_DEBUG=debug MESA_LOG_LEVEL=debug WINEDEBUG="+timestamp,+pid,+tid,-all,+err" PROTON_LOG=1 %command% -FastLaunchsteam-1250410.log