Tutorials do not work

xilvium

22-05-2009 15:37:17

Hello

I was doing the NxOgre tutorials by spacegaier but it does not seem to work?
The source compiles but completely freezes when run.
I am using this tutorial > http://www.ogre3d.org/wiki/index.php/BloodyMess_Tutorial_2
The program freezes when i add this command : mWorld = NxOgre::World::createWorld();
Is there any workaround for this?
I am using the latest NxOgre ( bleedingmess )
Thanks for reading.

-Xilvium

spacegaier

22-05-2009 15:48:56

Does it freeze, or does it actually crash (so is there any error message)?

PS: It's actually BloodyMess (=version 1.5.X) and Bleeding (= version 1.0.X) ;)

xilvium

22-05-2009 17:43:23

EDIT: Sorry guys i fixed the problem already. It appeared that my video driver worked but when used PhysX it crashed so i had to install the default driver (i had costum drivers :oops: )

neoranga

25-06-2009 10:35:25

Hi guys,

Mine is freezing here too. Bloody 1.5.4.

Nvidia's physx's demos are working so i dont think this is the Graphics card driver, it juste freeze at "mWorld = NxOgre::World::createWorld();"


// Physx -----------------------------------------------------------------
LogManager::getSingleton().logMessage(LML_NORMAL, "Before World");
mWorld = NxOgre::World::createWorld();
LogManager::getSingleton().logMessage(LML_NORMAL, "AfterWorld");

NxOgre::SceneDescription sceneDesc;
sceneDesc.mGravity = NxOgre::Real3(0, -9.8f, 0);
sceneDesc.mName = "BloodyMessTutorial2";

mScene = mWorld->createScene(sceneDesc);
mScene->getMaterial(0)->setStaticFriction(0.5);
mScene->getMaterial(0)->setDynamicFriction(0.5);
mScene->getMaterial(0)->setRestitution(0.1);
mRenderSystem = new OGRE3DRenderSystem(mScene);

mTimeController = NxOgre::TimeController::getSingleton();


// Physx -----------------------------------------------------------------


I am really tired of this, trying since many days, re installing all but -______-.

betajaen

25-06-2009 10:41:40

createWorld is a big function, with many things that could go wrong.

There is a may be message printed to the console. See if you can find it and show it here or better still run a debug trace and find the offending line.