Platform Variable not working properly in Oculus Quest 2 - Oculus for Business
April 8, 2021 12:00 AM
I designed a training with a fixed navigation map icon for the web and a non-fixed navigation map icon for VR. I set them both to not be visible, but loading each scene there is a platform check that shows the correct icon (for web and VR). It works great on our Oculus Quest 1, but we just got an Oculus for Business (OFB) which is a Quest 2, and the icon is not showing up. I'm not sure if I'm missing something or if this is an issue with the Quest 2 or the OFB.
If anyone has seen anything similar or knows any information about a possible issue with the platform variable in CenarioVR, please let me know.
For the time being, my workaround is to make the VR map icon visible by default and then hide it if the platform is web. This does appear to work, but I would prefer not to do that because the icon is briefly visible before disappearing when you look at it through the web. It looks like a glitch.
Thank you
Matt
Solution
So that's the issue, the current version is 2.5, and I just checked that link, it is at version 2.5. Maybe try and install it again? Is something perhaps caching for you?
Discussion (4)
Do you have the latest version of the CVR App on the OFB headset? One thing about OFB is that it does not auto update the App like it does on the store. You can always pick up the most recent version at:
https://public.cenariovr.com/builds/Quest/CenarioVR.apk
The platform variable came out in the most recent release of the App.
Good question. Yes I do have the latest releases. I installed everything fresh yesterday. The address you listed is what I used to install the CenarioVR app for OFB, it is version 2.47. I double checked the Oculus Quest 2, and I am running the latest update as well.
So that's the issue, the current version is 2.5, and I just checked that link, it is at version 2.5. Maybe try and install it again? Is something perhaps caching for you?
Thank you John, that must be what it was. I don't know how it would have been a caching issue as it was a brand new device, but I deleted the connection to the app from Workplace and re-added it, and that seems to have fixed the issue.
Thanks again!
Matt