http://forum.starling-framework.org/topic/handling-lost-context-on-mobile The Starling Framework Community en-US Thu, 23 May 2013 03:19:45 +0000 http://bbpress.org/?v=1.0.3 q http://forum.starling-framework.org/search.php http://forum.starling-framework.org/topic/handling-lost-context-on-mobile#post-9737 Mon, 06 Aug 2012 10:39:08 +0000 chixplusplus 9737@http://forum.starling-framework.org/ <p>@sHTiF, Sorry if my question is confusing (i think i need a copywriter :lol:).What I'm trying to ask is a method where i don't have to deal with lost context everytime the game/app loses it's focus (lock screen), like a normal display list. handling lost context on Samsung Galaxy S took around 7-8 secs, Which means, the user will have to deal with a "Blank Screen" for 8 sec everytime they unlock their screen while playing.</p> <p>I think doing it manually is my only option. Kinda' frustrating though, handling lost context is not a problem with iOS devices. I think Adobe needs to look at this. Thanks for the suggestions &lt;img src=&quot;http://forum.starling-framework.org/my-plugins/bb-smilies/default/icon_smile.gif&quot; title=&quot;:)&quot; class=&quot;bb_smilies&quot; /&gt; </p> <p>@tsangwailam hmmm, I'll try this one out! never thought of that. Thanks! </p> http://forum.starling-framework.org/topic/handling-lost-context-on-mobile#post-9735 Mon, 06 Aug 2012 10:24:02 +0000 sHTiF 9735@http://forum.starling-framework.org/ <p>I would suspect in his case the crashing is due to memory overload as he didn't mention that it crashes when the app goes to background, but who knows. </p> http://forum.starling-framework.org/topic/handling-lost-context-on-mobile#post-9734 Mon, 06 Aug 2012 10:15:12 +0000 tsangwailam 9734@http://forum.starling-framework.org/ <p>&gt;&gt;sHTiF</p> <p>Yes, This method only apply when using Starling.handleLostContext = true. I have this problem before. But after stop the rendering in deactivate and start rendering again when activate, the apps have no crashing. </p> http://forum.starling-framework.org/topic/handling-lost-context-on-mobile#post-9725 Mon, 06 Aug 2012 02:25:53 +0000 sHTiF 9725@http://forum.starling-framework.org/ <p>Activate/deactivate will not help you to avoid device loss, so if you set handleLostContext to false you will still need to handle it yourself. </p> http://forum.starling-framework.org/topic/handling-lost-context-on-mobile#post-9724 Mon, 06 Aug 2012 02:19:54 +0000 tsangwailam 9724@http://forum.starling-framework.org/ <p>You can try adding a activate/deactivate listener for the application. Then stoping the starling render when deactivate. And resume when it activate again. It should help a lot for crashing. </p> http://forum.starling-framework.org/topic/handling-lost-context-on-mobile#post-9714 Sun, 05 Aug 2012 19:23:03 +0000 sHTiF 9714@http://forum.starling-framework.org/ <p>I don't understand your question if starling doesn't dispose it then it will remain in memory therefore will lead to problems on low end devices. </p> <p>There are two options in this case.</p> <p>First option is to manage your assets so it doesn't take that much memory, load them only when needed, make lower resolution assets etc.</p> <p>Second option is to disable handling of the lost context and do it yourself reseting and recreating starling state/textures. </p> http://forum.starling-framework.org/topic/handling-lost-context-on-mobile#post-9708 Sun, 05 Aug 2012 17:33:18 +0000 chixplusplus 9708@http://forum.starling-framework.org/ <p>hi guys,</p> <p>using Starling.handleLostContext = true on mobile sometimes leads the app to crash especially on low-end devices since it eats a lot of memory. Is there a way or workaround where Starling/Stage3D will not dispose anything and retain it's state?</p> <p>Thanks! </p>