(20##) 10 9 8 7 6 5 4 3 2 1 0 <
DesktopWeb FormText   more Mesh.IntersectSat, 13 Aug 2005 16:23:13 GMT # 

(famous last words) i 'think' the collision detection is fixed ... again. er, um, actually it was OS that talked me through it. but another thing that bit me was Mesh.Intersect ... again. ZMan had straightened me out about the second vector being direction. so i started treating it purely as direction. thinking that if i put the direction as (1, 0, 0) or (2, 0, 0) then they would mean the same thing (positive X). but they're different! based on the Direction property of the IntersectInformation results, the actual collision will occur at different distances ... dont ask me why? direction means direction ... with some scale?