You are not logged in.

Pages: 1

#1 2024-12-22 00:20:05

Big Scorpio
Member
Registered: 2024-12-15
Posts: 45

[SOLV] Game doesnt start on Steam Proton: Vulkan & Wine instance error

Hello Arch Friends,

I am trying to play some Steam Games using Proton or Wine with no success yet. What happens is when I press PLAY, the game apparently "launches" (nothing being seen on the desktop) and it even shows me the logo on the desktop (like a floating image on top of it) for a few seconds and then terminates itself. This happens with Proton Hotfix (default), Proton 9 and Proton 8. The game is BioShock Remastered.

I tried using arguments like "PROTON_USE_WINED3D=1 %command%" and "PROTON_USE_VULKAN=1 %command%" to no avail.

Using PROTON_LOG=1 i dug into the log files and found this (using either PROTON_USE_VULKAN or neither of the above)

5729.004:011c:0120:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
5729.392:011c:0120:trace:seh:EnumProcessModulesEx (FFFFFFFF, 00B5E118, 1024, 0062FA30, 0)
info:  Game: BioshockHD.exe
info:  DXVK: v2.5.1-1-gd96fa54080320e9
info:  Build: x86 gcc 10.3.0
5732.202:011c:0120:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\winevulkan.dll" at 77A10000: builtin
info:  Vulkan: Found vkGetInstanceProcAddr in winevulkan.dll @ 0x77a20ec0
info:  Built-in extension providers:
info:    Platform WSI
info:    OpenVR
info:    OpenXR
info:  Enabled instance extensions:
info:    VK_KHR_get_surface_capabilities2
info:    VK_KHR_surface
info:    VK_KHR_win32_surface
5732.203:011c:0120:err:vulkan:wine_vkCreateInstance Failed to create instance, res=-9
5732.203:011c:0120:trace:seh:raise (22)
5732.267:0030:012c:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
pid 40533 != 40532, skipping destruction (fork without exec?)

Using PROTON_USE_WINED3D=1 yielded a different error

5022.856:0120:0124:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
5023.199:0120:0124:trace:seh:EnumProcessModulesEx (FFFFFFFF, 0079D6B8, 1024, 0062FA30, 0)
5026.059:0120:0124:err:wgl:X11DRV_WineGL_InitOpenglInfo  couldn't initialize OpenGL, expect problems
5026.059:0120:0124:err:d3d:wined3d_caps_gl_ctx_create Failed to find a suitable pixel format.
5026.060:0120:0124:err:d3d:wined3d_adapter_gl_init Failed to get a GL context for adapter 09C09BA8.
5026.082:0120:0124:err:d3d:wined3d_caps_gl_ctx_create Failed to find a suitable pixel format.
5026.083:0120:0124:err:d3d:wined3d_adapter_gl_init Failed to get a GL context for adapter 09469680.
5026.083:0120:0124:trace:seh:dispatch_exception code=c0000005 flags=0 addr=111713D1 ip=111713d1
5026.083:0120:0124:trace:seh:dispatch_exception  info[0]=00000000
5026.083:0120:0124:trace:seh:dispatch_exception  info[1]=00000000
5026.083:0120:0124:warn:seh:dispatch_exception EXCEPTION_ACCESS_VIOLATION exception (code=c0000005) raised

On Lutris I tried starting it directly from the executable using Wine but it didn't start. Not even a logo being displayed.

Did some research.
"vulkaninfo --summary" prints out normally

vulkaninfo --summary
WARNING: [Loader Message] Code 0 : Layer VK_LAYER_AMD_switchable_graphics_32 uses API version 1.3 which is older than the application specified API version of 1.4. May cause issues.
==========
VULKANINFO
==========

Vulkan Instance Version: 1.4.303


Instance Extensions: count = 24
-------------------------------
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_surface_maintenance1            : extension revision 1
VK_EXT_swapchain_colorspace            : extension revision 4
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
VK_LUNARG_direct_driver_loading        : extension revision 1
VK_NV_display_stereo                   : extension revision 1

Instance Layers: count = 6
--------------------------
VK_LAYER_AMD_switchable_graphics_32 AMD switchable graphics layer 1.3.301  version 1
VK_LAYER_NV_optimus                 NVIDIA Optimus layer          1.3.289  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.3.289
        driverVersion      = 565.77.0.0
        vendorID           = 0x10de
        deviceID           = 0x1b06
        deviceType         = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
        deviceName         = NVIDIA GeForce GTX 1080 Ti
        driverID           = DRIVER_ID_NVIDIA_PROPRIETARY
        driverName         = NVIDIA
        driverInfo         = 565.77
        conformanceVersion = 1.3.8.2
        deviceUUID         = 53d43949-6a13-e9b2-7da2-e5b953fec214
        driverUUID         = 5d948742-de2b-5e32-9692-c2a5621aed9a

Updating my NVidia drivers and installing them ( sudo pacman -Syu nvidia nvidia-utils ) resulted in a package conflict. So I installed nvidia-utils separately ( yay -S nvidia-utils ).

looking for conflicting packages...
:: nvidia-565.77-5 and nvidia-dkms-565.77-2 are in conflict (NVIDIA-MODULE). Remove nvidia-dkms? [y/N]  
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: nvidia-565.77-5 and nvidia-dkms-565.77-2 are in conflict

Also I was advised to install vulkan-nvidia but this package does not exist apparently.

yay -S vulkan-nvidia
 -> No AUR package found for vulkan-nvidia

Next, I was advised to check "echo $VK_ICD_FILENAMES" which yielded nothing at all.

Since I saw someone asking for additional info elsewhere with a similar game launching problem, I'll post in advance the results of "pacman -Qs vulkan"

local/lib32-amdvlk 2024.Q4.2-1
    AMD's standalone Vulkan driver
local/lib32-vulkan-icd-loader 1.4.303-1
    Vulkan Installable Client Driver (ICD) Loader (32-bit)
local/nvidia-utils 565.77-2
    NVIDIA drivers utilities
local/qt6-shadertools 6.8.1-1 (qt6)
    Provides functionality for the shader pipeline that allows Qt Quick to operate on Vulkan, Metal, and Direct3D, in addition to OpenGL
local/spirv-tools 2024.4.rc1-1 (vulkan-devel)
    API and commands for processing SPIR-V modules
local/vulkan-headers 1:1.4.303-1 (vulkan-devel)
    Vulkan header files
local/vulkan-icd-loader 1.4.303-1
    Vulkan Installable Client Driver (ICD) Loader
local/vulkan-tools 1.4.303-2 (vulkan-devel)
    Vulkan Utilities and Tools

and "lspci -knn"

00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers [8086:191f] (rev 07)
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:5000]
        Kernel driver in use: skl_uncore
        Kernel modules: ie31200_edac
00:01.0 PCI bridge [0604]: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) [8086:1901] (rev 07)
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:5000]
        Kernel driver in use: pcieport
00:02.0 Display controller [0380]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06)
        DeviceName:  Onboard IGD
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
        Kernel driver in use: i915
        Kernel modules: i915
00:14.0 USB controller [0c03]: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller [8086:a12f] (rev 31)
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:5007]
        Kernel driver in use: xhci_hcd
00:16.0 Communication controller [0780]: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 [8086:a13a] (rev 31)
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:1c3a]
        Kernel driver in use: mei_me
        Kernel modules: mei_me
00:17.0 SATA controller [0106]: Intel Corporation Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode] [8086:a102] (rev 31)
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:b005]
        Kernel driver in use: ahci
00:1b.0 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #17 [8086:a167] (rev f1)
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:5001]
        Kernel driver in use: pcieport
00:1b.2 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #19 [8086:a169] (rev f1)
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:5001]
        Kernel driver in use: pcieport
00:1b.3 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #20 [8086:a16a] (rev f1)
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:5001]
        Kernel driver in use: pcieport
00:1c.0 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #1 [8086:a110] (rev f1)
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:5001]
        Kernel driver in use: pcieport
00:1c.1 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #2 [8086:a111] (rev f1)
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:5001]
        Kernel driver in use: pcieport
00:1c.2 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #3 [8086:a112] (rev f1)
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:5001]
        Kernel driver in use: pcieport
00:1c.4 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #5 [8086:a114] (rev f1)
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:5001]
        Kernel driver in use: pcieport
00:1d.0 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #9 [8086:a118] (rev f1)
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:5001]
        Kernel driver in use: pcieport
00:1f.0 ISA bridge [0601]: Intel Corporation Z170 Chipset LPC/eSPI Controller [8086:a145] (rev 31)
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:5001]
00:1f.2 Memory controller [0580]: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller [8086:a121] (rev 31)
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:5001]
00:1f.3 Audio device [0403]: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller [8086:a170] (rev 31)
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:a036]
        Kernel driver in use: snd_hda_intel
        Kernel modules: snd_hda_intel, snd_soc_avs
00:1f.4 SMBus [0c05]: Intel Corporation 100 Series/C230 Series Chipset Family SMBus [8086:a123] (rev 31)
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:5001]
        Kernel driver in use: i801_smbus
        Kernel modules: i2c_i801
00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (2) I219-V [8086:15b8] (rev 31)
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:e000]
        Kernel driver in use: e1000e
        Kernel modules: e1000e
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1)
        Subsystem: NVIDIA Corporation Device [10de:120f]
        Kernel driver in use: nvidia
        Kernel modules: nouveau, nvidia_drm, nvidia
01:00.1 Audio device [0403]: NVIDIA Corporation GP102 HDMI Audio Controller [10de:10ef] (rev a1)
        Subsystem: NVIDIA Corporation Device [10de:120f]
        Kernel driver in use: snd_hda_intel
        Kernel modules: snd_hda_intel
04:00.0 SATA controller [0106]: ASMedia Technology Inc. ASM1061/ASM1062 Serial ATA Controller [1b21:0612] (rev 02)
        Subsystem: ASMedia Technology Inc. Device [1b21:1062]
        Kernel driver in use: ahci
05:00.0 USB controller [0c03]: Etron Technology, Inc. EJ168 USB 3.0 Host Controller [1b6f:7023] (rev 01)
        Subsystem: Device [7023:1b6f]
        Kernel driver in use: xhci_hcd
07:00.0 Ethernet controller [0200]: Qualcomm Atheros Killer E2400 Gigabit Ethernet Controller [1969:e0a1] (rev 10)
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:e000]
        Kernel driver in use: alx
        Kernel modules: alx
08:00.0 PCI bridge [0604]: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] [8086:1578]
        Subsystem: Device [2222:1111]
        Kernel driver in use: pcieport
09:00.0 PCI bridge [0604]: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] [8086:1578]
        Subsystem: Device [2222:1111]
        Kernel driver in use: pcieport
09:01.0 PCI bridge [0604]: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] [8086:1578]
        Subsystem: Device [2222:1111]
        Kernel driver in use: pcieport
09:02.0 PCI bridge [0604]: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] [8086:1578]
        Subsystem: Device [2222:1111]
        Kernel driver in use: pcieport
09:04.0 PCI bridge [0604]: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] [8086:1578]
        Subsystem: Device [2222:1111]
        Kernel driver in use: pcieport
41:00.0 Non-Volatile memory controller [0108]: Micron/Crucial Technology T705 NVMe PCIe SSD [c0a9:542b]
        Subsystem: Micron/Crucial Technology Device [c0a9:2b00]
        Kernel driver in use: nvme
        Kernel modules: nvme

So, Arch Friends, what is the problem and more importantly the solution here? I can see, that it's 

err:vulkan:wine_vkCreateInstance Failed to create instance, res=-9

but how to get past it?

Last edited by Big Scorpio (2024-12-22 03:09:17)

Offline

#2 2024-12-22 01:18:54

Big Scorpio
Member
Registered: 2024-12-15
Posts: 45

Re: [SOLV] Game doesnt start on Steam Proton: Vulkan & Wine instance error

Update: I tried running Mirror's Edge on Steam too. According to ProtonDB this must run out of the box - https://www.protondb.com/app/17410

Inspecting the logs from Proton I saw the exact same error

err:vulkan:wine_vkCreateInstance Failed to create instance, res=-9p

Offline

#3 2024-12-22 02:47:35

Big Scorpio
Member
Registered: 2024-12-15
Posts: 45

Re: [SOLV] Game doesnt start on Steam Proton: Vulkan & Wine instance error

*sigh*

I'm not sure what's the case. Either I'm an Arch Newbie (but not a noob in Linux) or these how-to's are secret treasures we have to dig up ourselves somehow.

I tried a bunch of more stuff to get it working and past the error and I have no idea what exactly it was, that solved it for me. Mirror's Edge runs on Steam with Proton for me now.

Among these things I tried something made it work:

- Arch Wiki for NVIDIA drivers (proprietary in my case with my GTX 1080 Ti, not the Nouveau. Also my kernel is just linux, not linux-lts) -> https://wiki.archlinux.org/title/NVIDIA
..- multilib for enabling the lib32 stuff -> https://wiki.archlinux.org/title/Offici … s#multilib
..- Nvidia utils for Vulkan -> https://wiki.archlinux.org/title/Vulkan#Installation
..- yay -S lib32-nvidia-utils
- Some help found on Reddit regarding Steam, Vulkan and drivers -> https://www.reddit.com/r/linux_gaming/c … _i_choose/ and more specifically
..-> Lutris community guide - installing more drivers to support lib32 projects -> https://github.com/lutris/docs/blob/mas … Drivers.md
..-> Lutris community guide - installing wine dependencies -> https://github.com/lutris/docs/blob/mas … dencies.md

That is not all I tried. There were a few other things but I can't remember what I did. Seemingly banging my head on the keyboard until it works figuratively speaking.

In any case may the next Arch person stumbling upon this problem find this helpful too.

Offline

#4 2024-12-22 13:08:24

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 13,242

Re: [SOLV] Game doesnt start on Steam Proton: Vulkan & Wine instance error

WARNING: [Loader Message] Code 0 : Layer VK_LAYER_AMD_switchable_graphics_32 uses API version 1.3 which is older than the application specified API version of 1.4. May cause issues

That only happens on arch systems where amdvlk /lib32-amdvlk are installed / used incorrectly (and make a mess of things) .

The typical reason amdvlk is installed is users not reading pacman output when installing things and accepting defaults without thinking .
Windows devices suffer from the next- next -next syndrome to install stuff , sometimes it seems linux  users suffer from its sibling enter-enter-enter .

The output of pacman -Qs vulkan wiil help to troubleshoot this.

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

Offline

#5 2024-12-22 15:50:07

Big Scorpio
Member
Registered: 2024-12-15
Posts: 45

Re: [SOLV] Game doesnt start on Steam Proton: Vulkan & Wine instance error

Lone_Wolf wrote:

The output of pacman -Qs vulkan wiil help to troubleshoot this.

I comply.

pacman -Qs vulkan
local/lib32-amdvlk 2024.Q4.2-1
    AMD's standalone Vulkan driver
local/lib32-nvidia-utils 565.77-1
    NVIDIA drivers utilities (32-bit)
local/lib32-vulkan-icd-loader 1.4.303-1
    Vulkan Installable Client Driver (ICD) Loader (32-bit)
local/nvidia-utils 565.77-2
    NVIDIA drivers utilities
local/qt6-shadertools 6.8.1-1 (qt6)
    Provides functionality for the shader pipeline that allows Qt Quick to operate on Vulkan, Metal, and Direct3D, in addition to OpenGL
local/spirv-tools 2024.4.rc1-1 (vulkan-devel)
    API and commands for processing SPIR-V modules
local/vulkan-headers 1:1.4.303-1 (vulkan-devel)
    Vulkan header files
local/vulkan-icd-loader 1.4.303-1
    Vulkan Installable Client Driver (ICD) Loader
local/vulkan-tools 1.4.303-2 (vulkan-devel)
    Vulkan Utilities and Tools

Offline

#6 2024-12-23 08:50:12

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 13,242

Re: [SOLV] Game doesnt start on Steam Proton: Vulkan & Wine instance error

remove lib32-amdvlk, then rerun vulkaninfo --summary .

If it doesn't report errors anymore you should be ok.

Are you sure you only have 1 videocard (nvidia ) in this system ?
If unsure, post the output of lspci -k

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

Offline

#7 2024-12-23 21:48:19

Big Scorpio
Member
Registered: 2024-12-15
Posts: 45

Re: [SOLV] Game doesnt start on Steam Proton: Vulkan & Wine instance error

Lone_Wolf wrote:

remove lib32-amdvlk, then rerun vulkaninfo --summary .

If it doesn't report errors anymore you should be ok.

Are you sure you only have 1 videocard (nvidia ) in this system ?
If unsure, post the output of lspci -k

Complying.
The error has vanished. Thanks.

vulkaninfo --summary
==========
VULKANINFO
==========

Vulkan Instance Version: 1.4.303

Regarding the GPU, I have indeed 2 of them. The Nvidia one and Intel HD Graphics 530 integrated in the CPU. See below:

00:02.0 Display controller: Intel Corporation HD Graphics 530 (rev 06)
        DeviceName:  Onboard IGD
        Subsystem: Gigabyte Technology Co., Ltd Device d000
        Kernel driver in use: i915
        Kernel modules: i915

Your suggestions?
Keep in mind, that disabling the Intel Integrated GPU (such as in the BIOS) is not my preferred way. I have a use case for it for running separate tasks e.g. Streaming.
However at this time I do not see a Video Encoder option to use the Intel GPU in OBS. Only NVIDIA NVENC H.264 and x264.

Offline

#8 2024-12-28 09:14:54

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 13,242

Re: [SOLV] Game doesnt start on Steam Proton: Vulkan & Wine instance error

Disabling is not needed, vulkan has mechanisms to switch between multiple videocards/drivers . The MESA_VK_DEVICE_SELECT  layer is what works best on linux and works well with wine & steam proton.

Install vulkan-intel and vulkan-mesa-layers packages .
Read https://wiki.archlinux.org/title/Vulkan … en_devices

Open Broadcaster Software relies on HW video acceleration (vaapi / vdpau ) , check https://wiki.archlinux.org/title/Open_B … r_Software .
The setup for those is not related to vulkan at all, you'll need to start another thread for that issue.

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

Offline

#9 2024-12-30 19:48:30

Big Scorpio
Member
Registered: 2024-12-15
Posts: 45

Re: [SOLV] Game doesnt start on Steam Proton: Vulkan & Wine instance error

Lone_Wolf wrote:

Disabling is not needed, vulkan has mechanisms to switch between multiple videocards/drivers . The MESA_VK_DEVICE_SELECT  layer is what works best on linux and works well with wine & steam proton.

Install vulkan-intel and vulkan-mesa-layers packages .
Read https://wiki.archlinux.org/title/Vulkan … en_devices

Open Broadcaster Software relies on HW video acceleration (vaapi / vdpau ) , check https://wiki.archlinux.org/title/Open_B … r_Software .
The setup for those is not related to vulkan at all, you'll need to start another thread for that issue.

Good to know, although with that i have encountered a new Warning. See here

$ vulkaninfo --summary
WARNING: [Loader Message] Code 0 : Layer VK_LAYER_MESA_device_select uses API version 1.3 which is older than the application specified API version of 1.4. May cause issues.

$ pacman -Qs vulkan
local/lib32-nvidia-utils 565.77-1
    NVIDIA drivers utilities (32-bit)
local/lib32-vulkan-icd-loader 1.4.303-1
    Vulkan Installable Client Driver (ICD) Loader (32-bit)
local/nvidia-utils 565.77-2
    NVIDIA drivers utilities
local/qt6-shadertools 6.8.1-1 (qt6)
    Provides functionality for the shader pipeline that allows Qt Quick to operate on Vulkan, Metal, and Direct3D, in addition
    to OpenGL
local/spirv-tools 2024.4.rc1-1 (vulkan-devel)
    API and commands for processing SPIR-V modules
local/vulkan-headers 1:1.4.303-1 (vulkan-devel)
    Vulkan header files
local/vulkan-icd-loader 1.4.303-1
    Vulkan Installable Client Driver (ICD) Loader
local/vulkan-intel 1:24.3.2-1
    Open-source Vulkan driver for Intel GPUs
local/vulkan-mesa-layers 1:24.3.2-1
    Mesa's Vulkan layers
local/vulkan-tools 1.4.303-2 (vulkan-devel)
    Vulkan Utilities and Tools

Offline

#10 2024-12-31 11:03:33

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 13,242

Re: [SOLV] Game doesnt start on Steam Proton: Vulkan & Wine instance error

WARNING: [Loader Message] Code 0 : Layer VK_LAYER_MESA_device_select uses API version 1.3 which is older than the application specified API version of 1.4. May cause issues.

Vulkan 1.4 was released on dec 3, mesa 25.0 trunk builds already support it.
Mesa stable however won't until 25.0.x is released (could be a few weeks or a few months) .

It's safe to ignore the warning for now.

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

Offline

#11 2025-01-03 07:53:33

Big Scorpio
Member
Registered: 2024-12-15
Posts: 45

Re: [SOLV] Game doesnt start on Steam Proton: Vulkan & Wine instance error

Alright. How can I know when I am to perform or change something in due time? Do I re-ask here in 3 months or so?

Offline

#12 2025-01-03 11:12:26

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 13,242

Re: [SOLV] Game doesnt start on Steam Proton: Vulkan & Wine instance error

You shouldn't have to do anything except updating your system.

In case there are issues due to nvidia using a newer version of vulkan then mesa, you can try using mesa-git or mesa-minimal-git from aur.
Make sure to read the pinned comments on the aur pages of those packages before using them.

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

Offline

Pages: 1

Board footer

Powered by FluxBB