Hi everyone, thank you for your replies - a lot of good stuff! I've been a bit sick so I haven't been here recently.
I have added a basic COLLADA loader to PAL, based on John Ratcliffs excellent light weight loader for PhysX:
im using IE7
Unfortunately I dont have IE7, and don't plan on installing it, so I'll put up a notice about that. Thanks for the report.
- Can you add the version and/or download date for each physics engine?
I'm working on adding this so it will automatically include it when the benchmark is run. This should make it easier to keep things up to date.
- Document the non-default settings used in the benchmark on the webpage. For example, did you use quickstep or worldstep in ODE?
I think this would be too difficult (I used worldstep), but I will add a note about this.
- Download information how you obtained each engine.
This is available on the engines list page.
- Adding convex mesh/hull collision tests. Perhaps other collision shapes, like heightfield, cylinders, capsules, compounds.
Great suggestion, I'll add this.
The metric I would report would be computational efficiency, do you have any additional ideas?
- ragdolls tests, just using unlimited point to point constraints, sliding on a sloped 3d triangle mesh
A nice idea, but I'm not sure what metric to report here? Do you think finding the distance between links ALA the bridge link test would be sensible? Would this test reveal any more information about the constraints system than the bridge test does?
- providing COLLADA files for each test.
Comming soon! I've included the PAL COLLADA loader now.
- TrueAxis cannot be disabled. Perhaps it is better to choose which engine to include, instead of exclused (it is a bit confusing).
Thats me being lazy with the python script
I'll see if I can't change that then
* Collision benchmark: it seems that only 3 engines are represented in the graphs?
Thats because the other engines do not pass this test! (You will see what happens if you compile and run the binary version of the test)
* For the Materials benchmark: Is it possible to plot the 'physically correct' analytical path as well?
Not easily (AFAIK - feel free to correct me!), but the ideal bounce hight can be calculated, there will be more info on this soon..
* Suggestion for another graph: stacking benchmark, but plot the error (e.g. in terms of total penetration etc...)
This would require a bit of collision detection code, does anyone have a simple convex-object/point test? (otherwise I'll write my own, not that hard).
But I will see if I can add this.
* Maybe use some plot ticks as well, so the different lines are better distinguishable?
The tests produce CVS files, so you can replot them in another package if you like. The online version is just to give you a general idea of it all.
not many support stiff motors/constraints
I hope to add a motor benchmark test soon too.
So "feature completeness" should be somehow considered.
A table of features will also be added soon..