I had the same annoying problem yesterday with a mesh that i ceated in blender. Took me hours to figure out why it wasn't working.
I made a mesh in blender, exported to directx8 using a newish export script. Loaded the mesh in directx mesh view, then when i tried it in tv3d model viewer it wouldnt show up, the poly count was being displayed correctly.. If u zoomed in(or out.. cant remember) alot it would set the polycount to 0 for some reason...
Baffled me all night, until I was just about to give up... then I opened a x file that did work on tv in notepad and looked at the bottom, there was a section describing materials which I didn't have in my file exported from blender. Then I set a material(just the default one) thn exported it again... and bang! It worked in tv3d
So in conclusion... x file format is so annoying, look at the file that is written in notepad and then check to see if there are things missing(like materials) and if that dont work... its probably something to do with the mesh.. I have noticed If what im trying to export hasnt had its normals calculated(i'm not sure if this is right way to describe it, i use blender so things may sound a little different..also very new to 3d) it dont work in tv either but will work in directx mesh view. (i think this can be fixed though by using recalulatenormals or something, inside tv)