Möller's ray/tri intersection test indicates an intersection when certain values are used, although in reality there shouldn't be any (drew it on paper to verify this); Ray origin is (48, 32, 64) Ray direction is (-48, 32, 0) Triangles vertices, counter-clockwise: (128, 64, 128), (64, 64, 108.8), (64, 64, 0) Debugging reveals that the determinant value from first dot product seems to be wrong. When I place breakpoint right after it debugger says det=222822. and calculating it by hand with calculator gives 301465.6 - could it be that this is too big value for floating point representation?

static bool RayTriIntersect(Vector &o, Vector &d, Vector &v1, Vector &v2, Vector &v3, Vector &ptHit)
{
	// Computes the intersection point of given ray and triangle if there is one.
	// Returns: true  if there is intersection and stores the isect point in ptHit
	//          false if given ray and triangle do not intersect
	Vector s, p, q, e1, e2;
	float  u, v, t, det, detInv;

	e1 = v2 - v1;
	e2 = v3 - v1;

	p = Vector::CrossProduct(d, e2);
	det = Vector::DotProduct(e1, p);

	if(det < M_EPSILON)
		return false;

	detInv = 1.0/det;

	s = o - v1;	
	u = detInv * Vector::DotProduct(s, p);

	if(u < 0 || u > det)
		return false;

	q = Vector::CrossProduct(s, e1);
	v = detInv * Vector::DotProduct(d, q);

	if(v < 0 || u+v > det)
		return false;

	t = detInv * Vector::DotProduct(e2, q);

	if(t > 1) // Make sure it's not longer than the original ray
		return false;

	ptHit = v1*(1 - u - v) + v2*u + v3*v;
	return true;
}
   

[edited by - ZiM on October 14, 2003 5:28:12 AM]

Seems like you were right. I get the same result now.

I managed to fix the problem by replacing

if(u < 0 || u > det) 

with

if(u < 0 || u > 1.0) 

, same for the u+v.

I wonder why the original code at http://www.acm.org/jgt/papers/MollerTrumbore97/code.html have these...