Hello @Vash63, I'm not going to consider this a regression because there's a good chance that the game changed to a completely different input method in this update and the fact it used to work doesn't indicate a regression on Proton's side.
Some lines of interest from the log:
err:vrclient:create_win_interface Don't recognize interface name: IVRInput_006
err:vrclient:ivrclientcore_get_generic_interface Failed to create win object IVRInput_006.
err:vrclient:create_win_interface Don't recognize interface name: FnTable:IVRInput_006
err:vrclient:ivrclientcore_get_generic_interface Failed to create win object FnTable:IVRInput_006.
Ok. It's likely not a regression within Proton itself, but it is from a game compatibility standpoint. Also worth noting is that it doesn't seem to be a blanket issue with the new Steam Input libraries, the same system has working controllers in Aperture Hand Labs which also uses the Index supporting API.
Thanks for reporting. Looks like we need to update our vr wrapper again.
I have this problem in B&S, too. Here's the proton log for it:
steam-629730.log
Can confirm that H3 now runs properly on Proton 4.11.
Hotdogs, Horseshoes, and Hand Grenades (7189098)
Issue transferred from https://github.com/ValveSoftware/Proton/issues/5290.
@Frityet posted on 2021-11-06T05:52:22:
Despite previously working one week ago, when I switch scenes from the main menu scene to any other scene, my wrist-menu (menu which shows all the options of the game, and allows switching of the scenes) is completely not there, and my quickbelt slots (Stores items on the players) are also missing.
Here is my game log: output_log.txt
Launch H3VR
Open a scene
Hello @Frityet, this looks like the line of interest from your log: wine: Call from 000000007B01239E to unimplemented function bthprops.cpl.BluetoothGetRadioInfo, aborting
Hello @Frityet, this looks like the line of interest from your log:
wine: Call from 000000007B01239E to unimplemented function bthprops.cpl.BluetoothGetRadioInfo, aborting
Thank you! I will try and disable bluetooth
Hi!
When starting H3VR inside the HMD, i can play without any problems (albeit with a performance hit). When inspecting my pc-screen, i'm prompted with an error message, and when i'm clicking on 'ok', the game crashes to desktop.
Ran fine with PROTON_LOG=1 gamemoderun %command% on proton experimental approximately 30 minutes.
I tried to upload the original log from proton as well, but i noticed that the log file accumulated to almost 65 MB.
There was almost 700 000 entries of messages such as 1938.362:005c:00c8:fixme:fsync:add_to_list too many allocated handles, not caching 0x404d24, could this maybe be relevant for the performance hit compared to windows?
Here's the proton-log without the fixme messages with the pattern mentioned.
OS: EndeavourOS Linux
KERNEL: 5.15.4-zen1-1-zen
CPU: AMD Ryzen 7 3700X 8-Core
GPU: NVIDIA GeForce RTX 2070
GPU DRIVER: NVIDIA 495.44
RAM: 16 GB
Have this error too, it doesn’t actually do anything though, you can ignore it!
On Nov 25, 2021, at 9:31 AM, OlavStornes @.***> wrote:
Hi!
When starting H3VR inside the HMD, i can play without any problems (albeit with a performance hit). When inspecting my pc-screen, i'm prompted with an error message, and when i'm clicking on 'ok', the game crashes to desktop.
Ran fine with PROTON_LOG=1 gamemoderun %command% on proton experimental approximately 30 minutes.
error.log https://github.com/ValveSoftware/Proton/files/7604557/error.log
output_log.txt https://github.com/ValveSoftware/Proton/files/7604558/output_log.txt
I tried to upload the original log from proton as well, but i noticed that the log file accumulated to almost 65 MB.There was almost 700 000 entries of messages such as 1938.362:005c:00c8:fixme:fsync:add_to_list too many allocated handles, not caching 0x404d24, could this maybe be relevant for the performance hit compared to windows?
Here's the proton-log without the fixme messages with the pattern mentioned.
steam-450540-stripped.log https://github.com/ValveSoftware/Proton/files/7604613/steam-450540-stripped.log
System informationOS: EndeavourOS Linux
KERNEL: 5.15.4-zen1-1-zen
CPU: AMD Ryzen 7 3700X 8-Core
GPU: NVIDIA GeForce RTX 2070
GPU DRIVER: NVIDIA 495.44
RAM: 16 GB—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/Proton/issues/2836#issuecomment-979377098, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGB7SONKYD3ISLCQ7IK7EMLUNZXHNANCNFSM4H3NI2QQ.
Compatibility Report
Name of the game with compatibility issues: Hotdogs, Horseshoes, and Hand Grenades (H3VR)
Steam AppID of the game: 450540
System Information
GPU: GTX 1080
Driver/LLVM version: NVIDIA 495.44
Kernel version: 5.4.0-91-generic
Link to full system information report as Gist: gist.github.com/Frityet/6093640fd4e71a60a6657e9edd5521d7
Proton version: Proton Experimental
I confirm:
that I haven't found an existing compatibility report for this game.
that I have checked whether there are updates for my system available.
Symptoms
The videos on the itemspawner refuse to load. I suspect this is because of the AVProVideo plugin which is used to load the videos.
Here is my game log: LogOutput.log
Reproduction
Open H3VR, and go into any scene with the new ItemSpawner
Hello @Frityet, this looks like the line of interest from your log:
wine: Call from 000000007B01239E to unimplemented function bthprops.cpl.BluetoothGetRadioInfo, abortingThank you! I will try and disable bluetooth
Did disabling bluetooth work? How did you get around this issue?
Hello @Frityet, this looks like the line of interest from your log:
wine: Call from 000000007B01239E to unimplemented function bthprops.cpl.BluetoothGetRadioInfo, abortingThank you! I will try and disable bluetooth
Did disabling bluetooth work? How did you get around this issue?
Sorry for late reply, I actually just had a corrupted game install, reinstalling fixed it
System Information:
OS: Nobara 37
CPU: i7-7700HQ
GPU: GTX 1060 Mobile
Driver version: NVIDIA 525.116.03
Kernel version: 6.2.14-300.fsync.fc37.x86_64
Proton version: Proton Experimental
Link to full system information report on Gist: gist.github.com/Frityet/6093640fd4e71a60a6657e9edd5521d7
Proton Log: steam-450540.log
Hi, I think there may be a regression with this game, it'll work fine for around ten minutes or so then lock up with a dialog box titled "Fatal Error in GC" appearing that says too many threads, clicking the OK button in the box will make the game recover but any action involving a firearm (discharging, removing/inserting magazine, cambering round etc) after that will cause the dialog box to reappear and the game to lock up again until the OK button is once again clicked, this will repeat until the game is closed and reopened. There's only one mention of this issue in the game's discussions and that's from another Linux user so I'm led to assume it's a Proton bug.
Thank you.
Replying to https://github.com/ValveSoftware/Proton/issues/2836#issuecomment-1548538756
I have the same issue, I just use an auto-clicker :rofl:
@FuzzyWuggzy I see you mention this being a regression - what is the most recent Proton version where it was not locking up?
@FuzzyWuggzy I see you mention this being a regression - what is the most recent Proton version where it was not locking up?
My bad, I meant a bug, I guess I said regression because I haven't seen anyone mention the issue before, so thought it was a recent thing.
I'll go through previous Proton versions when I have access to my HMD and report if the issue persists.
Sorry about that
No worries at all :) I am on the hunt for regressions from the 8.0 rebase (and actually I'm always on the hunt for regressions)... if this does turn out to be a regression and doesn't happen on earlier versions, that would be awesome because it means it is more likely something we can fix easily :)
Well this wasn't the outcome I was expecting, here are the results of my testing:
Experimenal and 8.0-2: Works but has the issue I've already described.
7.0-6 and 6.3-8: Crashes a second after the game's menu hub loads.
5.13-6 and 5.0-10: Crashes after about ten seconds, looks fine on screen though the HMD doesn't leave the SteamVR void.
I could've sworn it used to work on these older builds, could it be because I'm using a recent build of ALVR (v20.0.0-dev12, compiled from source)? I could try even older Proton versions but I can't see it being fruitful.
Using Proton 8.0.4 this happens after a while.
The "Too many threads" dialog pops up and need to be dismissed over and over again to continue.
I think it comes up when news sounds appear, e.g. Sosigs start talking after activation.
In addition Experimental currently does not work at all.
@thackel I'm not seeing any difference in behavior between 8.0-4 and experimental. If you are still seeing the problem with experimental:
a) Could you describe the failure in more detail?
b) Please copy your system information from Steam (Steam -> Help -> System Information and Steam -> Help -> Steam Runtime Diagnostics) and put each in a gist, then include a link to the gists in this issue report.
c) Could you also grab a log from 8.0-4 and Experimental so we can compare the differences? You can get a log by adding this to the launch options for the game: PROTON_LOG=+steam,+steamclient,+vrclient,+openxr %command%
proton 8.0x1 2023-12proton experimentalx5 2023-05proton 4.11x1 2019-07PROTON_LOG=+steam,+steamclient,+vrclient,+openxrx1 2024-01PROTON_LOG=1x2 2021-11
Compatibility Report
System Information
I confirm:
steam-450540.log
Symptoms
Vive wands don't work - at all. They're detected by the game and shown floating at the center of your tracking space but no buttons work and they aren't physically tracked.
Reproduction
Launch the game. Attempt to use controllers.
Important to note that this was not the case prior to the recent H3VR update that added Knuckles support. I don't have my Knuckles to test with yet (coming soon) but I did test this game a few months ago without problems and decided to test it again after hearing another user with this issue and was able to duplicate it.