Daz 3D is part of 
Connect
DAZ Productions, Inc.
224 S 200 W, Suite #250
Salt Lake City, UT 84101
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.Daz 3D is part of
Connect
DAZ Productions, Inc.
224 S 200 W, Suite #250
Salt Lake City, UT 84101
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
For any characters that require the Genesis 3 Head Morphs, do they also need to be selected in addition to the character itself?
Any changelog for the differences between the old (nuked) and new GenNext at github?
I'm sorry for my stupid questions, but I really am a newbie regarding scripts.
The thread is pretty long and I can't manage to find instructions.
First of all, thanks for your hard work! The interface is much more clear than I was expecting too!
I've loaded 2 G8 (one F and one M) characters into the scene, then I've opened the script.
The problem is that I can't select them in the menu of the script. I see "Genesis 8 Male/Female etc.", but if I select them (but the figures are not named that way), no morph appears.
What am I doing wrong?
The biggest change from the last version (that was not motivated by legal issues) is error catch. When the process errors out, it still doesn't notify you, but when you cancel, the error message no longer says check logs. But has the actual error. I have learned that this is stopping the error message being logged. So that needs fixing. One thing I should have reactivated before shipping is likely the cause of the hang up. If it doesn't finish correctly load a new scene. The objects left behind interfere with the process.
You can have a female version of anything, but that is not how you would do that. I'll explain more later. For now, just trust that the process you have in mind is flawed .
Basically, yes. And it gets worse. The process seems to take about 20 seconds per morph, now. Allow 2.5 minutes to set up and shut down and you hit a small snag when transferring hundreds of morphs. 200 Plus sent as a whole, will take 4000 seconds plus setup and shut down time (4 kiloseconds is 1 hour 6 minutes 40 seconds). Call that about an hour and 10 minutes total.
Sending a basic character can be done in less than 5 minutes. But a complex character takes a lot of time. This is why transferring whole products is not the default setting any longer. It eats too much time, and the jcms may not be needed. This way. You can test adding jams when you see the need rather than lose 40 minutes to each transfer.
Not really, other than it does not presently work with g1/2. I didn't make any user facing changes. Not will I be making any soon. I will try to keep track of that going forward.
The script doesn't do characters. It does morphs. Most characters are labeled as characters when launched as a character preset. While the script identifies the figure by name, it accesses them by label expressly to prevent presets being used. Transfers should be between unmorphed base figures, or it will not work correctly. What you call "not named that way" Daz calls changing the label. Since the labels are changed, the script can't see the figures.
thanks i would really love a a good explanation and would be really good have some "tutorials in future in how to use it" and i know it flawed it was just what come to my mind without using your tool as base, this was just a basic mind blow, if you tool alone would do all the process alone and better that would be perfect and really the best thing ever.
One question, the tool is just to export any genesis(1, 2, 3) and gender to G8, like G2F to G8F&M or G3M to G8F&M or it can be used to transfer morphs in any Generation?? like from G2F to G2M or G3M to G3F or like G3M to G2M&F??? if like that then it really is a big mindblow in the mixmatch you can do with it.
GenNext doesn't support Generation 1-4 at all. That's completely different technology from Genesis, and I haven't even begun to figure out how it works. After the last clones are done, it will support every Genesis (hopefully correctly, but I suspect issue with Genesis. Stupid curled fingers ruining everything). Any figure it supports, can transfer to any other figure it supports. It does not transfer HD morphs, but it will transfer the LowD morphs that control HD morphs, so you might see sliders for "whateverHD" and those sliders might make the figure shape change a bit, but they won't be HD.
As far as explaining how you go about transfering "gender," you don't. The products that say "shapes for G#F" aren't "female" shaped. outside Genesis, no morph is (I'm sure there are exceptions, but that's beside the point). Transfering a female morph set to a male figure will not feminize that figure much at all. Narrowing the waist and making the hips rounder won't be as effective as you might think because the basic shape it is being applied to is incorrect. You need to have a female shape on the male figure, already, to make that work (Rigging the transfer clones won't work as well as you might think, but it is one way to do it on Genesis 8--Edit: rigging the clones themselves is another bad idea, but you can make a new shape by dailing in the clone, exporting it, and importing it as a morph).
The way you go about making a female version of a male shape is to transfer the male shape to a female figure, without baking. Male shapes tend to be buff and defined, so expect that to happen to your female reproduction.
Why do you do it this way, you ask? Because transferring morph packages is generally a bad idea. If you know you will never get the version of that package that was made for that figure, it might be okay, but it will be an issue, otherwise. From what I can see, the base sets for all the figures have the same names. 200+ seems to be similar. Vendors tend to just remake the old version with a few new tricks. Having both installed on a figure can lead to bad things. (Edit: To be clear, Package X for G8F and Package X for G8M will have many of the same morphs names, as well. It may be safe to transfer gender specific morphs, individually, but you need to check and make sure you aren't creating a conflict.)
interesting, well i wanted to means "genesis" not generation, my bad, well i will keep testing, well for me at last it's for game development, i will give some tests later.
then a good way would be:
let's say get the minotaur 6 male, dail it into female, export it then get the exported one then import back to daz as a "morph to female", then use it right?
I have G8F rigged for G8M and viceversa, so adding that to the other morphs should do the trick.
Now I've managed to see a long list of morphs, transfering the shape presets of the characters I wanted to transfer on a base G8 figure.
The problem is that my characters use hundreds of morphs, and from what I've understood, this way I would have to check each one of them one by one, and the all transfer would take hours, am I right?
In any case, that wouldn't create a single slider with all the morphs, right?
So, I was thinking (I don't want to go off topic, but you seem the best people for this stuff), what if I created a custom character from a set of morphs, and then I applied it on the figure of the other genre?
I'm talking about the instructions contained in this video:
Do you think it would work right away?
Would I need to rig them afterwards? Could that be done with Shape Rigger Plus? (https://www.daz3d.com/shape-rigger-plus)
Basically, what I'd like to obtain in the end, is a single slider containing those hundreds of morphs that I could use to create slow transgender transformations...this is so hard
If you create a custom character AND save the shape as in the video AND reload the figure in a new scene the script will transfer it like any other morph.
The script doesn't care where the data come from. It only needs the files to be saved and the figure to be properly connected to the files (that is why new scene. It clears the cache).
Remember, a custom dialspun character converted to a morph can't be distributed. You can't share the shape, only the dail settings and products you used to make it. Edit: Obviously, that limitation doesn't apply to products that say you can use them to make morphs. Check your licenses.
Sorry for late reply, back from vacation.
I wouldn't think I would have to convert the shapes if I already had the shapes... Besides I mentioned I was dialling in the M5 shape.
Anyway, I think I found the problem. Once I dialed in both M5 AND M4 I got the shape. Wouldn't have thought I would have needed to since the M4 shape wasn't showing under Currently Used.
Thank you, as always, for your fast answer! :D
I have no interest at all in selling products. I refuse every commission they ask me, I only want to make my stories, since this won't be my main job!
Thanks, I'll learn that stuff then! :D
One thing: would it transfer that morph directly to 100%, or would I be able to slowly apply it with steps along the way? With a slider?
That raises a bunch of highly technical stuff I'm not going to go into. The short answer is that the script doesn't change presentation, so if the item transferred was a slider, it will be a slider after transfer. If it was a button or combobox it will be thar after. I skimmed the video, and I didn't see anything about advanced property creation, so anything you save ought to be a slider.
Thank you very much, I'll find a way! :D
Requesting a step-by-step tutorial since i'm not seeing any G3 Morphs to transfer to G8 when they are both in the scene. Thanks.
Playing around with this some more, I've used Blender to tidy up a couple of tiny niggles in the Lekkulion morph I transferred before - GenNext took an exceptional stab at the very challenging task of morphing away a finger from each hand and two toes from each foot, but the the transfer was just imprecise enough to leave some small scars that I wanted to remove. (However, I emphasise, morphing away a finger entirely is a much tougher task than trying to match normal changes in the shape, which is part of why I picked this morph as a test).
As such, I've started trying to port "Kate", the gorgon character I based on the morph, to G8F. It's only a rough attempt for now as I don't actually have the proper recipe for the G3 version of the character on this laptop (and so I'm mostly guessing), but it's allowed me to experiment more with my methods to transfer HD information between figures. (Hopefully something I'll be able to share the method for once I've refined the process).
Apologies for it being a fairly crude and simple render, I'm still on a fairly low powered laptop.
ok if not ask too much someone which already using the addon could provide a proper full noob beginner tutorial step by step from install to the convertion point???
When you say "addon" are meaning there's an add-on to the script or are you referring to the script itself? I've heard the term "addon" bandied about on here a few times as of late and I feel like I'm behind the curve somewhat.
yeah i mean the script, is really hard how to proper call it, normally this type of script i see being called addon or mod in others places then is complicated know what to call him here.
your script freezes at %27
Bummer, I thought I found a solution for a replacement for GenX but the script freezes after %27. Can you please help me?
srry i not tried yet use this script yet, then i can't help for now.
hey guys going back to my "crossgender" talk back, here my first attempt to make a "female reptilian and i can say which it worked really nice:
the only issues i get where on the tail, because the tails is a "male acessore" and i used the autofit on it and the other issue i noticed was some poses with the hands, like the fingers streching too much but overal, the transfer was almost a sucess, to make the repitilian "more round and big breast" i've used victoria 6 body as base, but i'm planning to use the true genesis 2 female body as mold base then add the body later, because when i was making the morph for head and body it ended a little bugged because the head also morphed the body a little more due to victoria morph but i'm planning to fix it later, if everything works fine then it's really possible to make a cross gender, even without need to use teh xgen script, i did that following the tutorial video someone posted few pages ago and this is a full female character which can use any "female morph" or cloth for genesis 2, soon i'm fix the lizard i will get my hands on the minotaur to test it too, if everything goes as planned then it can be done with any genesis from 2 to 8, the only issue would be which for the "texture" you would need to use a swap uv addon from here for genesis 3 and 8 characters, genesis 2 looks like don't have that issue since it's seens which both male and female share exactly the same uv form, then you can use a male texutere in female character and the opposite while g3 and 8 would need a addon from here to work(well so far at last the lizard base male texture can be used without any trouble for a female character).
It's a known issue: https://github.com/ArchitectMCP/GenNext/issues/1
I've not been able to test the new script much, but I THINK it might have something to do with the folder in "data" >> "Architect" >> "GenNext" >> "Holding" >> "Objs" - I think if you remove everything from that folder except the "null.gnxt" that seems to do the trick as far as getting it to go past 27%.
Every morph one tries to transfer puts Objs there and that seems to keep the script from going forward with the next morph transfer. That's just my guess though, as it seemed to work better once I cleared out the Objs from that "Holding >> Objs" folder and just left the null.gnxt file there and nothing else. One would have to clear that folder of everything except for "null.gnxt" after every morph transfer.
@Divamakeup - I saw your tip on Github and tried it, and didn't have any luck :( I've only been able to have it run successfully once or twice for the entire figure (head & body), but mostly it's worked for just the head. I'm really excited at the possibilities though! :)
The most likely reason for the current script to freeze at 27% is that you had a previous transfer and didn't clear the scene. If you attempt to do two transfers in a row (whether the first worked or not) it will fail, because the objects it used the first time interfere with the process.
At present, the script doesn't remove those for you because it can be helpful to determine the cause of failure to have those objects available. There are a whole lot of fiddly steps involved in getting this thing to do the thing, and tthere's no way to record the state of those steps except to look at the objects.
Bear in mind, this is not a working product. It's an open source project to reach a working product. If you have an issue that you want me to resolve, that issue needs to be on the Git. Otherwise, I'll assume you want advice from the community, and let them handle it.
Would probably help him more if you put this on GitHub :)
Laurie
The script doesn't currently support Genesis 1 or 2. That will happen when I figure some other things out.
When do you change the Bake Mode? Is it default(no bake) unless it's a base character (like Michael 7), or always change it off of default?
It depends on what you are trying to do.
Bake mode is off when transfering JCMs, MCMs, partitial shape morphs (e.g. long nails, nose 01, etc), and any morph that you DO NOT want to look exactly as it does on the source figure (e.g Star 2 to G3M to make a male version. You don't bake). Bake is on whenever you want to create a nigh exact match between the the original and the transfer (e.g Moving M6 to G3M and having the sampe dial in correctly with no additional steps, or transfering M7 to G3F and having G3F turn into a male shape, not a buff female).
The term bake is derived from general 3D where you take something that is generated manually or procedurally, and Bake it to a format where it no longer takes much effort to generate. For example, you can build a material with no textures at all, and make it look real, but the result is usually expensive to compute. So you bake the results into diffuse maps, specular maps, bump maps, normal maps, and you can then apply that to a simplified model, and save a bunch of time and electrons in rendering it.
Similar, you can bake the shape to include all the stuff that it had originally, or you can not bake it, which will typically require you to do manual fixes, and or get a copy of the original figure's shape and dail that in manually.
The reason you don't bake all of those things listed as no bake, even though it might mean results that need fixing, is that baking impacts the whole model. Say uo transfer nose 01 from G2F to G3F, and you don't think it looks as good, as the original, so you do it again, but with bake turned on. Well, you will get a nose 01 that looks very like the original, but the rest of G3F will shift to the shape of G2F. Because baking impacts the whole figures, excepty when the head and body options are enabled, and then it impacts the whole head and the whole body respectively. It would be impossible to put together a computationally reasonable way to do the head/body thing for arbitrary body parts because the figures don't line up exactly. So even if I could bake G2F's shape only into the nose (there is a way to do so, but the results really, really suck and) the nose would end up moving out of place, because G2F's nose is lowere than G8/3Fs because they are toller than G2F (and way taller than Genesis). So you don't bake JCMs because if you do, the figure will change shape every time you bend the referenced joint. You don't bake MCMs because--say you've activated Star 2 head and thus the eye closed MCMs--the controlling figure's (Star 2 in this case) shape will be doubled up. Once from the active shape, and once from the MCM. And this will continue to build with each MCM (i.e. both eyes closed mean 300% Star 2 shape, and so on).
So, for example, Elijah 7 to G8M, good idea to bake? Or try both and see which works better?
FWSA Seth for Elijah 7 don't bake because it's a shape based off of Elijah 7.
I'm just making sure I'm following your logic in regards to the script. I've done work in SQL, Oracle, etc., so I'd like to know I'm following the author's thoughts where the process is concerned.