V3Digitimes 2025 Compatibility Updates

V3Digitimes

Good morning,

this post will allow you to know the progress status of the updates of ALL my scripted products for Daz Studio 2025. As many of you know, many scripted products will not basically work with Daz Studio 2025 until they are updated, this is why I plan to update them all during the next weeks/months (depending on how difficult it is, I keep my fingers crossed it will only be weeks).

Iray Light Manager Pro : updated, progess 100%  – LOOKING FOR BETA TESTERS (1 mac / 1 pc ideally)!

Scene Optimizer : updated, progress : 100%  – LOOKING FOR BETA TESTERS (1 mac / 1 pc ideally)!

Shader Rotator : seems to work on super simple configurations, to be fully tested

Iray Converter For Genesis : Seems to work, log file must be analyzed, Genitalia transfer not tested yet

Iray Converter For Generation 4 : To be tested

Iray Converter For Genesis 2 : Fails, must be updated, update : 0%

Iray Converter For Genesis 3 : Fails, must be updated, update : 0%

Super Save : Fails, must be updated, update : 0%

Drops Generator : Fails, must be updated, update : 0%

Texture Booster : Fails, must be updated, update : 0%

All Face to Face products : seem to work for base scripts, to be confirmed on animation interfaces

Other products : not tested yet.

If some of you already had some of the scripts working on Daz Studio 2025, please let me know here. I rapidely tested "Shader Rotator" for instance, which seems to work (a more in depth test is required). The same way, if you see scripts having both the status "updated" and "update released", and that you see that it does not work for you (once updated on your side), let me know here.

Today I am working on Scene Optmizer and this is not easy to update, but I progress every hour.

I thank you in advance for all the feedback and information you would provide to fasten and ease this update process.

Elor

I thought only plugins would break. Currently, I don't (like most non PAs people I guess) have access to Daz Studio 2025, but I'll try to test your scripts once Daz Studio 2025 is available and installed on my computers.

If a script doesn't work on MacOS, should I assume that it also won't work on Windows or is it better to check on both OS ?

V3Digitimes

For Daz Studio 4, scripts worked almost all the time on both, or none. But with my 6 hours of background on DS 2025, I'm not able to answer. My guess is that a lot of scripts won't work for me, seeing the way I struggle in my Scene Optimizer to get things as simple as the sizes of the maps...

That's very generous from you to propose your help, I really do appreciate !

MissLeah

Thank you very much for being proactive and keeping us updated!  I use Scene Optimizer regularly, so it's great to know that you're updating it for the latest version of the software. I hope that other scripts I use all the time will be updated by other PAs as well.

V3Digitimes

You're welcome ;) I don't know for the others, I'm only in touch with one of them, but on my side I'll do everything I can to update everything I have. I would not feel well if I did not. But it's not gonna be an easy year for me, for sure, especially if it takes long to do that... All my projects are in stand bye, except maybe the latest one I was working on (I was at the documentation step, so near the end) that I'm gonna try to finish in parallel with the updates (when I'm fed up crying on why I'm not allowed to do stuff I used to do before in my scripts). 

I really hope the other scripts will be easier to update than this first one I'm working on, even if I still progress on it (after 3 hours struggling to update the maps size in the interface).

You are welcome to let me know other issues you see with my scripts, I'll test them all anyway, but users feedback is a way for me to make the process more robust.

 

Richard Haseltine

Elor said:

I thought only plugins would break. Currently, I don't (like most non PAs people I guess) have access to Daz Studio 2025, but I'll try to test your scripts once Daz Studio 2025 is available and installed on my computers.

Actually we were told that all plug-ins and at least some scripts would need updating. The underlying script engine (ECMA) has changed version that has had soem fundamental impacts, one that was pointed out in a recent discussion on one of these scripts was chnages in the way variable scopes are handled for example.

There may also be changes to the DS data structures - for example, in DS 3 almost all figures were DzSkeleton but in DS4 they inherit DzSkeleton but never are just that, so some scripts may have failed if they expected a figure to be a DzSkeleton. We haven';t had any like examples flagged up for us, possibly because there aren't any or because no one has asked a question where they are relvant, but it is another potential issue.

If a script doesn't work on MacOS, should I assume that it also won't work on Windows or is it better to check on both OS ?

Elor

I tested a couple of the ones I bought (I'll try to rest later, likely not today considering it's almost 7PM in France).

I tried to save the relevant part of the log each time I encountered an error. If you need them, I can provide them.

V3D Christmas Gifts and Tree: 

• MacOS: the script seemed to work, at least I ended with 250 props added to 'Random Ornament Group', they did seem to be around the tree, not inside and I saw no error in the log file.
• Windows: Edit: I forgot, I did test it in Windows and it worked. /Edit

Iray Light Manager Pro:

• MacOS: Didn't work: 'An error occurred while reading the file. See the log for more details.' I saved the relevant part of the log.
• Windows: Same error message, relevant part of the log also saved.

Drops Generators:

For scripts 1 to 5, I created a new cube and use the various scripts to select one of its faces before trying to use each script.

Because none of them worked, I loaded an old scene to test the rest of the scripts.

MacOS:

• Activating the geometry tool worked :D
• Scripts 02 to 05 didn't work, same error message as Iray Light Manager Pro and I think I also saved the relevant part of the log each time.
• Script 06 did work and seems to do what it is supposed to do. I also launched the script on Daz Studio 4.23.1.47 and I ended with a similar state in the scene tab.

Windows: same behavior as on MacOS, so I suppose if a script doesnt work on MacOS, it won't work on Windows.

• Script 06 to 14 seem to work and did not raise an error. 

I only tested them scripts 7 to 14 on Windows because I did a couple of spots render to check that no drops went missing after the ones doing some consolidations (as far as I can see, they were all where they were supposed to be), and it's faster to do a render with an RTX GPU.

Face to Face Autopose Arm G9

• MacOS: The first four scripts, including the basic script moving arms worked on MacOS. I never used the more advanced script, so I don't know how to use them, sorry.

Face to Face Autopose Arm

• MacOS: Worked as fine as the G9 version, with the same limitation: I only tested the first four scripts.

Face to Face Autopose Legs G9

• MacOS: All scripts worked. I loaded a bike, Genesis 9, then loaded high-heeled shoes, I saved the foot angle, asked autopose to pose the right leg, then loaded the saved foot angle. Everything went fine.

My guess is all Face to Face should also work on Windows (I have yet to test it because I wanted to use an old scene to test the G8 version, but I encountered a bug with Daz Studio itself…).

Texture Booster:

Only tested on Windows, because I felt optimistic and wanted to see if the changes were applied (so with Iray preview active). Well.

• 'V3DTBU Texture Splitter For Selected Surfaces' seems to work, at least no error happened (I have no idea what it is supposed to di, I only used Textures Booster with Genesis figures).
• 'V3DTBG Booster Options For Genesis Figures' seems to work.

Everything else failed to launch, with an error. I saved the relevant part of the logs (technically, I erased the log before trying to use the first script, then each time, I renamed log.txt with the name of the script).

----

Thank you for the clarification, Richard Haseltine :)

V3Digitimes

Thanks so much for all your tests Elor! Well there seems to be a lot of work for me. That is great that you have a Mac to test, because I don't ;) I think most of or almost my scripts with a user interface will somehow have to be updated. Whereas the scripts without or with minimal interface seem to be fine. I cannot be super efficient until sunday since i am far from home and the laptop i have to work is far less comfortable than my double screen 3d dedicated pc i have at home.. But i will go on updating anyway, since i want to put all this update period behind me as fast as possible. I deeply appreciate the way ypu got involved in this, it is really helpful. I will make yhe synthesis tomorrow since tonight my brain is cooked and over heated..

gram

I'll be happy to beta test updates to texture booster as I use that one quite a bit.

V3Digitimes

Thanks a lot, I'll contact you as soon as it is ready to test!!! I am currently working on both "Skin Managers", and "Texture Booster" should come just after.

Thanks again for your help proposal, it is so useful!

Rod Wise Driggo

If I can support testing just let me know. Own quite some of your scripts.

I'm on Mac and since the 2025 alpha is IMO already much better as the current Mac version of studio I guess I will be using 2025 most of the time nowadays.

Elor

V3Digitimes said:

I think most of or almost my scripts with a user interface will somehow have to be updated. Whereas the scripts without or with minimal interface seem to be fine.

It does look that way for Wet and Tan for Genesis 3 (I tested it this yesterday morning): every 'manager tool' refused to launch, with the 'An error occurred while reading the file. See the log for more details.' windows opening, but as far as I can see, every other scripts, the ones applying presets without opening a window, worked: I did not test them all, they are too many of them, but how taned a character is changed each time, same for the tan lines, the wetness and the bump (each time I used one of them, Iray Preview restarted from zero so these scripts did something).

Looking at the logs after trying to launch the manager tools, errors mainly seems to be 'a variable was used before it was declared', so hopefully for such problem, it'll be a 'simple' fix (I know next to nothing about Daz script, so maybe it's not so simple).

V3Digitimes

Rod Wise Driggo said:

If I can support testing just let me know. Own quite some of your scripts.

I'm on Mac and since the 2025 alpha is IMO already much better as the current Mac version of studio I guess I will be using 2025 most of the time nowadays.

THANKS A LOT for your proposal! I will probably need your help when more updates will ne finalized. That's very nice from you to propose your help.

V3Digitimes

Elor said:

V3Digitimes said:

I think most of or almost my scripts with a user interface will somehow have to be updated. Whereas the scripts without or with minimal interface seem to be fine.

It does look that way for Wet and Tan for Genesis 3 (I tested it this yesterday morning): every 'manager tool' refused to launch, with the 'An error occurred while reading the file. See the log for more details.' windows opening, but as far as I can see, every other scripts, the ones applying presets without opening a window, worked: I did not test them all, they are too many of them, but how taned a character is changed each time, same for the tan lines, the wetness and the bump (each time I used one of them, Iray Preview restarted from zero so these scripts did something).

Looking at the logs after trying to launch the manager tools, errors mainly seems to be 'a variable was used before it was declared', so hopefully for such problem, it'll be a 'simple' fix (I know next to nothing about Daz script, so maybe it's not so simple).

Ah this wonderful var declared after i saw hundreds of times these last days... Yes previously variables could be declared several time or after the function calling them without issues when you called this function after the variable declaration. This is over now. This part is not super complicated to solve, even if it can be long as yesterday with 80 widgets to redeclare for a single script... For now there is nothing i did not manage to solve, i am only worried for the issues i meet with the textures which i don't manage to handle as i usually did, making me use alternative complicated ways to reach a map path sometimes (and other times not, depending if catching maps is in a loop or not). I hope i will find a reliable and standard way to solve it because i solved it once and it was epic! Thanks anyway for confirming what i felt and began to observe. Today i am rather optimistic tegarding the updates which should for most of them be possible in a not too long term. But since today is also my last day on vacations, i duid not switch on my computer and ratger spent time with my family. Updates will restart sunday or monday. Thanks for your feeback and information.

jmucchiello

Elor said:

Iray Light Manager Pro:

• MacOS: Didn't work: 'An error occurred while reading the file. See the log for more details.' I saved the relevant part of the log.
• Windows: Same error message, relevant part of the log also saved.

I guess I won't be trying the Alpha any time soon. That's a showstopper for me. This asset would only be improved if it were a plugin that created a Lights Panel. 

MoreTN

Just a question. When you publish updates for Daz2025 will that make your scripts incompatible with earlier versions?

V3Digitimes

My goal is to have all the scripts compatible with ds 4.23 and 2025 simultaneously. So far it works for the ones i began to update. If it happens that on some scripts it is not possible, then i will make 2 versions for those ones. But sor far it was not necessary.

MelanieL

V3Digitimes said:

My goal is to have all the scripts compatible with ds 4.23 and 2025 simultaneously. So far it works for the ones i began to update. If it happens that on some scripts it is not possible, then i will make 2 versions for those ones. But sor far it was not necessary.

That is great news! Very generous of you to cover both. 

V3Digitimes

Thanks. Well i must admit that so far i was surprised by how well Daz Dev team had managed to transfer a maximum of elements to maximise compatibility. This is far from perfect but i anticipated something much more complicate... well maybe some updates will make me tell the opposite but for now, nothing was impossible to solve, even if sometimes it was difficult.

MoreTN

V3Digitimes said:

My goal is to have all the scripts compatible with ds 4.23 and 2025 simultaneously. So far it works for the ones i began to update. If it happens that on some scripts it is not possible, then i will make 2 versions for those ones. But sor far it was not necessary.

Thank you, that's wonderful news 

V3Digitimes

You're welcome !

29/04/25 : I'm looking for beta testers for Scene Optimizer and Iray Light Manager Pro. The goal is to confirm, ideally on PC and MAC, that they work as expected both the DS 2025 and the DS 4.20++ versions, before I submit it as an official update. Don't fight over the spots—trust me, there'll be plenty of products to test for everyone! 

Elor

I have both, but I'm rarely using Scene Optimizer so I'm not sure I would be a good beta tester for it (outside of playing the debuging monkey clicking everywhere until Daz Studio's persona decides to get out of my computer screen to punch me in the nose :o) but feel free to ask if you think it could be useful.

V3Digitimes

Thanks a lot for your answer!!! I'm still waiting to see if people are interested to test the update, I prefer to have your help on products you know well or you use on a regular basis. Maybe I'll also post elsewhere on the forum to have a better visibility. I don't feel like spending too much time on the tests, since updating can be considerably long sometimes (today 12 hours for 30% of a single script update!).... Thanks anyway for your answer, I feel "less alone" ;)