Sun, Feb 9, 5:43 PM CST

Renderosity Forums / DAZ|Studio



Welcome to the DAZ|Studio Forum

Forum Moderators: wheatpenny Forum Coordinators: Guardian_Angel_671, Daddyo3d

DAZ|Studio F.A.Q (Last Updated: 2025 Feb 06 11:16 pm)



Subject: Custom Character Workflow, with Aiko & Steph


MarkR151 ( ) posted Thu, 23 February 2012 at 10:08 PM · edited Tue, 30 July 2024 at 6:22 PM

 

I'm a little confused about the workflow regarding what to load first for custom characters, including those that involve a non-Victoria figure like Aiko or Stephanie.

For instance, one of the ReadMes mentions "A4 - Load Aiko 4 base figure, apply Aiko 4 morphs, Apply V4 Morphs++, apply SV7 Taryn Morphs & Textures."

At the risk of asking another stupid question, is that the exact order you load these things for A4 characters?

I thought you always had to load Victoria first, then the V4 morphs,  then the A4 or S4 morphs over that, and then the specific custom character over that. 

Does the procedure vary from one character to the next?


DarwinsMishap ( ) posted Thu, 23 February 2012 at 10:16 PM

Generally the V4 or M4 model is loaded first, then the additionals like Aiko or Hiro or Freak injection files.  Then I usually go for the base morphs, the ++ morphs, Enhanced, Elite, ect.

As long as you have the base V4 or M4 started the other sequences don't matter.  I hadn't gone through the DS manual since I learned on my own, but I would suggest maybe finding the pdf file in your Studio folder and seeing if that may answer a few questions?


PoppaC ( ) posted Thu, 23 February 2012 at 10:17 PM

you have it right that is the order that i go with  trry this:

build your bass A4 that way if you need her you already have her and all her morphs, then add what ever charater you need then save the "NEW " and "Keep A4"


RHaseltine ( ) posted Fri, 24 February 2012 at 8:50 AM

If you are using the PowerLoader script (if you et a dialogue when you bring the figure in) you don't need to add the morphs as a separate step.


MarkR151 ( ) posted Fri, 24 February 2012 at 4:18 PM

Quote - If you are using the PowerLoader script (if you et a dialogue when you bring the figure in) you don't need to add the morphs as a separate step.

But what do you recommend first Richard, loading V4 with Powerloader, or A4, which I think also has a Powerloader?

The character in question in this case is Taryn by SASE for A4. Although this could possibly also apply to any A4 based character. 

 

 


RHaseltine ( ) posted Sat, 25 February 2012 at 8:42 AM

Loading V4 or A4 will get you a figure, the difference is that if you choose the A4 version it will load with the A4 morph set to 1 (and if you use the Restore command it will restore to A4 = 1, instead of to a zeroed V4 as will happen with the Victoria 4 figure). Since you are going to be applying a character morph it doesn't matter which you load, as long as the needed morph sets were checked in PowerLoader.


MarkR151 ( ) posted Sat, 25 February 2012 at 10:51 PM

 

Okay, thanks. If it truly doesn't matter which I load first, I may just do it in the order Taryn's creator mentioned in the ReadMe. I just wanted to be sure first cause I had heard/read conflicting info on which is the correct 1st step. Also, because some use Poser instead of DAZ, I wasn't sure if that was the reason for the conflicting info.

I felt like I needed to gather more info here in the DAZ forum first b4 getting started on that. 

 


RHaseltine ( ) posted Sun, 26 February 2012 at 8:46 AM

Well, as I said if you use PowerLoader all you need to do is load the base figure, A4 or V4 (or any other) with the morph sets ticked and then apply the character poses. There shouldn't be any need to run the injection poses.


Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.