Hitbox request thread.

[Treewyrm]

The basic explanation for large surfaces causing problems here are the optimizations for real-time collision processing. Best to keep things simple but segmented. From what I understand, and from what I know based on experience with other embeddable physics engines in games and other 3D real-time environment simulations, is that to cut out unnecessary processing it computes collisions between surfaces within a specific boundary range. So if colliding polygon tries to "interact" with a part of another polygon that is off the boundary it ain't gonna detect anything and challenge will fail. I'm not entirely sure about how it works for Freelancer, no source code or anything here, but in general that's how it is and most likely applies to FL in one way or another as well.

Crashing to desktop can happen for many reasons. Gaps, wrong surface orientation, etc. Who knows, most of the time you can only guess why, and from trial and error experience get to feel what the game wants from you, what it will work with and what not. And for as long as the method I figured out works (it's a quite different from one posted there) I'm fine.

p.s. jinx, not even going to bother replying to your ot, take it to private or elsewhere.

@I_m_rdy: here. Or if you want direct link: http://www.mediafire.com/?ncyxidzw2dj