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).

Link 

In which version? DS 4 isn't getting updates, other than removing 3Delight, but I would expect Filament will get updated in DS 2025/6/etc. as the base code does, offset for development resources and testing of course.

[Will Filament receive any updates?] Title

vrba79 said:

Imagine a filatoon version of this, where you could apply Borderlands or Telltale game style hash-marks and detailing, or baked on ambient occlusion.

Therea re limits to what Filatoon, or Filament in general, can do - I have no idea whether this would be possible in principle.

is dHair fur something new? I see if mentioned twice in the description and you mention it above as well. Is this a new type of dForce hair? I love all your other furry creatures, of which I have many, and they all render great even in Filament. So I am hoping this is the same dForce hair/fur that you always use, with just a new name. But I would like to know one way or the other. I've lost track of how many different types of dForce hair and fur there are now. Some work great with Filament, others not so much. Yours have always worked for me though.

Richard Haseltine said:

FrankTheTank said:

There's just no reason to install the new version. It adds nothing, it doesn't fix any bugs, it just removes a feature, 3DL, so why would you even want to install it? At least wait for an update that adds something new or fixes some bugs. 

It does in fact have bugfixes http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log

Richard, what are these bug fixes you speak of? Below are the only "bug fixes" I found and they aren't even listed for the release channel, they are just listed for the beta. Assuming these are the same bug fixes you are speaking of these aren't really bug fixes. They don't affect Windows users of Daz Studio at all.

Fixed a regression in the script that backs the “Create Poser Companion Files…” action

This restores the correct functionality of the script, ensuring that users can generate Poser Companion Files (PCFs) — which enable Daz Studio content to be used in Poser — without errors. This update ensures compatibility and smooth interoperability between Daz Studio and Poser despite internal UI text changes

Extended DzApp public API; added Mac_26_0 enumerated value

indicates an update to support macOS version 26.0, which likely corresponds to a future version of the macOS operating system. This addition allows developers using the Daz Studio SDK to programmatically identify and handle this specific macOS version within their scripts or plugins, ensuring compatibility and proper functionality on newer macOS releases. The change is part of ongoing updates to the public API to keep pace with evolving operating system versions and maintain robustness across platforms

Updated public API documentation; DzApp

this means that the official documentation for the DzApp class in Daz Studio's software development kit (SDK) has been revised and improved. This includes clarifying existing functions, adding descriptions for new features (such as the Mac_26_0 enum or displayName property), and ensuring developers have accurate information when creating scripts or plugins. It helps ensure compatibility, especially after changes like the title case display update, by documenting how the application interface and scripting system now behave.

So, there are no bug fixes for Windows Daz users, Just removal of 3Delight. Updating does nothing for Windows users but remove functionality.

I would love to see some FIlament bug fixes before DS 4.24.x.x is retired. Not holding my breath on that though.

Crios said:

Anno nuovo, DAZ nuovo. Dopo diversi tentennamenti, ho deciso di installare il 4.24, e devo dire che funziona. Una cosa che mi ha indisposto però. è che non riesco a usare lo Spot Render, strumento di cui faccio abuso. Come contropartita posso però usare finalente il Filatoon, e devo dire che ci sono diverse cose da imparare su questo motore di rendering.

Qualcuno sa come posso fare per usare lo spot render con il 3Delight?

E un altra cosa, dove li trovo degli shader free per Filatoon?

A me  lo Spot Render funziona correttamente. Sei sicuro di aver selezionato lo strumento giusto per usarlo?

Filament non è un mototre di render ma solo un DrawStyle. Alla DAZ3D si rifiutano in modo categorico di svilupparlo oltre purtroppo... Di shader ne trovi tanti dappertutto, ma FilaToon vero e proprio lo trovi solo sullo store DAZ.