-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
All Unity games give the same error: Couldn't switch to requested monitor resolution #4477
Comments
Proton 5.13-4 and Proton Experimental are having issues launching games outside the Steam, 5.0-10 works fine though. Can you try 5.0-10 with the same command and see if the error still persists? |
So far I only tested with Ori and Getting over it, but it seems to work fine! Thank you. It's a shame that we can't launch games outside of Steam with the newest proton.. :/ |
@F1xteR Thank you for this! I was having the same problem, and running on Proton 5.0-10 works fine. Thanks again! |
Having the same "Couldn't switch to requested monitor resolution" issue using proton 6.3-5 for "mini motorways". Works fine using proton 5.0-10. |
I'm having the same issue no matter what proton version I use. |
I'm having the same issue with Far: Changing tides using proton experimental or 5.0-10 |
To anyone having this issue, try adding |
Compatibility Report
System Information
I confirm:
oriwotw_d3d11.log (I don't have a steam version of this game, so this is the only log I got)
Symptoms
When I try to launch a Unity game with Proton outside of Steam with the following command:
~/.steam/steam/steamapps/common/Proton\ -\ Experimental/proton run /game/path/here.exe
, this error appears.If I run the games with raw wine (latest from my package manager), most games seem to at least launch, although they have poor performance or major graphical glitches.
In games that show the Unity resolution selector window, the same error appears for all combinations of the resolutions and the fullscreen setting.
Reproduction
Try launching a game with the command mentioned above.
The text was updated successfully, but these errors were encountered: