Loading...
> >

Daz Studio 2026 Beta - version 6.25.2026.4408! (Updated February 18, 2026)

1…5859606163

Comments

  • Lord TherosLord Theros Posts: 73
    edited February 16

    felis said:

    Lord Theros said:

    Just started tryin the alpha version... but with the removal of 3dlight some older materials look weird on the view port, completely losing definition

    wich makes it near impossible to pose right.

    is there a fix for that of some sort?

     

    Thanks in advance!

    Theros

    Can't you just apply Iray Uber shader to all surfaces? 

    It even happens to some Iray materials, but Im gonna try it and report back

     

    Post edited by Richard Haseltine on
  • Lord TherosLord Theros Posts: 73

    I found the issue... it was the preview lights! the moment I turned them of I could see the scene again onthe viewport

    Its not as good as the old render engine, but its usable at least.

     

  • Richard HaseltineRichard Haseltine Posts: 108,996

    Lord Theros said:

    I found the issue... it was the preview lights! the moment I turned them of I could see the scene again onthe viewport

    Its not as good as the old render engine, but its usable at least.

    There is an issue with the lighting with Preview Lights (try to show the current liughts, not a special set of lights for prevewing) when the camera/view is away from the world centre.

  • GranvilleGranville Posts: 698

    I'm exiled in the 2026 Alpha with my 5080 card. What are people doing without the histogram plugin? 

  • jjb24jjb24 Posts: 36

    Granville said:

    I'm exiled in the 2026 Alpha with my 5080 card. What are people doing without the histogram plugin? 

    Just my two cents worth. Many people with new cards create scenes in the release version and render them in the alpha. I'm lucky enough to have a good enough PC to run them simultaneously and can work on one scene and render a different scene at the same time by doing this. 

  • FalcoFalco Posts: 259

    I think the most noticeable issue is that the outliner doesn't count as the viewport, so if you click on something in the outliner to select it, the hotkeys still won't work unless you click back to the viewport.  I do the majority of my selection using the outliner, so it makes using hotkeys a pretty tortured process.  

    JD said:

    Daz Studios ALPHA version 6.25.2026.2920 feedback.
    - The shortcuts now feels cluncky. The Viewport pane must be the active viewport for any keyboard shortcuts to work. I can see this is a step in the right direction of making it feel like Blender where it is "smart", but it's not quite there yet. Daz Studios currently isn't aware of the mouse location for the tabs it is currently hovering over. But I can assume this is what the Daz Dev team is trying to do with this update. Otherwise, I am not sure why this update was pushed.

    - For example, why I say this feels cluncky is that my workflow over the years relies on custom keybinds to speed up my creation process. I tried using this version for several scenes, but I ended up reverting back to the previous last year version, Daz 6.25.2025.35308, to feel a sense of normality of my workflow. Sure I can adjust my workflow to the new version's behavior, but I choose not to at this moment and hope for a change in the future.

    - To further explain why this feels cluncky, as some users stated, certain keybinds do not work as intended before, such as the symmetry shortcut. In order to get any shortcuts to work, the user has to click and make the Viewport tab active. This adds 1 extra step for all shortcuts.

     

     

    I tried to find the changelog information for this version update, however, I do not know enough to pinpoint the changes.

    https://docs.daz3d.com/public/software/dazstudio/6/change_log#6_25_2026_2920

     

     

    Honestly, I hope the key shortcuts issue will be fixed in future iterations, as I do not want to get left behind staying on version 6.25.2025.35308.

  • HavosHavos Posts: 5,610

    I noticed at the end of this change log: https://docs.daz3d.com/public/software/dazstudio/6/change_log#6_25_2026_2920

    It talks about a new version "DAZ Studio : Incremented build number to 6.25.2026.4408". It includes this line among the changes: "Switch application from alpha to beta"

    I assume this implies that the next version out will be a beta, rather than an Alpha, so maybe the SDK is close to finalisation.

  • JDJD Posts: 34

    Falco said:

    I think the most noticeable issue is that the outliner doesn't count as the viewport, so if you click on something in the outliner to select it, the hotkeys still won't work unless you click back to the viewport.  I do the majority of my selection using the outliner, so it makes using hotkeys a pretty tortured process.

    I agree. One of my workflows for exporting OBJs for morphs sculpting in Blender requires me selecting the object/figure node in the Scene tab (outliner) with a hotkey I assigned for export. The additional step of having to make the Viewport tab active to make the hotkeys functional is indeed a tortured process.

  • JDJD Posts: 34

    Havos said:

    I noticed at the end of this change log: https://docs.daz3d.com/public/software/dazstudio/6/change_log#6_25_2026_2920

    It talks about a new version "DAZ Studio : Incremented build number to 6.25.2026.4408". It includes this line among the changes: "Switch application from alpha to beta"

    I assume this implies that the next version out will be a beta, rather than an Alpha, so maybe the SDK is close to finalisation.

    Interesting catch. For me at least, the ALPHA build does feel stable enough. Most of the updated scripts have been working for several of the previous ALPHA versions.

    My guess is that the DAZ Dev team wanted to get Geometry Sculptor in a good position before moving the software from ALPHA to BETA?

  • TojiroTojiro Posts: 70
    edited February 18

    I got Premier and am using 2026 Alpha, and I used to like having the Render Queue restart Daz after each render to clear the VRAM.  But now with the Alpha when I turn on the setting to have it restart after each render, a box pops up after each render asking me if I want to save the file (even though nothing has changed in it).  This causes the RQ to stall.  Is there a workaround for this?

    Post edited by Tojiro on
  • jmtbankjmtbank Posts: 188

    Anyone having trouble with clothes not autofollowing past 100% in the latest build?

    Can't see this mentioned above so maybe just me.

  • FalcoFalco Posts: 259

    Can't speak to that specific problem, but Iray Server doesn't cost money anymore so it's another option for queing up renders.  Since it's a separate queue unrelated to Daz you don't have to have Daz running which can help on the memory side.   

    Tojiro said:

    I got Premier and am using 2026 Alpha, and I used to like having the Render Queue restart Daz after each render to clear the VRAM.  But now with the Alpha when I turn on the setting to have it restart after each render, a box pops up after each render asking me if I want to save the file (even though nothing has changed in it).  This causes the RQ to stall.  Is there a workaround for this?

  • Richard HaseltineRichard Haseltine Posts: 108,996

    jmtbank said:

    Anyone having trouble with clothes not autofollowing past 100% in the latest build?

    Can't see this mentioned above so maybe just me.

    For example?

  • nemesis10nemesis10 Posts: 3,878

    I can't seem to be able to select windows or click anything post login on my mac in this latest build!

  • jeffbdvsjeffbdvs Posts: 44

    I waited until the beta to give 2026 a try. I have a Mac Studio M2 Ultra running macOS 26.3. 

    The UI text is ridiculously small. Changing my display resolution from the default 2560x1440 all the way down to 1280x720 made the UI text more readable, but still not user-friendly.

    Since I haven't come across many Windows or Linux users that are having the same issue, I assume it's a Mac-only thing? For reference 4.24 (latest) handles the UI text much better. Although smaller than I would like at 2560x1440, it is functionally superior, and the font sizes relative to each other for tabs, menus and parameters are much more sensible than what 2026 beta has.

    The three attachments show 4.24.04 at 2560x1440, 6.25 at 2560x1440 and 6.25 at 1280x720. Hopefully the devs will agree that the UI font issue has to be solved. We were told before that Qt4 couldn't handle it, but Qt6 or Qt5 (whatever Studio is using now) surely is able to?

    42404At2560x1440.png
    5114 x 2870 - 3M
    625At2560x1440.png
    5106 x 2852 - 1M
    625At1280x720.png
    2556 x 1434 - 619K
  • Richard HaseltineRichard Haseltine Posts: 108,996

    jeffbdvs said:

    I waited until the beta to give 2026 a try. I have a Mac Studio M2 Ultra running macOS 26.3. 

    The UI text is ridiculously small. Changing my display resolution from the default 2560x1440 all the way down to 1280x720 made the UI text more readable, but still not user-friendly.

    Since I haven't come across many Windows or Linux users that are having the same issue, I assume it's a Mac-only thing? For reference 4.24 (latest) handles the UI text much better. Although smaller than I would like at 2560x1440, it is functionally superior, and the font sizes relative to each other for tabs, menus and parameters are much more sensible than what 2026 beta has.

    The three attachments show 4.24.04 at 2560x1440, 6.25 at 2560x1440 and 6.25 at 1280x720. Hopefully the devs will agree that the UI font issue has to be solved. We were told before that Qt4 couldn't handle it, but Qt6 or Qt5 (whatever Studio is using now) surely is able to?

    https://docs.daz3d.com/public/software/dazstudio/6/change_log 6.25.2025.34208

    • Implemented a workaround for a Qt/macOS bug where system memory is quickly consumed when devicePixelRatio is not 1.0 - e.g., 4K displays

      • High-DPI scaling is effectively disabled on macOS

        • Prevents the runaway memory situation from occurring at the expense of causing individual UI elements to appear smaller on screen

      • This workaround is not intended to be permanent

        • Intention is to allow other aspects of the application to continue testing while a proper solution to the underlying issue is sought

  • inquireinquire Posts: 2,439

    And of course, the Mac version is still running an emulation, Isn't it?

  • TojiroTojiro Posts: 70

    Falco said:

    Can't speak to that specific problem, but Iray Server doesn't cost money anymore so it's another option for queing up renders.  Since it's a separate queue unrelated to Daz you don't have to have Daz running which can help on the memory side.   

    Thanks!  I'll look into this! 

  • sidcarton1587sidcarton1587 Posts: 62

    Tojiro said:

    Falco said:

    Can't speak to that specific problem, but Iray Server doesn't cost money anymore so it's another option for queing up renders.  Since it's a separate queue unrelated to Daz you don't have to have Daz running which can help on the memory side.   

    Thanks!  I'll look into this! 

     

    Have you found a method to submit DAZ scenes directly to the iRay Server? As far as I am aware you still need to submit them through the iRay Server Bridge in DAZ Studio, but if you found a way around that would be really interested in knowing about it. :-)

     

     

     

     

     

  • Richard HaseltineRichard Haseltine Posts: 108,996

    inquire said:

    And of course, the Mac version is still running an emulation, Isn't it?

    You mean Rosetta 2? Yes, as far as I know - the change lof doesn't say otherwise.

  • Faery_LightFaery_Light Posts: 23
    edited February 19

    I can't find a download link even after installing the latest DIM, where is it?

     

    Never mind, finally got it to install tyhe correct dim and found it. :)

     

     

    Post edited by Faery_Light on
  • TugpsxTugpsx Posts: 819

    nemesis10 said:

    jbowler said:

    The LOD script doesn't work on Alpha at all.  I'm surprised that things are still being released that simply won't work on the next version.  It's not that _all scripts don't work_; 3DU's pose controls (the ones to lock and unlock the parameters) work just fine.  Good thing or I wouldn't be able to use the Alpha at all!  Iray Light Manager Pro, which I always found very useful, does not work but it's fairly old and I've worked out how to do all the important stuff myself (though dealing with emissive surfaces is still a PITA, with or without the script.)

    Most Scripts that are released will probably not work with the Alpha; that is kind of the point of being an Alpha i.e. to get a working proof of concept rather than a finished product for people to write scripts for.  Hence, the scripts work perfectly fine in the general release and Beta.  I would be if people were writing scripts for such an early work in progress.

    If the scripts are first edited in DS6 and then encrypted in DS4 they will work in both versions. Some scripts created in DS6 or DS4 and encrypted in DS6 will not work in DS4 due to the change in encryption schema.
    Some unencrypted scripts work great in both versions, but to distribute them they should be in DES format which causes them to no longer work in DS4 if DS6 is the encrypter.

  • MrRogerSmithMrRogerSmith Posts: 131

    I just tried out the new Beta and the keyboard navigation now moves smoothly.  I'm very excited about this, since this had been the number one obstacle to my using the new Daz.

  • FalcoFalco Posts: 259

    No I use the bridge from daz to add the scenes to the iray server queue, never had an issue with that workflow, you just need to keep both up to date.  

    sidcarton1587 said:

    Tojiro said:

    Falco said:

    Can't speak to that specific problem, but Iray Server doesn't cost money anymore so it's another option for queing up renders.  Since it's a separate queue unrelated to Daz you don't have to have Daz running which can help on the memory side.   

    Thanks!  I'll look into this! 

     

    Have you found a method to submit DAZ scenes directly to the iRay Server? As far as I am aware you still need to submit them through the iRay Server Bridge in DAZ Studio, but if you found a way around that would be really interested in knowing about it. :-)

     

     

     

     

     

  • Ron KnightsRon Knights Posts: 2,339
    edited February 20

    This morning, I tried running the Alpha version and got Access Violation errors. 

    Then I got the beta version on DIM, and ran it once. Then I went to lunch.

     

    access violation.png
    531 x 516 - 35K
    Post edited by Ron Knights on
  • Richard HaseltineRichard Haseltine Posts: 108,996

    Ron Knights said:

    This morning, I tried running the Alpha version and got Access Violation errors. 

    Then I got the beta version on DIM, and ran it once. Then I went to lunch.

    Looks like a style-related issue, installing while DS is running can cause those - but not usually a crash. It is also possible that a bad file, for that reason or others, is not being removed and repalced by the update. It may be worth unisntalling and making sure that the application folder (inm Program Files) is empty before trying to reinstall (you need to reinstall plug-ins anyway, so unlike with DS 4 it iisn't making more work than a regular update).

  • Richard HaseltineRichard Haseltine Posts: 108,996

    Tugpsx said:

    nemesis10 said:

    jbowler said:

    The LOD script doesn't work on Alpha at all.  I'm surprised that things are still being released that simply won't work on the next version.  It's not that _all scripts don't work_; 3DU's pose controls (the ones to lock and unlock the parameters) work just fine.  Good thing or I wouldn't be able to use the Alpha at all!  Iray Light Manager Pro, which I always found very useful, does not work but it's fairly old and I've worked out how to do all the important stuff myself (though dealing with emissive surfaces is still a PITA, with or without the script.)

    Most Scripts that are released will probably not work with the Alpha; that is kind of the point of being an Alpha i.e. to get a working proof of concept rather than a finished product for people to write scripts for.  Hence, the scripts work perfectly fine in the general release and Beta.  I would be if people were writing scripts for such an early work in progress.

    If the scripts are first edited in DS6 and then encrypted in DS4 they will work in both versions. Some scripts created in DS6 or DS4 and encrypted in DS6 will not work in DS4 due to the change in encryption schema.
    Some unencrypted scripts work great in both versions, but to distribute them they should be in DES format which causes them to no longer work in DS4 if DS6 is the encrypter.

    .dse rather than .des

  • MrRogerSmithMrRogerSmith Posts: 131

    MrRogerSmith said:

    I just tried out the new Beta and the keyboard navigation now moves smoothly.  I'm very excited about this, since this had been the number one obstacle to my using the new Daz.

    However, from time to time the viewport skips/jumps a small amount.  Still a big improvement, but worth noting for the dev team.

  • YuiYui Posts: 12

    How do I download this beta!? It doesn't show up in the DIM!

  • wsterdanwsterdan Posts: 3,106

    Ran a few initial tests with the Beta, so far so good. I can still load an audio file and hear it, apply lip synching to a character, render out a .mov file and import that into  video software with the audio track intact. Excellent. None of the functionality I need has been lost (so far).

    I could sure use bigger text, though. That's wearing a little thin...

Sign In or Register to comment.