[fixed] Newton 1.53 - Collision Issues

Report any bugs here and we'll post fixes

Moderators: Sascha Willems, Thomas

[fixed] Newton 1.53 - Collision Issues

Postby Rible » Sun May 31, 2009 8:16 pm

Hello everybody,

We are a group of five french students, and we're currently using the Newton engine in order to create a video game (as part of our studies).
We have to deliver our product wednesday, and our product is close to be the final one.
Little issue however : even if the collisions between the main actor (a spaceship) and the environment (the race) of our game are detected, some of them are ignored. Especially when the speed is increasing :/

The strange thing is that we know the collisions are detected, even when the ship is going through a wall, because our "collision sound" is played.

Despite this bug, everything is perfect with Newton ^_^

Please, somebody could help us ?

Many thanks,

Rible Studio
Last edited by Rible on Mon Jun 01, 2009 11:44 am, edited 3 times in total.
Rible
 
Posts: 4
Joined: Sun May 31, 2009 8:04 pm

Re: Newton 1.53 - Collision Issues

Postby Julio Jerez » Sun May 31, 2009 9:09 pm

I do not know why is it with that they wait until the last minute to report these issues.
If you deadline is Wednesday, it means it is too late to do anything meaningful.
These are my recommendation of steps that are very safe.

-Double for FPS, meaning that two steps at twice the frequency you are currently doing. (this is usually the best solution but it comes with a price in performmace).
-Set continue collision mode.
- do both step.

You can do then in the same order I mention and test it.

I hope that help, and for the record next time please do not wait until the last minute to ask for help on a serious problem like that.
Julio Jerez
Moderator
Moderator
 
Posts: 12249
Joined: Sun Sep 14, 2003 2:18 pm
Location: Los Angeles

Re: Newton 1.53 - Collision Issues

Postby Rible » Mon Jun 01, 2009 5:46 am

Many thanks, the continuous collision mode saved our lives, it's perferct ^^
Actually, we were doing it but only on materials, not on the entire body... But now everything is working !

When it comes to the last minute thing, we actually didn't expect to go so far on our project, so we kind of forget the idea to have nice collisions :D

So if it can help somebody, we just add this line right after the creation of our body (no need to change the framerate in our case)

_body = NewtonCreateBody(_world, collision); // creation of the boy
NewtonBodySetContinuousCollisionMode (_body, 1); // continue collision mode


Thanks again, especially for your really fast answer !

Best regards,

Rible Studio
Rible
 
Posts: 4
Joined: Sun May 31, 2009 8:04 pm

Re: Newton 1.53 - Collision Issues

Postby Rible » Mon Jun 01, 2009 7:06 am

Actually, after several tests, they are some case where the ship still go through a wall, even after setting the framerate :/ It's much less than before but not perfect :/
Rible
 
Posts: 4
Joined: Sun May 31, 2009 8:04 pm

Re: Newton 1.53 - Collision Issues

Postby Julio Jerez » Mon Jun 01, 2009 9:21 am

you object must be doing too fast,
tring doubling the FPS.


after you test teh only solution yo uhave is migrating to 2.0 which fixed mane of theso problems,
but I do no recomned you doing that tow day before a test.
That is why I said it is too late for any solution that requires modifing code.
Julio Jerez
Moderator
Moderator
 
Posts: 12249
Joined: Sun Sep 14, 2003 2:18 pm
Location: Los Angeles

Re: Newton 1.53 - Collision Issues

Postby Rible » Mon Jun 01, 2009 11:44 am

Hi again,

We actually did double the FPS and it didn't work. However, we tried to do 10 updates of the physic world per frame calculated by the 3D engine, and it worked perfectly !
You're a kind of genius, thanks a lot !!

Concerning the 2.0 engine, we didn't use it because it was called "beta version" (= not stable), but I think we will upgrade it later (not for wednesday :p) !

Best regards,

Rible Studio
Rible
 
Posts: 4
Joined: Sun May 31, 2009 8:04 pm


Return to Bugs and Fixes

Who is online

Users browsing this forum: No registered users and 9 guests

cron