Open Patola opened 3 years ago
Hello @Patola, warn:debugstr:OutputDebugStringA "Error [SPEC | xrGetInstanceProcAddr | VUID-xrGetInstanceProcAddr-instance-parameter] : XR_NULL_HANDLE for instance but query for xrInitializeLoaderKHR requires a valid instance\n"
looks like a possible line of interest from the log.
@kisak-valve thanks, indeed, again, using @gofman's patches (in my build https://github.com/Patola/wine/releases/tag/protola_6.3_rbespbgvwd) ran the game successfully. I don't remember if Proton Experimental already incorporated these patches, will try with it later.
The game apparently stopped working in VR after an update. Seems to require Windows.Perception.Spatial.Surfaces.SpatialSurfaceObserver for working in VR.
Trying a patch that was devised by @EsdrasTarsis to fix this, will tell if successful. 0001-windows.perception.spatial.surfaces-Add-dll.patch.txt
Ok, got it to work. An aggregate patch was needed and also a workaround to the odd manifest configuration the developer created. However, @EsdrasTarsis has changed a few things in his patch, so I am attaching the new version here. I will be creating a new proton build capable of running the game.
My build is ready at https://github.com/Patola/wine/releases/tag/protola_6.3-6-6_rbespbgvwd
I can't seem to get this game running, it always crashes on start. I tried the build by @Patola and even linked the manifest file as shown in the release notes.
Here's the log running the build by @Patola: steam-1562420.log
Any ideas?
Are you trying to run in VR or pancake mode?
What is your equipment? If unsure, inxi -bGI
helps
@Patola The VR version, pancake version runs with no issues with all newer Proton versions.
System:
Host: domi-workstation Kernel: 5.14.0-15.1-liquorix-amd64 x86_64 bits: 64
Desktop: GNOME 40.5 Distro: Ubuntu 21.10 (Impish Indri)
Machine:
Type: Desktop Mobo: ASRock model: X570 Phantom Gaming 4
serial: <superuser required> UEFI: American Megatrends v: P3.90
date: 01/26/2021
CPU:
Info: 8-Core AMD Ryzen 7 5800X [MT MCP] speed: 2389 MHz
min/max: 2200/3800 MHz
Graphics:
Device-1: AMD Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] driver: amdgpu
v: kernel
Display: x11 server: X.Org 1.20.13 driver: loaded: amdgpu
resolution: 2560x1440
OpenGL: renderer: AMD Radeon RX 6900 XT (SIENNA_CICHLID DRM 3.42.0
5.14.0-15.1-liquorix-amd64 LLVM 12.0.1)
v: 4.6 Mesa 21.2.4 - kisak-mesa PPA
Network:
Device-1: Intel Ethernet 10-Gigabit X540-AT2 driver: ixgbe
Device-2: Intel Ethernet 10-Gigabit X540-AT2 driver: ixgbe
Device-3: Intel I211 Gigabit Network driver: igb
Drives:
Local Storage: total: 4.09 TiB used: 1.83 TiB (44.7%)
Info:
Processes: 369 Uptime: 54m Memory: 15.55 GiB used: 3.08 GiB (19.8%)
Shell: Bash inxi: 3.3.06
Also, I'm using a Valve Index.
That's weird, I have a very similar setup, although I'm using Arch. And I've just taken part on a match on US servers, the entire match was flawless, I'm attaching the proton log, try to run the game with PROTON_LOG=1 %command%
and we can match our output to see where yours is failing. I'm using my proton build, protola_6.3-6-6_rbespbgvwd
For the record, here is my inxi -bGI
output:
System: Host: risadinha Kernel: 5.14.15-209-tkg-bmq x86_64 bits: 64 Desktop: IceWM 2.8.0 Distro: Arch Linux
Machine: Type: Desktop System: Micro-Star product: MS-7C37 v: 2.0 serial: <superuser required>
Mobo: Micro-Star model: MPG X570 GAMING PLUS (MS-7C37) v: 2.0 serial: <superuser required>
UEFI: American Megatrends LLC. v: A.D0 date: 05/20/2021
CPU: Info: 12-Core AMD Ryzen 9 5900X [MT MCP] speed: 3817 MHz min/max: 2200/3700 MHz
Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] driver: amdgpu v: kernel
Device-2: Microdia USB Camera type: USB driver: uvcvideo
Device-3: NONIN MEDICAL Usb Camera Audio type: USB driver: hid-generic,snd-usb-audio,usbhid
Device-4: Valve 3D Camera type: USB driver: uvcvideo
Display: x11 server: X.Org 1.20.13 driver: loaded: amdgpu unloaded: modesetting resolution: 2560x1080~144Hz
OpenGL: renderer: AMD Radeon RX 6800 XT (SIENNA_CICHLID DRM 3.42.0 5.14.15-209-tkg-bmq LLVM 12.0.1)
v: 4.6 Mesa 21.2.4
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169
Drives: Local Storage: total: 17.35 TiB used: 8.49 TiB (48.9%)
Info: Processes: 493 Uptime: 13h 24m Memory: 31.27 GiB used: 11.87 GiB (38.0%) Shell: Zsh inxi: 3.3.08
Just noticed that a Valve Index device is not appearing on your output, @DomiStyle: the headset dual cameras. Look at my output, there's Valve 3D Camera type: USB driver: uvcvideo
while yours are not showing. Are you starting the game from within SteamVR Home? Or from the steam interface, selecting SteamVR mode, when SteamVR is running?
@DomiStyle only saw your log now, can you do
rm -rf /mnt/data/games/steam/steamapps/compatdata/1562420
and try to run the game again (first ensure in the compatibility tab that my build of proton is selected)? This directory contains some meta-information and the wine prefix, if you remove it proton will recreate it from scratch, maybe with the right libraries.
Your log has these lines:
2022.266:013c:0140:fixme:combase:RoGetActivationFactory (L"Windows.Perception.Spatial.Surfaces.SpatialSurfaceObserver", {0f534261-c55d-4e6b-a895-a19de69a42e3}, 000000000021E028): semi-stub
2022.266:013c:0140:err:combase:RoGetActivationFactory Failed to find library for L"Windows.Perception.Spatial.Surfaces.SpatialSurfaceObserver"
While mine loads the library:
46967.083:0144:0148:fixme:combase:RoGetActivationFactory (L"Windows.Perception.Spatial.Surfaces.SpatialSurfaceObserver", {0f534261-c55d-4e6b-a895-a19de69a42e3}, 000000000021E028): semi-stub
46967.126:0144:0148:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\windows.perception.spatial.surfaces.dll" at 000000026E920000: builtin
@Patola I just didn't have my Index connected at the time I ran the command, I just checked with it connected and the line is there as expected.
I already tried clearing the prefix but no luck, still just crashes on start. Any idea where that library should come from? Wine? The game?
These library stubs (written by @EsdrasTarsis) are the ones that my build of wine have, @DomiStyle. You should not have this error message on the logs if you are using my build. Have you uncompressed it under ~/.steam/root/compatibilitytools.d
(thereby creating a directory there), restarted Steam, rm -rf /mnt/data/games/steam/steamapps/compatdata/1562420
on the terminal, left-clicked in the game entry in the library view, properties, compatibility, choose from the pull-down list "protola_6.3-6-6-rbespbgvwd"?
In your log, your selected proton looks like having the same signature as mine, though: Proton: 1631798300 proton-6.3-5-1-g6f35d1e
. That's weird. See if these files exist on your system, they are the library files:
ls -l /mnt/data/games/steam/steamapps/compatdata/1562420/pfx/drive_c/windows/system32/windows.perception.spatial.surfaces.dll /mnt/data/games/steam/steamapps/compatdata/1562420/pfx/drive_c/windows/system32/windows.perception.spatial.surfaces.dll
If they don't exist, your instance of my proton build is borked somehow...
Yes, I installed it in compatibilitytools.d like you wrote.
The file seems to be there just fine:
85001ad6af6527d0d48d657334b57065 windows.perception.spatial.surfaces.dll
It's a symlink to /home/domi/.local/share/Steam/compatibilitytools.d/protola-6.3-6-6-rbespbgvwd/dist/lib64/wine/windows.perception.spatial.surfaces.dll
.
@DomiStyle I don't know what to suggest. Everything seems to be right, but somehow your proton is unable to load that library? It's odd. Sorry... I'm out of ideas.
No worries, it works in non-VR so I'm just gonna play it like that for now.
Compatibility Report
System Information
I confirm:
Symptoms
Game does not start in VR mode. In pancake mode it seems to be working OK, although I haven't tested much yet.
Reproduction
The proton logfile ended up having 66 MiB, so I could not upload it in the bug report. Had to zip it to fit the bug report constraints.
steam-1562420.zip