Hey Team - i posted earlier about gpu memory not being cleared - after testing with changing scenes, I now see that as long as i dispose the view the gpu keeps memory untill the next texture is uploaded then it dumps left overs….
So… now im using stage3DManager and stage3DProxy to handle both away3D and its starling UI - and the core gameplay wich is pure starling
my problem is going from Away3D+IU(starling) -> to pure starling via the same stage3Dproxy” (as a reference to the current Stage3D layer) is giving me a red error bar caused by Context3D saying:
“Context3D error: Error #3685: Could not create renderer.”
im cleaing up in this order:
first the starling UI ontop of 3d
mStarling.stop()
StarlingScene(mStarling.root).destroyAll() //kill all objects
mStarling.dispose()
System.gc()
then i clear the away3d view:
stage3DProxy.removeEventListener(Event.ENTER_FRAME, onEnterFrame);
_view.dispose()
System.gc()
still no errors…
then i start the new Starling Scene:
stage3DProxy.context3D.dispose()
mStarling = new Starling(MainStarlingScene, stage, stage3DProxy.viewPort, stage3DProxy.stage3D)
mStarling.start()
and boom the new starling scene is going fine - with the red error on top propably from the old away instance -
- so what do i do to make the shift correctly
