Thanks

See if that one poly is added to the other thight group if so it might be what has happened if not yell  again and we can look at other thing that might do this

Quote - See if that one poly is added to the other thight group if so it might be what has happened if not yell  again and we can look at other thing that might do this

How do I do that?

well in poser you would  look in the group tool and see if when you click it and see what groups show up

Ok it looks like it should be apart of the lshin group but there are no random polygons highlighted red where they shouldn't be. There is also another hole on the same leg nearly in line with the pocket, which I didn't notice initially.

Try selecting the right thigh group and then the right shin and see if that one or two polys on the left leg highlight.

Also, render it, and then note if the hole is there, or is gone, or if the errant polys show up but are a bit shadowed.  Those two polys may have their normals facing inward.

Quote - Try selecting the right thigh group and then the right shin and see if that one or two polys on the left leg highlight.

Also, render it, and then note if the hole is there, or is gone, or if the errant polys show up but are a bit shadowed.  Those two polys may have their normals facing inward.

That is what I did, & as I said in the post above yours, no there weren't any errant polys& yes they are definite holes.

If that missing polygon is actually the very last one listed in the .obj, then this would happen if the .obj file lacks a line feed at the end.  Poser seems to require that extra blank line at the end of a .obj which is being used as a figure geometry, although it will import such a .obj file without the same error.  If the geometry is being used as a figure base, Poser apparently just stops reading the file and the last "f" line is skipped.

Just a guess.  That might not be the problem at all.  If more than one polygon is being affected, that's definitely not the problem.

No that doesn't seem to be the problem Cage, but thanks for the suggestion.

Oh well.  It was just a guess. 

Have you imported the converted .obj file to verify that it has the same holes?  Do the holes fall anywhere near a weld seam, where one .obj group would meet another?  The "f" lines section of the .obj can get awfully jumbled.

You might try running the .obj through something like UV Mapper or Stomp which is known to fix many .obj problems upon export.

I'll stop guessing.  :lol: 

It is actually on a group seam, between the lshin &lthigh groups, & when I looked at the obj in an old version of Cinema 3d I have, it looks like vertices are missing.

Oddly enough though, I just tried importing the obj in Poser like you suggested, & it doesn't show the missing vertices when I do that.

Quote - Oddly enough though, I just tried importing the obj in Poser like you suggested, & it doesn't show the missing vertices when I do that.

It shouldn't be missing vertices, unless the .obj isn't welded at the actor seams.  This seems like a problem somewhere in the "f" lines of the .obj, which is preventing Poser from reading all of the polygons properly.  Running the .obj (or a copy of it) through UV Mapper may clean up the "f" lines which define the polygons and correct the problem.

Edit: For that matter, exporting from Poser might fix the problem, if it is just jumbled face lines in the .obj....

I have UV mapper Pro, but have no idea how to do what you suggest. Could you do a step by step please, thanks.

Quote - I have UV mapper Pro, but have no idea how to do what you suggest. Could you do a step by step please, thanks.

It's a pretty simple idea.  Err, hopefully it is, anyway.  :lol:  You want to re-name the current .obj, say by adding the suffix "_OLD" or "_BAD" to the file name.

Then open the bad .obj in UV Mapper (or Poser, whatever program you want to use) and just save it out again.  When you save it, save as the original name, before you re-named the file.  Don't overwrite the original.  (Unless you want to for some reason.)

So you basically end up replacing the .obj which the .cr2 will read when it creates the figure, while backing up the original.

LOL well I screwed that up badly.

Using UV Mapper & the default settings, it made the 2 thigh groups disappear when I opened it again in Poser.

Using Poser the whole thing disappeared, something loaded,but nothing was there.

That's... unexpected.  :lol:  What export options did you use, in either case?  The attached shows the options I've used when doing this sort of thing with a .obj file.

Thanks, I just got home from work, will have a go with those in the morning.