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
I don't understand if this is a glitch or if it's meant to be this way.
https://postimg.cc/8FsXpfq0
Previously, I used orbit and held down the right mouse button to get precise camera control, but now it suddenly jumps if I move the mouse even a little faster.
The gif shows how camera movement using the square button is choppy and unstable.
This is causing significant discomfort. Is there a fix for this?
This is a known issue - it happens when the camera is away from the world centre - I find that using the mouse weheel to zoom in/out restores the camera's angle, but it is a matter of luck whether that is the orientation you want.
I'm not using 2025, but just out of interest does it do it when you are viewing through a camera or just when you are in perspective view, as shown in the attachment?
(Edited by mod to fix quote)
Richard, I resolved my problem by changing my primary monitor on the MacMini to my HP monitor which has a lower resolution and D|S (both versions) opens just fine there. I have had to adjust my personal habits but that is on me. So the folks working on D|S don't feel bad, my Apple Studio Display shrinks down every window I pull over to it and I often have to squint to see them. Just depends on what I am working on what is useful for me.
On my Windows 11 computer I am not having any issues. And regarding the metadata, that was on me. I was trying to work on both computers the previous day and started to miss products. So no issues with that.
Mary
If you start 4.24 first, then start the 2025(alpha).
2025 will disable all of your plugins, including autofit.
You need to start 2025 first , then 4.24 second if you plan to run both at the same time.
I have a script error. Not sure which version of Alpha broke scripts like this. I have a specific example trying to load Tara 9 Succubus Makeup. I believe using Mike D sweat tool also crashes with similar errors, but I don't have the log for that. Here's the log for the Tara 9 script error.
The result is that the metallicity image is applied as the makeup layer, and then an error box pops with the script error. The only fix is to reload the scene.
Those errors are due to changes in the JS engine in DS 6 (which is more strict and also have some important changes ). Most scripts from DS 4 fails in DS 6, some are easy to fix, some are beasts to fix.
I downloaded and installed this December update and its working fine except the type in the panels now is so small its almost impossible to to read even with reader glasses. Also making changes to poses seems to take forever. No sure how to correct either of those.
How do i keep 2025 Alpha up to date? cant find any updates via install manager? when opening 2025 i have it set to once a day but not sure thats doing anything....
Which version do you currently have?
Mac? On the font size, it is a temporary workaround - see 6.25.2025.34208 in the change log http://docs.daz3d.com/doku.php/public/software/dazstudio/6/change_log
My pc guy who just built my computer put in a 5060 card despite my instructions to use a 4000 series card. I've decided to deal with it because this will probably be the last time I update my pc for many years. However, I can't find it in DIM to install it. Do I need to manually download it?
I believe you need to enable 'Public Builds' in DIM. If I'm right here's how you do that:
Thank you that did it
Glad it helped. You may already know what I'm about to say but just in case you haven't seen it. I build scenes in 4.24 and render them in 2025 alpha for 3 reasons: 1) script based products may or may not work in 2025 alpha and I've come to depend upon the ones I own, 2) plug-in products do not work at all in 2025 alpha and I depend upon the ones I own, and 3) the viewport lag in 2025 alpha makes it difficult and frustrating to work with. Things should get better when 2025 becomes beta software and even better when it's released but for now I believe you need both versions. My computer is pretty good so I can open both programs at once but I'm careful to make sure the same scene is not open in both programs. I suspect that would create quite a mess!
Your PC guy probably couldn't find a 4000 series card that was 1) new, and 2) less expensive than a 5000 series card.
Small issue but I noticed the "Visible in Viewport" flag on objects doesn't seem to work in 2025. As an example on my clothing objects I've set all the rigid follow nodes to not be visible in the viewport, but they all show up again in 2025.
I'm on a fresh install, and I'm still having the keyboard navigation issue. When using the keyboard, the movement is slightly stuttery (step by step, not smooth), but not when using controls in Scene Navigator. There's a delay after pressing any move keys, and pressing two keys at once (w+a, for example) does not work at all.
Resetting the workspace makes it work until the first mouse click (any mouse click).
Is there a fix for this, or is this still buggy?
This is still being worked on - so no fix yet, but it hasn't been forgotten.
Thank you for the information, Richard. I'm glad to see it's being worked on! Is there any estimate when the fix could be coming? After all, navigation is the most elementary aspect of using the software. Especially since Daz 2025 is the only choice for people with the 5xxx GPUs.
No ETA, but I have to point out that keyboard navigation was added only part way through the DS 4 cycle.
The default type size on a UHD (4K, 3840x2140) monitor is way too small on both Windows and Linux (KDE at least) if the "screen zoom" is set to 100%. This applies to everything. On both operating systems go into Settings/Display and try different values of the "Scale" parameter. I run at 200% and the result is workable.
Reading glasses do not help; they just allow you to get _closer_ to the screen, in the manner of a magnifying glass. This is counterproductive.
There are bugs in Daz; the consistent use of white on white, grey on grey and even black on dark gray text in the various colour schemes obviously does not work. E.g., bad:
[Image of Light "Metallicity" Intensity parameter showing almost completely unreadable black text on grey background deleted because it makes the post too long]
Unacceptable:
The latter was obtained by tracking the cursor over the setting (from the Surfaces pane in this case) and screen shotting that to show the highlight; white text on a white background!
I trust these will be fixed before the Alpha is released; they are trivial to find, it just takes a few seconds.
That's a different kettle of fish. There are reports of delays in the UI dialogs. The easiest way to slow the UI to a crawl is Hair. If one or more of the "PS" hair properties (in Surfaces) are set much above the default the viewport will pretty much stop. If you have strand-based Hair check the surfaces for that hair. This is from the Gaelle Candy product; it doesn't have the problem out-of-box but the curls in the hair require more points, a lot more, than the default not to dForce intersect the character:
[image of PS Points (Per Hair) set to 20 deleted because it makes the post too long.]
"20" is a compromise, it's enough so that the curls appear but not enough to totally clobber the viewport. The defaul tis 8, 1 is pretty damn quick ;-) and I discovered the problem with 50! I render that hair with 320, this removes all the sharp angles.
There are other issues. I routinely run with SubD level 4 in the viewport because that controls the "smoothing" in the render (not the render SubD) and that does slow viewport update quite a lot. Something was also seriously wrong with the ActivePose Tool at the start of the alpha (it lost mouse clicks somehow) but that seems to be fixed. It's still pretty slow.
Is anyone else experiencing broken preview lights?
I wish I could search just this forum thread to see if it's been talked about before, but I can't seem to find it being talked about yet... apologies if it has and I missed it!
When viewing "through" my spotlights the scene is completely black, usually I fix that by hitting "CTRL + L" to enable/disable preview lights, but that's just doing nothing now?
It's very frustrating seeing as that means I can't adjust any spotlights using fly controls and have to do it manually from the 'third person' which makes them incredibly annoying to aim!
I've done it manually too through the menus and that doesn't change the result.
It does toggle properly when looking through a camera instead, except that it doesn't show the preview lights functioning. It just goes from full scene view to completely black when I activate preview lights.
Any help would be appreciated!
Okay, I found out it was because there's a cap on how many spot lights are in the scene?
I had 29 spotlights going on (using them as street lights as well as character lighting) and apparently that's one too many!
I deleted one and suddenly a few could then be seen in the preview (but not all), deleted another and some more could be seen, etc...
I don't know what the threshold is to have all preview lights showing or if that's something that can be changed in settings, but at least the scene is now partially visable in preview!
There is a limit on the number of lights that can be previewed, it used to be seven (eight minus the headlamp). However, there is also an issue with loking through a camera that is suficiently far from the centre darkening or kiling the light (and also messing up the view manipulation controls) and I would suspect the Spotlights often are sufficiently far to trigger that.
Work in DS 4.xx and Render in 2025 (for Nvidia 50xx Card speed)
Has anyone experimented using the Iray Server installed on a local workstation ?
I don't have a Nvidia 50xx Card to test with. But I think this might be a nice interim solution for those who do.
I currently use the Iray Server installed so I can better manage the GPU Vram usage. It works pretty good (with some hacks).
I only have a Nvidia 2080 Super with 8GB of Vram. But so far the Iray Server installed on the same machine has helped me render stuff without restarts of DS to clear the Vram memory.
It's also nice to setup a bunch of renders to Iray Server, then start the queue to have them all run overnight.
Apparently the Iray server version has to match the Iray version in DS, so this isn't a way to render directly to a 50x0 card from DS 4. I had hoped it might be myself.
That was the case.
The latest version of Iray Server (2025.0.3) supports all the DS Bridge version protocols. I can connect to it and render from DS 4.22, 4.24, and 2025 Alpha.
It will also support other versions that I haven't tested. I tell Iray Server to only load the three that I need with the following option on the command line.
"C:\Program Files\NVIDIA Corporation\Iray Server\server\iray_server.exe" --install-path "C:\Program Files\NVIDIA Corporation\Iray Server" --cm-path "E:\irayServer\cacheManager" --disable-cpu-fallback --workers 363600.9587 373000.3036 387700.2665
If you specify
--workers ALL
It will startup workers for all 9 protocols that the latest version supports.
I think that goes back to: Iray RTX 2021.0.4 , build 344800.12856 , 16 Mar 2022, nt-x86-64