This one has me stumped. I have a completed model that I've assigned groups and materials to. I realised that I needed another group, so I added another one and assigned the materials that I wanted to, to that group. I ran the object through PHI Builder, set up the hierarchy, tested it there and all looked good. Now when I try to convert the hierarchy file in Poser, I am getting the following error (see attached image). I have had this problem crop up before, but I seem to recall that deleting the rsr file from the geometries folder solved it. Not this time, however. Have I missed a secret file somewhere that I should have deleted? I can't think of any. Any assistance would be greatly appreciated, as I'm wearing out my desk with all my head banging.

Stefan

Easy suggestions might be to run the .obj through UV Mapper, which often corrects formatting problems, and to check the .phi to verify that the correct file path is specified.  I've had PhiBuilder get muddled up on me, now and then.

But I've never seen that error.  Huh.  I'd like to know what causes it, too, just in case....

 

Hmm, the phi file is pointing to the correct object. I'll just keep going until I work this out.

Check the spelling on your group naming very thoroughly, including the letter case. The group names in the OBJ file must match the actor names in the PHI file exactly.

EnglishBob, I knew all the spelling was correct, but your idea started me thinking. I deleted the underscore from the SthWallHardware group name and tried again. Poser then told me there was no geometry for any of the group names, so I shut it down, re-started it and tried again. This time Poser converted the hierarchy file flawlessly. I don't see how one little underscore could make all that difference, but at least I now have a working cr2.
Now for the morph targets......

Print this out and pin it to your wall: Poser is weird That should help you in future. :biggrin: If you're saying that the underscore shouldn't have been there, then that's your answer right there. An underscore is a part of the name as far as Poser knows, so it has to be right just as much as the rest of it.

Ah, but that's the strange thing. The underscore was part of the name. I just deleted it to see what would happen and then it all worked correctly. As you say, Poser is very strange.

Hmmm...

Wonder if it's anything to do with the fact that Underscore (hex 5F) is similar to DELete (hex 7F)??

Just a possibility... (those type of characters sometimes undergo "special" processing in parsers..)

Cheers,
Diolma