[Crayder]

Quote:

Originally Posted by vermaritt Take the "nearby" object's collision radius into account. If the first object does not detect the collision to the "nearby" object, then the "nearby" object would have to detect the collision as we will be doing a future check with collision radius itself. EDIT: According to me, for this process ColAndreas's raycating would not be needed actually. As we are doing more prominent raycasting (kinda) for collision detection. But, ColAndreas's raycating would obviously be needed for map to object collision detection rather than object to object. To Pottus, a suggestion for you. What about SetFPS(amount) or SetPlayerFPS(amount) ? Will be useful to perform simulations through pawn, I guess.

The collision radius is not the best option here. For example, what if I threw a ball in the a hangar object? If we used axis-raycasting we could detect the walls inside the hangar, but if we used the radius it would always be near the hangar object.




Now @Pottus: How would the program handle breakable objects? Their collision would still be there as long as the object is not destroyed, so it would be detected even when the object is broken (unless you have some check for that)... Not a big deal for me, just thought I'd ask.