Problems with new RTX 2080-TI -solved

CelaviehereCelaviehere Posts: 18
edited February 2020 in Daz Studio Discussion

Hi

I hope that somebody can help me.

Just got an additional W10 PC with RTX 2080-Ti graphic card. PC's are identical

I have made exact same setting on the new PC

Both PC's are running DAZ Studio 4.12.0 Pro Edition (64-bit) Publick build

Both PC's have latest GForce driver 442.19

Pc's share library from a third computer.

The old PC has perfect result where the new one render with some kind of distortion or gritty.

Various benchmark programs gives the same result for the graphic cards.

Anyone who knows where to search for the problem?

A longer rendering time doesn't change the result.

New RTX-2080-TI.png
648 x 800 - 1M
RTX2080 TI Good.png
627 x 810 - 1M
Post edited by Celaviehere on
«1

Comments

  • Are you 100% sure the render settings are identical? The first image is less converged than the second so I suspect that the second had a denoiser run on it.

  • nicsttnicstt Posts: 11,714

    The image with noise is likely the more accurate one; characters, that use the denoiser often look like the one you state to be perfect, which actually looks fake to me. In effect, it's too perfect. :)

  • Thanks for your answers.

    How do I control the "denoiser" Doesn’t seems to be a parameter I can find

  • Are you 100% sure the render settings are identical? The first image is less converged than the second so I suspect that the second had a denoiser run on it.

    Yes and no - my problem is that I can’t find any different, so that’s why I ask for help. Quite sure that some minor issue cause the render problem. You’re probably right with the denouser but no clue where to search.

    Thanks again

  • Render Settings->Filtering->Post Denoiser Available->Post Denoiser Enable

  • Render Settings->Filtering->Post Denoiser Available->Post Denoiser Enable

    Thanks for your answer but realized that it's disabled on all my machines. I tried to enable it but with no effect.

    What I haven't mentioned - I have another machine with Nvidia 1070 8 MB and that is rendering perfect too.

  • There is fairly obviously some render setting different between the two. You're going to have to compare all of them until you find which one it is.

     

  • There is fairly obviously some render setting different between the two. You're going to have to compare all of them until you find which one it is.

    Thanks for your answer.

    I know and that's my biggest headache 

    All my render machines ar hooked up through remote desktop and all DAZ material are on 1 HDD. All render settings are from the scene so there should not be any differents.

    NVidia settings on the PC's have been compared with 1 by 1 setting.

    I'm running out of ideas and hope that someone can recognize something in the images that can lead me to the missing settings.

     

  • PaintboxPaintbox Posts: 1,633

    Can you compare the render logs (and maybe post here?) so check the little render window and push the history/details button. 

  • Paintbox said:

    Can you compare the render logs (and maybe post here?) so check the little render window and push the history/details button. 

    Thanks sure

    Will make 2 similar renders and post it - please hold :-)

  • Paintbox said:

    Can you compare the render logs (and maybe post here?) so check the little render window and push the history/details button. 

    Thanks sure

    First I'm using Studio version of NVdia driver - not gaming.

    I have been reading that it can be related to Optix prime and it may be caused by switching between the CPU and GPU

    Rendering time for the bad one is 10 times longer than the good one - this is the reason for the fuzzy image.

    I hope you have a good solution.

    Appreciate your help

    First image (good) took 4 minutes for rendering

    Second image (bad) took 40 minutes to render

     

     

     

     

    pdf
    pdf
    Log files.pdf
    401K
  • stiggstigg Posts: 6
    You're using the CPU instead of the GPU. Check the 2080 ti is selected in the advanced render settings tab.
  • I only bring it up because you mention it is a new PC.

    But double check you NVIDIA drivers as well. If windows does an update, it seems to overwrite the NVIDIA drivers. So if you set everything up and then went through a windows update, you may not have the correct NVIDIA driver.

  • PaintboxPaintbox Posts: 1,633

    Checked the log, it seems your GPU isn't  initialized at all. So Daz Studio/Iray can't find the GPU. So first check if Daz Studio, in preferences I believe, your card is seen at all.

  • You also need to check the Nvidia control panel to verify that DS is allowed to use the card.

    Definitely verify that the driver is new and disable Windows Update from installing any drivers.

  • Hi all

    Thanks for your help. Problem solved.

    It was not NVIDIA, but DAZ studio. It seems that very latest version has problems with rtx 2080-TI. I found an earlier version and installed it, and now it’s working.

    Again thanks for your help

  • PaintboxPaintbox Posts: 1,633

    Glad to hear you got it running! 

  • Hi all

    Thanks for your help. Problem solved.

    It was not NVIDIA, but DAZ studio. It seems that very latest version has problems with rtx 2080-TI. I found an earlier version and installed it, and now it’s working.

    Again thanks for your help

    Plenty of people use 4.12 with 2080ti's. That was not the issue.

  • dijituldijitul Posts: 146
    edited February 2020

    I have dual 2080 Ti with DAZ 4.12 and do not have this issue.  

    Noise can be cause by a couple of things.  Most often it's due to inadequate light in the scene.  Increase the environment or spotlight brightness.  Another is if you're using emitters versus spotlights.  Another is if you're using built-in lamps but NOT the Spotlight.  Another is if there is reflective surfaces and you're catching bounced rays or if Caustics are enabled.  Another is if you have lower convergence settings.  Another is CPU vs GPU, which I think someone pointed out in your logs. Just a few guesses.

    From your log file:

    2020-02-18 14:34:59.102 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CPU: using 8 cores for rendering

    Post edited by dijitul on
  • I have dual 2080 Ti with DAZ 4.12 and do not have this issue.  

    Noise can be cause by a couple of things.  Most often it's due to inadequate light in the scene.  Increase the environment or spotlight brightness.  Another is if you're using emitters versus spotlights.  Another is if you're using built-in lamps but NOT the Spotlight.  Another is if there is reflective surfaces and you're catching bounced rays or if Caustics are enabled.  Another is if you have lower convergence settings.  Another is CPU vs GPU, which I think someone pointed out in your logs. Just a few guesses.

    From your log file:

    2020-02-18 14:34:59.102 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CPU: using 8 cores for rendering

    In fact that's not the case. I thought that it was solve but new renders showed the problem again. I have 2 similar machines sharing my work. 2 identical machines rendering the same material. Old machine is perfect - new one switch to CPU. For the new machine I increased the power supply with no result - increased memory to 32GB with no result. I have been through all the settings and they are identical. Been through almost every forum and haven't found the magic trick yet. When I read various forums it seems very random. What happen - after few sec/minutes it switch to use the CPU. If I render small job's it's not an issue and continue to render with GPU's but as soon as the job is fairly larger it switches to CPU. It seems to load my power supply with almost 100 % on the new machine - with the old one I have no issues. I have tried various versions of DAZ Studio - used NVidia studio driver and game drivers. Switch back to previous NVidia drivers with same result. I can use the machine but rendering time needs to be 100 to 150 % longer because it switch to CPU - that means significant slower than my third machine with 1070-Ti running older version of DAZ. 

    My last setting gives me an error telling that there is errors using GPU and Optix no longer is supported - even when it's not switch on.
    Any idea what it could be? - I ran out of ideas.

  • What precisely are the specs of the system.

    CPU, motherboard, PSU, storage systems, even the cooling and the case. If it is a prebuilt, by who? Since you got it have you updated all drivers? Have you run DDU and then installed the newest Nvidia driver?

  • What precisely are the specs of the system.

    CPU, motherboard, PSU, storage systems, even the cooling and the case. If it is a prebuilt, by who? Since you got it have you updated all drivers? Have you run DDU and then installed the newest Nvidia driver?

    Thanks for your answer:

    I have 2 similar computers with RTX2080 -Ti which I bought back in September - it works perfect and use DAZ Studio 4.11.0.366 - unfortunately I can't find it anywhere - tried 388 with no luck. I have rendered at least 50 various images with same result.

    I can use the computer for rendering if I set rendering time to a factor 4.

    It starts using RTX 2080 - Ti but after short time it switch to CPU

    CPU and Optix are unchecked

    I have asked the Nvidia driver settings to use CUDA from RTX2080-Ti

    Edition Windows 10 Pro
    Version 1903
    OS build 18362.657
    Processor i7-9700 @ 3GHz
    RAM 32 GB
    System 64 - bit

    Power supply Hydro 800W
    Computer Shark Gaming - prebuild
    NVidia driver 442.19 tried both gaming and studio version
    DAZ Studio 4.12.0.86

    DDU run - yes with every attempt

    No Denoiser activated

    Got following warnings when I start DAZ Studio

    2020-02-25 23:16:01.485 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): peer performed orderly shutdown errno=0
    2020-02-25 23:19:23.690 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): recv failed errno=10054

    2020-02-26 07:57:05.611 WARNING: QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout

    It starts perfect but after short time:

    2020-02-26 08:17:25.588 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Emitter geometry import (16 light sources with 63216 triangles, 1 instance) took 0.002s

    2020-02-26 08:17:25.588 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating environment.

    2020-02-26 08:17:25.931 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating backplate.

    2020-02-26 08:17:25.932 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating lens.

    2020-02-26 08:17:25.933 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating lights.

    2020-02-26 08:17:25.933 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating object flags.

    2020-02-26 08:17:25.933 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating caustic portals.

    2020-02-26 08:17:25.933 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating decals.

    2020-02-26 08:17:25.936 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER ::   1.0   IRAY   rend warn : The 'iray_optix_prime' scene option is no longer supported.

    2020-02-26 08:17:25.969 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Allocating 1-layer frame buffer

    2020-02-26 08:17:26.014 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Using batch scheduling, caustic sampler disabled

    2020-02-26 08:17:26.014 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Initializing local rendering.

    2020-02-26 08:17:26.023 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : CPU: using 8 cores for rendering

    2020-02-26 08:17:26.023 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering with 1 device(s):

    2020-02-26 08:17:26.023 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : CPU

    2020-02-26 08:17:26.023 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering...

    2020-02-26 08:17:26.023 Iray [INFO] - IRAY:RENDER ::   1.6   IRAY   rend info : Initializing Embree

    2020-02-26 08:17:26.023 Iray [VERBOSE] - IRAY:RENDER ::   1.4   IRAY   rend progr: CPU: Processing scene...

    2020-02-26 08:17:36.848 Iray [INFO] - IRAY:RENDER ::   1.6   IRAY   rend info : Importing lights for motion time 0

    2020-02-26 08:17:36.849 Iray [INFO] - IRAY:RENDER ::   1.6   IRAY   rend info : Initializing light hierarchy.

    2020-02-26 08:17:37.542 Iray [INFO] - IRAY:RENDER ::   1.6   IRAY   rend info : Light hierarchy initialization took 0.692s

    2020-02-26 08:17:37.659 Iray [VERBOSE] - IRAY:RENDER ::   1.6   IRAY   rend stat : Native CPU code generated in 0.099s

    2020-02-26 08:17:37.761 Iray [INFO] - IRAY:RENDER ::   1.4   IRAY   rend info : CPU: Scene processed in 11.738s

    2020-02-26 08:17:37.817 Iray [INFO] - IRAY:RENDER ::   1.4   IRAY   rend info : CPU: Allocated 205.995 MiB for frame buffer

    2020-02-26 08:17:59.517 Iray [INFO] - IRAY:RENDER ::   1.4   IRAY   rend info : Allocating 1-layer frame buffer

    2020-02-26 08:17:59.923 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00001 iterations after 33.899s.

    2020-02-26 08:18:00.114 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER ::   1.0   IRAY   rend warn : The 'iray_optix_prime' scene option is no longer supported.

    2020-02-26 08:18:21.888 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00002 iterations after 55.864s.

    2020-02-26 08:18:22.004 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER ::   1.0   IRAY   rend warn : The 'iray_optix_prime' scene option is no longer supported.

    2020-02-26 08:18:43.962 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00003 iterations after 77.939s.

    2020-02-26 08:18:44.042 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER ::   1.0   IRAY   rend warn : The 'iray_optix_prime' scene option is no longer supported.

    2020-02-26 08:19:06.103 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00004 iterations after 100.079s.

    2020-02-26 08:19:06.209 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER ::   1.0   IRAY   rend warn : The 'iray_optix_prime' scene option is no longer supported.

    2020-02-26 08:19:28.093 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00005 iterations after 122.070s.

    2020-02-26 08:19:28.189 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER ::   1.0   IRAY   rend warn : The 'iray_optix_prime' scene option is no longer supported.

    2020-02-26 08:19:50.166 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00006 iterations after 144.144s.

    2020-02-26 08:19:50.270 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER ::   1.0   IRAY   rend warn : The 'iray_optix_prime' scene option is no longer supported.

    2020-02-26 08:20:12.376 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00007 iterations after 166.354s.

    2020-02-26 08:20:12.445 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER ::   1.0   IRAY   rend warn : The 'iray_optix_prime' scene option is no longer supported.

    2020-02-26 08:20:34.618 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00008 iterations after 188.595s.

    2020-02-26 08:20:34.702 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER ::   1.0   IRAY   rend warn : The 'iray_optix_prime' scene option is no longer supported.

    ......

    CPU load switch to 95 to 100% where my old system keeps it at 38 %

    It seems that many have these issues but so far I haven't seen any proper solution that works for me.

    Thanks for your help

    /Bob

     

  • Most likely something is misconfigured in the system.

    Less likely the 2080ti is not good and needs to be RMA'd.

    Either way contact the seller and explain your issue. Since they sold you both machines they should be able to figure out what's the difference.

  • Most likely something is misconfigured in the system.

    Less likely the 2080ti is not good and needs to be RMA'd.

    Either way contact the seller and explain your issue. Since they sold you both machines they should be able to figure out what's the difference.

    Thanks for your answer. The problem is that the 2080 -Ti seems to work and for me it look's like a software issue. They'll probably just say that the machine works as expected. I'll try make some more benchmark on the 2080 -Ti to see if something looks different.

    Thanks for your help

     

  • RayDAntRayDAnt Posts: 1,120
    edited February 2020

    Most likely something is misconfigured in the system.

    Less likely the 2080ti is not good and needs to be RMA'd.

    Either way contact the seller and explain your issue. Since they sold you both machines they should be able to figure out what's the difference.

    Thanks for your answer. The problem is that the 2080 -Ti seems to work and for me it look's like a software issue. They'll probably just say that the machine works as expected. I'll try make some more benchmark on the 2080 -Ti to see if something looks different.

    Thanks for your help

     

    Go to Render Settings > Advanced > Hardware > Photoreal Mode > Devices and un-check your 2080Ti in the list. Then immediately re-check it and start a test render. There's a good chance your GPU may now suddenly start being used.

    Post edited by RayDAnt on
  • It's a shot in the dark, but in comparing the two logs, one difference I saw was Optix error.

    For the 2080-ti machine, don't check the box.

    I don't know why it would make a difference, but I do recall another poster having a problem that unchecking the box solved. I seem to recall that Optix is not required for new 2xxx cards, but don't depend on me for that. 

    Another thing, I'm assuming once the render drops to CPU, and you try something else, you are restarting Daz over again before trying another render?

    There is another thread that explains it better, but I have experienced it as well with a 2080ti, once you drop to CPU, (for me it is usually a scene was too big), it will continue to use CPU only, unless you restart Daz.

  • It's a shot in the dark, but in comparing the two logs, one difference I saw was Optix error.

    For the 2080-ti machine, don't check the box.

    I don't know why it would make a difference, but I do recall another poster having a problem that unchecking the box solved. I seem to recall that Optix is not required for new 2xxx cards, but don't depend on me for that. 

    Another thing, I'm assuming once the render drops to CPU, and you try something else, you are restarting Daz over again before trying another render?

    There is another thread that explains it better, but I have experienced it as well with a 2080ti, once you drop to CPU, (for me it is usually a scene was too big), it will continue to use CPU only, unless you restart Daz.

    Thanks for your feedback

    I never use Optix so that's not the case. Tried almost everything and I always shut down and restart. Thanks for your shot :-)

     

  • CelaviehereCelaviehere Posts: 18
    edited February 2020

    It's a shot in the dark, but in comparing the two logs, one difference I saw was Optix error.

    For the 2080-ti machine, don't check the box.

    I don't know why it would make a difference, but I do recall another poster having a problem that unchecking the box solved. I seem to recall that Optix is not required for new 2xxx cards, but don't depend on me for that. 

    Another thing, I'm assuming once the render drops to CPU, and you try something else, you are restarting Daz over again before trying another render?

    There is another thread that explains it better, but I have experienced it as well with a 2080ti, once you drop to CPU, (for me it is usually a scene was too big), it will continue to use CPU only, unless you restart Daz.

    Weird - un-check and check - for 10 minutes it was working but then switched back to CPU 

     

     

     

    Post edited by Celaviehere on
  • RayDAnt said:

    Most likely something is misconfigured in the system.

    Less likely the 2080ti is not good and needs to be RMA'd.

    Either way contact the seller and explain your issue. Since they sold you both machines they should be able to figure out what's the difference.

    Thanks for your answer. The problem is that the 2080 -Ti seems to work and for me it look's like a software issue. They'll probably just say that the machine works as expected. I'll try make some more benchmark on the 2080 -Ti to see if something looks different.

    Thanks for your help

     

    Go to Render Settings > Advanced > Hardware > Photoreal Mode > Devices and un-check your 2080Ti in the list. Then immediately re-check it and start a test render. There's a good chance your GPU may now suddenly start being used.

    Weird - un-check and check - for 10 minutes it was working but then switched back to CPU 

  • stiggstigg Posts: 6
    Have you considered the hardware may be faulty? Try swapping the 2080 tis over and see it the problem follows the card. I had a 2080ti I had to RMA because it developed a fault. It's would drop to CPU after a few minutes. It was also unstable when trying to play games on it. I figured it was memory controller/vram related as it became stable again after downclocking the memory speed.
Sign In or Register to comment.