Hello - wondering how to best resume my application when it looses Context3D ?

On mobile this happens when device is rotated or goes to sleep (tested on Android), and deskop when screensaver kicks in or cntrl-alt-del.

I would love a few pointers on this one, I am currently re-creating everything to get it work again, but not sure that is the best solution. Any pointers would be most welcome…

Best regards, and big thanks to the lovely community / away core team for everything so far…

Karim Beyrouti

When the Context3D is lost you cannot display anything anymore in it and a new Context3D must be requested in order to display anything. So recreating a View3D is the way to go but I would still call dispose() on the old one before discarding it to make sure Away3D release the Stage3D correctly.

Yep, that’s what I was doing - however the problem was loosing all states in my 3D… However - I just found out Context3D loss, has been addressed in the ParticlesFeature branch, which now re-uploads everything…. So all working fine now, which is great…

This has also been fixed in the release branch of the away3d-core-fp11 GitHub repository.

Hi,
I have the same problem,
can you please post sample how to solve it ?

THANKS

Use the latest version of Away3D.

Hi,
I use https://github.com/away3d/away3d-core-fp11 this one, but when I had blocked phone, and unblocked phone, the screen is black.

edit:
screen = away3D view

With Away3D 4.0.9 Gold it is the same problem

That seems weird. People have reported that the issue was solved. Can you please create a minimal use case that reproduces (a single class, preferably) and submit a bug report at http://github.com/away3d/away3d-core-fp11/issues?

Hi,
it works in windows when I press CTRL ALT DEL. It not work only if I have started this application on mobile and then I press hold button and ublock phone - screen is still black (lost content3D). I will try other devices (I have HTC 3D EVO).

It would be great if you could gather everything you know about it issue (when it happens, on what devices et c) and file a bug report at the URL mentioned above. Thanks!