Morphs from G3 to G8

1444547495071

Comments

  • I tried the script.  But It wouldn't run.  Looked in the log and just found the following.

    "2018-02-18 18:28:29.970 Error in script execution: Z://Scripts/Morph Transfer Prototype/PrototypeVerbose.dse"

    Now I have to ask if things are hard coded in the script to only work in the default location?  I do have both the script and G3F in the first library listed in the content library tab.  

    The script must be installed correctly, yes. Correctly being is the first library and in the standard Daz libtrary format.

    Well my main (and only) Library is the Z drive.  I have it on a server so I can access it from multiple computers.  If it needs to be on the same drive as the program that could be problematic.

  • It doesn't need to be on the same drive as the program.

  • barbultbarbult Posts: 24,755

    I have been trying to go over all these posts and have gotten more and more confused with what the current best practices for transferring a character's morph from G3 to G8.  I tried the process from Redz that I found here and initially was overjoyed when it worked but then I posed her.  She had alien finger syndrome.  So I came back and started reading through but after a while, my eyes became crossed and things that previously made sense started to not.  So my question is what are the Current best practices when doing such a Morph transfer and what are the most updated files?  I'm sure if it was possible these would have a post-it right at the top of the thread but without that, I figured I would just ask what the most common and successful process has been? Especially for bodies that aren't the same dimensions as the base (Mine seems to be a little shorter in the torso for the one I have been testing.)

    There are a bunch of factors here, but the short form of it is this:

    The manual methods are called morph transfer. They aren't. Not really. They are morph creation. And morph creation requires a lot more than just getting the shape.

    I've considered getting into the long form, for a minute at least, but I tend to be very long when being long. Hopefully, I can sum up.

    Basically, the reason people can sell morphs is that making them so that they work well is not a fast and easy process. It takes an amount of art, and a larger amount of often tedious work. (Not always, of course, but mostly.) What manual transfers do is skip the art part (you are, one could say, transfering the art part between figures) but it does nothing about tedious work part.

    What you call alien finger is simply the fact the figure bones don't line up. Because the "morph" on the original figure had attitional data to tell the figure where the bones need to be. You can google Daz Studio adjust rigging to shape to find out how that works, and you'll get fast decent results (I don't mean to make this sound impossible, because it is not). But there are human element aspects that can't be just ignored if you want the figure to work well. Several face bones just don't like to line up correctly when adjust rigging is used. If the final shape is too different from the base shape, adjust rigging will not work at all, at least with default settings, and so on.

    In the case of your pictured issues, I would assume the core issue is that adjust rigging just wasn't done. Doing so will solve the gross movement issues in the fingers, but will probably add issues to the face. Studying how to use the rigging tools in Studio will help with that. If you don't mind stuff in the face bones being a bit off, then you can probably get by with just that. You can't skip it though, and you can't leave the face bones out. Sometimes you can, but the difference in figure height means all bones have to be moved, and the auto alignment calculations always get the face a bit wrong.

    I tried the script.  But It wouldn't run.  Looked in the log and just found the following.

    "2018-02-18 18:28:29.970 Error in script execution: Z://Scripts/Morph Transfer Prototype/PrototypeVerbose.dse"

    Now I have to ask if things are hard coded in the script to only work in the default location?  I do have both the script and G3F in the first library listed in the content library tab.  

    The script must be installed correctly, yes. Correctly being is the first library and in the standard Daz libtrary format.

     

    barbult said:

    Since everything seems to be working well for me now, I stopped using PrototypeVerbose.dse and started using Prototype.dse.

    I get an error when running Prototype.dse that I do not get when running PrototypeVerbose.dse. The error is WARNING: Script Error: Line 1370. I was transferring Tyrone from G8M to G3M, but I don't think it is related to the specific character, because I saw this same issue on another transfer with Prototype.dse, too.

    Even though I got the error on Prototype.dse, the morphs were transferred to G3M and seemed to work. So I deleted the whole folder of Tyrone morphs from G3M and transferred again with PrototypeVerbose.dse to capture log details of the error, but no error occurred. I am attaching both logs. 

    P.S. I downloaded again to be sure I have the latest versions. wink

    There's pasting error in prototype, it seems. I'm amazed it works at all. I'll try to have a correction soonest.

    Thanks. I'll try to remember to download it when the time comes. blushwink

  • I have been trying to go over all these posts and have gotten more and more confused with what the current best practices for transferring a character's morph from G3 to G8.  I tried the process from Redz that I found here and initially was overjoyed when it worked but then I posed her.  She had alien finger syndrome.  So I came back and started reading through but after a while, my eyes became crossed and things that previously made sense started to not.  So my question is what are the Current best practices when doing such a Morph transfer and what are the most updated files?  I'm sure if it was possible these would have a post-it right at the top of the thread but without that, I figured I would just ask what the most common and successful process has been? Especially for bodies that aren't the same dimensions as the base (Mine seems to be a little shorter in the torso for the one I have been testing.)

    There are a bunch of factors here, but the short form of it is this:

    The manual methods are called morph transfer. They aren't. Not really. They are morph creation. And morph creation requires a lot more than just getting the shape.

    I've considered getting into the long form, for a minute at least, but I tend to be very long when being long. Hopefully, I can sum up.

    Basically, the reason people can sell morphs is that making them so that they work well is not a fast and easy process. It takes an amount of art, and a larger amount of often tedious work. (Not always, of course, but mostly.) What manual transfers do is skip the art part (you are, one could say, transfering the art part between figures) but it does nothing about tedious work part.

    What you call alien finger is simply the fact the figure bones don't line up. Because the "morph" on the original figure had attitional data to tell the figure where the bones need to be. You can google Daz Studio adjust rigging to shape to find out how that works, and you'll get fast decent results (I don't mean to make this sound impossible, because it is not). But there are human element aspects that can't be just ignored if you want the figure to work well. Several face bones just don't like to line up correctly when adjust rigging is used. If the final shape is too different from the base shape, adjust rigging will not work at all, at least with default settings, and so on.

    In the case of your pictured issues, I would assume the core issue is that adjust rigging just wasn't done. Doing so will solve the gross movement issues in the fingers, but will probably add issues to the face. Studying how to use the rigging tools in Studio will help with that. If you don't mind stuff in the face bones being a bit off, then you can probably get by with just that. You can't skip it though, and you can't leave the face bones out. Sometimes you can, but the difference in figure height means all bones have to be moved, and the auto alignment calculations always get the face a bit wrong.

    I tried the script.  But It wouldn't run.  Looked in the log and just found the following.

    "2018-02-18 18:28:29.970 Error in script execution: Z://Scripts/Morph Transfer Prototype/PrototypeVerbose.dse"

    Now I have to ask if things are hard coded in the script to only work in the default location?  I do have both the script and G3F in the first library listed in the content library tab.  

    The script must be installed correctly, yes. Correctly being is the first library and in the standard Daz libtrary format.

     

    barbult said:

    Since everything seems to be working well for me now, I stopped using PrototypeVerbose.dse and started using Prototype.dse.

    I get an error when running Prototype.dse that I do not get when running PrototypeVerbose.dse. The error is WARNING: Script Error: Line 1370. I was transferring Tyrone from G8M to G3M, but I don't think it is related to the specific character, because I saw this same issue on another transfer with Prototype.dse, too.

    Even though I got the error on Prototype.dse, the morphs were transferred to G3M and seemed to work. So I deleted the whole folder of Tyrone morphs from G3M and transferred again with PrototypeVerbose.dse to capture log details of the error, but no error occurred. I am attaching both logs. 

    P.S. I downloaded again to be sure I have the latest versions. wink

    There's pasting error in prototype, it seems. I'm amazed it works at all. I'll try to have a correction soonest.

    Ok So if I am reading this right there is an issue with the Script which make it so that the creator of said Script is surprised it works for anyone, and for me I am one that it doesn't work for and no useful log information to pinpoint an issue is created.

    If this is the case is there an alternative method that is also generally successful other than Redz' early method, which did seem to work for some but I'm not counted in that number.

    I'm willing to try many things but I just have to admit that trying to track steps and processes over multiple different posts seems to get me more confused.

  • barbultbarbult Posts: 24,755

    PrototypeVerbose script works fine for me. It is the Prototype script that has the problem. Both scripts are included in the download zip file. Just use PrototypeVerbose for now, would be my advice. All necessary instructions are repeated several times, from several people's point of view, in the very recent pages of this thread. 

  • Singular BluesSingular Blues Posts: 737
    edited February 2018

    I have been trying to go over all these posts and have gotten more and more confused with what the current best practices for transferring a character's morph from G3 to G8.  I tried the process from Redz that I found here and initially was overjoyed when it worked but then I posed her.  She had alien finger syndrome.  So I came back and started reading through but after a while, my eyes became crossed and things that previously made sense started to not.  So my question is what are the Current best practices when doing such a Morph transfer and what are the most updated files?  I'm sure if it was possible these would have a post-it right at the top of the thread but without that, I figured I would just ask what the most common and successful process has been? Especially for bodies that aren't the same dimensions as the base (Mine seems to be a little shorter in the torso for the one I have been testing.)

    There are a bunch of factors here, but the short form of it is this:

    The manual methods are called morph transfer. They aren't. Not really. They are morph creation. And morph creation requires a lot more than just getting the shape.

    I've considered getting into the long form, for a minute at least, but I tend to be very long when being long. Hopefully, I can sum up.

    Basically, the reason people can sell morphs is that making them so that they work well is not a fast and easy process. It takes an amount of art, and a larger amount of often tedious work. (Not always, of course, but mostly.) What manual transfers do is skip the art part (you are, one could say, transfering the art part between figures) but it does nothing about tedious work part.

    What you call alien finger is simply the fact the figure bones don't line up. Because the "morph" on the original figure had attitional data to tell the figure where the bones need to be. You can google Daz Studio adjust rigging to shape to find out how that works, and you'll get fast decent results (I don't mean to make this sound impossible, because it is not). But there are human element aspects that can't be just ignored if you want the figure to work well. Several face bones just don't like to line up correctly when adjust rigging is used. If the final shape is too different from the base shape, adjust rigging will not work at all, at least with default settings, and so on.

    In the case of your pictured issues, I would assume the core issue is that adjust rigging just wasn't done. Doing so will solve the gross movement issues in the fingers, but will probably add issues to the face. Studying how to use the rigging tools in Studio will help with that. If you don't mind stuff in the face bones being a bit off, then you can probably get by with just that. You can't skip it though, and you can't leave the face bones out. Sometimes you can, but the difference in figure height means all bones have to be moved, and the auto alignment calculations always get the face a bit wrong.

    I tried the script.  But It wouldn't run.  Looked in the log and just found the following.

    "2018-02-18 18:28:29.970 Error in script execution: Z://Scripts/Morph Transfer Prototype/PrototypeVerbose.dse"

    Now I have to ask if things are hard coded in the script to only work in the default location?  I do have both the script and G3F in the first library listed in the content library tab.  

    The script must be installed correctly, yes. Correctly being is the first library and in the standard Daz libtrary format.

     

    barbult said:

    Since everything seems to be working well for me now, I stopped using PrototypeVerbose.dse and started using Prototype.dse.

    I get an error when running Prototype.dse that I do not get when running PrototypeVerbose.dse. The error is WARNING: Script Error: Line 1370. I was transferring Tyrone from G8M to G3M, but I don't think it is related to the specific character, because I saw this same issue on another transfer with Prototype.dse, too.

    Even though I got the error on Prototype.dse, the morphs were transferred to G3M and seemed to work. So I deleted the whole folder of Tyrone morphs from G3M and transferred again with PrototypeVerbose.dse to capture log details of the error, but no error occurred. I am attaching both logs. 

    P.S. I downloaded again to be sure I have the latest versions. wink

    There's pasting error in prototype, it seems. I'm amazed it works at all. I'll try to have a correction soonest.

    Ok So if I am reading this right there is an issue with the Script which make it so that the creator of said Script is surprised it works for anyone, and for me I am one that it doesn't work for and no useful log information to pinpoint an issue is created.

    If this is the case is there an alternative method that is also generally successful other than Redz' early method, which did seem to work for some but I'm not counted in that number.

    I'm willing to try many things but I just have to admit that trying to track steps and processes over multiple different posts seems to get me more confused.

    This is an alpha test. It's not really meant to be not confusing or easy.

    I appreciate people who get that, and work at it. They're helping me make it better. They help me find little errors.

    I'm also under araft of personal problems and I just don't have a lot of time or energy for "fix this for me."

    I was able to see the root of the pasting error because the was a whole log file attached. 

    You gave me one incomplete line of log.

    Mayhaps that all there is. But I can usually learn a lot from what isn't in a log, and how it isn't there. For a third time, data, data, data. I cannot make bricks without clay. I have been doing troubleshooting and support across two scripts and helping people with unrelated issues for while now, and I've hit the wall. I'm in pain. I'm not particularly happy, but I am trying to help. But I'm only going to help to the extent I am helped to help. You give me low detail issues, I give low detail responses. You give data, data, data, (specifically, the data I asked for, ProtoypeVerbose runs when there's an issues, and log, log, log. Screenshots of distortions in in textured wireframe, etc) and I will overload you with answers.

    It's kinda "you get what you pay for."

    EDIT: To be abundantly clear, a Verbose run after a failure, in this case, would provide a vital clue, since one script is broken and one is not. However, the short form of your implied "is this causing my issue" is "probably not." It's possible, but surprised it works or not, it does work. I've run it, and so did barbult. 

    Post edited by Singular Blues on
  • 3dOutlaw3dOutlaw Posts: 2,480

    @Singular Blues just tried this, after lurking for a while, and it worked great!  Aiko7 onto G8F worked like a champ.  yes  Great job!

    I think you mentioned you were possibly going to include G2F or Genesis in a future product?  Would be interested, as they have my goto body shapes for Anime styles at the moment.

     

  • I have been trying to go over all these posts and have gotten more and more confused with what the current best practices for transferring a character's morph from G3 to G8.  I tried the process from Redz that I found here and initially was overjoyed when it worked but then I posed her.  She had alien finger syndrome.  So I came back and started reading through but after a while, my eyes became crossed and things that previously made sense started to not.  So my question is what are the Current best practices when doing such a Morph transfer and what are the most updated files?  I'm sure if it was possible these would have a post-it right at the top of the thread but without that, I figured I would just ask what the most common and successful process has been? Especially for bodies that aren't the same dimensions as the base (Mine seems to be a little shorter in the torso for the one I have been testing.)

    There are a bunch of factors here, but the short form of it is this:

    The manual methods are called morph transfer. They aren't. Not really. They are morph creation. And morph creation requires a lot more than just getting the shape.

    I've considered getting into the long form, for a minute at least, but I tend to be very long when being long. Hopefully, I can sum up.

    Basically, the reason people can sell morphs is that making them so that they work well is not a fast and easy process. It takes an amount of art, and a larger amount of often tedious work. (Not always, of course, but mostly.) What manual transfers do is skip the art part (you are, one could say, transfering the art part between figures) but it does nothing about tedious work part.

    What you call alien finger is simply the fact the figure bones don't line up. Because the "morph" on the original figure had attitional data to tell the figure where the bones need to be. You can google Daz Studio adjust rigging to shape to find out how that works, and you'll get fast decent results (I don't mean to make this sound impossible, because it is not). But there are human element aspects that can't be just ignored if you want the figure to work well. Several face bones just don't like to line up correctly when adjust rigging is used. If the final shape is too different from the base shape, adjust rigging will not work at all, at least with default settings, and so on.

    In the case of your pictured issues, I would assume the core issue is that adjust rigging just wasn't done. Doing so will solve the gross movement issues in the fingers, but will probably add issues to the face. Studying how to use the rigging tools in Studio will help with that. If you don't mind stuff in the face bones being a bit off, then you can probably get by with just that. You can't skip it though, and you can't leave the face bones out. Sometimes you can, but the difference in figure height means all bones have to be moved, and the auto alignment calculations always get the face a bit wrong.

    I tried the script.  But It wouldn't run.  Looked in the log and just found the following.

    "2018-02-18 18:28:29.970 Error in script execution: Z://Scripts/Morph Transfer Prototype/PrototypeVerbose.dse"

    Now I have to ask if things are hard coded in the script to only work in the default location?  I do have both the script and G3F in the first library listed in the content library tab.  

    The script must be installed correctly, yes. Correctly being is the first library and in the standard Daz libtrary format.

     

    barbult said:

    Since everything seems to be working well for me now, I stopped using PrototypeVerbose.dse and started using Prototype.dse.

    I get an error when running Prototype.dse that I do not get when running PrototypeVerbose.dse. The error is WARNING: Script Error: Line 1370. I was transferring Tyrone from G8M to G3M, but I don't think it is related to the specific character, because I saw this same issue on another transfer with Prototype.dse, too.

    Even though I got the error on Prototype.dse, the morphs were transferred to G3M and seemed to work. So I deleted the whole folder of Tyrone morphs from G3M and transferred again with PrototypeVerbose.dse to capture log details of the error, but no error occurred. I am attaching both logs. 

    P.S. I downloaded again to be sure I have the latest versions. wink

    There's pasting error in prototype, it seems. I'm amazed it works at all. I'll try to have a correction soonest.

    Ok So if I am reading this right there is an issue with the Script which make it so that the creator of said Script is surprised it works for anyone, and for me I am one that it doesn't work for and no useful log information to pinpoint an issue is created.

    If this is the case is there an alternative method that is also generally successful other than Redz' early method, which did seem to work for some but I'm not counted in that number.

    I'm willing to try many things but I just have to admit that trying to track steps and processes over multiple different posts seems to get me more confused.

    This is an alpha test. It's not really meant to be not confusing or easy.

    I appreciate people who get that, and work at it. They're helping me make it better. They help me find little errors.

    I'm also under araft of personal problems and I just don't have a lot of time or energy for "fix this for me."

    I was able to see the root of the pasting error because the was a whole log file attached. 

    You gave me one incomplete line of log.

    Mayhaps that all there is. But I can usually learn a lot from what isn't in a log, and how it isn't there. For a third time, data, data, data. I cannot make bricks without clay. I have been doing troubleshooting and support across two scripts and helping people with unrelated issues for while now, and I've hit the wall. I'm in pain. I'm not particularly happy, but I am trying to help. But I'm only going to help to the extent I am helped to help. You give me low detail issues, I give low detail responses. You give data, data, data, (specifically, the data I asked for, ProtoypeVerbose runs when there's an issues, and log, log, log. Screenshots of distortions in in textured wireframe, etc) and I will overload you with answers.

    It's kinda "you get what you pay for."

    EDIT: To be abundantly clear, a Verbose run after a failure, in this case, would provide a vital clue, since one script is broken and one is not. However, the short form of your implied "is this causing my issue" is "probably not." It's possible, but surprised it works or not, it does work. I've run it, and so did barbult. 

    Well I went back and made sure to document everything.

    My process was to load up the figure I wanted to try and get moved over.  I went through all the used Parameters and marked them to be favorites.  I then Zero'd the character to get it back into the original state.  At this point I did try to save the scene to reload it but found that the favorites are temporary and don't even save with a scene so I had to do it all over again.

    Once everything was zero'd and I was ready to run the verbose script I opened up the log file and cleared it out so that the output was purely to do with the script.  I ran the verbose script and got a popup error.  I am attaching a screenshot of the error that came up.  I am also attaching what is in the log. This is the same error I saw before though this is a different computer with it's only Library on an external drive.  The Prototype script I am using was downloaded today.

     

    txt
    txt
    Prototype Verbose log.txt
    230B
    Prototype Verbose Error.PNG
    526 x 364 - 19K
  • barbultbarbult Posts: 24,755

    I have been trying to go over all these posts and have gotten more and more confused with what the current best practices for transferring a character's morph from G3 to G8.  I tried the process from Redz that I found here and initially was overjoyed when it worked but then I posed her.  She had alien finger syndrome.  So I came back and started reading through but after a while, my eyes became crossed and things that previously made sense started to not.  So my question is what are the Current best practices when doing such a Morph transfer and what are the most updated files?  I'm sure if it was possible these would have a post-it right at the top of the thread but without that, I figured I would just ask what the most common and successful process has been? Especially for bodies that aren't the same dimensions as the base (Mine seems to be a little shorter in the torso for the one I have been testing.)

    There are a bunch of factors here, but the short form of it is this:

    The manual methods are called morph transfer. They aren't. Not really. They are morph creation. And morph creation requires a lot more than just getting the shape.

    I've considered getting into the long form, for a minute at least, but I tend to be very long when being long. Hopefully, I can sum up.

    Basically, the reason people can sell morphs is that making them so that they work well is not a fast and easy process. It takes an amount of art, and a larger amount of often tedious work. (Not always, of course, but mostly.) What manual transfers do is skip the art part (you are, one could say, transfering the art part between figures) but it does nothing about tedious work part.

    What you call alien finger is simply the fact the figure bones don't line up. Because the "morph" on the original figure had attitional data to tell the figure where the bones need to be. You can google Daz Studio adjust rigging to shape to find out how that works, and you'll get fast decent results (I don't mean to make this sound impossible, because it is not). But there are human element aspects that can't be just ignored if you want the figure to work well. Several face bones just don't like to line up correctly when adjust rigging is used. If the final shape is too different from the base shape, adjust rigging will not work at all, at least with default settings, and so on.

    In the case of your pictured issues, I would assume the core issue is that adjust rigging just wasn't done. Doing so will solve the gross movement issues in the fingers, but will probably add issues to the face. Studying how to use the rigging tools in Studio will help with that. If you don't mind stuff in the face bones being a bit off, then you can probably get by with just that. You can't skip it though, and you can't leave the face bones out. Sometimes you can, but the difference in figure height means all bones have to be moved, and the auto alignment calculations always get the face a bit wrong.

    I tried the script.  But It wouldn't run.  Looked in the log and just found the following.

    "2018-02-18 18:28:29.970 Error in script execution: Z://Scripts/Morph Transfer Prototype/PrototypeVerbose.dse"

    Now I have to ask if things are hard coded in the script to only work in the default location?  I do have both the script and G3F in the first library listed in the content library tab.  

    The script must be installed correctly, yes. Correctly being is the first library and in the standard Daz libtrary format.

     

    barbult said:

    Since everything seems to be working well for me now, I stopped using PrototypeVerbose.dse and started using Prototype.dse.

    I get an error when running Prototype.dse that I do not get when running PrototypeVerbose.dse. The error is WARNING: Script Error: Line 1370. I was transferring Tyrone from G8M to G3M, but I don't think it is related to the specific character, because I saw this same issue on another transfer with Prototype.dse, too.

    Even though I got the error on Prototype.dse, the morphs were transferred to G3M and seemed to work. So I deleted the whole folder of Tyrone morphs from G3M and transferred again with PrototypeVerbose.dse to capture log details of the error, but no error occurred. I am attaching both logs. 

    P.S. I downloaded again to be sure I have the latest versions. wink

    There's pasting error in prototype, it seems. I'm amazed it works at all. I'll try to have a correction soonest.

    Ok So if I am reading this right there is an issue with the Script which make it so that the creator of said Script is surprised it works for anyone, and for me I am one that it doesn't work for and no useful log information to pinpoint an issue is created.

    If this is the case is there an alternative method that is also generally successful other than Redz' early method, which did seem to work for some but I'm not counted in that number.

    I'm willing to try many things but I just have to admit that trying to track steps and processes over multiple different posts seems to get me more confused.

    This is an alpha test. It's not really meant to be not confusing or easy.

    I appreciate people who get that, and work at it. They're helping me make it better. They help me find little errors.

    I'm also under araft of personal problems and I just don't have a lot of time or energy for "fix this for me."

    I was able to see the root of the pasting error because the was a whole log file attached. 

    You gave me one incomplete line of log.

    Mayhaps that all there is. But I can usually learn a lot from what isn't in a log, and how it isn't there. For a third time, data, data, data. I cannot make bricks without clay. I have been doing troubleshooting and support across two scripts and helping people with unrelated issues for while now, and I've hit the wall. I'm in pain. I'm not particularly happy, but I am trying to help. But I'm only going to help to the extent I am helped to help. You give me low detail issues, I give low detail responses. You give data, data, data, (specifically, the data I asked for, ProtoypeVerbose runs when there's an issues, and log, log, log. Screenshots of distortions in in textured wireframe, etc) and I will overload you with answers.

    It's kinda "you get what you pay for."

    EDIT: To be abundantly clear, a Verbose run after a failure, in this case, would provide a vital clue, since one script is broken and one is not. However, the short form of your implied "is this causing my issue" is "probably not." It's possible, but surprised it works or not, it does work. I've run it, and so did barbult. 

    Well I went back and made sure to document everything.

    My process was to load up the figure I wanted to try and get moved over.  I went through all the used Parameters and marked them to be favorites.  I then Zero'd the character to get it back into the original state.  At this point I did try to save the scene to reload it but found that the favorites are temporary and don't even save with a scene so I had to do it all over again.

    Once everything was zero'd and I was ready to run the verbose script I opened up the log file and cleared it out so that the output was purely to do with the script.  I ran the verbose script and got a popup error.  I am attaching a screenshot of the error that came up.  I am also attaching what is in the log. This is the same error I saw before though this is a different computer with it's only Library on an external drive.  The Prototype script I am using was downloaded today.

     

    Right from the beginning, you have made a mistake in following the instructions. You are supposed to load the unmodified base character (Genesis 8 Female or Genesis 3 Female, for example), not a "character". After loading the base character, do not make any changes to shape or posing. In Parameters pane, mark a morph for the character you want to transfer as a favorite, but do NOT dial the character in. 

  • edited February 2018
    barbult said:

    I have been trying to go over all these posts and have gotten more and more confused with what the current best practices for transferring a character's morph from G3 to G8.  I tried the process from Redz that I found here and initially was overjoyed when it worked but then I posed her.  She had alien finger syndrome.  So I came back and started reading through but after a while, my eyes became crossed and things that previously made sense started to not.  So my question is what are the Current best practices when doing such a Morph transfer and what are the most updated files?  I'm sure if it was possible these would have a post-it right at the top of the thread but without that, I figured I would just ask what the most common and successful process has been? Especially for bodies that aren't the same dimensions as the base (Mine seems to be a little shorter in the torso for the one I have been testing.)

    There are a bunch of factors here, but the short form of it is this:

    The manual methods are called morph transfer. They aren't. Not really. They are morph creation. And morph creation requires a lot more than just getting the shape.

    I've considered getting into the long form, for a minute at least, but I tend to be very long when being long. Hopefully, I can sum up.

    Basically, the reason people can sell morphs is that making them so that they work well is not a fast and easy process. It takes an amount of art, and a larger amount of often tedious work. (Not always, of course, but mostly.) What manual transfers do is skip the art part (you are, one could say, transfering the art part between figures) but it does nothing about tedious work part.

    What you call alien finger is simply the fact the figure bones don't line up. Because the "morph" on the original figure had attitional data to tell the figure where the bones need to be. You can google Daz Studio adjust rigging to shape to find out how that works, and you'll get fast decent results (I don't mean to make this sound impossible, because it is not). But there are human element aspects that can't be just ignored if you want the figure to work well. Several face bones just don't like to line up correctly when adjust rigging is used. If the final shape is too different from the base shape, adjust rigging will not work at all, at least with default settings, and so on.

    In the case of your pictured issues, I would assume the core issue is that adjust rigging just wasn't done. Doing so will solve the gross movement issues in the fingers, but will probably add issues to the face. Studying how to use the rigging tools in Studio will help with that. If you don't mind stuff in the face bones being a bit off, then you can probably get by with just that. You can't skip it though, and you can't leave the face bones out. Sometimes you can, but the difference in figure height means all bones have to be moved, and the auto alignment calculations always get the face a bit wrong.

    I tried the script.  But It wouldn't run.  Looked in the log and just found the following.

    "2018-02-18 18:28:29.970 Error in script execution: Z://Scripts/Morph Transfer Prototype/PrototypeVerbose.dse"

    Now I have to ask if things are hard coded in the script to only work in the default location?  I do have both the script and G3F in the first library listed in the content library tab.  

    The script must be installed correctly, yes. Correctly being is the first library and in the standard Daz libtrary format.

     

    barbult said:

    Since everything seems to be working well for me now, I stopped using PrototypeVerbose.dse and started using Prototype.dse.

    I get an error when running Prototype.dse that I do not get when running PrototypeVerbose.dse. The error is WARNING: Script Error: Line 1370. I was transferring Tyrone from G8M to G3M, but I don't think it is related to the specific character, because I saw this same issue on another transfer with Prototype.dse, too.

    Even though I got the error on Prototype.dse, the morphs were transferred to G3M and seemed to work. So I deleted the whole folder of Tyrone morphs from G3M and transferred again with PrototypeVerbose.dse to capture log details of the error, but no error occurred. I am attaching both logs. 

    P.S. I downloaded again to be sure I have the latest versions. wink

    There's pasting error in prototype, it seems. I'm amazed it works at all. I'll try to have a correction soonest.

    Ok So if I am reading this right there is an issue with the Script which make it so that the creator of said Script is surprised it works for anyone, and for me I am one that it doesn't work for and no useful log information to pinpoint an issue is created.

    If this is the case is there an alternative method that is also generally successful other than Redz' early method, which did seem to work for some but I'm not counted in that number.

    I'm willing to try many things but I just have to admit that trying to track steps and processes over multiple different posts seems to get me more confused.

    This is an alpha test. It's not really meant to be not confusing or easy.

    I appreciate people who get that, and work at it. They're helping me make it better. They help me find little errors.

    I'm also under araft of personal problems and I just don't have a lot of time or energy for "fix this for me."

    I was able to see the root of the pasting error because the was a whole log file attached. 

    You gave me one incomplete line of log.

    Mayhaps that all there is. But I can usually learn a lot from what isn't in a log, and how it isn't there. For a third time, data, data, data. I cannot make bricks without clay. I have been doing troubleshooting and support across two scripts and helping people with unrelated issues for while now, and I've hit the wall. I'm in pain. I'm not particularly happy, but I am trying to help. But I'm only going to help to the extent I am helped to help. You give me low detail issues, I give low detail responses. You give data, data, data, (specifically, the data I asked for, ProtoypeVerbose runs when there's an issues, and log, log, log. Screenshots of distortions in in textured wireframe, etc) and I will overload you with answers.

    It's kinda "you get what you pay for."

    EDIT: To be abundantly clear, a Verbose run after a failure, in this case, would provide a vital clue, since one script is broken and one is not. However, the short form of your implied "is this causing my issue" is "probably not." It's possible, but surprised it works or not, it does work. I've run it, and so did barbult. 

    Well I went back and made sure to document everything.

    My process was to load up the figure I wanted to try and get moved over.  I went through all the used Parameters and marked them to be favorites.  I then Zero'd the character to get it back into the original state.  At this point I did try to save the scene to reload it but found that the favorites are temporary and don't even save with a scene so I had to do it all over again.

    Once everything was zero'd and I was ready to run the verbose script I opened up the log file and cleared it out so that the output was purely to do with the script.  I ran the verbose script and got a popup error.  I am attaching a screenshot of the error that came up.  I am also attaching what is in the log. This is the same error I saw before though this is a different computer with it's only Library on an external drive.  The Prototype script I am using was downloaded today.

     

    Right from the beginning, you have made a mistake in following the instructions. You are supposed to load the unmodified base character (Genesis 8 Female or Genesis 3 Female, for example), not a "character". After loading the base character, do not make any changes to shape or posing. In Parameters pane, mark a morph for the character you want to transfer as a favorite, but do NOT dial the character in. 

    Let me check if this is what I have to do it go in.  Note down all of the parameters used for a custom created character so several dozen.  Then start over in a new scene, load up G3F, which should have the same exact morphs loaded on it and since both are fully zero'd should be in the exact same position and have the exact same dialed parameters.  I am curious what is the functional difference?  This would be useful information in understanding how DazStudio works with its assets.

    Post edited by theweezel_c08014c91f on
  • Singular BluesSingular Blues Posts: 737
    edited February 2018

    Let me check if this is what I have to do it go in.  Note down all of the parameters used for a custom created character so several dozen.  Then start over in a new scene, load up G3F, which should have the same exact morphs loaded on it and since both are fully zero'd should be in the exact same position and have the exact same dialed parameters.  I am curious what is the functional difference?  This would be useful information in understanding how DazStudio works with its assets.

    That would be a natural thought. It's not what happens. The key point to this particular issue that the script relies on a bit of datat associated with properties.it is called assetUri. Unmodified, assetUri should resolve to the relative path of the file related to the property. (I simplify) when a property is modified, this changes, and can cause the the assetUri to return a fragment, or null.

    The actual shape and postion of the figure wouldn't matter otherwise. But the only time one can be sure all aspects of the figure are in unmodified state is when it loads. As of now, there are workarounds but I don't know if they all work.

    As to the reason the script does not work, I can't really help because you aren't sharing the logs.

    Remember that part where I specifically said, I can tell a lot by what isn't in a log? Well, if nothing is in a log I can't tell anything because the log is empty of all things. It's like saying "the murderer has never visited Jupiter." Well, that's everyone, so the murderer could be anyone. Similarly, I can't learn from anything by the contents or missing data in the log because you cleared everything out of the log. So anything that could be absent is absent, so anything that could be wrong might be the problem.

    In earlier issues I was able to see X was not a problem because if it had been, things would have been in the log BEFORE the script was run, indeed before the figures were done loading. Other times I was able to narrow down the issue because of what studio did when it shut down.

    If you give me a carefully sanitized log, you give me nothing.

    Post edited by Singular Blues on
  • Well I just checked.  I went through and on paper I noted down all of the morphs used, every last one.  Closed down and got a new scene and loaded up G3F into it fresh and new.  Then I went through my list and found each Parameter and favorited each one which was easy for this one as it only had 20 morphs used.  Once all were favorited and double checked I ran the Verbose script again.  The same error occured and the same two lines in the log were created.

    Now for @Singular Blues I really am sorry that there is no other errors that are showing.  If there was I could at least have a starting point to find if there is an issue on my own systems that is causing this.  And even though it isn't working for me I am thankful there are people like you out there who are willing to share the work you have done with others and help out lots of us in automating the process significantly and recducingthe possibility of human error.  I undersand you are going through a bad time and you should take care of you first and foremost just know that your work and you are appreciated. 

  • Let me check if this is what I have to do it go in.  Note down all of the parameters used for a custom created character so several dozen.  Then start over in a new scene, load up G3F, which should have the same exact morphs loaded on it and since both are fully zero'd should be in the exact same position and have the exact same dialed parameters.  I am curious what is the functional difference?  This would be useful information in understanding how DazStudio works with its assets.

    That would be a natural thought. It's not what happens. The key point to this particular issue that the script relies on a bit of datat associated with properties.it is called assetUri. Unmodified, assetUri should resolve to the relative path of the file related to the property. (I simplify) when a property is modified, this changes, and can cause the the assetUri to return a fragment, or null.

    The actual shape and postion of the figure wouldn't matter otherwise. But the only time one can be sure all aspects of the figure are in unmodified state is when it loads. As of now, there are workarounds but I don't know if they all work.

    As to the reason the script does not work, I can't really help because you aren't sharing the logs.

    Remember that part where I specifically said, I can tell a lot by what isn't in a log? Well, if nothing is in a log I can't tell anything because the log is empty of all things. It's like saying "the murderer has never visited Jupiter." Well, that's everyone, so the murderer could be anyone. Similarly, I can't learn from anything by the contents or missing data in the log because you cleared everything out of the log. So anything that could be absent is absent, so anything that could be wrong might be the problem.

    In earlier issues I was able to see X was not a problem because if it had been, things would have been in the log BEFORE the script was run, indeed before the figures were done loading. Other times I was able to narrow down the issue because of what studio did when it shut down.

    If you give me a carefully sanitized log, you give me nothing.

    Attached are complete logs.

    txt
    txt
    Prototype Verbose log.txt
    106K
  • Singular BluesSingular Blues Posts: 737
    edited February 2018

    You didn't load the target figure.

    presently the script only supports G3 and G8. But that's 4 figures. It only knows what figure you want to transfer from and what to transfer to by what is loaded and selected.

    Based on you  log, you loaded G3F and ran the script.

    You are supposed to load the target, load the source, (or vice versa, shouldn't matter what order) select the source, CTRL select the target, and then run the script. The order of selection tell the script which target is source and which is target. The favorites tell the script what products to trasnfer.

    EDIT: I'd expect a different error. that alone should prevent the script running an should cause the script to return a specific error. But it is still the first, most obvious, issue.

    Post edited by Singular Blues on
  • You didn't load the target figure.

    presently the script only supports G3 and G8. But that's 4 figures. It only knows what figure you want to transfer from and what to transfer to by what is loaded and selected.

    Based on you  log, you loaded G3F and ran the script.

    You are supposed to load the target, load the source, (or vice versa, shouldn't matter what order) select the source, CTRL select the target, and then run the script. The order of selection tell the script which target is source and which is target. The favorites tell the script what products to trasnfer.

    Ah ha.  Well that makes sense.  I was following the instructions given by @nonesuch00 which say to run the script then load the G8F.  I will try again the right way and check it out.

  • You didn't load the target figure.

    presently the script only supports G3 and G8. But that's 4 figures. It only knows what figure you want to transfer from and what to transfer to by what is loaded and selected.

    Based on you  log, you loaded G3F and ran the script.

    You are supposed to load the target, load the source, (or vice versa, shouldn't matter what order) select the source, CTRL select the target, and then run the script. The order of selection tell the script which target is source and which is target. The favorites tell the script what products to trasnfer.

    EDIT: I'd expect a different error. that alone should prevent the script running an should cause the script to return a specific error. But it is still the first, most obvious, issue.

    Ok this time I used the instructions on your own post.  I loaded G3F, Favorited the Parameters, Loaded G8F, Selected the Source, CTRL+Selected the Target, and ran the verbose script.  It still gave the same error but attached is the full log.

    txt
    txt
    Prototype Verbose log.txt
    349K
  • Then the question to ask is what's so special about you that you can't load a script?

    Can you load any script? Given exaclty the same script, everyone else has had it run. Maybe it broke, but it ran. It's not even loading for you. So what's different about you? At this point, I don't think it's the script, per se because the script isn't actually running. Like I said (and just tested to be sure) if you do everything wrong it should give a specific error. THis one, to be exact:

    2018-02-19 15:22:09.567 WARNING: general\dzscene.cpp(5707): Index out of range in DzScene::getSelectedNode()

    2018-02-19 15:22:09.568 WARNING: general\dzscene.cpp(5707): Index out of range in DzScene::getSelectedNode()

    2018-02-19 15:22:09.576 WARNING: Script Error: Line 715

    2018-02-19 15:22:09.576 WARNING: TypeError: Result of expression 'oSrcNode' [null] is not an object.

    2018-02-19 15:22:09.576 WARNING: Stack Trace:

    <anonymous>()@D:/Users/Dyson/DAZ 3D/Studio/My Library/Scripts/Morph Transfer Prototype/PrototypeVerbose.dse:715

    2018-02-19 15:22:09.579 Error in script execution: D:/Users/Dyson/DAZ 3D/Studio/My Library/Scripts/Morph Transfer Prototype/PrototypeVerbose.dse

    You don't get that. Because your system isn't letting it run at all. Either you have a badly corrupted file to begin with, which is certainly possible, or you've got some other special elelemt specific to you that won't let the script run.

    You know your stuff, so what's special about you?

  • Then the question to ask is what's so special about you that you can't load a script?

    Can you load any script? Given exaclty the same script, everyone else has had it run. Maybe it broke, but it ran. It's not even loading for you. So what's different about you? At this point, I don't think it's the script, per se because the script isn't actually running. Like I said (and just tested to be sure) if you do everything wrong it should give a specific error. THis one, to be exact:

    2018-02-19 15:22:09.567 WARNING: general\dzscene.cpp(5707): Index out of range in DzScene::getSelectedNode()

    2018-02-19 15:22:09.568 WARNING: general\dzscene.cpp(5707): Index out of range in DzScene::getSelectedNode()

    2018-02-19 15:22:09.576 WARNING: Script Error: Line 715

    2018-02-19 15:22:09.576 WARNING: TypeError: Result of expression 'oSrcNode' [null] is not an object.

    2018-02-19 15:22:09.576 WARNING: Stack Trace:

    <anonymous>()@D:/Users/Dyson/DAZ 3D/Studio/My Library/Scripts/Morph Transfer Prototype/PrototypeVerbose.dse:715

    2018-02-19 15:22:09.579 Error in script execution: D:/Users/Dyson/DAZ 3D/Studio/My Library/Scripts/Morph Transfer Prototype/PrototypeVerbose.dse

    You don't get that. Because your system isn't letting it run at all. Either you have a badly corrupted file to begin with, which is certainly possible, or you've got some other special elelemt specific to you that won't let the script run.

    You know your stuff, so what's special about you?

    Well chances of it being corrupt having downloaded it multiple times and different systems seems unlikely.

    As for running scripts, I regularly use several script; BreastJig Script for DazStudio, Look at Me by RiverSoft Art, Brow Remover, and VWD.  None of which have given me problems loading up, including on on the scene I had made to do your script.  If you would like I can send you the logs that include all but VWD being used on the G3F in the scene.  So scripts in general seem to work fine.

    I have also tested the non-verbose version and it also comes up with the same refusale to load.

    Perhaps it is a versioning issue.  I am on Version 4.10.0.107 of Daz Studio.

    Of course that is the system I travel with which is just a Surface Pro 2 with an external drive holding my Library.  Once I get home tonight I will be able to test it on a my laptop and desktops to confirm if there is similar behavior between the three systems.

  • barbultbarbult Posts: 24,755

    Did you download the latest version of the zip file and extract all the items from the zip file and place them in your main (first listed) NON-CONNECT Daz Studio content library?I made the mistake once of thinking I had the latest zip file, when in fact, mine was a day old. Downloading the latest made all the difference in the problem I had (which was different than your problem). Maybe at this point you need to show your Content Directory Manager listing of Daz Studio content libraries and show a screenshot of the folders where you installed the contents of the zip files. Maybe a second pair of eyes on that installation will spot a problem.

  • barbultbarbult Posts: 24,755
    edited February 2018

    Then the question to ask is what's so special about you that you can't load a script?

    Can you load any script? Given exaclty the same script, everyone else has had it run. Maybe it broke, but it ran. It's not even loading for you. So what's different about you? At this point, I don't think it's the script, per se because the script isn't actually running. Like I said (and just tested to be sure) if you do everything wrong it should give a specific error. THis one, to be exact:

    2018-02-19 15:22:09.567 WARNING: general\dzscene.cpp(5707): Index out of range in DzScene::getSelectedNode()

    2018-02-19 15:22:09.568 WARNING: general\dzscene.cpp(5707): Index out of range in DzScene::getSelectedNode()

    2018-02-19 15:22:09.576 WARNING: Script Error: Line 715

    2018-02-19 15:22:09.576 WARNING: TypeError: Result of expression 'oSrcNode' [null] is not an object.

    2018-02-19 15:22:09.576 WARNING: Stack Trace:

    <anonymous>()@D:/Users/Dyson/DAZ 3D/Studio/My Library/Scripts/Morph Transfer Prototype/PrototypeVerbose.dse:715

    2018-02-19 15:22:09.579 Error in script execution: D:/Users/Dyson/DAZ 3D/Studio/My Library/Scripts/Morph Transfer Prototype/PrototypeVerbose.dse

    You don't get that. Because your system isn't letting it run at all. Either you have a badly corrupted file to begin with, which is certainly possible, or you've got some other special elelemt specific to you that won't let the script run.

    You know your stuff, so what's special about you?

    Well chances of it being corrupt having downloaded it multiple times and different systems seems unlikely.

    As for running scripts, I regularly use several script; BreastJig Script for DazStudio, Look at Me by RiverSoft Art, Brow Remover, and VWD.  None of which have given me problems loading up, including on on the scene I had made to do your script.  If you would like I can send you the logs that include all but VWD being used on the G3F in the scene.  So scripts in general seem to work fine.

    I have also tested the non-verbose version and it also comes up with the same refusale to load.

    Perhaps it is a versioning issue.  I am on Version 4.10.0.107 of Daz Studio.

    Of course that is the system I travel with which is just a Surface Pro 2 with an external drive holding my Library.  Once I get home tonight I will be able to test it on a my laptop and desktops to confirm if there is similar behavior between the three systems.

    A dse (encrypted script) will only run on the version it was encrypted with or later. Singular Blues *probably* encrypted with the latest version 4.10.0.123. I bet it will work if you update Daz Studio. I am running 4.10.0.123.

    Post edited by barbult on
  • barbult said:

    Did you download the latest version of the zip file and extract all the items from the zip file and place them in your main (first listed) NON-CONNECT Daz Studio content library?I made the mistake once of thinking I had the latest zip file, when in fact, mine was a day old. Downloading the latest made all the difference in the problem I had (which was different than your problem). Maybe at this point you need to show your Content Directory Manager listing of Daz Studio content libraries and show a screenshot of the folders where you installed the contents of the zip files. Maybe a second pair of eyes on that installation will spot a problem.

    Perhaps you are correct. Attached is a screenshot of my Content Library showing where I am running the script from.  I also have open the folder for the script to show the files themselves.  I did also download and open the file and opened to confirm that the file date and time is the same so it seems to be the latest version of the script.  To install I just took the data and Scripts folders that were there after unzipping the file and copied them as is into my Daz Library folder.  I didn't put them in some odd location, it is right next to all my regularly used scripts.

    Prototype Install.PNG
    1920 x 1041 - 123K
  • barbult said:

    Then the question to ask is what's so special about you that you can't load a script?

    Can you load any script? Given exaclty the same script, everyone else has had it run. Maybe it broke, but it ran. It's not even loading for you. So what's different about you? At this point, I don't think it's the script, per se because the script isn't actually running. Like I said (and just tested to be sure) if you do everything wrong it should give a specific error. THis one, to be exact:

    2018-02-19 15:22:09.567 WARNING: general\dzscene.cpp(5707): Index out of range in DzScene::getSelectedNode()

    2018-02-19 15:22:09.568 WARNING: general\dzscene.cpp(5707): Index out of range in DzScene::getSelectedNode()

    2018-02-19 15:22:09.576 WARNING: Script Error: Line 715

    2018-02-19 15:22:09.576 WARNING: TypeError: Result of expression 'oSrcNode' [null] is not an object.

    2018-02-19 15:22:09.576 WARNING: Stack Trace:

    <anonymous>()@D:/Users/Dyson/DAZ 3D/Studio/My Library/Scripts/Morph Transfer Prototype/PrototypeVerbose.dse:715

    2018-02-19 15:22:09.579 Error in script execution: D:/Users/Dyson/DAZ 3D/Studio/My Library/Scripts/Morph Transfer Prototype/PrototypeVerbose.dse

    You don't get that. Because your system isn't letting it run at all. Either you have a badly corrupted file to begin with, which is certainly possible, or you've got some other special elelemt specific to you that won't let the script run.

    You know your stuff, so what's special about you?

    Well chances of it being corrupt having downloaded it multiple times and different systems seems unlikely.

    As for running scripts, I regularly use several script; BreastJig Script for DazStudio, Look at Me by RiverSoft Art, Brow Remover, and VWD.  None of which have given me problems loading up, including on on the scene I had made to do your script.  If you would like I can send you the logs that include all but VWD being used on the G3F in the scene.  So scripts in general seem to work fine.

    I have also tested the non-verbose version and it also comes up with the same refusale to load.

    Perhaps it is a versioning issue.  I am on Version 4.10.0.107 of Daz Studio.

    Of course that is the system I travel with which is just a Surface Pro 2 with an external drive holding my Library.  Once I get home tonight I will be able to test it on a my laptop and desktops to confirm if there is similar behavior between the three systems.

    A dse (encrypted script) will only run on the version it was encrypted with or later. Singular Blues *probably* encrypted with the latest version 4.10.0.123. I bet it will work if you update Daz Studio. I am running 4.10.0.123.

    That makes sense.  I will go through the update and see if that works.

  • barbult said:

    Then the question to ask is what's so special about you that you can't load a script?

    Can you load any script? Given exaclty the same script, everyone else has had it run. Maybe it broke, but it ran. It's not even loading for you. So what's different about you? At this point, I don't think it's the script, per se because the script isn't actually running. Like I said (and just tested to be sure) if you do everything wrong it should give a specific error. THis one, to be exact:

    2018-02-19 15:22:09.567 WARNING: general\dzscene.cpp(5707): Index out of range in DzScene::getSelectedNode()

    2018-02-19 15:22:09.568 WARNING: general\dzscene.cpp(5707): Index out of range in DzScene::getSelectedNode()

    2018-02-19 15:22:09.576 WARNING: Script Error: Line 715

    2018-02-19 15:22:09.576 WARNING: TypeError: Result of expression 'oSrcNode' [null] is not an object.

    2018-02-19 15:22:09.576 WARNING: Stack Trace:

    <anonymous>()@D:/Users/Dyson/DAZ 3D/Studio/My Library/Scripts/Morph Transfer Prototype/PrototypeVerbose.dse:715

    2018-02-19 15:22:09.579 Error in script execution: D:/Users/Dyson/DAZ 3D/Studio/My Library/Scripts/Morph Transfer Prototype/PrototypeVerbose.dse

    You don't get that. Because your system isn't letting it run at all. Either you have a badly corrupted file to begin with, which is certainly possible, or you've got some other special elelemt specific to you that won't let the script run.

    You know your stuff, so what's special about you?

    Well chances of it being corrupt having downloaded it multiple times and different systems seems unlikely.

    As for running scripts, I regularly use several script; BreastJig Script for DazStudio, Look at Me by RiverSoft Art, Brow Remover, and VWD.  None of which have given me problems loading up, including on on the scene I had made to do your script.  If you would like I can send you the logs that include all but VWD being used on the G3F in the scene.  So scripts in general seem to work fine.

    I have also tested the non-verbose version and it also comes up with the same refusale to load.

    Perhaps it is a versioning issue.  I am on Version 4.10.0.107 of Daz Studio.

    Of course that is the system I travel with which is just a Surface Pro 2 with an external drive holding my Library.  Once I get home tonight I will be able to test it on a my laptop and desktops to confirm if there is similar behavior between the three systems.

    A dse (encrypted script) will only run on the version it was encrypted with or later. Singular Blues *probably* encrypted with the latest version 4.10.0.123. I bet it will work if you update Daz Studio. I am running 4.10.0.123.

    That makes sense.  I will go through the update and see if that works.

    Well that seemed to be the issue with the script the whole time.  Anyone running the script must be on the same version as it was made for.  Sadly after all the finger issue is there.  May have to look at what other options there are.  Everything else seems to have been fine and since the morphs are individually ported over I have more options to see what the problem morph is and if I can do something about it.  It is progress.  Thanks barbult you were extremely helpful and insightful.

    Prototype convert.PNG
    868 x 872 - 286K
  • barbultbarbult Posts: 24,755
    barbult said:

    Then the question to ask is what's so special about you that you can't load a script?

    Can you load any script? Given exaclty the same script, everyone else has had it run. Maybe it broke, but it ran. It's not even loading for you. So what's different about you? At this point, I don't think it's the script, per se because the script isn't actually running. Like I said (and just tested to be sure) if you do everything wrong it should give a specific error. THis one, to be exact:

    2018-02-19 15:22:09.567 WARNING: general\dzscene.cpp(5707): Index out of range in DzScene::getSelectedNode()

    2018-02-19 15:22:09.568 WARNING: general\dzscene.cpp(5707): Index out of range in DzScene::getSelectedNode()

    2018-02-19 15:22:09.576 WARNING: Script Error: Line 715

    2018-02-19 15:22:09.576 WARNING: TypeError: Result of expression 'oSrcNode' [null] is not an object.

    2018-02-19 15:22:09.576 WARNING: Stack Trace:

    <anonymous>()@D:/Users/Dyson/DAZ 3D/Studio/My Library/Scripts/Morph Transfer Prototype/PrototypeVerbose.dse:715

    2018-02-19 15:22:09.579 Error in script execution: D:/Users/Dyson/DAZ 3D/Studio/My Library/Scripts/Morph Transfer Prototype/PrototypeVerbose.dse

    You don't get that. Because your system isn't letting it run at all. Either you have a badly corrupted file to begin with, which is certainly possible, or you've got some other special elelemt specific to you that won't let the script run.

    You know your stuff, so what's special about you?

    Well chances of it being corrupt having downloaded it multiple times and different systems seems unlikely.

    As for running scripts, I regularly use several script; BreastJig Script for DazStudio, Look at Me by RiverSoft Art, Brow Remover, and VWD.  None of which have given me problems loading up, including on on the scene I had made to do your script.  If you would like I can send you the logs that include all but VWD being used on the G3F in the scene.  So scripts in general seem to work fine.

    I have also tested the non-verbose version and it also comes up with the same refusale to load.

    Perhaps it is a versioning issue.  I am on Version 4.10.0.107 of Daz Studio.

    Of course that is the system I travel with which is just a Surface Pro 2 with an external drive holding my Library.  Once I get home tonight I will be able to test it on a my laptop and desktops to confirm if there is similar behavior between the three systems.

    A dse (encrypted script) will only run on the version it was encrypted with or later. Singular Blues *probably* encrypted with the latest version 4.10.0.123. I bet it will work if you update Daz Studio. I am running 4.10.0.123.

    That makes sense.  I will go through the update and see if that works.

    Well that seemed to be the issue with the script the whole time.  Anyone running the script must be on the same version as it was made for.  Sadly after all the finger issue is there.  May have to look at what other options there are.  Everything else seems to have been fine and since the morphs are individually ported over I have more options to see what the problem morph is and if I can do something about it.  It is progress.  Thanks barbult you were extremely helpful and insightful.

    yes 

    When you figure out what morphs is causing the problem, maybe one of us has the same one and can try it. Does the finger problem happen even when the character is not posed? Does the morph work properly on the source figure in the same/similar pose?

  • barbult said:
    barbult said:

    Then the question to ask is what's so special about you that you can't load a script?

    Can you load any script? Given exaclty the same script, everyone else has had it run. Maybe it broke, but it ran. It's not even loading for you. So what's different about you? At this point, I don't think it's the script, per se because the script isn't actually running. Like I said (and just tested to be sure) if you do everything wrong it should give a specific error. THis one, to be exact:

    2018-02-19 15:22:09.567 WARNING: general\dzscene.cpp(5707): Index out of range in DzScene::getSelectedNode()

    2018-02-19 15:22:09.568 WARNING: general\dzscene.cpp(5707): Index out of range in DzScene::getSelectedNode()

    2018-02-19 15:22:09.576 WARNING: Script Error: Line 715

    2018-02-19 15:22:09.576 WARNING: TypeError: Result of expression 'oSrcNode' [null] is not an object.

    2018-02-19 15:22:09.576 WARNING: Stack Trace:

    <anonymous>()@D:/Users/Dyson/DAZ 3D/Studio/My Library/Scripts/Morph Transfer Prototype/PrototypeVerbose.dse:715

    2018-02-19 15:22:09.579 Error in script execution: D:/Users/Dyson/DAZ 3D/Studio/My Library/Scripts/Morph Transfer Prototype/PrototypeVerbose.dse

    You don't get that. Because your system isn't letting it run at all. Either you have a badly corrupted file to begin with, which is certainly possible, or you've got some other special elelemt specific to you that won't let the script run.

    You know your stuff, so what's special about you?

    Well chances of it being corrupt having downloaded it multiple times and different systems seems unlikely.

    As for running scripts, I regularly use several script; BreastJig Script for DazStudio, Look at Me by RiverSoft Art, Brow Remover, and VWD.  None of which have given me problems loading up, including on on the scene I had made to do your script.  If you would like I can send you the logs that include all but VWD being used on the G3F in the scene.  So scripts in general seem to work fine.

    I have also tested the non-verbose version and it also comes up with the same refusale to load.

    Perhaps it is a versioning issue.  I am on Version 4.10.0.107 of Daz Studio.

    Of course that is the system I travel with which is just a Surface Pro 2 with an external drive holding my Library.  Once I get home tonight I will be able to test it on a my laptop and desktops to confirm if there is similar behavior between the three systems.

    A dse (encrypted script) will only run on the version it was encrypted with or later. Singular Blues *probably* encrypted with the latest version 4.10.0.123. I bet it will work if you update Daz Studio. I am running 4.10.0.123.

    That makes sense.  I will go through the update and see if that works.

    Well that seemed to be the issue with the script the whole time.  Anyone running the script must be on the same version as it was made for.  Sadly after all the finger issue is there.  May have to look at what other options there are.  Everything else seems to have been fine and since the morphs are individually ported over I have more options to see what the problem morph is and if I can do something about it.  It is progress.  Thanks barbult you were extremely helpful and insightful.

    yes 

    When you figure out what morphs is causing the problem, maybe one of us has the same one and can try it. Does the finger problem happen even when the character is not posed? Does the morph work properly on the source figure in the same/similar pose?

    Well so far the tests seem to show that it is the full body morph which was originally for the character Rain.  Once I remove that the finger issue goes away but if I use any full body morphs that change the height of the character those issues return if they are shorter or go the other way if the model is grown.  I found a body morph that gets about the right shape and I am looking to pose the original character, the messed up hand character, and my new version nest to one another so as to see how much difference there is.  When the hands are not posed in the problem one then the hands look fine.  I had a similar issue when I tried Redz method.  Since I now have a roadmap I will probably be doing this a couple times to get it right then doing it so that I can save the files made and be able to back it all up in case I need to reinstall at some point.

  • barbultbarbult Posts: 24,755
    My GUESS is that the rigging wasn't adjusted to shape before the original Rain character was saved. I don't own that character. If that is the problem, I would expect posing problems in the source version of the fbm, not only your transferred version. Keep us posted.
  • IchibanIchiban Posts: 113

    I can't get it to work when I try to transfer G3M morphs to G8M. I don't know much about accessing the log, but I also noticed my My Daz Library is not at the top of the list, Daz Connect is. Would that make a difference? If I can get my setup right to try this, I'll be more than happy to give logs. Just needing a little help with getting them and setting up for this. I appreciate the effort put into this.

  • barbult said:
    My GUESS is that the rigging wasn't adjusted to shape before the original Rain character was saved. I don't own that character. If that is the problem, I would expect posing problems in the source version of the fbm, not only your transferred version. Keep us posted.

    That is my guess too.  I think what I will probably do is try to convert it again at some point without the rain morph at all.  Then I will see if that helps and if I can find another G8F morph that will do something similar (give her a little younger proportions and a little skinnier).  There was always going to be some trial and error and tweaking since this is based off a real person.  Luckily that person is in the loop about it so working with her to get it right should allow us to still be accurate.

  • Well so far the tests seem to show that it is the full body morph which was originally for the character Rain.  Once I remove that the finger issue goes away but if I use any full body morphs that change the height of the character those issues return if they are shorter or go the other way if the model is grown.  I found a body morph that gets about the right shape and I am looking to pose the original character, the messed up hand character, and my new version nest to one another so as to see how much difference there is.  When the hands are not posed in the problem one then the hands look fine.  I had a similar issue when I tried Redz method.  Since I now have a roadmap I will probably be doing this a couple times to get it right then doing it so that I can save the files made and be able to back it all up in case I need to reinstall at some point.

    Restart studio, reload the Target figure. I  suspect you'll find the issue is gone, and everything works correctly.

     

    Ichiban said:

    I can't get it to work when I try to transfer G3M morphs to G8M. I don't know much about accessing the log, but I also noticed my My Daz Library is not at the top of the list, Daz Connect is. Would that make a difference? If I can get my setup right to try this, I'll be more than happy to give logs. Just needing a little help with getting them and setting up for this. I appreciate the effort put into this.

    That is a list of lists. Your library must be at the top of the list under DAZ Studio Formats. The list of lists is always in that order.

    The log can be found under the Help Menu. Troubleshooting > View Log File.

  • FenixPhoenixFenixPhoenix Posts: 3,111
    edited February 2018

    Well so far the tests seem to show that it is the full body morph which was originally for the character Rain.  Once I remove that the finger issue goes away but if I use any full body morphs that change the height of the character those issues return if they are shorter or go the other way if the model is grown.  I found a body morph that gets about the right shape and I am looking to pose the original character, the messed up hand character, and my new version nest to one another so as to see how much difference there is.  When the hands are not posed in the problem one then the hands look fine.  I had a similar issue when I tried Redz method.  Since I now have a roadmap I will probably be doing this a couple times to get it right then doing it so that I can save the files made and be able to back it all up in case I need to reinstall at some point.

    If you mean SC Rain for Genesis 3 Female I just successfully transfer her to G8F via the verbose script. I did several poses to see if there was a problem with her fingers, but didn't find it. Her morph transferred perfectly.

    Rain.jpg
    800 x 1035 - 237K
    Post edited by FenixPhoenix on
Sign In or Register to comment.