My app already supports Go & Gear VR. Moving to Go only. What should users expect?
I'm not clear on what my Gear VR users should expect if I change my existing app to support only Go moving forward. We would do this because of upgrading the SDK suite / integration from version 1.41 or lower to 1.42 or higher within the Unity project. As Oculus no longer officially supports the platform, we need to follow suit at some point or be stuck with an old SDK for too long. This is okay, given our small population of Gear users. However, we'd like to let them know in advance what will happen, and I really don't know for certain from the information seen thus far. The official announcement only clarified perhaps the most obvious points (I can't post links yet, but it was November 7, 2019 "Gear VR App Development no Longer Supported From Oculus SDK Suite 1.42 and Future Versions"). The current build on our STORE channel is Gear compatible. At some point we would update with one produced with a newer SDK, which will not be Gear compatible (Go only). Has anyone else done this already? If so, what did your Gear users experience? If their last compatible build remained installed, could it still be restored if it got uninstalled at some point later? We are aware that a newer incompatible build is not supposed to appear in the Gear store. If another build channel were created to have all the Gear users as members, would it change the situation at all? Anything else noteworthy? We are looking for an official response as well, but it's good to have the answer clarified among the community.
Debugging of Virtual Reality application in Unity .. How to do?
I am developing a virtual reality application in unity. Every time I want to test my application I build and run the application on android note 5, Please tell me the way to debug the code? How to debug the VR application in unity and Visual studio?
some question for Blend Render Compositor layer( OvrOverlay ) with Opaque & Transparent model
First of all, Compositor layer contain two type, called them Overlay and Underlay. i have readed the post https://forums.oculusvr.com/developer/discussion/comment/536880#Comment_536880 which talk about how the 3d model correctly show or hide while using Compositor layer. i want ask a extra qustion to confirm my assumption for using Compositor layer right. Is Oculus Gear vr home app using "Underlay" to Render Ui Panel ? oculus staff said "we do use overlay in Gear VR home, and the fact is that everything is made by overlay in gear VR home", while gear controller & its white laser can display in front of ui panel shown below. if gear home using "Overlay" not "Underlay" to render ui panel into cylinder, i do not figure out a valid method to render controller & its laser in front of ui panel, because of "Overlay" blend with eye buffer using Overlay Rt's alpha value. while "Underlay" blend using eye buffer's alpha value. using Overlay Rt's alpha value for blend and "Overlay" render in front of all things, make the "Overlay" layer can not leak a hole to show the controller. consider what i assume is right, there must be "Underlay". so gear vr home need "poke a hole" for eye buffer while shader the hole's alpha = 0, which ui panel can blend into eye buffer correctly. Finally, the render action list for using Compositor layer combine with controller & room shown below: 1. render cinema and some opaque things except gear controller 2. render some transparent things except gear controller laser 3. in simple, clear total eye buffer alpha into 0 4. render controller & laser, write them alpha to corresponding location 4. Underlay ui panel blend with eye buffer, leave eye buffer alpha = 1 not blend so, Is it right render order for gear vr home ? but the method above can not handle the situation while gear controller behind the UI panel render using "Underlay" because their alpha already = 1. Or there contian other method to use"Overlay" render ui and make contrller render right? thanks for your time
