Merge remote-tracking branch 'origin/main' into fix/input-action-origins-binding-info#320
Merge remote-tracking branch 'origin/main' into fix/input-action-origins-binding-info#320nokichan wants to merge 2 commits intoSupreeeme:mainfrom
Conversation
…TrackedDeviceInfo
8db1695 to
b5aabb1
Compare
b5aabb1 to
dd87c9c
Compare
|
I've tried to test, but seems like NMS is not launching in VR mode again :( |
Not sure if this could help, but in the General Options of No Man's Sky on Steam I've added these options: And to tackle this VR problem I think that is related with the Proton version. I've changed the Proton version in the compatibility tab to the Proton-CachyOS one |
Thanks to reply. My nms broke after I switch to CachyOS. Some time I go it was fixed with nightly xrizer and experimental branch, but seems like some update broke it again. My current launch options are following. PRESSURE_VESSEL_IMPORT_OPENXR_1_RUNTIMES=1 PRESSURE_VESSEL_FILESYSTEMS_RW=/var/lib/flatpak/app/io.github.wivrn.wivrn VR_OVERRIDE=$HOME/Games/xrizer_fixed/target/release PROTON_ENABLE_NVAPI=1 DXVK_ASYNC=1 %command% -HmdEnable 1 |
As you are using flatpak, honestly no idea how it handles flatpak with a compiled version outside flatpak of this xrizer module, I have steam, xrizer and Wivrn installed "directly", no flatpak around. Did you think about permissions in the involved flatpak packages that are you using to try to run the game? |
|
Alright , today NMS randomly started, I guess another experimental NMS update fixed it, however I still see For the sake of experiment I replaced the flatpak WinVRn version with the one from Arch repo , but it didn't change anything. I am pretty sure it uses build from your PR , as I don't have any other instances of xrizer installed (wivrn even issued a warning about it) |
This PR solves the #162 issue