HexiDave
04-07-2006 19:23:10
Has there been a change in the latest CVS and SDK that causes a problem using PagingLandScapePageManager::getPage()? It seems whenever I use it now, the PageManager goes out of scope or something - the terrain still loads fine, just when I try to access with something like:
*mSceneMgr is a PagingLandScapeSceneManager*, but I've used it like that for quite a while without this issue.*
It breaks inside getPage() at:
mWidth and mHeight are inaccessible - seems like mPageManager went dead.
The callstack isn't any help at all, just goes straight from where I called it.
Using VS 7.1, tried SDK and latest CVS in Debug mode, will try to recompile in Release, but I really don't see that helping much.
I'm also going to try to create a totally stripped down application with the bare minimum to see if it happens there as well.
Thanks for any help.
mSceneMgr->getPageManager()->getPage(5,5);
*mSceneMgr is a PagingLandScapeSceneManager*, but I've used it like that for quite a while without this issue.*
It breaks inside getPage() at:
if (x < mWidth && z < mHeight)
mWidth and mHeight are inaccessible - seems like mPageManager went dead.
The callstack isn't any help at all, just goes straight from where I called it.
Using VS 7.1, tried SDK and latest CVS in Debug mode, will try to recompile in Release, but I really don't see that helping much.
I'm also going to try to create a totally stripped down application with the bare minimum to see if it happens there as well.
Thanks for any help.