[Solved][Git]Possible VisualDebugger bug

G'day my fellow NxOgre users.

I've noticed a small issue with the Visual Debugger. It seems to be very picky about when to draw everything. Also it seems that when it doesn't draw everything properly, there are no physics simulations.

A few pictures to make life easier.

When it's working.


When it's not.

As far as I know, these seem to be random times.

Also it seems that when it doesn't draw everything properly, there are no physics simulations.

Eh? When the Visual Debugger doesn't draw part of that triangle mesh, the collision doesn't work? Are you sure?

It must be a PhysX bug - it must be.

Im not sure, but in the first screenshot, the cube had fallen to the ground before I took the screenshot, but as you can see, I had the time to step back and take a screenshot and the cube still hadn't fallen, so its not a case of the collisions not occuring, it's more a case of the collisions not even starting.

Could of the TriangleGeometry have moved somehow? I can't see how PhysX would forget that the NxTriangleMesh/NxActor was there.

The only moving I've made the Geometry do is when I create the Scene Geometry.
// Create the SceneGeometry

// Structure
pPhysScene->createSceneGeometry( pTriangleEntranceStatic, NxOgre::Matrix44( NxOgre::Vec3( 700,0.01f,700 )));
pPhysScene->createSceneGeometry( pTriangleWalls, NxOgre::Matrix44( NxOgre::Vec3( 700,0.01f,700 )));
pPhysScene->createSceneGeometry( pTriangleChangeRooms, NxOgre::Matrix44( NxOgre::Vec3( 700,0.01f,700 )));

//Shopping Aisles
pPhysScene->createSceneGeometry( pTriangleFrontRight, NxOgre::Matrix44( NxOgre::Vec3( 700,0.01f,700 )));
pPhysScene->createSceneGeometry( pTriangleBackRight, NxOgre::Matrix44( NxOgre::Vec3( 700,0.01f,700 )));
pPhysScene->createSceneGeometry( pTriangleFrontLeft, NxOgre::Matrix44( NxOgre::Vec3( 700,0.01f,700 )));
pPhysScene->createSceneGeometry( pTriangleBackLeft, NxOgre::Matrix44( NxOgre::Vec3( 700,0.01f,700 )));

// Other
pPhysScene->createSceneGeometry( pTriangleCheckouts, NxOgre::Matrix44( NxOgre::Vec3( 700,0.01f,700 )));
pPhysScene->createSceneGeometry( pTriangleEntranceScanners, NxOgre::Matrix44( NxOgre::Vec3( 700,0.01f,700 )));
pPhysScene->createSceneGeometry( pTriangleDisplays, NxOgre::Matrix44( NxOgre::Vec3( 700,0.01f,700 )));

Could this be the case?

Nope that seems to be fine - Although technically you can put all of those TriangleGeometries into one StaticGeometry.

If you can replicate the error repeatedly, I'll see if I can duplicate it too. See if I can trace it, but at the moment. I can't think what is causing it do that.

Well, the issue is solved. It seems that I committed one of the greatest programming sins one could make, I forgot to delete my "new" singletons. The problem was memory leaks, and a tonne of them, so I've wrestled a 238kb file down to an 8kb file. I probably would have never figured it out if it weren't for one of my fellow developers lol.

Thanks for the help, and putting up with my newbishness lol.

Silly Monkey!