-
Notifications
You must be signed in to change notification settings - Fork 112
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
OriginMode strange behavior on Quest #883
Comments
Have you updated the data layout of your SKSettings struct? There were a few fields removed. The recent commits for v0.4 do introduce a good number of breaking changes, so if you're trying to keep the rust bindings up with /develop, make sure you're watching the change-log really carefully! See here: |
Of course and the proof could be that the behavior change when I change the AppMode value. I checked all the commits to apply the changes. But if you don't have this problem, I have to triple check :o). |
I guess also, you probably mean origin mode, not app mode? AppMode.XR should be the only option that makes much sense on Quest. |
of course yes. |
I do see some strange behavior with origin mode. Local is quite solid. Stage seem to be behaving pretty fine, a little odd in stationary boundary mode, but still reasonable. Floor is giving me some unexpected results, which is a little odd since Quest directly supports that extension. |
I believe that you fixed the problem of the camera waltzing rather than rotating. And I wonder if that might not be the origin of the problem. For example, every time the virtual keyboard opens, it opens at my belly button. EDIT : I tested again and the watz problem occurs with Stage but not with Floor ... So maybe you didn't fix it ... I guess you should implement my little IStepper FlyOver to see the problem. it was odd before 0.40 and it's more odd now. https://github.com/mvvvv/StereoKit-rust/blob/master/src/tools/fly_over.rs |
Description
Hi! I updated my Rust binding with the commits published yesterday. The fishing rod works really well on the Quest 2, except for the buttons that crackle when the trigger is activated (a problem that toggles and radio buttons don’t have, as they only trigger on a state change).
The more troublesome issue relates to the SKSettings mode (AppMode) parameter: On the Quest 2, I have the following mappings:
Local corresponds to Floor.
Floor corresponds to Local.
Stage surprisingly has the power to swap left and right for my movement tool using the sticks. 🎮
Platform / Environment
rust binding. Linux 23.10 gnome wayland + Quest 2
The text was updated successfully, but these errors were encountered: