Thank you, My renders took 4-12 hours on a 3090. Slow means weeks. But I am still not clear on the what needs the alpha, so I want to get this into some yes / no questions, then I'll follow up with another.

• Do you need to enable CPU fallback to use iRay preview. I am not asking about the render, so I wasn't clear if that was included in the answer.
• Will the GPU do anything at all with "fallback" enabled? If not, then why not just disable it completely?

Those are my main questions WRT to the membership.

---

Based on current plans, when is there going to be a beta (i.e. feature complete), and when is there going to be finished software? And if there are no dates, are these times measured in months or years?

And I am grateful for any help here, even if it's a "we simply don't know". I'm sure you can appreciate that these are very serious questions for me. If there's no support planned in 2026, then I'll need to consider selling the hardware if I can't even use iRay Preview with GPU.

---

To satisfy my curiousity, because I'm sure there is a reason, why is it possoble to add completely new render engines like Filament without rewriting everything, but impossible to replace the iRay engine with one that implements the latest nVidia API and supports new hardware unless TK is upgraded (and whatever else)? And like I say, I'm sure there is a reason for this, because software that only runs on out of production GPUs is a more serious problem for Daz than for me.

Richard Haseltine said:

Old content with Poser materials will geenrally require work in any application, 3Delight materials will not work in Poser.

Yeah, but those were minor tweeks to material settings. Like maybe changing the specularity, or changing the diffuse color, etc.

As far as 3Delight not working with Qt6, that's fine. My problem is that Daz no longer offers ANY biased render engine at all. They didn't replace 3Delight with anything. They just said "well, we are IRay and Filament only now." And as I said, there are artistic lighting effects that you can achieve in a biased render engine that are difficult or impossible to achieve in a PBR engine. It's not that I'm in love with 3Delight. I just want a biased render engine because it is the only way I can achieve some effects.

If we're asking for wishes that are highly unlikely to be granted, I'd rather see DAZ first fix its wiki section and documentation pages, beginning with finally updating the now nearly 10 years' out of date User Manual, which ws written for DS 4.6, only addresses the no longer supported 3DL renderer, uses the 12 year old Genesis 2 as the most up to date base figure, and was written long before Iray, Filament, DForce and Volumetrics existed... not to mention failing to explain dozens of other "now critical for basic use" functions like geoshells.  I've lost track of how many people I've reccomended DS to who have subsequently dropped it like a hot potato when they discovered just how utterly useless the documentation now is, which is just DAZ walking a goodly percentage of new users straight out the door. 

interesting, slightly off topic

Toyota is releasing a new game engine and it will use Filament

I have to use both (because of Iray RTX 5000 issue), but on the 2026 6.25 in Filament mode, viewport is not updating unless clicking in it, moving the viewport to force a redraw.

Interestingly, sometimes it starts to work correctly, but couldn't figure out how to trigger it, and I think in the same session (without changing any settings) it starts happening again.

Any fix for this?

Richard Haseltine said:

Worse how? Is this just a complaint about no 3deliight (which was never an option with DS 2025/6, as there was no binary compatible version that woudl work in a Qt 6 application and use the RSL materials from store products) or are there other issues for you? If so you need to explain, a non-specific "worse" is useless as feedback.

The fact that DAZ Studio no longer includes a biased rendering engine is a show stopper for a lot of people, yes. But also, they appear to have broken Filament as well. Is Iray the only rendering engine that Daz intends to use moving forward? Cause if it is, Poser might make a strong comeback.

Edit: My bad on filament. It was user error on my part for why it wasn't working.

chriswongbiz said:

Another question，I'm used to the old version DS studio 4, which I render with 3Ddelight.  But now that I have moved to DS 4.23, when I render, there is no option for 3Ddelight?  Ony IRAY?  very slow. Is there anything I can do to make it show up for use?

I have just recently been getting back into poking at Daz for a variety of things, and was a bit surprised by the loss of 3Ddelight.  It does appear that the "real time" renderer provided by Filament can be enhanced a bit using various tricks and  might be suitable for your needs depending on where they fall.  While it won't give the same results as you get from an IRAY render, it is very fast to get the results.  The biggest learning curve seems to be dealing with shadows within Filament, though there are plenty of impressive examples once you get past that challenge.

I know its only in the Alpha stage , but are there any plans to make the filament draw options available in alpha? . the contrast ,exposure controls etc were really useful 

Hmmm.  Using a jog shuttle or such isn't likely to change things much as a lot of the lag you experience with DAZ Studio usually isn't so much of a result of the parameter dials themselves as it seems to be from your computer trying re-render the screen repeatedly as you keep updating the inputs, thereby slowing everything down the more you have loaded, how complex the lighting is, etc.  For any kind of major adjustment, I generally find that it's well worth switching to a faster renderer for a lot of the basic scene building and posing process, as the response time from moving a parameter dial is generally much faster with 3DL than it is Iray, with Filament being even faster, and plain old wireframe being better yet.  Now, all that said, have you tried using the puppeteer or powerpose panels?  They're both alternative means of manipulating objects and data within DS and many people find those options' manner of inputting data quicker and more intuitive once they get the hang of them.

Hi! I just setup DAZ on a fresh install of Nobara, on a 4070 gamer laptop. I think it might help a few people out there. The troubleshooting steps above need some adaptation to get the Nvidia to be seen by DAZ. It´s surprisingly straightforward:

- Nobara must be fully set up with the Nvidia proprietary drivers. You´ll get Wine 11 by default. You can double check in the terminal with "wine --version"
- Download the DAZ install Manager like you would on Windows and just run the .exe to let Wine take over.
- After a successful install of DAZ and a few assets, running it just worked. I set the default scene to iRay to avoid the Filament issues.

>> Only the CPU appeared in the rendering options, which is expected. 
- Download the last nvidia-libs from GitHub: https://github.com/SveSop/nvidia-libs/releases
- Extract the nvidia-libs folder somewhere easy to find. Open the terminal and cd into it (for the beginners: just type "cd Desktop" then "cd cd nvidia-libs-v1.0.0/" if the folder is on the Desktop)
- Run the command ./setup_nvlibs.sh install - you should get the message "WINEPREFIX is not set! This may create a wineprefix in the default distro folder) Continue? (Y/N)" - reply "y"
- If everything works as expected, you will get the message:
"Symlinks created in . Do NOT remove this source folder!
OBS! NVML is NOT enabled by default. See Readme_nvml.txt for info or run nvml_setup.sh
You can also use: WINEDLLPATH='/home/name/Desktop/nvidia-libs-v1.0.0/x64/wine' env variable to use NVML
You need to REMOVE old overrides if older version of nvml have been used in"
That´s it! After this operation, my Nvidia 4070 was there, and activated in the render settings by default :)
If you try to install the nvidia-libs through the Nobara package manager, it won´t work, you will get the usual error message telling you that the installation is conflicting with X11 or something alike. You need to download the folder manually.
On this system, I didn´t expect it would be that simple.
 

kyoto kid said:

...when working on scene I create a "Floor Camera" that is even with the floor plane (so you see just a line) and lock its (X, Z) rotation and (Y) transition sliders.  Sometimes applying a pose preset can put a character's feet or body slightly above or below the floor plane while still indicating "0.00" position in the Y transition slider.

I do a similar trick by creating a white plane primative and dropping it to the floor, then put the figures on it. That makes it easy to fairly see if the feet are solidly planted or hovering with Iray, 3DL or FIlament and gives you an easy horizontal refence to match things that aren't touching to.  Best part:  you can parent multiple figures to the same plane and then move them all at once just by moving the plane, then hide the plane once you have everything where you want it.  

korb said:

As described above, my experience with the latest WINE updates has been less than stellar, hence my menus bug filed with WineHQ.
However, I am also seeing another baffling new behaviour - significant lag in the UI while working on posing a scene.
For example, I have three characters in a scene and I have the viewport set to Filament mode. When I mouse over the characters, it can take anywhere from 1/4 of a second or longer - sometimes 3-4 seconds - for the node highlighting to be displayed. This is very annoying and really slows down my workflow, though it still works. I have the "__GL_MaxFramesAllowed=1" variable added to prod Daz/WINE to update the viewport more quickly, but with that unset, I still see that weird behaviour. If anyone else has seen that and has some idea as to what to try to get it resolved, I'm all ears.
Perhaps yet another WINE bug is in my future.
BTW, I am seeing this with 11.0 (stable), 11.1 (staging), and 11.1 (devel). Same with the menu issue.

FYI, I had been holding off on upgrading from Mint 21.3 to Mint 22 because Daz was working well and I did not want to risk project progress to upgrade.
With the problems I started seeing after my latest apt update/upgrade on 21.3, I decided it was time to take the plunge, so I spent Friday and part of yesterday getting to 22.3.
Unfortunately, that did not resolve the Daz/Qt menu issue, but it did help with the UI lag. It's still there, but much better than it was. The one other regression that I did see was that saving files and enumerating files in a file dialog seem to be taking longer than they used to, but that's not a big deal.
I am now at the latest Daz Studio, nvidia-libs, Linux Mint, NVidia drivers, etc. Even though it didn't fix all my issues, I'm certainly better off than I was. *shrug*

mateskulala said:

be careful ram cards are starting to get expensive. buy now while they are cheaper. do you happen to have a pc with Nvidia 5050 or newer that's why I'm asking if you also happen to have a problem with daz .. it says that people have a problem with some aplha version

its my old Win7, no graphics card, was using Filament on it

probably not worth buying new RAM and not the first set of sticks that failed on it either

more annoying it was my Poser7 machine with the physics plugin

I used it a lot for creating animated ragdoll animations  

and also only machine that ran Virtual World Dynamics 

I am fully aware of the RAM crisis so likely going to mothball it for now

are a lot of music programs on it I use too, so disappointing 

As described above, my experience with the latest WINE updates has been less than stellar, hence my menus bug filed with WineHQ.
However, I am also seeing another baffling new behaviour - significant lag in the UI while working on posing a scene.
For example, I have three characters in a scene and I have the viewport set to Filament mode. When I mouse over the characters, it can take anywhere from 1/4 of a second or longer - sometimes 3-4 seconds - for the node highlighting to be displayed. This is very annoying and really slows down my workflow, though it still works. I have the "__GL_MaxFramesAllowed=1" variable added to prod Daz/WINE to update the viewport more quickly, but with that unset, I still see that weird behaviour. If anyone else has seen that and has some idea as to what to try to get it resolved, I'm all ears.
Perhaps yet another WINE bug is in my future.
BTW, I am seeing this with 11.0 (stable), 11.1 (staging), and 11.1 (devel). Same with the menu issue.

Richard Haseltine said:

You could try Filament, or sending it to Blender and using one of its render engines (Cycles is quick). The other option would be to hire a hardware upgrade by using a render farm with more/faster GPUs (though you'd want to test the scene thoroughly first to reduce the chnace of nasty surprises)

Thanks so much!

You could try Filament, or sending it to Blender and using one of its render engines (Cycles is quick). The other option would be to hire a hardware upgrade by using a render farm with more/faster GPUs (though you'd want to test the scene thoroughly first to reduce the chnace of nasty surprises)

inquire said:

Another update to DAZ Studio 4 Has been released. Does it run any better than the previous version? I haven't updated, but the version I'm using, the previous version, crashes all the time in emulation mode on my Mac studio, with Tahoe as the OS. If I update, will there be an improvement? Does anyone know?
The updates, I Have found, sometimes make things worse.

My experience with it is somewhat negative. Since I upgraded, I've had a lot of weird little things happen with the system suddenly highlighting everything anywhere near my cursor as if I was clicking on things (which I wasn't), and I've had a higher number of freezes and crashes. In fact, I had bought the RSSY 3DL to Iray converter, and any time I try to run it, Daz just closes immediately. Still no ability to use filament/filatoon tools, and an uptick in dForce explosions and simulation freezes. I'm kinda wishing I'd held off on upgrading. 

Hello!

I'm looking for a little help wih my Daz. I recently upgraded my PC and immediately noticed that something is off and I honestly don't know what's causing this or how to resolve it. 

In the first attachement, as you can see, CPU usage is turned off. Even so, the GPU doesn't move an inch. Viewport is empty and set to Iray but at the bottom there's the message "Preparing Scene..." and the progress bar on the right, loading, but there's literally nothing to prepare. It just loads continuously until I change the view to something other than Iray.

Second screen shows the character in Filament view, that works ok - but the third sreen is showing the same character in Iray and that's not what it should look like. I know there are no lights set up etc...but still. And of course, "Preparing Scene..." is doing its own thing without progress.

Last picture is a render preview and as it shows, it's a big nothing.

I just can't figure out what's happening and Youtube did not help at all this time.

Maybe there's someone on this forum who could enlighten me?

Many thanks in advance!

I've started Daz with Iray mode by default, loaded Gen 8, and get white figure. I've also switched in and out of iray mode to filament, texture shaded, etc. When I go back to Iray, its white. Daz Studio 2025 (6.25) Public Build loaded about 12/23/25. NVIDIA Studio Driver 591.74 which I installed recently to try and fix, but issue spans this and the previous driver, but was working fine maybe before 6.25 install. Ryzen 7, 32GB, NVIDIA 5070 TI 16 GB, Windows 11 Home, 24H2 26100.7623.

Has anyone [ported Wendy 9 to Blender] done this successfully? I'm using Diffeomorphic, which does work except on the eyebrows... The eyebrows seems to be strand based, however, and there are no Preview PR or Line Tessellation parameters availabe... Is there a way to add those while in DS? Or is there a workaround for this in Blender? (I have very basic Blender skills.) Oh, just an FYI, the eyebrows also don't show up when using Filament in DS either (for the same reason).