V3Digitimes Daz Studio 2025 (6) compatibility Status

V3Digitimes

No problem, always glad to share when I can.

twitchew

thanks for going about updates in an organized way.  
i hope that DAZ will start tagging products as "2025" compatible.
i will problaby hold off any  purchases unless there is a 2025 version.

V3Digitimes

Thanks for your comment.
I am starting the updates with the wet and tanned skins series (all generations). I will update the main thread in parallel as updates are submitted first, then live.

DoctorJellybean

I don't see the various Extract and Append scripts on any list. Does it already work in DS 6?

V3Digitimes

DoctorJellybean said:

I don't see the various Extract and Append scripts on any list. Does it already work in DS 6?

The honest answer is: mostly yes, but with one important limitation.

Extract and Append works well in DS6 as long as the source scene does not contain very large cached dForce simulation data. This can happen with some heavily simulated hair or other dForce items. In that specific case, DS6 will hang or crash while parsing the DUF file.

I have already developed a temporary workaround for DS6. The "upcoming" (depending on Daz answer) update includes an optional Safe Mode that first pre-analyzes the file and, when necessary, creates a temporary copy with the problematic simulation data removed before parsing it. The original DUF file is never modified. This makes the process safe in DS6, although the preliminary analysis takes additional time.

This workaround is included in a larger update that also contains several quality-of-life improvements. The update is ready, but has not yet been submitted.

The underlying issue is not something I can directly fix inside the script: DS6 crashes when parsing some files containing very large simulation_data blocks, sometimes stored in a single line several megabytes long. The same files are parsed correctly in DS4. This is a single line of code, and the access to the underlying treatment of this called function is not on my side (native function).

I have reported the issue to Daz, and it has been passed to the development team. I am currently waiting to see whether they can provide a solution before deciding whether to submit the current "Safe Mode" update. If no native solution is possible, I may eventually - mi term - include an external Python-based parser, but for now I prefer to wait for Daz’s feedback so that I can communicate clearly about the final solution.