I just ran into an odd problem.  I've modeled an outfit for Blackhearted's Anastasia figure (which is based on Alyson 2) and I'm having trouble setting up the conforming shorts.  Here is the procedure I used:

1. Pregrouped the shorts

2. Imported the OBJ into Poser

3. Used the Set Up room to load the Alyson2 rig (just the base, not one with the Anastasia morph applied)

4. Saved the shorts to the library

5. Edited the Shorts.cr2 to point to my original OBJ (not the one the setup room generated)

6. Started a new scene, loaded in Alyson, applied the Anastasia morph, and zeroed Alyson's joints.

7. Loaded in the shorts (they look fine at this point--see the image on the left)

8. Conform the shorts to Alyson  (now things get wonky--see the right image)

The image on the right shows the shorts after they are conformed.  I haven't even bent any body parts yet, and there is pokethrough.  Any ideas as to why this is happening?

Well, I just figured out something. For some reason, when I conform the shorts, the thighs bend at -12 and twist at 2.  If I zero the shorts joints, there is no poke-through at the zeroed position.  I resaved them to the library, and reloaded them, but they're still doing it.  Any thoughts?

it does that sadly :) I had an apparantly over complicated way of fixing it.  But some kind fellows pointed out that Zeroing the conformer then using the memorize option before saving it to the library sorts it out.

John.

Fugazi (without the aid of a safety net)

https://www.facebook.com/Fugazi3D

EOD,

I've noticed things like this sometimes after using the set up room. One thing you can try is to look at your figure with the Joint Editor open and check the Falloff Zones. Insure that the weightmapped zone is set to "replace". On occation I've had to set any and all falloff zones to "ADD" then "Merge Zones" into a NEW Weight map, after whicih I deleted the older Falloff zones leaving only the new group I'd created.

I'm not sur why, but I think whn transfering the Falloff zones they some times interact causing the problem you discribe.

You might also concider using the Poser saved Object file. This SHOULDN;T cause a problem but you never know... Poser does some weird things with minute objecct translations that may be caused by the tiny scale Poser uses internally and rounding of values after the decimal place, but I'm not sure if that;s actually Poser or windows at fault.

Quote - it does that sadly :) I had an apparantly over complicated way of fixing it.  But some kind fellows pointed out that Zeroing the conformer then using the memorize option before saving it to the library sorts it out.

John.

 

Sweet!  Thanks you so much!  That did it John! 

When I had orignially exported Alyson2 with the Anastasia morph applied to use as my modeling base, I zeroed her joints prior to export.  When Alyson loads in her default pose, her thighs are bent at -12 and twisted at 2 and -2 respectively.  I wonder if you exported her without zeroing and modeled your clothes on her if you would have this issue?

Thanks again man!

--Jeff

BTW, what is that xmp file that's created in the figure folder along with the clothing.  Is it needed?

Hi Jef

Nah for some reason the Alyson CR2 which I used to make my blank has a few values in the x,y and zrot channels on the thighs.  I thought it was something I was doing in making the blank, but no matter what I did it was the same thing over and over.

Then I went through all the joint channels in the cr2 and set any non zero values to 0 and it worked :)  The memorize thing is much simpler though :)

John

Fugazi (without the aid of a safety net)

https://www.facebook.com/Fugazi3D

Hey John, Thanks that;s much easier than the hunt and peck whay I've been doing it. and on reflection, totally understandable since Alyson has that wierd default pose!

THanks from me as well

The XMP file is metadata information on the saveditem, it can be edited with the metadata builder Pything script in poser or any xmp editor. It ads info to the item that can be seen in the info at the bottom infowindow in the Library.

It can safely be left out of the package unless SM changes things in the future.

 

 

Quote - The XMP file is metadata information on the saveditem, it can be edited with the metadata builder Pything script in poser or any xmp editor. It ads info to the item that can be seen in the info at the bottom infowindow in the Library.

It can safely be left out of the package unless SM changes things in the future.

 

 

 

Ah, OK, great to know!  Thanks so much!  :-)

The first paid clothing to come out for Anastasia, leather shorts and top, had the same problem with the shorts as you demonstrated. The author included a pose file to fix it. Without the pose file, her butt showed through just like yours upon conforming. 

Quote - The first paid clothing to come out for Anastasia, leather shorts and top, had the same problem with the shorts as you demonstrated. The author included a pose file to fix it. Without the pose file, her butt showed through just like yours upon conforming. 

Ah, too bad the vendor had to do that.  The fix John suggested worked perfectly!

EOD, I saw this thread on RDNA's Poser9/2012, forum and it goes into a lot of detail about metadata and it's current an potential future uses. I thought you might find it interesting. http://www.runtimedna.com/forum/showthread.php?67863-Metadata-and-its-use-in-Poser

Quote - EOD, I saw this thread on RDNA's Poser9/2012, forum and it goes into a lot of detail about metadata and it's current an potential future uses. I thought you might find it interesting. http://www.runtimedna.com/forum/showthread.php?67863-Metadata-and-its-use-in-Poser

Oh wow, thank you!  I'm going to check this out right now!

ive encountered this before and managed to get rid of it like this:
when you transfer weight maps to a clothing item, and then save that clothing item to your CR2 library, Poser re-saves the OBJ to the folder you saved that CR2 to (and references this new OBJ in the CR2).
if you take the ORIGINAL .OBJ file and replace this one (or, preferably, edit the CR2 file reference to point to the original object in your Runtime/Geometries/... location) then this might go away.  this may have to do with Poser's rounding errors/etc upon export.

  *edit:

just re-read what EOD posted and it looks like he did replace the original object.  glad John's fix worked, ill have to keep that in mind for the future :)