Arch Linux

Teiolass

Member

Registered: 2022-08-02

Posts: 5

Proton not launching with newer versions

Hello everyone,

It is months that I am experiencing troubles with Proton. In particular I can't run games with proton version strictly higher than 4.2 (which isn't terrible as long as the fix to some problem is "use newer proton version"). I don't really know what kind of infos provide, so here's the log of the game The Witness when run with proton experimental: LINK. Disabling vulkan through PROTON_USE_WINED3D=1 %command% doesn't help.

I am using the GPU: NVIDIA GeForce GTX 850M (but on the laptop it is installed a Intel HD Graphics 5500 too),

Output of pacman -Qs nvidia:

local/egl-wayland 2:1.1.10-1
    EGLStream-based Wayland external platform
local/lib32-nvidia-utils 515.57-1
    NVIDIA drivers utilities (32-bit)
local/libnvidia-container-bin 1.9.0-1
    NVIDIA container runtime library
local/libnvidia-container-tools-bin 1.9.0-1
    NVIDIA container runtime library (command-line tools)
local/libvdpau 1.5-1
    Nvidia VDPAU library
local/libxnvctrl 515.57-1
    NVIDIA NV-CONTROL X extension
local/nvidia-container-toolkit 1.9.0-1
    NVIDIA container runtime toolkit
local/nvidia-lts 1:515.57-7
    NVIDIA drivers for linux-lts
local/nvidia-prime 1.0-4
    NVIDIA Prime Render Offload configuration and utilities
local/nvidia-settings 515.57-1
    Tool for configuring the NVIDIA graphics driver
local/nvidia-utils 515.57-1
    NVIDIA drivers utilities
local/xf86-video-nouveau 1.0.17-2 (xorg-drivers)
    Open Source 3D acceleration driver for nVidia cards

Output of pacman -Qs vulkan:

local/lib32-nvidia-utils 515.57-1
    NVIDIA drivers utilities (32-bit)
local/lib32-vulkan-icd-loader 1.3.221-1
    Vulkan Installable Client Driver (ICD) Loader (32-bit)
local/nvidia-utils 515.57-1
    NVIDIA drivers utilities
local/spirv-tools 2022.1-1 (vulkan-devel)
    API and commands for processing SPIR-V modules
local/vulkan-extra-layers 1.3.216.0-1 (vulkan-devel)
    Extra layers for Vulkan development
local/vulkan-extra-tools 1.3.216.0-1 (vulkan-devel)
    Vulkan lunarg tools
local/vulkan-headers 1:1.3.221-1 (vulkan-devel)
    Vulkan header files
local/vulkan-html-docs 1:1.3.221-1 (vulkan-devel)
    Vulkan html documentation
local/vulkan-icd-loader 1.3.221-1
    Vulkan Installable Client Driver (ICD) Loader
local/vulkan-tools 1.3.217-1 (vulkan-devel)
    Vulkan Utilities and Tools
local/vulkan-validation-layers 1.3.216.0-1 (vulkan-devel)
    Vulkan Validation Layers

Output of glxinfo -B:

display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel (0x8086)
    Device: Mesa Intel(R) HD Graphics 5500 (BDW GT2) (0x1616)
    Version: 22.1.4
    Accelerated: yes
    Video memory: 8661MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) HD Graphics 5500 (BDW GT2)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 22.1.4
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 22.1.4
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 22.1.4
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

Output of vulkaninfo --summary

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

Vulkan Instance Version: 1.3.221


Instance Extensions: count = 19
-------------------------------
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_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_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

Instance Layers: count = 9
--------------------------
VK_LAYER_KHRONOS_validation       Khronos Validation Layer     1.3.216  version 1
VK_LAYER_LUNARG_api_dump          LunarG API dump layer        1.3.216  version 2
VK_LAYER_LUNARG_monitor           Execution Monitoring Layer   1.3.216  version 1
VK_LAYER_LUNARG_screenshot        LunarG image capture layer   1.3.216  version 1
VK_LAYER_NV_optimus               NVIDIA Optimus layer         1.3.205  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         = 4206797 (1.3.205)
	driverVersion      = 2161000448 (0x80ce4000)
	vendorID           = 0x10de
	deviceID           = 0x1391
	deviceType         = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
	deviceName         = NVIDIA GeForce GTX 850M
	driverID           = DRIVER_ID_NVIDIA_PROPRIETARY
	driverName         = NVIDIA
	driverInfo         = 515.57
	conformanceVersion = 1.3.1.0
	deviceUUID         = 53c90fe0-55bd-6aaa-5534-b308e76a7628
	driverUUID         = 9b799bb9-29e0-5c8d-9f6d-28dae6381a33

Thank you all guys!

edit: typo

Last edited by Teiolass (2022-08-02 09:46:11)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 23,935

Re: Proton not launching with newer versions

That error is a bug in a vulkan support check in wine together with intel , there's an old thread about this, somewhere will see if I can dig it out. Does installing {lib32-}intel-vulkan help? Have you tried explicitly prime-run %command% ?

Found the thread which as bissected a relevantly broken commit in wine, which doesn't really help you for prebuilt protons: https://bbs.archlinux.org/viewtopic.php … 2#p1947812

Last edited by V1del (2022-08-02 10:53:47)

Teiolass

Member

Registered: 2022-08-02

Posts: 5

Re: Proton not launching with newer versions

I have tried your ideas and none of them seems to work. I have also tried to get rid of vulkan using flags like PROTON_USE_WINED3D11=1 but with no luck either.

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 13,279

Re: Proton not launching with newer versions

Is xf86-video-intel installed ?
If so, try removing it.

Another possibility :
you have nvidia-container-toolkit from aur installed and it is  out-of-date (it was updated to 1.10 on july 9 )
update them and test.
If that doesn't help, test without them present. (maybe they interfere with normal nvidia functionality ) .

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 23,935

Re: Proton not launching with newer versions

Mhm... try setting

VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/nvidia_icd.json 

generally in your environment or explicitly as a launch option in steam.

Teiolass

Member

Registered: 2022-08-02

Posts: 5

Re: Proton not launching with newer versions

xf86-video-intel was already not installed. I tried both to update and remove nvidia-container-toolking, but nothing changed

Teiolass

Member

Registered: 2022-08-02

Posts: 5

Re: Proton not launching with newer versions

Setting

VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/nvidia_icd.json 

still does nothing.

I noticed a different behaviour wether I launch steam from rofi or from terminal: in the first case when I click the play button, the button shows the text "Stop", the program does something for a few seconds, and then the button gets back at "Play" again. In the latter case after clicking on play the program gets stuck indefinitely (or at least for a very long time). HERE is the link to the log of the version with steam launche from terminal (where I forced the exit after a while).

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 23,935

Re: Proton not launching with newer versions

I doubt that has much of a relevance. This log still contains

243.662:0020:00c0:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
243.662:0020:00c0:err:winediag:nodrv_CreateWindow The explorer process failed to start.

Does standard wine work? Try running

winecfg

I'm expecting it to fail in a similar manner.

Teiolass

Member

Registered: 2022-08-02

Posts: 5

Re: Proton not launching with newer versions

This the output of winecfg:

002c:fixme:winediag:LdrInitializeThunk wine-staging 7.14 is a testing version containing experimental patches.
002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when filing bug reports on winehq.org.
0080:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0080:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0080:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0080:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
MESA-INTEL: warning: Performance support disabled, consider sysctl dev.i915.perf_stream_paranoid=0
0094:err:seh:KiUserCallbackDispatcher ignoring exception
wine: Unhandled page fault on execute access to 00007F66E2952A50 at address 00007F66E2952A50 (thread 0094), starting debugger...

After that the process is still active but unresponsive (a ctrl-c isn't enough to exit)