Closed anirul closed 7 months ago
Sounds like overflow…
Yea but why? I do all my calculation in double
so this is a bit weird. Also this happen from one frame to the next there is no intermediary, if it was an error accumulating it would not be like that.
I wonder if this does come from the dt going wild? like if you try to move to somewhere very fast then it could corrupt the position as fast? Still experimenting...
I hard corrected one of the error but I still have a camera issue... still working on it!
So... I thinks this is ok now. This was coming from the camera as I m not using any quaternion for it it sometime freak out and put Nan in the position of the forward vector (that contaminate the whole thing after). So I just detect when this is happening and reverting the forward to a safe direction and it work.
This is a memory corruption somewhere...
This was in effect coming from the async implementation, I reverted it 'painfully' and now it seams not to be there anymore.
Discover that sometime the position of the character is switch to
-inf
and also the dt... why?