Closed GoogleCodeExporter closed 8 years ago
This assertion happens ALL over the place when using character controller.
I've seen other engines just simply return a 0,0,0 vector3 instead of crashing
on the normalization method. You need about 3-4 guards to check for "fuzzyZero"
before getting anywhere.
stepForwardAndStrafe : walkMove
convexSweepTest (if the start and end position are the same, it should just
return, not throw an assertion)
I believe in release mode the crash won't happen and return a 0 vector, so why
not just have a soft interrupt like a log message?
Original comment by AdventUn...@gmail.com
on 17 Feb 2014 at 6:54
moved to github https://github.com/bulletphysics/bullet3/issues/61
Original comment by erwin.coumans
on 30 Mar 2014 at 5:04
Original issue reported on code.google.com by
clemens....@gmail.com
on 8 Jan 2014 at 1:30