protonscr

All Unity games give the same error: Couldn't switch to requested monitor resolution

protonopen
ValveSoftware/Proton#4477 · opened 2020-12-18 by SparkyTD · updated 2026-07-17 · 8 comments · github
SSparkyTD 2020-12-18 github

Compatibility Report

  • Name of the game with compatibility issues: Ori and the Will of the Wisps, Among Trees, Firewatch, Getting over it, etc...

System Information

  • GPU: RTX 3070 (also tested on GTX 1060)
  • Driver/LLVM version: nvidia 455.45.01
  • Kernel version: 5.9.14-2-MANJARO
  • Link to full system information report as Gist:
  • Proton version: Experimental

I confirm:

  • [x] that I have checked whether there are updates for my system available.
  • [x] that I haven't found an existing compatibility report for this game.

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.

FF1xteR 2020-12-26 github

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?

SSparkyTD 2020-12-30 github

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.. :/

Kktaherig 2021-05-15 github

@F1xteR Thank you for this! I was having the same problem, and running on Proton 5.0-10 works fine. Thanks again!

Sshirnschall 2021-07-21 github

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.

Ffr4nk3n5731n 2022-12-04 github

I'm having the same issue no matter what proton version I use.
GPU: RTX 2080 Ti
Driver: 525.60.11-2
Kernel: 6.0.11-arch1-1

Ffcancelinha 2023-07-04 github

I'm having the same issue with Far: Changing tides using proton experimental or 5.0-10

IIgnisFlamme 2024-04-09 github

To anyone having this issue, try adding __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia %command% to your launch commands.

Ggeudrik 2026-05-12 github

I'm having the same issue as @SparkyTD in OP, running latest nvidia drivers on Ubuntu 25.10 (latest kernel). Trying to play Ori Definitive Edition

==========
VULKANINFO
==========

Vulkan Instance Version: 1.4.321


Instance Extensions: count = 26
-------------------------------
VK_EXT_acquire_drm_display             : extension revision 1
VK_EXT_acquire_xlib_display            : extension revision 1
VK_EXT_debug_report                    : extension revision 10
VK_EXT_debug_utils                     : extension revision 2
VK_EXT_direct_mode_display             : extension revision 1
VK_EXT_display_surface_counter         : extension revision 1
VK_EXT_headless_surface                : extension revision 1
VK_EXT_surface_maintenance1            : extension revision 1
VK_EXT_swapchain_colorspace            : extension revision 5
VK_KHR_device_group_creation           : extension revision 1
VK_KHR_display                         : extension revision 23
VK_KHR_external_fence_capabilities     : extension revision 1
VK_KHR_external_memory_capabilities    : extension revision 1
VK_KHR_external_semaphore_capabilities : extension revision 1
VK_KHR_get_display_properties2         : extension revision 1
VK_KHR_get_physical_device_properties2 : extension revision 2
VK_KHR_get_surface_capabilities2       : extension revision 1
VK_KHR_portability_enumeration         : extension revision 1
VK_KHR_surface                         : extension revision 25
VK_KHR_surface_maintenance1            : extension revision 1
VK_KHR_surface_protected_capabilities  : extension revision 1
VK_KHR_wayland_surface                 : extension revision 6
VK_KHR_xcb_surface                     : extension revision 6
VK_KHR_xlib_surface                    : extension revision 6
VK_LUNARG_direct_driver_loading        : extension revision 1
VK_NV_display_stereo                   : extension revision 1

Instance Layers: count = 9
--------------------------
VK_LAYER_INTEL_nullhw             INTEL NULL HW                1.1.73   version 1
VK_LAYER_MESA_device_select       Linux device selection layer 1.4.303  version 1
VK_LAYER_MESA_overlay             Mesa Overlay layer           1.4.303  version 1
VK_LAYER_NV_optimus               NVIDIA Optimus layer         1.4.329  version 1
VK_LAYER_NV_present               NVIDIA Presentation Layer    1.4.329  version 1
VK_LAYER_VALVE_steam_fossilize_32 Steam Pipeline Caching Layer 1.3.207  version 1
VK_LAYER_VALVE_steam_fossilize_64 Steam Pipeline Caching Layer 1.3.207  version 1
VK_LAYER_VALVE_steam_overlay_32   Steam Overlay Layer          1.3.207  version 1
VK_LAYER_VALVE_steam_overlay_64   Steam Overlay Layer          1.3.207  version 1

Devices:
========
GPU0:
	apiVersion         = 1.4.329
	driverVersion      = 595.58.3.0
	vendorID           = 0x10de
	deviceID           = 0x2b85
	deviceType         = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
	deviceName         = NVIDIA GeForce RTX 5090
	driverID           = DRIVER_ID_NVIDIA_PROPRIETARY
	driverName         = NVIDIA
	driverInfo         = 595.58.03
	conformanceVersion = 1.4.3.3
	deviceUUID         = 887aa7a3-b960-e4ea-05db-3d9786e525ea
	driverUUID         = 4d57923b-9f0d-587f-a383-262812d65e19
GPU1:
	apiVersion         = 1.4.318
	driverVersion      = 25.2.8
	vendorID           = 0x1002
	deviceID           = 0x13c0
	deviceType         = PHYSICAL_DEVICE_TYPE_INTEGRATED_GPU
	deviceName         = AMD Ryzen 9 9950X3D 16-Core Processor (RADV RAPHAEL_MENDOCINO)
	driverID           = DRIVER_ID_MESA_RADV
	driverName         = radv
	driverInfo         = Mesa 25.2.8-0ubuntu0.25.10.1
	conformanceVersion = 1.4.0.0
	deviceUUID         = 00000000-7000-0000-0000-000000000000
	driverUUID         = 414d442d-4d45-5341-2d44-525600000000
GPU2:
	apiVersion         = 1.4.318
	driverVersion      = 25.2.8
	vendorID           = 0x10005
	deviceID           = 0x0000
	deviceType         = PHYSICAL_DEVICE_TYPE_CPU
	deviceName         = llvmpipe (LLVM 20.1.8, 256 bits)
	driverID           = DRIVER_ID_MESA_LLVMPIPE
	driverName         = llvmpipe
	driverInfo         = Mesa 25.2.8-0ubuntu0.25.10.1 (LLVM 20.1.8)
	conformanceVersion = 1.3.1.1
	deviceUUID         = 6d657361-3235-2e32-2e38-2d3075627500
	driverUUID         = 6c6c766d-7069-7065-5555-494400000000

@IgnisFlamme 's suggestion didn't work for me, and trying to force anything DX9 related crashes because DX9 can't be found.

Is this a wayland compat issue?