Closed furrycoding closed 2 weeks ago
The only way to get Pico 4 controllers working with that version of Beat Saber is by setting SteamVR input compatibility mode to Quest 2 controllers. That seemingly changes the name that Unity.XR.InputDevices returns to "Oculus Quest2".
Unity.XR.InputDevices
BeatLeader.Core.Managers.ReplayEnhancer.TrackingDeviceEnhancer uses that API in ProcessOpenVRDevices to set the HMD and controller name info. However ProcessOpenVRSettings that is called later uses another method to obtain the headset type - via SteamVR setting "LastKnown.HMDManufacturer". That method would have detected the HMD correctly, however, it doesn't end up getting used as the ReplayInfo.hmd field is already filled in.
BeatLeader.Core.Managers.ReplayEnhancer.TrackingDeviceEnhancer
ProcessOpenVRDevices
ProcessOpenVRSettings
ReplayInfo.hmd
One solution would be to add a special case into ProcessOpenVRSettings for Pico, but I'm not sure it is the best way
Sorry, but 1.29.1 is not supported anymore.
The only way to get Pico 4 controllers working with that version of Beat Saber is by setting SteamVR input compatibility mode to Quest 2 controllers. That seemingly changes the name that
Unity.XR.InputDevices
returns to "Oculus Quest2".BeatLeader.Core.Managers.ReplayEnhancer.TrackingDeviceEnhancer
uses that API inProcessOpenVRDevices
to set the HMD and controller name info. HoweverProcessOpenVRSettings
that is called later uses another method to obtain the headset type - via SteamVR setting "LastKnown.HMDManufacturer". That method would have detected the HMD correctly, however, it doesn't end up getting used as theReplayInfo.hmd
field is already filled in.One solution would be to add a special case into
ProcessOpenVRSettings
for Pico, but I'm not sure it is the best way