09-12-2024 03:28 PM
I am submitting a fully MR only app to Meta Quest store early access and I am getting rejection due to the app failing VRC.Quest.Functional.9 : The user's forward orientation is not reset when the Oculus Home button is long-pressed.
I have selected the tracking origin to be Floor and enable Allowed Recenter on OVR Manager, yet I am still getting this rejection.
Also, I feel that this should be an requirement for a fully MR app since all the objects in the scene are tracked to user's space and should be change or be recentered.
Anyone know what do I need to do to fulfil the requirement?
For more context, I am using MRUK to detect user's space.
Solved! Go to Solution.
09-23-2024 02:33 PM
[SOLVED]
I am using Meta XR SDK and Unity 2022.3.26f1. I found out the main cause of the rejection is because i enabled World Lock feature under MRUK. It is weird that this feature is causing this issue because it is suppose to anchor your objects in the real world environment while creating a MR experience.
Anyway, I disabled it and also manaully subscribed to the reset event using the code below to ensure user's forward direction is reset when user long pressed on Meta Home button.
My app is finally approved and disabling the world locking feature does not seems to affect anything for my MR app.
https://www.meta.com/en-gb/experiences/take-a-leap/8154603794652880/
09-23-2024 02:33 PM
[SOLVED]
I am using Meta XR SDK and Unity 2022.3.26f1. I found out the main cause of the rejection is because i enabled World Lock feature under MRUK. It is weird that this feature is causing this issue because it is suppose to anchor your objects in the real world environment while creating a MR experience.
Anyway, I disabled it and also manaully subscribed to the reset event using the code below to ensure user's forward direction is reset when user long pressed on Meta Home button.
My app is finally approved and disabling the world locking feature does not seems to affect anything for my MR app.
https://www.meta.com/en-gb/experiences/take-a-leap/8154603794652880/
11-01-2024 09:47 AM - edited 11-01-2024 09:49 AM
I too have this problem and keep getting VRC 9 failed 😞
But the above method is not a solution for me, If I disable world lock it does mess up my whole game.
Perhaps this is because I'm using anchor prefab spawners to place screens and pictures over real world screens and pictures.
On world lock being disabled the pictures/screens can/will be rotated out of position with a recentre? I've tried 3 times to submit the game, do they actually Read the comments? or is it automated? As a reply has not been given, or any kind of acknowledgement that someone has read my comment when submitting?
Is a bit poor that we can not select MR when submitting as recentring is not needed.
11-01-2024 12:29 PM
I believe this is a bug in the review process, which I am not sure how we can report it. I don't believe that commenting on the submission helps as I did not get any reply back then.
The world lock feature is new so I suppose not a lot of app are using it yet.
11-01-2024 12:35 PM
thanks for letting me know I've been on to Dev support so will relay this being a possible bug, I'm just looking at the discovery app files off github as they have World lock working, when you hold reset/menu on their app, it sort off moves but then all item are put back to normal anchored positions in a frame or two.
If I find away around it I will post back.
11-01-2024 03:17 PM
Yes please, it's a matter of time I will need to use world lock feature in my next app.
Hopefully Meta will fix this problem.