search

ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
24.29k stars 1.06k forks source link

Unable to run anything with a window with proton. NtUserEnumDisplaySettings Invalid device name L"" nodrv_CreateWindow Application tried to create a window, but no driver could be loaded. #6374

Open ayunami2000 opened 1 year ago

ayunami2000 commented 1 year ago

I just get warn:system:NtUserEnumDisplaySettings Invalid device name L"". and 00c4:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded. 00c4:err:winediag:nodrv_CreateWindow The explorer process failed to start.

It works if I use something like Xephyr to create a nested X display, but that has it's own issues with 3d acceleration and stuff...

Note, I have a quite complex and potentially unsupported setup, HOWEVER it used to work and now it does not.

Let me know what logs you might want. To start, the entire desktop is virtual (Xvfb), but has acceleration (vkcube, glxgears, and steamvr all work). Wine works, but proton does not. Not even GE-Proton works. Note, cmd works, because it does not open a window.

Visually, when you launch a game that uses proton, the button says stop for a bit but soon switches back to play.

On a somewhat unrelated side note, VRChat's EasyAntiCheat keeps giving me error code #1 and I don't know what to do about that. But that can be saved for some other time or thread.

Any help is greatly appreciated! (e.g. quick fixes, workarounds; I'll take anything!!)

Also if this needed to be on the main proton repo, let me know, but I suspect the issue/fix lies here.

kisak-valve commented 1 year ago

Hello @ayunami2000, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report. Also, please add PROTON_LOG=1 %command% to a couple game's launch options, reproduce the issue, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.)

ayunami2000 commented 1 year ago

turns out it was a misconfiguration due to what is very likely an unsupported setup. I'll reproduce it in a bit anyways, though, because it's still somewhere where wine works but proton does not.