ODE Middleware

Mehnix · May 29, 2013, 6:06pm

coppertop:

while walking on the roof player sometime’s shifts forward for some distance.

This is probably caused by the room’s trimesh. ODE is quite sensitive in this regard, so the models for trimeshing must be very nice and clean, otherwise you get strange results sometimes. I will update the map asap with a better version.

when lamp is switched off, FPS meter shows ~120, when I switch a lamp on - framerate drops to ~58-60.

That’s related to lighting and shaders. When you look into the main.py file you’ll see that there’s render.setShaderAuto(). If you disable that you’ll get much better performance at the price of much worse looking flashlight effect. There might be a way to deal with that to some extend (you will always get a frame drop), but I haven’t looked into that yet.
On faster graphic cards it obviously shouldn’t be an issue.

player walk’s through the desk sometimes

Oh… That’s interesting. Can you provide more details in what situations this happens? It might be, again, related to trimesh – with ODE it’s much better to use in-engine shapes. I used the trimesh extensively in this sample only because I needed a working environment quickly up and running for codding.

btw, should there be shadows in this sample?

No, this is not supposed to look pretty . There aren’t even static shadows there.

However if you say It’ll happen everytime then I will tell you that that ODE can behave differently between versions and systems.

Boldagiri · May 29, 2013, 8:26pm

Mehnix:

coppertop:

while walking on the roof player sometime’s shifts forward for some distance.

This is probably caused by the room’s trimesh. ODE is quite sensitive in this regard, so the models for trimeshing must be very nice and clean, otherwise you get strange results sometimes. I will update the map asap with a better version.

when lamp is switched off, FPS meter shows ~120, when I switch a lamp on - framerate drops to ~58-60.

That’s related to lighting and shaders. When you look into the main.py file you’ll see that there’s render.setShaderAuto(). If you disable that you’ll get much better performance at the price of much worse looking flashlight effect. There might be a way to deal with that to some extend (you will always get a frame drop), but I haven’t looked into that yet.
On faster graphic cards it obviously shouldn’t be an issue.

player walk’s through the desk sometimes

Oh… That’s interesting. Can you provide more details in what situations this happens? It might be, again, related to trimesh – with ODE it’s much better to use in-engine shapes. I used the trimesh extensively in this sample only because I needed a working environment quickly up and running for codding.

btw, should there be shadows in this sample?

No, this is not supposed to look pretty . There aren’t even static shadows there.

However if you say It’ll happen everytime then I will tell you that that ODE can behave differently between versions and systems.

Can you prove what you said ? ODA can behave differently between versions and systems …I don’t think so

stereoscopic · May 11, 2015, 5:37pm

getting an error.
for childNode in branch.getChildren():
AssertionError: !is_empty() at line 345 of panda/src/pgraph/nodePath.cxx

rdb · May 11, 2015, 6:06pm

You’re calling getChildren() on an empty NodePath.

ramseydonovan · March 5, 2017, 2:21am

I am getting the same error as stereoscopic when running main.py,

We know we are calling .getChildren() on an empty node but we do not know why it is empty. We dont fully understand “-PandaNode” in map.egg, we cant find PandaNode anywhere in the file. Any help would be appreciated.