Attached Link: http://www.renderosity.com/messages.ez?Form.ShowMessage=224451

[The nudity is in the link above, referred to below.] Some time ago while fiddling with the standard Poser horse (using Compose to insert the magic triangle for importation into Amorphium) I noticed Compose listed an unnamed group. Being curious, I exported just the hips, head and the unnamed group and discovered it was a little sliver in the "left wrist", just above the hoof. I didn't think any more of it until I got Poser Pro Pack, whereupon I noticed this sliver was missing when I loaded the horse. I finally made the connection that this was the same situation as the cr2 group problem that showed up on some people's figures that had a lot of morphs applied -- see http://www.renderosity.com/messages.ez?Form.ShowMessage=224451 In short, as explained by Curious Labs Lead Quality Assurance Engineer Joe Grover, files are being read differently in Pro Pack than in Poser 4. In an obj file (and cr2 and pz3 files, which use some of the same structure) lines beginning with "g" denote groups of polygons for the various body parts, followed by facet lines (beginning with "f") specifying the vertices making up the polygons. According to the obj file specification, if the file contains a "g" line with no group name, the following facets are supposed to be assigned to the "default" group. Poser 4 simply ignored the orphan "g" command and put those facets in the preceding named group. Pro Pack instead is ignoring those _facets,_ resulting in "holes" in affected models. Mr. Grover says Curious Labs is working on a patch to correct this, but as a workaround you can search for and delete any lines in .cr2 files that contain only a "g". If you use a programmer's text editor, you can perform this search using the regular expression ^[ t]*g[ t]*$ Some people suggest you change the orphan "g" lines to "g blah" or some other name; it doesn't seem to make a difference with a cr2, these just happen to be polygons that were grouped at some point, and later ungrouped. The big difference with the horse is that this isn't in a cr2, it's in the main geometry file, in :Runtime:Geometries:horseHi:horseHiP3.obj The offending orphan "g" line is line 28220, or you can search for a g followed by two spaces followed by end-of-line. You must delete the orphan "g" line to fix it; "g blah" would put these facets in a body part called "blah" probably with unfortunate effects. (Unless you want a horse with the blahs.) Of course, before editing any file, you should save a copy of the original in a safe place (outside the Runtime folder) in case you encounter problems after editing, so you can put the original back, or try editing again.

Thanks for the info Petercat. I usually use UVmapper to regroup anything strange like that. But in this case. Using a text editor looks like it would be faster. I noticed that Compose would not let me create a name for that odd little piece. That kind of pissed me off a little. ;-) ScottA