Firstly, not all figures, clothes and especially environments are equal - some will be MUCH more taxing on the GPU than others. Not to mention when you throw lighting into the mix. Generally you should probably use Textured or Filament modes when building / modifying a scene and just switch to iray to check things out a bit before switching back to make adjustments.

jparks123 said:

paradisepd said:

i wanted to ask you, hows the viewport speed like on the 4060ti 16gb? i saw that you said its OK. but what kind of ok is it? 
does it move fast enough where it doesn't feel slow? and you won't get bugged by it.
or does it feel slow but its acceptable. hows the experience in iray and moving things, and just working on daz?
just dying to hear it. i just don't want to end up buying something i'll regret, when its slow af.
i come from an acer nitro laptop with a cut down 3060 with 6gb ram cos its a laptop gpu version.
and my viewport is slow like 25 sec-30sec stalls and i can't even load 2 chars most of the time!
thats why i am thinking i want the 4060ti 16gb over the 4070 even though by all accounts ppl say its a huge leap in speed, but i don't want no 12gb anymore after what i experienced with 6gb vram.

I am not really sure what you consider an acceptable speed for the viewport.

30 second viewport update is slow but not unheard of; I turn off things like hair or clothing when I get that, and it speeds up again.

For any non-trivial scene, Daz iRay preview is never going to let you spin the camera around like a video game or pose characters in real time like they were dancing. Daz has the Filament renderer for that.

The 4060 TI passed through my hands on its way to someone else so I'm not used to it; I did the benchmark while I had it (7.23 iterations/sec). As I said in the other thread, I normally use a 4080. (This reminds me, that I run the Daz benchmark for the 4080 sometime).

ah i see, thank you. yeah thanks so much for the benchmark, for my first build i don't mind slower render times, as long as the viewport speed is ok. haha yeah i guess i have to start moderating my expectations for render speed. hey if ppl got by 3060, i am sure i will be ok with 4060. 
thanks so much J.

paradisepd said:

i wanted to ask you, hows the viewport speed like on the 4060ti 16gb? i saw that you said its OK. but what kind of ok is it? 
does it move fast enough where it doesn't feel slow? and you won't get bugged by it.
or does it feel slow but its acceptable. hows the experience in iray and moving things, and just working on daz?
just dying to hear it. i just don't want to end up buying something i'll regret, when its slow af.
i come from an acer nitro laptop with a cut down 3060 with 6gb ram cos its a laptop gpu version.
and my viewport is slow like 25 sec-30sec stalls and i can't even load 2 chars most of the time!
thats why i am thinking i want the 4060ti 16gb over the 4070 even though by all accounts ppl say its a huge leap in speed, but i don't want no 12gb anymore after what i experienced with 6gb vram.

I am not really sure what you consider an acceptable speed for the viewport.

30 second viewport update is slow but not unheard of; I turn off things like hair or clothing when I get that, and it speeds up again.

For any non-trivial scene, Daz iRay preview is never going to let you spin the camera around like a video game or pose characters in real time like they were dancing. Daz has the Filament renderer for that.

The 4060 TI passed through my hands on its way to someone else so I'm not used to it; I did the benchmark while I had it (7.23 iterations/sec). As I said in the other thread, I normally use a 4080. (This reminds me, that I run the Daz benchmark for the 4080 sometime).

Crios said:

Sono anni che uso Google per fare ricerche nel forum, ormai la ricerca era inutile.

A proposito di Filament:

RSSY 3Delight And Iray To Filament | Daz 3D

Quel pacchetto è poco utile se non rendono FIlament un motore serio. Al momento le trasparenze sono rotte, le luci sono sfasciate, le ombre sono sfondate e l'area di render è devastata.

Sono anni che uso Google per fare ricerche nel forum, ormai la ricerca era inutile.

A proposito di Filament:

RSSY 3Delight And Iray To Filament | Daz 3D

I may have missed any other announcements but as far as new "features" I think Omnivese is the first big thing officially announced. We've been told (first page in the thread) that Filiment will finally be available for Mac users (after almost three years), the Qt update should improve the user interface (and possibly make it a little more customizabale), they were trying to make it Apple Silicon Native but weren't sure if they could do it for the DAZ Studio 5 release, and it will make some use of Apple Metal for Mac users (but outside of preview rendering, no idea what, it may just be regarding getting Filament to work).

If anyone else has more info on what we should be excited for, please share. I'm afraid my excitement fizzled out a while back and at this point I'm afraid it's going to take a bit more than Filament to get me jazzed up and buying again.

-- Walt Sterdan

My example didn't have anything unusual or special about it except the figures using subdivision, so there's probably not a lot I can do. I'll try a test with no textures and one with Filament and see if the delays are still there.

edit: Filament renders instantly, amazing...too bad it's...awful. Having no textures does speed things up, but of course that isn't practical.

barbult said:

There are many plugins that are part of the Daz Studio installation itself. Filament is one of those. If you look through the list, you will see many plugins that you didn't install with DIM.

I can't brag agout the amount of time it has taken me to learn what little I know.

There are many plugins that are part of the Daz Studio installation itself. Filament is one of those. If you look through the list, you will see many plugins that you didn't install with DIM.

brainmuffin said:

lostindebian said:

lostindebian said:

After spending days with bottles and wine-staging I got it working with Lutris. This is how I think I did it.

My system.

• DAZ Studio 4.21.0.5
• Debian 11.
• ASUS GeForce RTX 3060 12GB DUAL OC V2.
• NVIDIA-SMI 470.161.03
• Driver Version: 470.161.03
• CUDA Version: 11.4

My steps.

1. Install NVIDIA drivers for Debian. Not sure which, but the recommended that you use for everything.
2. Install "Lutris".
3. Install "DAZ Studio".
4. Start "DAZ Studio" and set the viewport to NOT use "filament". Else it will crash later!
5. Download and extract "nvidia-libs-0.7.7.tar.xz" and enter folder in terminal.
6. Run the script "WINEPREFIX=/home/user/Games/daz ./setup_nvlibs.sh install".
7. Start "DAZ Studio" and the GPU rendering WORKS!. At least I think it works.

Big thanks to this thread. Could not have done it without you!
   

My method no longer works.

I recently upgraded to Debian 12 and Daz GPU is no longer visible or working. I tried re-installing most of *nvidia* "470.199.02-1~deb12u1" and/or *nvidia* "525.125.06-1~deb12u1". Tried them with nvidia-libs-0.7.7 and 0.7.11. Rebooted between tries.

Thought I had solved it, but with Debian 12 it won't work.

 

Not tried reinstalling daz studio yet.

The last time I updated Mint, I had to wait for the NVidia drivers to be corrected for GPU support. Once it was, download, and install, GPU was back in Studio.

I had the same problems with Debian 11 and Lutris but the problem was always fixed when Lutris upgraded. Good to hear I'm not alone. :D

lostindebian said:

lostindebian said:

After spending days with bottles and wine-staging I got it working with Lutris. This is how I think I did it.

My system.

• DAZ Studio 4.21.0.5
• Debian 11.
• ASUS GeForce RTX 3060 12GB DUAL OC V2.
• NVIDIA-SMI 470.161.03
• Driver Version: 470.161.03
• CUDA Version: 11.4

My steps.

1. Install NVIDIA drivers for Debian. Not sure which, but the recommended that you use for everything.
2. Install "Lutris".
3. Install "DAZ Studio".
4. Start "DAZ Studio" and set the viewport to NOT use "filament". Else it will crash later!
5. Download and extract "nvidia-libs-0.7.7.tar.xz" and enter folder in terminal.
6. Run the script "WINEPREFIX=/home/user/Games/daz ./setup_nvlibs.sh install".
7. Start "DAZ Studio" and the GPU rendering WORKS!. At least I think it works.

Big thanks to this thread. Could not have done it without you!
   

My method no longer works.

I recently upgraded to Debian 12 and Daz GPU is no longer visible or working. I tried re-installing most of *nvidia* "470.199.02-1~deb12u1" and/or *nvidia* "525.125.06-1~deb12u1". Tried them with nvidia-libs-0.7.7 and 0.7.11. Rebooted between tries.

Thought I had solved it, but with Debian 12 it won't work.

 

Not tried reinstalling daz studio yet.

barbult said:

Filament IS a plugin! You can see it in the plugin list (Help>About Installed Plugins).

I never looked for it there. It's not on the DIM list.

I'm glad you got it working. I hope it keeps working!
Filament is a draw style for the viewport, not a render engine. But you can render the viewport to a file while the viewport is in Filament draw style. In Render Settings, set Viewport as your render engine (instead of Iray or 3Delight, etc.) And Filament Viewport render is very very fast. I tried to attach such a render, but the uploads are not working now.

I'm glad I asked about these things. Thank you for your help. I say, I only know what I read. I'll try rendering with Filament now.

lostindebian said:

After spending days with bottles and wine-staging I got it working with Lutris. This is how I think I did it.

My system.

• DAZ Studio 4.21.0.5
• Debian 11.
• ASUS GeForce RTX 3060 12GB DUAL OC V2.
• NVIDIA-SMI 470.161.03
• Driver Version: 470.161.03
• CUDA Version: 11.4

My steps.

1. Install NVIDIA drivers for Debian. Not sure which, but the recommended that you use for everything.
2. Install "Lutris".
3. Install "DAZ Studio".
4. Start "DAZ Studio" and set the viewport to NOT use "filament". Else it will crash later!
5. Download and extract "nvidia-libs-0.7.7.tar.xz" and enter folder in terminal.
6. Run the script "WINEPREFIX=/home/user/Games/daz ./setup_nvlibs.sh install".
7. Start "DAZ Studio" and the GPU rendering WORKS!. At least I think it works.

Big thanks to this thread. Could not have done it without you!
   

My method no longer works.

I recently upgraded to Debian 12 and Daz GPU is no longer visible or working. I tried re-installing most of *nvidia* "470.199.02-1~deb12u1" and/or *nvidia* "525.125.06-1~deb12u1". Tried them with nvidia-libs-0.7.7 and 0.7.11. Rebooted between tries.

Thought I had solved it, but with Debian 12 it won't work.

Not tried reinstalling daz studio yet.

Filament IS a plugin! You can see it in the plugin list (Help>About Installed Plugins). I'm glad you got it working. I hope it keeps working!
Filament is a draw style for the viewport, not a render engine. But you can render the viewport to a file while the viewport is in Filament draw style. In Render Settings, set Viewport as your render engine (instead of Iray or 3Delight, etc.) And Filament Viewport render is very very fast. I tried to attach such a render, but the uploads are not working now.

barbult said:

I think I don't have KeyMate and GraphMate tabs in my menu anymore because I probably disabled the plugins some time ago. After installing a plugin with Daz Studio running, you have to close Daz Studio and reopen it to get the plugin to work. Try that if you haven't already.

Ha! I tried closing Daz while your test file was displaying (all white) in Filament. Then I reopened Daz, reopened the test file in Fllament, and Filament displayed just fine. Filament behaves like a plugin. I'm going to Restart the OS a time or two to see if it holds.

Who in the entire world would have ever thought to do this. Unbelievable.

Thanks...

This is a scene with a blue sphere (duf file attached). See if you can view it in Filament draw style.

It should look like this:

barbult said:

Well, at least we made some progress on one of your problems.
I'll see if I can think of anything else that might cause that Filament problem. Maybe Richard will pop in with an idea. Are there any error messages or warnings in your log file related to Filament (In Daz Studio, Help>Troubleshooting>View Log File... )

I've looked in the log a lot. The results have been inconsistent and inconclusive. There was even ONCE in my series of uninstall/reinstall/reboots where Filament actually worked correctly. I thought, oh good, it's fixed. Then it disappeared.

Are you running the same version of Daz Studio that you ran Filament in successfully before? What version is that?

Not likely. I don't know what I was running before, but it wasn't this version. I do know that my W10 install now is far beyond (or behind?) what I was running before.

There's something flakey about this install. For example, at the moment, Keymate won't show up on the list of Panes, even though DIM says it's there. It has come and gone a few times. All the other programs have settled down. Not this one though.

Daz forum uploads have been broken for weeks. You can post the image to an external location and link the image here, if you want to. Sometimes uploads work late at night. Sometimes they don't.

Forum notifications don't happen any more either. You will need to watch you threads manually to see if anyone responded. Lots of information gets missed because of the missing notifications. People think nobody has responded. It's hard to help people that way.

I knew I was missing notifications, but I didn't know why.

I do hope v5.0 becomes a reality.

Well, at least we made some progress on one of your problems.
I'll see if I can think of anything else that might cause that Filament problem. Maybe Richard will pop in with an idea. Are there any error messages or warnings in your log file related to Filament (In Daz Studio, Help>Troubleshooting>View Log File... )

Are you running the same version of Daz Studio that you ran Filament in successfully before? What version is that?

Daz forum uploads have been broken for weeks. You can post the image to an external location and link the image here, if you want to. Sometimes uploads work late at night. Sometimes they don't.

Forum notifications don't happen any more either. You will need to watch you threads manually to see if anyone responded. Lots of information gets missed because of the missing notifications. People think nobody has responded. It's hard to help people that way.

barbult said:

Here's a WP Guru video to help you with Filament Options settings. It is a good Filament overview, too.

He doesn't go near the extreme all-white that I have. The forum wasn't accepting any uploads today, otherwise I would have posted a screen shot. I did add a Filament Draw Options button, all the values were nominal, nothing set to exteme. FWIW, Filament worked fine for me until two weeks ago, when my HD croaked. This all white behavior only began after the rebuild. Multiple uninstall/reinstall did not fix it. I would have purged the registry too, except that Daz is behind every blade of grass. Purging the registry of Blue Iris, by comparison, was a picnic.

I can work around it, but I hate to lose it for no good reason.

Here's a description of the NVIDIA green tint problem. There are also several discussions of this issue in this forum. You say blue, and this says green, but maybe your perception of "blue" is "green" to some other people.

The driver version I settled on is the very version named in the NVIDIA post (I can't imagine how you found that post). And to think all I really had to do was disable one setting. I may reinstall the latest version and just turn that switch off.

Color is an interesting thing. When I see red, and you see red, do we each see the same thing? Aqua or Turquoise might have been a more accurate term.

Here's a WP Guru video to help you with Filament Options settings. It is a good Filament overview, too.

Here's a description of the NVIDIA green tint problem. There are also several discussions of this issue in this forum. You say blue, and this says green, but maybe your perception of "blue" is "green" to some other people.