HoloLite Posted January 7, 2018 Share Posted January 7, 2018 I have a test app with 2 sessions which I can switch back and forth by clicking a button (thanks to the new UI). The rendering of both sessions works as expected in the browser (non-vr), but not quite when I go into the vr mode. When viewing in vr headset (using wmr odyssey), I am seeing double vision when switching session. I am guessing this has something to do with VRExperienceHelper which is created per scene object (via Scene.CreateDefaultVRExperience()). Probably it's not safe to create more than one instances of the vr helper object ? But then what should you do when you have multiple session objects ? Please advise, thanks. Quote Link to comment Share on other sites More sharing options...
brianzinn Posted January 7, 2018 Share Posted January 7, 2018 Sounds like you are using full screen UI, which does not work in VR mode. If you want GUI in VR you need to attach to a mesh. Quote Link to comment Share on other sites More sharing options...
HoloLite Posted January 7, 2018 Author Share Posted January 7, 2018 Well I remembered Deltakosh mentioned this but I am not using full screen UI though. It won't even render properly in any scene. The first scene with button works just fine but as soon as I switched to the second scene, I am seeing double vision. Quote Link to comment Share on other sites More sharing options...
brianzinn Posted January 7, 2018 Share Posted January 7, 2018 I haven't tried switching scenes in VR - hopefully somebody can chime in, but otherwise make a PG and I'll look. Cheers. Quote Link to comment Share on other sites More sharing options...
brianzinn Posted January 8, 2018 Share Posted January 8, 2018 Transitioning between separate scenes while keeping VR active is currently not possiblehttps://github.com/BabylonJS/Babylon.js/issues/3308 It was assigned recently a 3.2 Milestone. HoloLite 1 Quote Link to comment Share on other sites More sharing options...
HoloLite Posted January 8, 2018 Author Share Posted January 8, 2018 @brianzinn, thanks for the confirming this is a known issue. I guess I can work around it by creating my own virtual session objects which is based on single babylonjs.session object. But look forward to the fix in 3.2.! brianzinn 1 Quote Link to comment Share on other sites More sharing options...
GameMonetize Posted January 8, 2018 Share Posted January 8, 2018 We will introduce containers in 3.2 to handle this problem First drop here: https://github.com/BabylonJS/Babylon.js/pull/3494 Quote Link to comment Share on other sites More sharing options...
HoloLite Posted January 9, 2018 Author Share Posted January 9, 2018 @deltakosh good to hear and thanks for the fix. Btw, when is the eta for 3.2 release ? Quote Link to comment Share on other sites More sharing options...
GameMonetize Posted January 9, 2018 Share Posted January 9, 2018 Yes https://github.com/BabylonJS/Babylon.js/milestones Quote Link to comment Share on other sites More sharing options...
HoloLite Posted January 11, 2018 Author Share Posted January 11, 2018 @deltakosh, is the container included in 3.2-alpha2 ? Quote Link to comment Share on other sites More sharing options...
GameMonetize Posted January 11, 2018 Share Posted January 11, 2018 Nope, but I've just merged it so it is on the preview cdn and will be in next npm update Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.