Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hellblade: Senua's Sacrifice VR Edition crash when PROTON_ENABLE_NVAPI=1 #113

Closed
gareth-anthony-hulse opened this issue Mar 21, 2023 · 3 comments · Fixed by #114
Closed

Comments

@gareth-anthony-hulse
Copy link

Was recommended to report here. Originally I brought up the issue at ValveSoftware/Proton#4370.

Error message as soon as game starts:
Screenshot_20230318_113223

Log output with PROTON_LOG=1 %command% as launch option: steam-747350.log

When launch option is set to PROTON_ENABLE_NVAPI=0 %command% the game works without issue. I have PROTON_ENABLE_NVAPI=1 in /etc/environment just to avoid adding it to every game's launch option.

Specs: https://linux-hardware.org/?probe=d32441b2c3
SteamVR version: 1.25.6

@jp7677 jp7677 linked a pull request Mar 21, 2023 that will close this issue
@jp7677
Copy link
Owner

jp7677 commented Mar 21, 2023

Thanks for the report, could you try this PR #114 ? It should let the VR edition start. I haven't my headset currently attached, so I could not enter the game and verify that it actually works.

You can grab a build from GitHub actions, https://github.com/jp7677/dxvk-nvapi/actions/runs/4482562149

@gareth-anthony-hulse
Copy link
Author

gareth-anthony-hulse commented Mar 22, 2023

I used the build from GitHub actions and it fixed the issue.

@jp7677
Copy link
Owner

jp7677 commented Mar 22, 2023

Nice, thanks for the confirmation. I’ll complete this PR and land it on master, probably on Friday.

Edit: I was slightly faster, merged and thanks again for the report.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants