fiesch
27-10-2005 02:22:21
I have the following "flow" in my prog for testing right now:
start->"MainMenueMode"
This creates a camera, a viewport and a cegui sheet, on exit it calls
then its "MainMenueMode"-->"PlayMode"
which, again, creates a camera and a viewport.
This i where the app crashes, in
void PagingLandScapeOptions::calculateCFactor()
Line 672
because of an invalid Viewport Pointer "v"
i couldn't watch the camera pointer the whole app because this strangely enough only occurs if i don't start the app from vc but from the explorer..
but my guess is that the options kept the camera pointer to the first camera and didn't update to the second.
the cam used for updating in the sm that run was at 0x0f1607c0, the one in the options was at 0x0f160830 (similar but quite clearly not the same object)
start->"MainMenueMode"
This creates a camera, a viewport and a cegui sheet, on exit it calls
mRoot->getAutoCreatedWindow()->removeAllViewports();
mSceneMgr->destroyAllCameras();
mSceneMgr->getRootSceneNode()->removeAllChildren();
then its "MainMenueMode"-->"PlayMode"
which, again, creates a camera and a viewport.
This i where the app crashes, in
void PagingLandScapeOptions::calculateCFactor()
Line 672
because of an invalid Viewport Pointer "v"
i couldn't watch the camera pointer the whole app because this strangely enough only occurs if i don't start the app from vc but from the explorer..
but my guess is that the options kept the camera pointer to the first camera and didn't update to the second.
the cam used for updating in the sm that run was at 0x0f1607c0, the one in the options was at 0x0f160830 (similar but quite clearly not the same object)