If you set your library search to shallow instead of deep it won't search for that long. Might be something to consider.

Yeah the chips are a lot of fun to play with. I've been converting M4 and even older M3/M2 clothing to L'Homme. CrossDresser was easy to get the hang of. Now if only I could convert boots and shoes - lots of outfits are dependent on having the right footwear.

Here's L'Homme in his cool new threads!

Great expression, a touch of elegant arrogance I'd call it :) He reminds me of someone, did you base him on anyone specifically?

I really like all these little splashes of colour against the white!

Yay! Glad it worked for you :)

Can't you save the figure to your library, open up the other poser file and add the saved figure with the morph from the library? I'm not sure if I understood your question so I don't know if this helps.

Ok, here's what you do but I've only tried this with hair. I bring in the hair .cr2 and instead of conforming I go to the Figure menu/Set figure parent and choose the head of my character. Once it's parented I save it in the library with a different name so as not to overwrite the original.

Then navigate to the folder where you saved it and change the .cr2 to .pp2. Open it up in a text editor and find the 2nd instance of actor BODY. Below that you will see many entries. If you compare the .cr2 and .pp2 you'll see the .cr2 has "parent UNIVERSE" whereas in the one you saved and changed to a .pp2 it has "parent head:1" change this to "smartparent head:1. Resave and open your .pp2 in Poser. The .cr2 will come in and be parented now - no need to conform.

Hope this helps!

What error exactly?

Let me just add that if the hair happens to be a figure, that is a .cr2, you will select it's BODY and translate/scale that to position and then from your Figure menu select Set Figure Parent and parent the whole figure to the head.

Have you cleared your cache? It might be that they have changed but you can't see it.

Quoted from BagginsBill:

"Look I've explained this before but for some reason it doesn't reach everybody.

Normal maps are a hack for real-time game rendering from olden times. We don't need to use them. Normal mapping from normal maps does not give you any different results than normal mapping from bump maps, assuming both are done correctly. But that assumption is rarely valid.

Poser doesn't use normal maps correctly. Poser does use bump maps correctly. As a consequence, no matter how you make your normal map (there are "right" ways and wrong ways), the result will come out different. It should not be different.

Bump maps are normal maps without the pre-baked math - the renderer does the math on each render, which takes a few dozen extra milliseconds than the normal map. But the bump map comes out right and the normal map does not. This is because the pre-baked math is not fully agreed upon by every 3D program.

Half the 3D programs use normal maps differently than the other half. All of them produce their normal maps from bump maps.

Therefore the only logical thing to do is just use bump maps."

Well the OP asked about finding items from a favourite vendor and the easiest way to do that is to go the vendor's store Of course this works on any page in the Marketplace.

If you go to a vendor's store just by looking at the thumbs you can see which ones you've purchased. The shopping cart icon of the items you've already purchased is a darker, duller green as you can see from the attached image:

Those products were not supposed to be included (Kayla Hair and Oriental Fantasy Hair) and have been removed from the article. I apologize for any confusion.

@PenelopeFlynn could you tell me what Legacy items are missing for you?

Is this the product you're talking about? If so, you are correct, it's dynamic and ready to go as is. But it does NOT have body parts, it can't because it's just a prop not a figure. Where are you seeing these body parts? Are you talking maybe about material zones? Can you show us a screencap of your material room with the sleeves material selected because maybe for some reason a transparency was set there by mistake?