In my experience, any expression made on the base figure will get you uncanny results when applied on a custom figure. So for this reason, I always create figure specific expressions. You can try them on other figure, tweak and resave.
Well, of course, but having a controller for several expression morphs has some benefits. Generally you might have the problem that your e.g. smile looks great at 100% , but odd at 35%. You can key your controlled morphs in the parameter tab. If this is done correctly, your smile can look great at any value.
@@roxylindholm5179 Has no fkin benefit other than slowing your load times. I am so fuckin pissed right now. I just made a program to uninstall all useless morphs and convert useful ones to presets. It took me 5 minutes to load character because of morphs ( on 13900k). Back to few seconds loading with access to all expressions as before. And in those 5 min difference load time I can make a fkin expression anyway.
Just FYI: a controller and a morph are two different things. Morphs move an object's vertex positions, controllers move existing sliders. So the controller itself doesn't actually add any significant load times, but morphs definitely can and do. There are ways to deal with that, like the Turbo Loader script, or by spreading content across multiple libraries, or by uninstalling content you currently don't use. The latest beta version of Daz Studio 4.21.1 has load time improvements too, especially for Genesis 9. Worth checking out.
This is something I still don't understand about Daz. Initially you created a dial, which is very useful because I can adjust the value of that dial, but if something isn't right I can go back, see which dials it has affected and tweak them. But don't I lose that flexibility once I export it to a morph? The way I understand it everything you export in Daz is a morph. Prior it could have been created either as a dial or as a morph (as in export the mesh to Blender, change the geometry (not the topology) and reimport it into Daz) but does that even matter if it's exported as a morph?
It depends on the use case really. Combining multiple sliders into a single morph is great as a final step, if you intend to remove the original products, or if you don't need them in your target project. Think of exporting it into a game engine or modelling app, or for reducing load times on the genesis figures. Combining them into a controller slider on the other hand gives the same ease of use, but retains the flexibility of going back to the original morphs for later fine tuning. Often in 3D there's more than one way of doing things, and it depends on what works best for you and what the project needs.
@@WPguru Thank you for the quick response :) I understand the pros and cons of both workflows, so my follow-up question would be if I have control over what I export? Can I export a controller slider as opposed to a morph?
Sadly no, other applications only understand the change in vertex positions, but not how that change is brought about. It's a bit like the difference between a native Photoshop file with layers, and a JPG in that respect. The controller will only be available natively in Daz Studio, while the resulting morph can be imported into other applications as a change in vertex positions.
@@WPguru No, I meant Daz alone. That is exporting a controller slider and sharing it with other Daz users? Is that possible and if so do you have a tutorial on that?
In my experience, any expression made on the base figure will get you uncanny results when applied on a custom figure. So for this reason, I always create figure specific expressions. You can try them on other figure, tweak and resave.
Moin! Sehr schön. Das ist hilfreich. 🥰
Thanks!
Fresh cut brah!
Isn't this possible with combining morphs too? I mean isn't it the same like combine them and create a new morph with the morph loader pro?
Well, of course, but having a controller for several expression morphs has some benefits.
Generally you might have the problem that your e.g. smile looks great at 100% , but odd at 35%. You can key your controlled morphs in the parameter tab. If this is done correctly, your smile can look great at any value.
@@roxylindholm5179 Has no fkin benefit other than slowing your load times. I am so fuckin pissed right now. I just made a program to uninstall all useless morphs and convert useful ones to presets. It took me 5 minutes to load character because of morphs ( on 13900k). Back to few seconds loading with access to all expressions as before. And in those 5 min difference load time I can make a fkin expression anyway.
Just FYI: a controller and a morph are two different things. Morphs move an object's vertex positions, controllers move existing sliders. So the controller itself doesn't actually add any significant load times, but morphs definitely can and do. There are ways to deal with that, like the Turbo Loader script, or by spreading content across multiple libraries, or by uninstalling content you currently don't use. The latest beta version of Daz Studio 4.21.1 has load time improvements too, especially for Genesis 9. Worth checking out.
@@WPguru Oh okay, now I get it. Using daz for over a year now and I'm still a beginner. ^^' Okay that makes sense, thank you! ^^
@@roxylindholm5179 Thank you too! I didn't know that!
This is something I still don't understand about Daz. Initially you created a dial, which is very useful because I can adjust the value of that dial, but if something isn't right I can go back, see which dials it has affected and tweak them. But don't I lose that flexibility once I export it to a morph? The way I understand it everything you export in Daz is a morph. Prior it could have been created either as a dial or as a morph (as in export the mesh to Blender, change the geometry (not the topology) and reimport it into Daz) but does that even matter if it's exported as a morph?
It depends on the use case really. Combining multiple sliders into a single morph is great as a final step, if you intend to remove the original products, or if you don't need them in your target project. Think of exporting it into a game engine or modelling app, or for reducing load times on the genesis figures. Combining them into a controller slider on the other hand gives the same ease of use, but retains the flexibility of going back to the original morphs for later fine tuning. Often in 3D there's more than one way of doing things, and it depends on what works best for you and what the project needs.
@@WPguru Thank you for the quick response :) I understand the pros and cons of both workflows, so my follow-up question would be if I have control over what I export? Can I export a controller slider as opposed to a morph?
Sadly no, other applications only understand the change in vertex positions, but not how that change is brought about. It's a bit like the difference between a native Photoshop file with layers, and a JPG in that respect. The controller will only be available natively in Daz Studio, while the resulting morph can be imported into other applications as a change in vertex positions.
@@WPguru No, I meant Daz alone. That is exporting a controller slider and sharing it with other Daz users? Is that possible and if so do you have a tutorial on that?
Yes that you can do. It's the same principle that I've explained in the packaging morphs video you've commented on.