Original Post
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?
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?
