You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The approach used in #24 to solve #20 did not take into account OVR Space Calibrator. Since we're calculating from raw space, we end up getting the offsets prior to calibration, instead of after calibration.
The text was updated successfully, but these errors were encountered:
I think there's two approaches we could take here:
Only use static standing space for the HMD height above ground level, and send it as a separate field.
This simplifies everything else that interacts with steamvr, since they can just care about standing space.
I think this is the route I'm inclined to take, given the issues I had applying the offset in the overlay.
Try to calculate an offset from 'current' standing space to 'static' standing space, and apply that to standing space instead of coming from raw space.
we'd essentially be querying what the current playspace offset is every frame, per item that needs to interact with steamvr.
blinks wait, did we ever work okay with space calibrator? we switched from using raw space to using a modified raw space. why would that break space calibrator?
EDIT: it was reported as an issue with controllers -- i.e. feeder app's domain, and not that it worked previously. Updating title.
kitlith
changed the title
[Regression] SlimeVR no longer works well with OVR Space Calibrator
SlimeVR Feeder doesn't work well with OVR Space Calibrator
Jun 26, 2023
I am worried that we'll still have issues if I work around it in feeder app, but someone offsets the headset to match the controllers instead of the controllers to match the headset.
The approach used in #24 to solve #20 did not take into account OVR Space Calibrator. Since we're calculating from raw space, we end up getting the offsets prior to calibration, instead of after calibration.
The text was updated successfully, but these errors were encountered: