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
Any clue about why I get the OpenGL message when rendering Filament? Do you see the same?
https://github.com/google/filament , among other things, describes the features of Filament and so what properties it needs.
Yes, I do - you can of course disable the message.
https://github.com/google/filament page is beyond my comprehension. I'll have to wait for the TLDR version.
Is DS working as intended with all those properties and an OpenGL message or not, is what I am trying to find out. If nobody can answer, well, I have reported what I see. Developers can decide whether it needs attention or not.
Thank you. At least I am not alone in seeing this. Yes, I can disable it. It seems "wrong", so I wanted to provide that feedback as part of Alpha testing.
I get that same popup message in the 4.23 beta. IDK if I get it in anything else. That's the only place I've tried Filatoon.
This may be a little off topic but this is my first experience using Public Builds and I understand what most of the available items are but one of them is a mystery to me. Can anyone tell me what "Public Build Install Modules" is? Thanks!
Yes, you are a little off topic. This is explained in the Install Manager thread. https://www.daz3d.com/forums/discussion/comment/9149831/#Comment_9149831
Why viewport fps is very low for me? Feels like 10-20fps in 2025, but 4.23 runs with rock solid 100fps. No matter filament or texture shaded. Low fps even in empty scene.
Win 11 24H2, RTX [email protected]
I have a G9 character in my scene. The viewport is in Iray Preview. When I save the scene, the Iray preview stops showing the Iray version. The character is white. I wait and wait, but the Iray preview is never refreshed.
Yes, it sometimes feels uncomfortably jerky.
Windows 10, RTX 3080 driving the display and render.
Hmm, it is working for me. Does the log indicate anything?
So guys, a suggestion: having the progress bar in a different color, like the old yellow, made it easier to understand the render progression at a glance. Right now, it's much harder to see in both themes.
The interface is still a W.I.P
which makes this the perfect moment for suggestions ;-)
I was finally able to download DS 2025 on my Win11. I had to open DIM, untick the items necessary items needed for download and then tick them again and refresh DIM. The downloads then appeared. I did have to search for the sku 109051, but it was there also now.
I have been working back on 4.23 on my MacMini and I have noticed its performance has degraded. Is there an expected impact of the DS 6 on DS 4? I have started working on updating my Poser/3DL products to .duf/Iray so I won't lose some of my favorite older products when DS 6 goes fully live. Thank you to Code66, RiversoftArt and SickleYield for their work over the past few years.
What exactly is slower in DS 6? I see uo to a three times speed boost with some of my scripts on DS vs. DS4 when it comes to loading stuff (but that did require updating them for DS 6)
For me, the biggest issue remains lag. It's GREAT otherwise, but I can't fully commit to it until the laggy movement in Iray Preview is ironed out.
There are also smal delays between moving between Viewport and Aux Viewport. Once that's sorted, I'll be fully in on 2025, only returning to previous versions for plugin work.
I've just tried rendering a scene in Studio 2025 and Iray does not appear to be recognising my RTX 3070.
Pictures are of viewport. When cpu is ticked the iray preview works, when gpu only is ticked it remains greyscale.
Also if I click render it will start then finish straight away with just a blank chequerboard.
Problem solved - needed an latest NVidia driver update.
It wasn't scripts but when I was adding additional categories for Smart Content to products I had installed from my existing library of products. I have categories that help me find items more easily and that seemed to lag when I was adding them. Or just looking at the product to ensure it had the correct category or where it was located. Sometimes I am able to recall the image better than a name, and having an idea where an obscure item is located helps me save time. And sometimes a character is not assigned the correct category in Smart Content. They may only have 'Figures' but nothing after, or be Male, when they are Female, or a Creatures when they are a Dog and should be an Animal. And as I pause between work, I find the swirly gets longer. I also found with the scripts I did have to reboot my MacMini M4, DS 4.23.1.47 locked up. I had just used it too long. Need to add in a reboot in long sessions of work.
The CMSDB (Postgres databse) sometimes gets really screwed up if it has crashed too many times ( A database is a system that sooner or later will corrupt the data you store there / old djungle maxim )
I sometimes reset the cms 8 by exporting user data then reminit it and reimport metadata), then it usually gets fast and snippy again.
For me Viewport performance in iray is noticable weaker, less responsive, lower FPS.
I applied the same settings and have latest drivers. (RTX 4080, AMD 5950x, 32gb ram)
I tested a product called 'Autumn Cottage'. Quite intense scene and the alpha 2025 just simply unable to handle it, struggles even to load it and upon load everythnig freezes.
Other complex, high poly scenes are also problematic, regardless of view type, it makes DAZ unusable.
Not an option, however, if one installs with Connect.
After restarting the computer today and reloading the scene, it is updating the Iray preview after saving the file, but there is a longer than expected hesitation in doing so. In contrast, DS 4.23.1.47 Beta doesn't lose the Iray preview and go all white when saving a scene. The log file shows that after saving the file, it reports a warning. I don't know what that warning means. What is an Invalid ICC Illuminant??? I am using the default render settings loaded when the DS Alpha loaded. The Engine is shown as NVIDIA Iray (MDL) and the Environment mode is Dome and Scene. Draw Dome is on and the DTHDR-RuinsB-500 HDR file is in the Environment Map. I have no other lights in the scene and no emissives.
2025-04-28 10:14:18.516 [INFO] :: Saved image: N:\DAZ 3D\Scenes\Testing Alpha.duf.png
2025-04-28 10:14:18.968 [WARNING] :: Invalid ICC illuminant
2025-04-28 10:14:53.524 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 01729.86 iterations after 03:48.065.
The whole log is attached.
Are these options not available when installing through connect, or is the metadata not available for reimport when installed through connect?
Have you tried playing around with the draw settings for Iray?
In particular ensure the Interactive Viewport Delay is Off, and the Response Threadhold(msec) is high, I have mine set to 5000.
For me having aux viewport also slows things down, especially if it's in iray mode.
If i close the aux viewport everything is snappy; aux viewport open, main viewport gets relatively sluggish.
The "interactive delay" setting etc do not really fix it, compared to earlier daz it is notably slower.
I dont think its unusable and old Daz also could get very sluggish in complex scenes but this version is slower in simple scenes as well.
@Masterstroke, Richard explaned to me (or, rather, unintentionally reminded me) that lighting in non-render modes are limited by the hardware to 8 lights, and from what I have seen, those emissives do not stretch to all corners of a scene, unfortunately. I've also had this problem where I want to look in Cartoon Shaded or other shaded fast-render/quick-motion depictions, and even with a headlamp on the camera, the entire scene is dark or near dark. I then rely on Filament, but then I have to tone-map and increase the exposure value so that I can see what I am doing, and then remember to reset it so that it doesn't render darker than intended.
[Feature request would be something like please keep the tonemappings for different render engines separate, or at least remember them separately, so the back and forth isn't necessary....but that's for another day .]
Weirdly, after playing around the Alpha (both versions,so far) for a couple of days. Everything was (within the parameters of it being an Alpha release) working fine.
Launched the app this morning and Iray won't work in the viewport anymore. It just shows OGL.
Filament works.
Textured works.
But Iray will not appear in the viewport.
Works fine as a full render though.
I've reinstaleld the newest Nvidia drivers, reinstalled the alpha, rebooted, launched the Beta version (which works fine).
No Iray in the viewport for the Alpha, after it worked fine for days.
No clues in the render log either.
-edit-
Okaaay then. It just started working again.
The products certainly aren't available for reimport, they have to be reinstalled (though the system should spot that the ones on disc match the ones on the servers and so not actaully download them, assumning the destination directory is unchanged).