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
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
Yep, in both cases. Has always been set to that in previous releases as well. Only DAZ 2025 has that lagginess.
Edit: After a driver update, Iray itself is better, but there's still a momentary lag when switching between Panes (particularly Viewport and Aux Viewport).
Everything save for scripts runs magnificently, as for the viewport, ironically you can actually navigate to at least 3-4 fps while in Iray-mode, otherwise, it's unusable...
EDIT: Just read the post above me, and can confirm the aux viewport is ganked!
I don't know where send the bugs of the alpha version, but the render
Subject: Request to Keep the "Free to Use" Option Available
Dear DAZ 3D Team,
I am a passionate user of DAZ Studio and a strong supporter of your platform. One of the things that makes DAZ Studio truly special is its accessibility — offering it as free software has opened creative opportunities for countless artists, hobbyists, and newcomers around the world.
I respectfully ask that you continue to keep DAZ Studio free to use. The free access empowers people of all skill levels and backgrounds to explore 3D art, storytelling, and design without financial barriers. It also helps build a vibrant, diverse community that ultimately benefits the entire DAZ ecosystem, including your marketplace.
Thank you for your consideration and for providing such a powerful tool to the creative community. I’m excited to see how DAZ continues to grow and inspire!
Dear Daz Team,
I am a regular user of your software, and I truly appreciate the value it provides. One of the aspects I find most important is the availability of the "free to use" option, which makes daz 3d accessible to a wide range of people, including those who may not be able to afford a paid version.
once again Thank you for your understanding and for the amazing software .
Sincerely,
rajesh kumare
I'm majorly disappointed. I've spent the better part of two days fixing a computer problem and installing Window 11 on a new NVME drive.
I'm in the middle of uing DIM to install all my content from scratch.
I can't seem to get DIM to install DAZ Studio 2025. I looked at a couple threads and found no info.
It's 2:21AM, and I need to drag myself to bed.
Help?!
Do you see it in DIM? Is it checked in the Downloads setting of DIM? There is also an Install Module to make it easier.
I tried the aux viewport today, and I have to say: if the main viewport is laggy at 15 FPS, the aux one runs at 2 FPS, simply unusable
I should add that I only use DIM or Content Wizard to install products into Daz Studio. I generally 'export user data' each day I am in D|S. Of course, with Macs, crashes are expected. It generally takes four crashes when D|S or a opening a script to get D|S stable and then I am good to go in the Beta. It is better than it used to be. But I try to never log into DAZ. It messes everything up.
DAZ Studio 2025 is listed in DIM.
What happens when you try to install it?
There has been absolutely no indication that Daz Studio 2025 will undergo any changes in this respect.
I do need to note that a product, Bay Bridge DS SKU 8973, that I had initially installed in the MacMini Pro M4 for the Beta and had to uninstall because it was calling for or unable to find textures, or something and is showing up in Smart Content greyed out. It should only do that on the Install pane. And on the Install pane I have six products there including four I have never attempted to install on this computer. One a centaur and the other a lite version of an HDR Mesh Light that I have the full version installed. The other two I Genesis Ranger and its texture set, don't want to install. One other, a shader, I decided to uninstall, not a problem with it, just too complex for me.
So only two items should be reflected on the Install pane, and four should not but are in the Alpha.
One is on Smart Content in Lost and Found that is not installed in the Alpha.
These do not show up in the Beta.
I normally do not have the Install pane open, did this only to check on it for this entry.
Animation playback FPS using Filament is nearly half in 2025 vs 4.23. Posing lag is also worse. Switching to Texture Shaded does improve it (and looks way better than it looks in 4.23, butt darker than Filament).
With regards to the comments about DAZ being not great for animation - yes, its not a swiss army knife with all the bells and whistles like a Maya or Blender... it won't create production quality sharp animations. However, for certain situations, it is MUCH faster to prototype and produce a decent animation in DAZ without all the fancy IK rigs, etc. It has a different approach and I appreciate that. It is just another tool in the toolbox.
DAZ animation has some very interesting tools/implementations like Auto IK with its posing tools (Universal + ActivePose with pins), Puppeteer, and Animate2.. along with paid plugins/tools like Spring Dynamics, LimbStick, and various others. Other than the plugins, the main tools are not seen in any other 3D app and it is a class of its own. I dare say way ahead of its time. I just wish DAZ had continued to foster further development and improvements on these tools like Puppeteer.
As for the timeline... it needs a complete rework, honestly. However, sadly animation is just a "side thing" for DAZ. They really should open source many of these tools so the community can help here.
Filament can do a lot more, I hope DAZ continues to plumb it all together so that it will be a render engine of choice rather than just a preview option.
Richard, I use DIM to install everything. It appeared that DAZ Studio 2025 was installed properly.
It still doesn't show in the Start menu, or in the Windows File Manager.
have you given it permission to add a desktop icon and link in your start menu?
anyway one can manually do both
I worked in DS 2025 this morning, creating a scene, with three characters and Stonemason's newest set. I was mostly in texture shaded and used the default camera. As I needed to adjust clothing, poses, hair, I found the lack of light deficult to work in. I did add an HDRI. Only one outfit was able to simulate so I had to close off two characters and the scene. There was a lag when closing the eye and I found that if I then clicked on the item the eye closed. I was able to close the scene file at the upper level, but not the two characters.
On the character with clothing and hair to simulate, I found it difficult to see where the layered fabric might mesh against each other. Trying to raise the shawl off of the pants or top was difficult, there seemed to be no reaction from the available parameters. I have used the outfit before and have not run into this.
I kept thinking that if the lighting issue continues we might need a way to easily do a temporarily color fabrics on an outfit so the contrast with one another so they can be seen in low light. And then select the desired materials. This set came with materials that were in a tonal range that was very close together. I did try looking at the scene in Filament but switching back and forth from it to Iray can stress my computers sometimes and it crashes. So, unless I totally work in Filament, but want to render in Iray, I am stuck. The render did finish on the MacMini M4 in 1 hr 36 min for 100%.
This is mostly about the light and eye closing lag. Sorry about the rambling.
Mary
Using Daz Studio 2025 ALPHA - version 6.25.2025.11417 with a Intel Arc A380 with drivers gfx_win_101.6737 and i also get the gray viewport.
Looks like Intel did a bad job implementing OpenGL in their drivers or in the hardware.
I was able to fix this bug using Mesa 3d ( a software OpenGl renderer )
Not the best way to test Alpha software but worth mentioning.
I took a short nap, and ran DIM again. There was a bunch of files to be downloaded. I don't think they were there before.
At any rate, DA Studio 2025 was installed, and resides in the Start menu with all the other fine DAZ products.
I still need to go into DAZ Studio and connect to the many Runtime collections I created.
It's easier for me when the content is broken down by categories (Genesis, etc) as their own Runtime folders.
From what I understand, "adaptive subdivision" is a game changer as it allows to greatly reduce the tesselation required for large scenes. On the contrary "pre-tessellation" seems a bogger if it replaces normals with real geometry, "vastly more memory usage" is not good as it means a scene that worked before may go out of vram. Also the "improved work scheduling" seems to improve rendering times at the cost of interactivity which may be what most people perceives as lag in the viewport.
If any DAZ expert can clarify those points it would be useful, thank you.
HOLY [COW]! Maybe I'm going insane, or it's just me—but I think I found a way to reduce viewport lag!
Basically, add both the Aux Viewport and Viewport panes to your workspace, close them, and then just open the main viewport.
Somehow, this actually reduced my viewport lag!
[My goodness], it worked for me, too. Why does this work? Still not as smooth as 4.23, but better than before.
A variant to the classic "Have you tried to turn it off and on again?"
TÉCHNÓLÓLÝ
I don't know what prompted you to try this but I'm sure glad you did. It made a large difference for me too and perhaps discovering this will help them fix the underlying issue. Thanks for sharing!
A few days ago I reported an issue with DAZ Studio 2025 alpha by submitting a 'Request' but the person who responded told me that all '2025' issues should be reported by posting here. I asked if they would send the information in my request where it needed to go but they didn't reply. This post may be redundant if they forwarded the information.
The problem involves a change in the way some objects are hidden (the 'eyeball' icon under 'V' in the 'Scene' tab) for a particular product. I have not encountered the problem with any other products during my time working in DAZ Studio 2025 alpha so I don't know if it's only this product or if other products have the problem too. I described the problem with screen shots in a powerpoint presentation and I'm attaching a PDF version of the presentation.
I have a quick question about scripting: The new code is still on development or we can already access the documentation and try to fix our non-working scripts?
Perhaps with some helpful guide to understand which code went deprecated and how to replace it with new code...
There are some info on scripting changes in this thread: https://www.daz3d.com/forums/discussion/727631/daz-studio-2025-6-25-2025-x-evergreen#latest
However since it's an alpha it's entirely possible there will be more changes coming.
I've been struggling with confusion about the eyeball icon. Like you said, the visibility of the item changes, but the eyeball icon doesn't immediately change to reflect that change. It has been very confusing. Thanks for the tip about making the viewport update to make the eyeball icon update.
Since I have a 5090 video card that's a paper weight in 4.23 I created a kluge workaround for the change in the way lighting works in Texture Shaded mode in DAZ Studio 2025 alpha. I don't always need it but when I want to place or pose objects in a shadowed area of a scene in Texture Shaded mode the image becomes so dark I can't see anything in it. My kluge is pretty silly but it's working for me and I thought I'd share it. It's intended to allow you to work on poses and placements with plenty of light but should always be hidden when rendering the scene.
I created a group of lights containing 4 distant lights in a square shape all pointing towards the center of the square. I can move the group of lights around in the scene in x, y, and z to place the center of the square on the part of the scene I'm working on. The square is large enough that anything in the vicinity will be well lit from all directions. My square is 400 x 400 and my lights are set at 2500 lumens but you can make the square any size and the lights any intensity that works for you. Using this tool an area in a scene that is too dark to work on can be made easily visible if you turn preview lights on. Moving the group of lights around in large scenes and remembering to hide them before rendering are extra steps in the workflow but for me it's worth it. I saved the group of lights as a scene subset so I can easily bring them into any scene I'm working on.
Of course I'd prefer not to use my kluge so if anyone has a better way to bring light into dark spaces when in Texture Shaded view mode I'd love to learn about it. I'm sort of hoping the final version of DAZ Studio 2025 has a button to toggle Texture Shaded mode between the way 4.23 works and the new way that 2025 works but that may be asking too much.