Forum Discussion
GlassBall
5 years agoExplorer
Oculus Integration 31.2 Passthrough works, broken when i upgrade to v33?
Hi! My program, Custom Home Mapper, uses pass-through features. I released an update when v31.2 was available and integrated AR features into a dozen minigames, really opened up the usability and f...
Hyper_active
5 years agoStart Partner
Hey i've also fully integrated passthrough into my game and it's been there since v31 runs fine on v33. The hit list is still the same:
- OpenXR Backend
- IL2CPP
- Arm64
- Enable passthrough on OVRManager
- Allow passthrough in Manifest
- Allow experimental in Manifest
Though of it was working before for you then you were doing it right. And the same apk build worked on v31 and doesn't work on v33 ?
Are you only talking about firmware version or also SDK versions updates?
So your game SDK v31 worked, and now updated to v33 doesn't work?
- GlassBall5 years agoExplorer
Thanks for response! Sorry for confusion about integration vs public firmware release versions.
Yes, passthrough functions fine in Oculus unity integration SDK v31.2, I updated the game a few weeks back and users report having a good time. This is actually a collection of 12 games/apps, so it has a pretty robust implementation in a bunch of styles/modes. Public released build worked on my quest1 up until q1 hit firmware v34. Currently still works on my quest2, because i've stopped it from updating to v34 (is on firmware v33)
My assumption was that i'm going to have to update the integration package SDK to v34 when it comes out, otherwise my users will not be able to continue to use current AR/passthrough features (its deprecated, and v34 wont allow it). Am i correct that, even if i updated to integration package v33, that it still wont work on my firmware v34 quest? Does your app (on integration sdk v33) currently work on a firmware v34 quest?Regardless, yes i've checked the right boxes, but perhaps the manifest is the issue? I never explicitly set anything, just allowed oculus to generate a store compatible one. Normally when i release one of my other games to applab, i export to android studio, edit the manifest directly, and then rebuild it, but I don't do that for the mapper since it isn't for applab. Is there a specific line i should be adding? surely, if i regenerate the manifest, it should add the appropriate lines to my unity built manifest, no?
Quick Links
- Horizon Developer Support
- Quest User Forums
- Troubleshooting Forum for problems with a game or app
- Quest Support for problems with your device
Other Meta Support
Related Content
- 12 months ago
- 2 months ago