Daz3D vs. Nvidia 418.81

tomyboy06

Well-Known Member
Jul 31, 2017
1,047
20,351
Hello.

Today i upgraded my device driver 417.35 -> 418.81. I did clear install. After Daz didn't want to Iray render with GPU only CPU. Have someone this problem or not?
I install back 417.35 and work all fine again!

Config :
i7 7700HQ
16GB Ram
GFX 1060 6GB
 

Porcus Dev

Engaged Member
Game Developer
Oct 12, 2017
2,582
4,681
Have you checked that the graphic is checked for use in rendering, in renders settings > advanced?

Have you checked that it is not a problem that the scene exceeds the memory of the graphic and therefore DAZ uses the CPU instead of the GPU? (you can try to render a simple scene, a single object without characters or scenarios)
 

Joraell

Betrayed
Donor
Game Developer
Jul 4, 2017
2,441
8,708
I saw wrning on web about that gpu drivers they have issue with iray. Just skip them.
 

tomyboy06

Well-Known Member
Jul 31, 2017
1,047
20,351
Have you checked that the graphic is checked for use in rendering, in renders settings > advanced?

Have you checked that it is not a problem that the scene exceeds the memory of the graphic and therefore DAZ uses the CPU instead of the GPU? (you can try to render a simple scene, a single object without characters or scenarios)
1. In Render setting -> advanced gfx 1060 pipe, cpu unpipe -> rendering only cpu 418.81
2. i have only 2 character, only backdrop color -> rendering only cpu 418.81
3. i run optimizer wizzard, low textures whole scene -> rendering only cpu 418.81
4. i chech memory usage 8,5-9gb -> rendering only cpu 418.81

5. reload original scene, memory usage 11.4gb -> rendering gpu 417.35

I just wanted to ask someone to have met this one. I leave the new driver, older work fine.
 

Porcus Dev

Engaged Member
Game Developer
Oct 12, 2017
2,582
4,681
1. In Render setting -> advanced gfx 1060 pipe, cpu unpipe -> rendering only cpu 418.81
2. i have only 2 character, only backdrop color -> rendering only cpu 418.81
3. i run optimizer wizzard, low textures whole scene -> rendering only cpu 418.81
4. i chech memory usage 8,5-9gb -> rendering only cpu 418.81

5. reload original scene, memory usage 11.4gb -> rendering gpu 417.35

I just wanted to ask someone to have met this one. I leave the new driver, older work fine.
Ok, then as @Joraell comments, these drivers must have some problem with Iray... it's not always good to use the last thing that comes out, haha, if something works well, don't touch it :LOL:

I'm curious about the memory, the two data you have put exceed your 6GB of VRAM ... not refer to RAM consumption of the system instead of VRAM of the graph? To check the current use of the graphics VRAM you can use the GPU-Z program, in the "sensors" tab you will have information about RAM usage, GPU processor usage, temperatures, etc...
 

tomyboy06

Well-Known Member
Jul 31, 2017
1,047
20,351
It's my fault, i checked only the system memory not the VRAM. When preparing render and the system memory run out the limit (16GB) rendering is interrupted. So I just look at this. Probably this is bad, but it has worked so far.
Only interesting :)
log.02.08.gif
This say VRAM 4,5GB right?
 

Porcus Dev

Engaged Member
Game Developer
Oct 12, 2017
2,582
4,681
It's my fault, i checked only the system memory not the VRAM. When preparing render and the system memory run out the limit (16GB) rendering is interrupted. So I just look at this. Probably this is bad, but it has worked so far.
Only interesting :)
View attachment 241582
This say VRAM 4,5GB right?
This values are while rendering? Then you're not rendering with your GPU, 'cause "GPU Load" is at 3%, would have to be above 90%... and GPU Core Clock/Memory Clock are lower... seems that used memory from GPU (4564MB) is used by other program, have you opened some other program while rendering? Have you switched to the simplest view in viewport in DAZ?

BTW, I think that when you reach your max RAM system, windows uses your HDD as RAM (slower), so make sure you have free space on your disk (usually if you haven't changed it, the C:)... I recommend 30GB free minimum.
 

tomyboy06

Well-Known Member
Jul 31, 2017
1,047
20,351
I've done some tests.
I've have 75GB free space in SSD. Windows and Daz3D installed here.
1. run only daz without scene.
daz ground screen view perspective.gif
2. scene loaded one character.
daz only one character backdrop color viewpoint perspective view.gif
3. during rendering
rendering1.gif
render.PNG
render 1.PNG
4. settings
settings.PNG

I think everything is fine :)
 
  • Like
Reactions: Porcus Dev

Porcus Dev

Engaged Member
Game Developer
Oct 12, 2017
2,582
4,681
Perfect, then you're rendering with your GPU :D

I suggest to check "OptiX Prime Acceleration", and uncheck "CPU" in "Interactive Devices".
 
  • Like
Reactions: tomyboy06

Pebble

Newbie
Jun 19, 2017
79
70
Issues with the new driver, I also had them and so did other people that posted in the Daz forums. I reverted back to the older driver and now it works fine. Gonna wait a while before I update again.
 

f95zoneuser463

Member
Game Developer
Aug 14, 2017
219
1,016
I'm still at 417.01. It works and I will not touch it, no GeForce Experience, no Telemetry or automatic driver update BS enabled.
MaxCarna said in another :
You probably already know that Nvidia drivers 418.* made RTX cards stop working even on Daz 4.11, we will be stucked on 417.7 until the new Iray (and probably Daz) version came out. 418 is the first drive that use the tensor cores, this makes Daz experience a GPU error and fall back to cpu rendering.
I guess 417.71 is the last 'known good' driver then. Last official (non beta) drivers are:
  • 418.81 - 2019-02-04
  • 417.71 - 2019-01-15
  • 417.35 - 2018-12-12
  • 417.22 - 2018-12-03
  • 417.01 - 2018-11-26
  • 416.94 - 2018-11-13
The same with Windows 10 updates. Currently old build 1709 installed. Win 10 was installed shortly after launch, automatic updates disabled using W10privacy, only did one manual update to 1709 once. After all the drama about people have their data deleted in "some cases" with the last W10 update I'm glad I did that.
 

Emoon

Member
May 4, 2017
118
224
Always make sure to read the changelog, especially the open issues section.
It was first mentioned in the 418.91 driver changelog and has been fixed in 419.17.
Unfortunately there where some API changes lately which often results in a bugfest and it takes a while to iron them out.


  • [Iray][OptiX]: Iray GPU acceleration crashes and falls back to CPU acceleration. [2503738]