Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2026 Daz Productions Inc. All Rights Reserved.
Comments
The script throws the warning as it is, I tested, so it isn't an issue with the main script from which it is excerpted.
It's possible to run multiple DS6 instances at the same time in the same way as it is with DS4 so I see no reason why running DS4 and DS6 at the same time will be impacted. Just put a version number on the command line, or, indeed, a version name.
There are problems if you want to run multiple instances with different content manager libraries but those aren't new; they arise because there is only one CMS database instance by default.
I had a similar issue with spotlights where the spread angle was set to 180 which prevented using the gizmo on any objects, but 179.9 worked fine. In your case the issue seems to be with the SV-ShortsClosedZipperG9 object that is parented to SV-Shorts Closed G9. If you delete that specific object your gizmo will work again. I have no idea why that breaks your scene, but just fyi deleting it fixed the issue for me. So if you run into this issue start deleting objects from your scene until it starts working again to narrow it down.
Thanks for the fix!
I'm using the 2026 beta build 6.25.2026.6423 and I'm having a strange problem. I use both 4.24 and 2026 beta on the same PC and they share the same DAZ database.
I built a scene in 4.24 with a number of G8 and G3 figures in it. There are no G9 figures in the scene. I had already closed the scene in 4.24 and opened it in 2026 beta when I noticed that I forgot to set one of the G8 Female character's feet for the heels she's wearing. Since it was only a small detail I decided to fix her feet rather than closing the scene and re-opening it again in 4.24. If I had been using 4.24 I would have selected a 'Low Heels' pose that's I put into my 'Favorites. It's from one of the numerous Zeddicus products I own: Z Coffee Love Prop and Pose Mega Set. Unfortunately it's not in my 'Favorites' in 2026 beta but I thought it would be easy to find using the 'Smart Content' pane. Unfortunately I was very wrong.
I selected my G8 Female character and went to the 'Smart Content' pane and to my surprise only 6 G9 feet poses showed up. I then un-checked the 'Filter by Content' box to search for my usual 'Low Heels' pose for G8. To my surprise it found 113 feet poses but all of them are for G9 even with 'Filter by Content' unchecked. I don't know what was so special about the original 6 that were found, they are for G9 but so are the other 107 that were found when I un-checked 'Filter by Content'. I closed the scene and opened it in 4.24 and with the same G8 Female character selected and 'Filter by Content' checked if found 373 feet poses and all are for G8. If I un-check 'Filter by Content' if finds 754 feet poses including G3, G8, and G9.
Does anyone have any idea why the 'Smart Content' pane is behaving so badly? Since I always create my scenes in 4.24 I haven't noticed this before now.
Filter ByContext, not Filter By Content.
Are the content directories the same in both versions of DS?
Hopefully the developers are aware that Apple plans to phase out Rosetta 2 starting late next year.
Sorry about the incorrect word, my bad. Both versions of DAZ are using the same content folders so they should show exactly the same results. More importantly, the situation I was having was fixed by exiting both versions of DAZ and re-starting both of them. Now both 4.24 and 2026 beta are showing the exact same results - 373 feet poses when 'Filter by Context' is checked and 754 when it is unchecked. I cannot explain why it happened and I have no idea how to make it happen again. When it was happening I used more than one scene file and it happened with every scene file. After re-starting both versions of DAZ it no longer happens on any of my scene files. I know it's virtually impossible to fix things that aren't reproducible and re-starting the programs seems to fix it so there's nothing to do about this. Cheers!
According to the "Evergreen" thread
Hey guys!
I think I've come across a real bug this time. I was working on a scene 3 G9s+medium size environment and an HDRI (4k I believe). All of the sudden I got a crash with an error saying "Faild to load image...(followed by the path to my HDRI)". I saved the report but I'm not sure how to submit it.
The biggest issue is that now I can't even load an HDRI in any scene that I get this crash error. I tried rebooting my machine, clearing Daz cache, creating a whole new scene, different HDRIs, and reinstalling but nothing seems to work.
I probably need to clear some files to start a new installation fresh? Everything works with Daz 4.24 normally, that's why I assume the problem is just some Daz 2026 Beta files having been corrupted during that first crash, am I wrong?
Thanks, appreciate the help as always.
I'm confused by this post. Are you saying the 3d mouse is supported now? Judging from the screenshot. But you're also asking for support, so no? Mine just says "no device installed" in that menu too.
OpenGL comparison: Maya, Blender, Daz Studio 2026 Beta.
Please provide the specs as text, not just a screenshot. The AMD GPU drivers have had issues with being "too advanced" for OpenCL to work, it may be a similar issue with OpenGL. The chnage log does indicate, however, that there has been OpenGL-related work.
I found an item in a product I purchased from DAZ that causes the 2026 Beta to freeze with a blank "not responding" message. The same item in the product works properly in 4.24. The item is the "CyberpunkSiren Necklace" in the product "Cyberpunk Outfit for Genesis 8 Female(s)". I am attaching a picture showing the item and the blank error message. The same scene without the problem item works normally in both 4.24 and 2026 Beta.
Here's what I did:
1) Working in 4.24 I created a scene with 3 characters to test outfits for a scene I'm working on. I have a 5090 video card so to see what they looked like when rendered I closed the scene and tried to open it in 2026 Beta. The application froze with a blank "not responding" error message and I had to resort to "End Task" in Task Manager.
2) By trial and error using 4.24 and 2026 Beta back and forth deleting different items from the scene each time I learned which item caused the problem.
2) In 4.24 I saved the scene after deleting the problem item, closed the scene, and then opened it in 2026 Beta and it worked normally. I attempted to put the item onto one of the characters in the scene and it appeared on the character but shortly afterwards the same blank "not responding" error message appeared and once again I had to use Task Manager.
Do you have an SKU for Cyberpunk Outfit for Genesis 8 Female(s)?
SKU:71687
Thank you. The error message is actually not blank. Looking into it.
Maybe it wasn't blank for you but you saw my attachment which included a screen shot and it is definately blank on my computer. I have no idea why you got a message and I didn't. Did your's "pop under"? Mine did, I didn't know it was there at first.
It's probably white on white so you can't see it. There should be some way in the preferences to change the colors.
It was just luck that I saw it, other times it was blank.
Interesting idea but if you're right then I guess I need to report another bug. I have never seen any color settings in this app so I certainly haven't changed them, If the default error message colors are white on white that's a bug!
Potentially DS 6 doesn't like tga files.
It does has an tga importer, it's being looked at.
The updated\current build (x.9715) fixes the memory issue on macOS when using 4k scaling. 4k Scaling should now be available again.
Woo hoo! Thanks for the update, downloading now!
I have an intermittent problem that forces me to restart the beta build (x9715). Sometimes when using the node selection tool and/or the universal tool I click on a node in the scene on the main viewport and the wrong node is selected on the scene tab. Most recently I clicked on character's left thigh but on the scene tab it selected the character's eye instead. I switched back and forth between the two tools but the same thing happened either way. After a half dozen or so clicks it started picking a different node on the character but it was not the left thigh that I was clicking on. In the viewport the left thigh highlights when I click on it so I know I'm not missing it. If I restart this incorrect node selection problem goes away but once in a while it starts happening again. It's infrequent and I have no idea what I'm doing that starts this behavior. Has anyone seen this and, if so, do you know what's causing it? If I knew what I'm doing that causes it I'd stop doing it! I should probably mention that I've never had this problem in 4.24 but it has happened occassionally throughout the alpha builds. Since it was very infrequent and I had no idea what causes it I never posted about it before.
Sorry, that's something I should have said in the first place. I'm on Windows 11.
I noticed there seems to be a bug when using keyboard shortcuts. They only work after I click into a viewport? Shift-y for example, the symmetry thing. Has this been reported?
Not sure but I think theres an issue with scripting iRay render size outputs in 2026 (Latest Build) that work correctly in DS 4.24.0.4
// IrayRenderSizeRepro.dsa
//
// Minimal reproduction script for DAZ bug report:
// "Iray DirectToFile renders ignore imageSize / Render Width / Render Height —
// output is always viewport-sized."
//
// Steps to reproduce:
// 1. Open any scene with at least one object.
// 2. Ensure Iray is the active renderer.
// 3. Run this script.
// 4. Check the Script IDE console and the two output files.
//
// Expected: render_091x091.png is 91x91 pixels,
// render_256x256.png is 256x256 pixels.
// Actual : both files are the same size (viewport resolution).
//
// Tested on DAZ Studio 2026.
(Forgive the formatting of the script)
Please see the attached script and be sure to change the path to somewhere you have permissions to write to.