Druha
12-11-2009 20:12:39
I am using this commit: http://github.com/betajaen/nxogre/commi ... 50b4a4afb3
I am writing a server app for my game. In fact I have to run physics on it too.
First versions was not using physics, but when i turn physic simultaion on, memory consumption raised from approx 2mb to (!) 152mb.
After some expiriments with debugger i traced, that memory got allocated somewhere inside World::createWorld().
I've tried to run some demos from PhysX SDK - same thing happened to them, above 160mb of memory each.
Looks like this is not NxOgre related problem, but I hope someone here can suggest me how to decrease amount of used memory.
And finaly, problem may be caused by my own PhysX installation - please, look whether someone has the same behaviour of PhysX.
P.S. In OllyDbg's memory map I see two 80mb memory blocks, that got allocated after NxOgre/PhysX initialisation
I am writing a server app for my game. In fact I have to run physics on it too.
First versions was not using physics, but when i turn physic simultaion on, memory consumption raised from approx 2mb to (!) 152mb.
After some expiriments with debugger i traced, that memory got allocated somewhere inside World::createWorld().
I've tried to run some demos from PhysX SDK - same thing happened to them, above 160mb of memory each.
Looks like this is not NxOgre related problem, but I hope someone here can suggest me how to decrease amount of used memory.
And finaly, problem may be caused by my own PhysX installation - please, look whether someone has the same behaviour of PhysX.
P.S. In OllyDbg's memory map I see two 80mb memory blocks, that got allocated after NxOgre/PhysX initialisation