assert (axis != 0) about qu3e HOT 7 CLOSED

The idea is nothing should ever trigger this assert. Did you actually hit this assert? It's just here to make sure the implementation is correct and there are no obvious bugs.

Feel free to re-open this issue or comment more of like, just closing for now :)

from qu3e.

I did check and I am hitting the assert. Should I send you a dump with the results?

from qu3e.

Yeah if you can dump the world just before the assert I can try debugging it.

from qu3e.

Just make sure the assert is hit after you load up the dump -- the dump doesn't save cached impulses so results will vary slightly.

from qu3e.

I haven't been able to find a way to consistently trigger the assert. It is always extremely random if it triggers or not. But I am also wondering if you can explain what triggers this assert because I do not understand.

from qu3e.

I'm still not exactly sure how this case is being hit, but, maybe simply returning no collision in this case is appropriate, since it's more or less saying none of the axes were selected as penetrating. Let me know if this causes any problems for you.

ad3feda

If I do get a reproduction, then I can investigate with the debugger to figure out exactly what's going on.

from qu3e.

I got your new version. It is working perfect now. Thank You!

from qu3e.