collision depends on frame rate

Post by **Nowic** » Thu Feb 22, 2007 7:25 pm

The collision should not depend on the frame rate.

Example:
Every time Amarok shows the name of the next track (with OSD), the number of frames gets very low and all NPCs fall through the floor. I looks funny but...

You can use it for cheating too. With a low frame rate (or a frame drop) you can walk through the balustrade and visit the lower floors of the space station.

Edit: ->> https://dev.orxonox.net/ticket/204

Post by **x3n** » Thu Feb 22, 2007 8:03 pm

To fix this, the collision engine must recognize whether there was a collision between the two locations of the player in two frames or not, because as it is now, the collision engine just checks if the location is valid.

example:

Code: Select all

Frame 1:
....P....[     ].........

Frame 2:
high fps: .........[  P  ].........  collision detected
low fps:  .........[     ]....P....  no collision

Or let's just say:
+1 feature: tunneling effect

Post by **beni** » Thu Feb 22, 2007 8:30 pm

It's a feature again I see: It's the amarok tunneling effect. Very interesting!

Post by **Nowic** » Thu Feb 22, 2007 9:36 pm

Amarok tunneling effect! Great! *lol*

Post by **patrick** » Fri Feb 23, 2007 9:42 am

I created a ticket for this yesterday (the mainloop ticket) https://dev.orxonox.net/ticket/204. Suggestions, ideas?

claudio · Post by **claudio** » Fri Feb 23, 2007 5:56 pm

I'm working on a solution as suggested by x3n. I think it's the fastest way to get rid of that 'feature'.
I like your ticket, Patrick.
However, after thinking a lot on the redesign of the main loop, I doubt, whether we should already implement it in the cleanup branch. If I worked on the reimplementation of the main loop, I'd probably rather create further bugs before anything became better.
Thus, couldn't the PPS assistants suggest this ticket as a PPS-Project?

Orxonox

collision depends on frame rate

collision depends on frame rate

Who is online