I went the route of the double trace and I’ve reached a point where collision can be detected consistently for speeds up to 10000-15000.
At 20000 is starts to fail again, not as badly as before but bad enough to be unreliable.
I basically kept my collision detection code but branched the result based on the hit: if TRUE the collision is detected and the trajectory is calculated normally.
If FALSE, so no collision at all, another trace is started to the previous location and on hit the same logic is used again to calculate the new trajectory, then the location is stored for the next cycle.
I I’m going to test what RedOverDrive suggested but it needs some redesign of what I’m using now, while I was in the process of tinkering and testing a few bugs came out and I need to address those first.
In the meantime thank both you guys.