Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HoloJSWebViewer doesn't show an app / image when lens is waking up from sleep mode #146

Open
ghost opened this issue Feb 27, 2018 · 4 comments

Comments

@ghost
Copy link

ghost commented Feb 27, 2018

Hi,

I try to develop an web app and started to test the web samples in the edge browser on HoloLens. When the lens is turned off and I start it, everything works fine. But when I put the lens into sleep mode and turn it on again I got a problem: When I click a web-ar link, the edge browser window disappears but the gaze point stays and I see nothing but this point. I checked the processes and the web viewer runs in background but doesn't show anything to me.
The only way to get an image again is to shut down the Lens and turn it on so the web viewer app is closed again.

How can I fix this problem?

Thanks :)

@Almost-Done
Copy link
Member

Thanks for reporting this.

The native host app (the viewer app in this case) must handle graphics device lost and tracking lost cases, which it does not currently. When the HoloLens comes out of sleep, the native side should either reload the script or send a "device lost" notification so the script can re-initialize its rendering.

I'll work on a solution.

@Almost-Done
Copy link
Member

Can you please try the develop/device-lost branch and see if the problem persists? I wired webglcontextlost and webglcontextrestored events from the native host, so ThreeJS should be able to re-create its resources on device lost.

@ghost
Copy link
Author

ghost commented Jun 1, 2018

I'll try it out next week. Thank you :)

@ghost
Copy link
Author

ghost commented Jun 12, 2018

Hi. So I hadn't had time to look it up last week. I tried the master branch today because I couldn't find the branch develop/devise-lost. The master branch still doesn't solve the problem. Sorry for the late response.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant