ETA for script usability in DAZ alpha 6.25?

2»

Comments

  • V3DigitimesV3Digitimes Posts: 3,366

    memcneil70 said:

    As a user without programmer knowledge, but with both 4.24.0.3 Beta and 6.25.17807 Alpha currently installed on my MacMini M4 and my Windows 11 computers I am assured that my scripts on the Beta are not messed with by the Alpha. I am the one who decides which product/script/plugin to attempt to use on the Alpha, not the programs. So far I have only tested three of Code66's scripts just to see if the Alpha will keep them in my Favorites from one update to another. If I need my scripts/plugins, I use my Beta then open the file in the Alpha if necessary. For the Mac it is the ability to use Filament that is the big plus. By contributing to the Alpha thread what you observe will only help improve it. I would help the PAs in testing but I am probably the last person they would want because I stumble around many scripts. But I will support their work fully no matter what form it arrives in. They provide a service I can not do myself.

    So far it's the best idea. As Totte said, some scripts are longer to update than others. I just finished the update of three products, which will be linked to a product to come (some features will appear as a linked bonus in the updated products). Some of the scripts took me one hour or a few hours (time to move variables where they should go and to make cross compatible connects). The genitalia transfer script I use in many products took me one week (still not able to have the DoDuplicate working, I had to totally get rid off it) So far I planned to update everything, but if I find a script which sales at 4 copies per year and I see that it should take me one week or more to update, I might give up. But so far, except the script using the duplicates, it's just a "big update" work.. And I keep my fingers crossed..
  • Richard HaseltineRichard Haseltine Posts: 108,079
    edited July 10

    windli3356 said:

    Richard Haseltine said:

    windli3356 said:

    So the big question is what would happen to all recent scripts in the final build? Some later released scripts and utitlies got to be auto compatible like it's in 4.25.  For example all my purchased scripts and unilities are from 2020 - 2025.  such as pose converter, mesh smoother, mesh grabber etc.  if they can't be auto converted in final build, I'd imaging it's gonna cost users alot.   

    The issue with scripts is geenrally  changesin the scripting engine or possibly changes in DS - either way if they are incompatible now they will likely still be incompatible in a final release unless/until the PA addresses the issues, though that is not absolutely set in stone.

    " if they are incompatible now they will likely still be incompatible in a final release "  I hope that process will be mandatory for all PAs, if the benchmark is Alpha 6.25, then unfortunately nearly no scripts works at moment, from the most basic pose/cloth converter (big deals for users who own tons of resource on G3/8/9) to a slightly complex ones like mesh grabber to fiso physics engine.  Personally I hope the most basic ones can be addressed by DAZ, I image if PA don't come up with any updates upon release, it's gonna upset a lot of people here. 

    Mesh Grabber and Fisio are plug-ins, not scripts. All plug-ins are incompatible and cannot be fixed until there is a stabvle SDK to work from. Mesh Grabber 1  - 3 will not be geting updates as it iis now Geometry Sculptor, owned by Daz, and that is currently being worked on according to the change log (but Mesh Grabber is available only to Premier members). Fisio will have to wait until the PA has an SDK, at which point they will be able to review their options.

    [Edited to make it clear that it is mesh Grabber tself that is available only to Premier Member and not - currently - the updates listed in the Change Log]

    Post edited by Richard Haseltine on
  • barbultbarbult Posts: 26,235
    I suggest that Daz make a bridge to send a scene back and forth between 4.24 and the 2025 Alpha, so users can easily access scripts and plugins that only work in DS 4, then continue in the 2025 version.
  • TotteTotte Posts: 14,711

    barbult said:

    I suggest that Daz make a bridge to send a scene back and forth between 4.24 and the 2025 Alpha, so users can easily access scripts and plugins that only work in DS 4, then continue in the 2025 version.

    I usually have both open, and save/open the scene, but a bridge might make it easier, but it's pretty easy as it is. 

  • windli3356windli3356 Posts: 290

    Richard Haseltine said:

    windli3356 said:

    Richard Haseltine said:

    windli3356 said:

    So the big question is what would happen to all recent scripts in the final build? Some later released scripts and utitlies got to be auto compatible like it's in 4.25.  For example all my purchased scripts and unilities are from 2020 - 2025.  such as pose converter, mesh smoother, mesh grabber etc.  if they can't be auto converted in final build, I'd imaging it's gonna cost users alot.   

    The issue with scripts is geenrally  changesin the scripting engine or possibly changes in DS - either way if they are incompatible now they will likely still be incompatible in a final release unless/until the PA addresses the issues, though that is not absolutely set in stone.

    " if they are incompatible now they will likely still be incompatible in a final release "  I hope that process will be mandatory for all PAs, if the benchmark is Alpha 6.25, then unfortunately nearly no scripts works at moment, from the most basic pose/cloth converter (big deals for users who own tons of resource on G3/8/9) to a slightly complex ones like mesh grabber to fiso physics engine.  Personally I hope the most basic ones can be addressed by DAZ, I image if PA don't come up with any updates upon release, it's gonna upset a lot of people here. 

    Mesh Grabber and Fisio are plug-ins, not scripts. All plug-ins are incompatible and cannot be fixed until there is a stabvle SDK to work from. Mesh Grabber 1  - 3 will not be geting updates as it iis now Geometry Sculptor, owned by Daz, and that is currently being worked on according to the change log (but is available only to Premier members). Fisio will have to wait until the PA has an SDK, at which point they will be able to review their options.

    I know, they are just as unusable like the scripts, hence this topic.  Good to know mesh grabber will be available, even tho behind the paywall, but fair enough.  So other utilities and plugins are still depend on PAs and they will need Daz to release the public build's SDK to even start working (if they are willing)?   Sound like a long wait.    

  • windli3356windli3356 Posts: 290

    Totte said:

    barbult said:

    I suggest that Daz make a bridge to send a scene back and forth between 4.24 and the 2025 Alpha, so users can easily access scripts and plugins that only work in DS 4, then continue in the 2025 version.

    I usually have both open, and save/open the scene, but a bridge might make it easier, but it's pretty easy as it is. 

    WOW~ i thought I'm the only one doing this, con is I often forgot which build I was on last time.  

  • memcneil70memcneil70 Posts: 5,316

    windli3356 said:

    Totte said:

    barbult said:

    I suggest that Daz make a bridge to send a scene back and forth between 4.24 and the 2025 Alpha, so users can easily access scripts and plugins that only work in DS 4, then continue in the 2025 version.

    I usually have both open, and save/open the scene, but a bridge might make it easier, but it's pretty easy as it is. 

    WOW~ i thought I'm the only one doing this, con is I often forgot which build I was on last time.  

    Change the color scheme slightly between the two. Not radically, but just enough so you know 4.24 is a soft green highlight and 6.25 is a soft blue highlight as an example to clue you in. 

  • barbultbarbult Posts: 26,235
    Totte said:

    barbult said:

    I suggest that Daz make a bridge to send a scene back and forth between 4.24 and the 2025 Alpha, so users can easily access scripts and plugins that only work in DS 4, then continue in the 2025 version.

    I usually have both open, and save/open the scene, but a bridge might make it easier, but it's pretty easy as it is. 

    I've done that a time or two. It just feels cumbersome to me.
  • This issue is what's preventing me from making the switch to 6.25, and I know I'm not alone. For my work, I can't imagine using Daz without a few select scripts. It's a shame because 6.25 looks great.

Sign In or Register to comment.