Jump to content
  • Advertisement
Sign in to follow this  
bpj1138

X-Purge 6

This topic is 2123 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hello everybody,

I've been working on my 3d verlet engine, and I thought I should share some insight about this before I upload the new version. First of all, if you haven't noticed, the previous versions of the engine would occasionally "BLOW UP" for no apparent reason.

Well, that is what is being addressed in the current version. Things that I have found out in the process are:


1) don't assume the problem is the friction calculation (see below)
2) if the intersection code is faulty, all bets are off, therefore friction calculation can fail as the result
3) most of the errors are caused when velocity vanishes, this means there is no tangent vector!
4) when all else fails, just abort the operation... the next interation will handle it

Your thoughts?

Share this post


Link to post
Share on other sites
Advertisement

Your thoughts?

My thoughts? My thoughts are I'm not sure how to respond to this thread. Are you asking for specific feedback about a specific problem/question/potential solution?

Share this post


Link to post
Share on other sites

[quote name='bpj1138' timestamp='1348299648' post='4982600']
Your thoughts?

My thoughts? My thoughts are I'm not sure how to respond to this thread. Are you asking for specific feedback about a specific problem/question/potential solution?
[/quote]

I'm asking for other people's experiences solving the contact force problem. It seems to me when objects come to rest, which is obviously the solution, velocity goes to zero, therefore, you have to "catch" that condition in the code, which is obviously an invalid condition... velocity is zero, therefore time is zero, or objects are "at rest"...

Share this post


Link to post
Share on other sites
When such an error occurs, he X-Purge engine will print out an error message, like "tangent not unit"... which means, relative collision velocity was zero, therefore there was no tangent vector. It's always at the extremes where the system fails.

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!