JOODE: COLLISIONS

[arne]

yeah I kinda thought about that, too, but it's only one class.
And it's actually universable useable - it hasn't got anything JOODE specific

[arne]

Ok FPSCounter finished   

Check it out on the cvs. And please care to read my javadoc - I explain my algorithm there.

*It would be too much to post it here again

what fps-curves do you get?

I've changed SphereCollisionTest and OctTreeSpaceTest to use my new fps measuring method.
All other tests using TestingWorld will also use it, but they will only log and use the current fps for step sizes, but never print statistics.

Ohh and I changed my X-Axis to time instead of the frames. I think it's better this way, because then you can see analogies to the things that happened on the scene better. (I bet your fps isn't that low, that you actually can count the frames he?)

[Amos Wenger]

Ooooone, twoooooo, threeeeee, ^^ no fps isn't that low, hehe, but pretty irregular, see the curve I get for OctTreeSpaceTest :

Games published by our own members! Check 'em out!

[arne]

yeah my first screenshot isn't that irregular, because I have set it there not to save so many values. It looks even more irregular, if I show even more frames. (Change that constant in FPSCounter, if you want to play around with that)

I also get pretty low fps on my first frames. In both, OctTreeSpaceTest and SphereCollissionTest.

We should make a testcase, where it starts with a clean start - not something, where many Geoms intersect.