Daz Studio 2025 ALPHA - version 6.25.2025.11417! (UPDATED)

Daz SoftwareDaz Software Posts: 39
edited April 25 in Daz Studio Discussion

Daz 3D is pleased to announce Daz Studio 2025 ALPHA - version 6.25.2025.11417!

 


Highlights:

 

NOTE: For details on the minimum GPU driver required by the NVIDIA Iray version included in a specific version of the application, consult the threads linked above. The last minimum noted persists until a newer version of NVIDIA Iray is integrated into a newer version of the application.

 


Frequently Asked Questions:

 

 


Previous Public Build Threads:

 

  • ...
    • 6.25.2025.11417 (April 25, 2025)
    • 6.25.2025.11206 (April 22, 2025)

 

  • 4.23.1.47 (April 15, 2025)
    • 4.23.1.44 (March 31, 2025)
    • 4.23.1.40 (February 25, 2025)
    • 4.23.1.36 (February 14, 2025)
    • 4.23.1.27 (January 30, 2025)
    • 4.23.1.23 (January 23, 2025)
    • 4.23.1.20 (January 16, 2025)
    • 4.23.1.18 (January 13, 2025)
    • 4.23.1.8 (December 10, 2024)

 


General Release Threads:

 

  • ...
  • 4.23.0.1 (October 7, 2024)
  • 4.22.0.16 (February 27, 2024)
    • 4.22.0.15 (December 18, 2023)
  • 4.21.0.5 (October 12, 2022)
  • 4.20.0.17 (April 29, 2022)
    • 4.20.0.2 (February 18, 2022)
  • 4.16.0.3 (November 22, 2021)
    • 4.15.0.30 (September 2, 2021)
    • 4.15.0.2 (January 7, 2021)
  • 4.14.0.10 (December 2, 2020)
    • 4.14.0.8 (November 10, 2020)
Post edited by rbtwhiz on
«13456714

Comments

  • IceCrMnIceCrMn Posts: 2,181
    edited April 22

    Thank you Daz developers for this new version of Studio

     

    For the curious

    2025 is using qt6

    2025-04-22 09:27:34.656 [INFO] :: Qt Version: 6.9.0

     

    My RTX 3060 12GB is supported and was working right after install with no additional setup or anything using Nvidia Driver version 572.83

    ---

    There are some very obvious performance increases

    Loading assets like characters and loading clothing onto them is vastly improved.

    The new "texture shaded" view is much easier to see and work in.

    Text seems to be a bit larger and easier to read in some of the panes...will need others to try this out and see if I'm just seeing it differently.

    All the mdl shaders from Nvidia that I've tried seem to be working correctly. Not everyone will have these as they are an additional download and require a semi-advanced install, but fot those that do have and use them the few I've tried all worked.

    If I leave the Iray preview renderer running and change shaders or Surface settings it seems to be nearly instantly updated in the preview.

    I'll end this here and continue playing with the new 2025.

    So far it's a major improvement.

    Well done Daz developers! Homerun!

    Post edited by IceCrMn on
  • evacynevacyn Posts: 979

    Do we know what won't work with this new ALPHA? Do older plugins still work? Was there any UI redesign (i.e., can I still use my current layouts, etc.)?

  • IceCrMnIceCrMn Posts: 2,181

    I just copied my layout from the last beta version and it worked just fine.

    I didn't expect my 3rd party plugins to work because 2025 ALPHA was litterally just release a few minutes ago.

    I certainly do hope at least manfriday updates meshgrabber for it

  • Just tried it.

    Viewport and Filament have gotten Much worse performance wise as it is. but a fully clothed character immediately causes a lot of viewport lag, also already adjusted my settings, didn't help.

    Compared to 4.23 where i barely have any viewport lag in the same scenes.

    Strand-based hair works, but no longer reacts to "viewport color" and stays black, also already seeing a few Opacity map issues.

    In it's current state it's unbearable to work with due to the viewport lag.

  • IceCrMnIceCrMn Posts: 2,181

    I'm not seeing much viewport lag.

    What issues are you having with opactiy maps?

  • Ghosty12Ghosty12 Posts: 2,077

    Just downloaded iit and it does look swish, can wait for the general release to have all my plugins and what not up and running. smiley

  • LeanaLeana Posts: 12,063

    evacyn said:

    Do we know what won't work with this new ALPHA? Do older plugins still work? Was there any UI redesign (i.e., can I still use my current layouts, etc.)?

    Older plugins do not work at all, they all would need to be updated (recompiled with the new SDK at minimum).

    Some scripts do work, some will also need an update as there were changes to the scripting engine and SDK.

    So far UI seems similar, but since the framework which handles the UI was updated I don't know how compatible older layouts are.

  • memcneil70memcneil70 Posts: 4,459
    edited April 22

    Any word on when simulation/dForce will be available on DAZ 2025?

    Never mind, it just formed up on my screen. Seems to be a lag.

    But I couldn't find USC2 or Power Pose or Mesh Grabber.

    Post edited by memcneil70 on
  • MasterstrokeMasterstroke Posts: 2,104

    IceCrMn said:

    I'm not seeing much viewport lag.

    What issues are you having with opactiy maps?

    I'm having a viewport lag as well and already had my first crash.
    AMD CPU 64GB RAM
    NVIDEA 3060 12GB
    Driver: 537.58

  • IceCrMn said:

    I'm not seeing much viewport lag.

    What issues are you having with opactiy maps?

    I'm seeing that on some things using opacity, there is a excessive non-opaque area showing, as if the maps aren't working fully.

    as for the viewport, for me it's immediately noticeable, but even without anything in the scene, the viewport feels less responsive, when something such as a clothing set is loaded in, there is an immediate dip in FPS and can feel it became laggy and sluggish to move around.

  • IceCrMnIceCrMn Posts: 2,181

    Masterstroke said:

    IceCrMn said:

    I'm not seeing much viewport lag.

    What issues are you having with opactiy maps?

    I'm having a viewport lag as well and already had my first crash.
    AMD CPU 64GB RAM
    NVIDEA 3060 12GB
    Driver: 537.58

    The new version of iray requires a newer version of the nvidia driver

    https://www.daz3d.com/forums/discussion/comment/9142856/#Comment_9142856

    • REQUIRES:
      • NVIDIA Driver 57x.xx (R570) on Windows
      • See NVIDIA Driver Downloads
        • NVIDIA recommends installing Studio Drivers (SD)
      • ​SSSE3 enabled CPU is a minimum requirement on macOS/x86
  • LeanaLeana Posts: 12,063

    memcneil70 said:

    But I couldn't find USC2 or Power Pose or Mesh Grabber.

    None of your plugin for DS4 will work with DS 2025 "as is".

  • ElorElor Posts: 2,265

    memcneil70 said:

    But I couldn't find USC2 or Power Pose or Mesh Grabber.

    Plugins won't work at all without an update, which explain the missing USC2 and Mesh Grabber (at least if you're speaking about Mesh Grabber 3, I'm not Premier currently so no idea if the Premier version was updated for Daz Studio 2025).

    Scripts may work, but some will require an update.

    Power Pose should still work but you'll likely have to reopen it, either by right clicking in an empty space on the panel you want to attach it, selecting 'Add a pane to group' > 'Power Pose' or if you prefer to have it as a floating windows, Windows > Panes (Tabs) > Power Pose.

  • IceCrMnIceCrMn Posts: 2,181
    edited April 22

    could someone please post an example of the opacity map problem?

    I can't seem to reproduce it.

    Post edited by IceCrMn on
  • ElorElor Posts: 2,265

    There seems to be a one time bug with MacOS: on Ventura, when I launched Daz Studio 2025 for the first time, each entry of the menu was duplicated (so I had two Tools entries, and so on). Daz crashed when I tried to load a figure (Willow 9, I don't think it's related to that figure).

    Once I reloaded Daz Studio 2025, the duplicate entries were not here anymore and I could load Willow 9 without any problem.

    I didn't thought about saving the log file, sorry.

    Other peoples on the Mac FAQ also had the same problem, so if a Mac user also have it, relaunching Daz Studio 2025 after that first crash should solve the problem.

     

  • IceCrMn said:

    could someone please post an example of the opacity map problem?

    I can't seem to reproduce it.

    Try something that is not hair (on hair it's fine), but an item that uses opacity maps for me at least there are some clear issues. also when you are using instances, i've noticed that every instance has an unremovable Tri-ax (like what you use to move things around with in a scene) above each instance.

  • IceCrMnIceCrMn Posts: 2,181
    edited April 22

    dbmelvin1993 said:

    IceCrMn said:

    could someone please post an example of the opacity map problem?

    I can't seem to reproduce it.

    Try something that is not hair (on hair it's fine), but an item that uses opacity maps for me at least there are some clear issues. also when you are using instances, i've noticed that every instance has an unremovable Tri-ax (like what you use to move things around with in a scene) above each instance.

    yea, I've tried clothes, primitive plane, cube, cone, bodysuits, hair, brows, all of mine seem to be working.

    Not sure what could be the difference between what I'm doing and what you are that would have us seeing different output.

     

    So far the only thing I've noticed that doesn't work is the "Brow Eraser" for "Beautiful Brows".

    It applies, but the output is terrible.

    I'll play with that more latter as right now I'm looking for just general "things that don't work".

    I'll figure out the "why don't they" and "how do I fix it, if I can" part later today :)

     

    anyway, if you could, would you please post a screen shot of the problem.

    it would help alot for those interested in finding out why it doesn't function properly

    Post edited by IceCrMn on
  • Thanks for your effort, but the new version isn't for me. I haven't noticed any advantages when working with it (yet). Quite the opposite. Unfortunately, no settings have been carried over from the current version. I would now have to do everything again. So years of work have been completely in vain. No paths are carried over, no custom styles. It's good that at least the categories I've added myself are still there. So please let me know when the new version is ready, so that I can just carry on working with the new version without having to repeat years of work, only to find that a new program update once again doesn't recognize the paths and settings of the previous version.

  • IceCrMnIceCrMn Posts: 2,181
    edited April 22

    mfrank01328_e9ea05b22a said:

    Thanks for your effort, but the new version isn't for me. I haven't noticed any advantages when working with it (yet). Quite the opposite. Unfortunately, no settings have been carried over from the current version. I would now have to do everything again. So years of work have been completely in vain. No paths are carried over, no custom styles. It's good that at least the categories I've added myself are still there. So please let me know when the new version is ready, so that I can just carry on working with the new version without having to repeat years of work, only to find that a new program update once again doesn't recognize the paths and settings of the previous version.

    All I did was copy my "user styles" and "user layouts" folders from %appdata%/Daz 3D/Studio4 Public Build to %appdata%/Daz 3D/Studio6 Public Build, launch 2025 and set them in the Styles/layout menu.

    My scripts/favorties aren't in the menu bar, but thats an ongoing problem with all versions of Studio. Every time I get an update it removes them and I have to replace them.

     

    Post edited by IceCrMn on
  • MKDAWUSSMKDAWUSS Posts: 95

    So is this what used to be the long-waited DS 5?

  • Looking at that version naming convention it is DAZ 6...

  • dbmelvin1993dbmelvin1993 Posts: 83
    edited April 22

    Okay, So just did a side-by-side comparison between 4.23 and the Alpha Build. Opening the same scene on both.

    4.23 moves around my scene with little to no lag, and i can move around very smoothly, On the Alpha build, it's one laggy mess at the moment and just unbearable and unusable for me like that, the decrease in FPS is immediately visible and can be felt very much too.

    Until that improves, i'm not going to bother with this alpha build.

    Post edited by dbmelvin1993 on
  • LeanaLeana Posts: 12,063

    mfrank01328_e9ea05b22a said:

    Thanks for your effort, but the new version isn't for me. I haven't noticed any advantages when working with it (yet). Quite the opposite. Unfortunately, no settings have been carried over from the current version. I would now have to do everything again. So years of work have been completely in vain. No paths are carried over, no custom styles. It's good that at least the categories I've added myself are still there. So please let me know when the new version is ready, so that I can just carry on working with the new version without having to repeat years of work, only to find that a new program update once again doesn't recognize the paths and settings of the previous version.

    Beta (and alpha) versions have separate settings and application data files from the general release on purpose, so that changing settings to accomodate the beta wouldn't impact your general release. 

    You can copy over layouts and paths quite easily.

  • IceCrMnIceCrMn Posts: 2,181
    edited April 22

    I'm sure it was called an "alpha" version on purpose becasue the develpoers felt it wasn't production ready.

    So far, I'm liking what I see very much.

    Deleteing things from a scene is very fast. So is changing shaders and surface parameters, loading characters and assets. These things are nearly instant for me.

    The new veiwport drawstyle for texture shaded is much easier to see and work in for me.

    Others seem to be having lag issues, but I'm assuming it's framebuffer related or whatever. It's an alphs build so I assume that can be improved.

    We aren't at the video game type expereince yet, but we are closer now that we have been.

    I think this is a very well done alpha preview.

     

    Did you guys see the new html color code input option on the color select popup menu or the built-in color picker?

    this is a nice feature

    Post edited by IceCrMn on
  • LeanaLeana Posts: 12,063

    IceCrMn said:

    I'm sure it was called an "alpha" version on purpose becasue the develpoers felt it wasn't production ready.

    From the blog post: "This is an ALPHA build—meaning features are still under development and bugs are expected. We’ll continue rolling out updates and improvements as we work toward the full release."

  • IceCrMnIceCrMn Posts: 2,181
    edited April 22

    Leana said:

    IceCrMn said:

    I'm sure it was called an "alpha" version on purpose becasue the develpoers felt it wasn't production ready.

    From the blog post: "This is an ALPHA build—meaning features are still under development and bugs are expected. We’ll continue rolling out updates and improvements as we work toward the full release."

    Correct

    So don't expect it to be feature complette or production ready just yet. 

    Sorry I think I misundersttod your post.

    I think you trying to correct me.

    Yes, I've been involved with software for over 40 years now.

    I know what an alpha version is thank you :)

    I've been compliling my own linux OS's since 2004. Even writting the boot scripts. My latest Arch install I boot straped from bare metal just for the entertainment value.

    I'm very familiar with software versioning.

    I was trying to point out exactly that.

    This is an alpha version. Therefore not feature complete, nor production ready :)

     

    anyway, I'm off to go explore our new toy.

    lot's of things have been improved and other new things to discover from what I've read on the notes.

    I'll check back later this evening and see what others have discovered.

    Post edited by IceCrMn on
  • Hello everyone

    I just downloaded Alpha build to try out rendering with 50 series card, but I find out that WASD movement is not working properly

    when I hold the key, camera is not moving, but if I single click the key it will move little bit

    Also I tried to use tool setting for scene navigator, if I click move control once I can hold WASD and it moves smoothly, but as soon as I drag camera with my mouse it move back to single click move again

    Is this a bug or am I missing something, thanks

  • Pantros2Pantros2 Posts: 102

    MKDAWUSS said:

    So is this what used to be the long-waited DS 5?

    No and Yes, This is the next generation of Daz. Daz 5 was scrapped/completely overhauled at some point and a new project was started which is Daz Studio 2025 or DS 6. But, most of what was going to go into Daz 5 is probably going to show up in Daz2025. 

  • LeanaLeana Posts: 12,063

    IceCrMn said:

    Leana said:

    IceCrMn said:

    I'm sure it was called an "alpha" version on purpose becasue the develpoers felt it wasn't production ready.

    From the blog post: "This is an ALPHA build—meaning features are still under development and bugs are expected. We’ll continue rolling out updates and improvements as we work toward the full release."

    Correct

    So don't expect it to be feature complette or production ready just yet. 

    Sorry I think I misundersttod your post.

    I think you trying to correct me.

    Yes, I've been involved with software for over 40 years now.

    I know what an alpha version is thank you :)

    I've been compliling my own linux OS's since 2004. Even writting the boot scripts. My latest Arch install I boot straped from bare metal just for the entertainment value.

    I'm very familiar with software versioning.

    I was trying to point out exactly that.

    This is an alpha version. Therefore not feature complete, nor production ready :)

    I was not trying to correct you or explain what an alpha is, just pointing out that Daz stated it was still a work in progress in the blog too.

  • ImagoImago Posts: 5,400

    AniMate is missing... Is that just an "ooops!" or it will be eliminated totally?

Sign In or Register to comment.