No problem, Earl. You're welcome. Give a shout-out if you run into anything else that has you stuck.
Oh - while I'm thinking of it - I wanted to warn you. When saving materials, make sure you put a copy of the textures into the DS Runtime/Texture folder, and remove the textures from the Poser/Runtime/Textures folder to test.
The reason I mention that, is because if you have textures installed in both places, Studio will default to reading from the Poser textures folder. Whereas if the textures are ONLY installed to the DS textures folder, then Studio will read from that one instead.
So it's very easy to pack something up and a DS-only person who does not install the Poser version, could end up missing textures, while it all would work fine on your end prior to packaging. I always remove the textures from the Poser textures folder for testing for just that reason.
I just wanted to give you a heads-up on that. I ran into that oopsie myself when I first started packaging things for Studio. A user sent me an email mentioning the missing files, and told me about that quirk. I checked my own install, and sure enough it was calling from the Poser textures folder... so now I just remove textures temporarily from the Poser folder when I'm testing for a DS-conversion of a Poser product.
Oh - while I'm thinking of it - I wanted to warn you. When saving materials, make sure you put a copy of the textures into the DS Runtime/Texture folder, and remove the textures from the Poser/Runtime/Textures folder to test.
The reason I mention that, is because if you have textures installed in both places, Studio will default to reading from the Poser textures folder. Whereas if the textures are ONLY installed to the DS textures folder, then Studio will read from that one instead.
So it's very easy to pack something up and a DS-only person who does not install the Poser version, could end up missing textures, while it all would work fine on your end prior to packaging. I always remove the textures from the Poser textures folder for testing for just that reason.
I just wanted to give you a heads-up on that. I ran into that oopsie myself when I first started packaging things for Studio. A user sent me an email mentioning the missing files, and told me about that quirk. I checked my own install, and sure enough it was calling from the Poser textures folder... so now I just remove textures temporarily from the Poser folder when I'm testing for a DS-conversion of a Poser product.