Open cabanier opened 2 years ago
Maybe I'm overcomplicating it and I should just fix Oculus browser. Then when we ship, we update the profile...
Yeah, fixing it and keeping the profile name makes more sense to me since afaik the only headsets that support it are those two
On Fri, 11 Mar 2022, 17:21 Rik Cabanier, @.***> wrote:
Maybe I'm overcomplicating it and I should just fix Oculus browser. Then when we ship, we update the profile...
— Reply to this email directly, view it on GitHub https://github.com/immersive-web/webxr-hand-input/issues/113#issuecomment-1065321596, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABAHSMTFF5OMPFZVEA2O33TU7N6JRANCNFSM5QQGHGRA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message ID: @.***>
@toji I believe you updated the profile in the past. If you have a browser that returns different joints, would you be able to fix it up?
While porting the Oculus browser to OpenXR, we realized that there is a difference between some joints. This manifests itself as a hand that is slightly deformed. Wondering which runtime is correct, I asked @Yonet how hands are rendering on the Hololens. It turns out that they are rendering deformed as well.
Is this the correct forum to solve this?
I've been thinking about how we can fix it and I believe that the cleanest way would be to return a new profile name that points to an updated hand mesh. This mesh would be compatible with future Oculus browser and current Hololens. Hololens would have to update its native code to return this new profile name. Alternatively, I could update the profile name of the current Oculus browser and we copy the existing profile to it.
@toji @Manishearth @thetuvix, what do you think?