Culling polys by texture name.

Ok, this one has me completely stumped. I'm trying to cull polys based on their texture name. More specifically, I'm loading a Quake 3 BSP, and I want keep the renderer from drawing any faces that use the texture "null.jpg". Seems simple enough. I have something like this:

Code:

for(int i=0; i<numQ3bspFaces; i++){
 Q3BSPFace *pTri = &q3bspFace[i];
 int materialIndex = pTri->texID;

 string::size_type loc = texMgr->textures[q3bspMaterial[materialIndex][0]]->name.find("null");
 if(loc == string::npos){
  //"null" not found, so draw normally
 }
}

(not actual code, but the nearly the same thing.

However, it still draws everything anyway. I have no idea why. I had it working once, but then I tried to change the texture that prevents rendering, and it stopped working again. I've also tried having the if statement use a goto statement, but to no avail.

Please help. Please tell me i'm just doing something stupid. Because it really doesn't make much sense to me.

Thanks.

EDIT: I should also mention that I know that there are faces in the mesh using the texture. In fact, a test mesh I have all use that texture, but it's still rendered.

Nevermind, I've got it working.

Rather than checking the texture name at run-time, I check it when the mesh is loaded. If the texture contains "null", it skips loading any textures, and sets the current texture index in a bool array to true. This array is then checked at run-time.

Not 100% sure why this works, but it's also faster than string checking, so i'm sticking with it anyway.

It works b/c you set the texture member to NULL in the constructor of the mesh class don't you?

As long as that is NULL then you know you don't have a texture.

It works b/c you set the texture member to NULL in the constructor of the mesh class don't you?

Well, actually i'm not doing that for some reason. But now I set it to NULL if the texture contains "null". Why the hell did I set a value in a different array for this?

*sighs*

Dunno. Maybe too much late night coding? Usually is the case for me.