Loading...
> >

Daz Studio Pro BETA - version 4.12.2.60! (*UPDATED*)

1…2627293132…74

Comments

  • Wildman oSWildman oS Posts: 121
    edited November 2019

    Using  (NON beta) 4.12.0.86  AND beta 4.12.1.16 with the latest Nvidia studio drivers 441.12 RTX2080ti

    Still getting fallback to CPU rendering

    Closing DAZstudio and then restarting, even with nothing in the scene, 25gb of ram free, 10.2gb VRAM free immediately goes to CPU rendering (ofc there's nothing to see because there's nothing in the scene)

    I wish daz would get their finger out and fix this as the program is useless atm

     

    Post edited by Wildman oS on
  • Richard HaseltineRichard Haseltine Posts: 100,839
    Wildman oS said:

    Using  (NON beta) 4.12.0.86  AND beta 4.12.1.16 with the latest Nvidia studio drivers 441.12 RTX2080ti

    Still getting fallback to CPU rendering

    Closing DAZstudio and then restarting, even with nothing in the scene, 25gb of ram free, 10.2gb VRAM free immediately goes to CPU rendering (ofc there's nothing to see because there's nothing in the scene)

    I wish daz would get their finger out and fix this as the program is useless atm

    Daz cannot change Iray - or the drivers. Iray is a closed system, Daz just writes the code to pass the scene and settings to it and receive the rendered output from it.

  • Wildman oSWildman oS Posts: 121
    Richard Haseltine said:
    Wildman oS said:

    Using  (NON beta) 4.12.0.86  AND beta 4.12.1.16 with the latest Nvidia studio drivers 441.12 RTX2080ti

    Still getting fallback to CPU rendering

    Closing DAZstudio and then restarting, even with nothing in the scene, 25gb of ram free, 10.2gb VRAM free immediately goes to CPU rendering (ofc there's nothing to see because there's nothing in the scene)

    I wish daz would get their finger out and fix this as the program is useless atm

    Daz cannot change Iray - or the drivers. Iray is a closed system, Daz just writes the code to pass the scene and settings to it and receive the rendered output from it.

    So you are suggesting that it is recent Nvidia studio drivers that are causing the cpu rendering problem ?

    I don't believe that is the case, as the cpu rendering problem started for me after I installed the latest Daz beta drivers

    the nvidia studio drivers were unchanged at that time

    it was only when the cpu problem became evident that I updated to the nvidia  drivers 441.12, and the problem persisted

    However,  if it is the nvidia drivers which are causing the problem then the simple fix is to reinstall older studio drivers

    I still have the nvidia studio 431.86 drivers, so I shall revert back to them and see if it resolves the cpu issue

  • LeanaLeana Posts: 11,694
    Wildman oS said:

    So you are suggesting that it is recent Nvidia studio drivers that are causing the cpu rendering problem ?

    Richard meant is that Iray is not developped by Daz, nvidia provides the various versions as some kind of "black box component" to Daz and Daz only writes DS code to use that component.

    But yes, the new nvidia drivers are probably part of the problem. It wouldn't be the first time nvidia broke something related to iray when releasing new drivers, and needed to relased a new version of either the drivers or iray to fix that.

    Wildman oS said:

    I don't believe that is the case, as the cpu rendering problem started for me after I installed the latest Daz beta drivers

    There's no such thing as "Daz beta drivers".
    The DS beta probably included a newer version of Iray than the version you used previously though, and it's possible that version has problems with the drivers you use. That would be something for nvidia to fix as they develop both Iray and the drivers, and then if that requires a fix in iray Daz will have to create a DS version with the new iray version once they have it.

  • Wildman oSWildman oS Posts: 121
    Leana said:

    Richard meant is that Iray is not developped by Daz, nvidia provides the various versions as some kind of "black box component" to Daz and Daz only writes DS code to use that component.

    But yes, the new nvidia drivers are probably part of the problem. It wouldn't be the first time nvidia broke something related to iray when releasing new drivers, and needed to relased a new version of either the drivers or iray to fix that.

    There's no such thing as "Daz beta drivers".
    The DS beta probably included a newer version of Iray than the version you used previously though, and it's possible that version has problems with the drivers you use. That would be something for nvidia to fix as they develop both Iray and the drivers, and then if that requires a fix in iray Daz will have to create a DS version with the new iray version once they have it.

    Thank you for the clarification, although I think you misunderstood my comment

    Yes, my error I should have written Daz beta 'application', not Daz beta drivers

    Here was my dilema:

    Nvidia Studio drivers 431.86 + DazStudio beta 4.11.0.383 (or whatever version was immediately prior to 4.12.1.16) Works fine for me, no noticeable problems

    Nvidia Studio drivers 431.86 + upgrade to Daz Studio beta 4.12.1.16 << As soon as this DAZSTUDIO beta update was installed THEN the cpu rendering began

    This would suggest it is that which has changed that has caused the problem, not that which has remained the same

    therefore the new Daz Studio beta application and not the Nvidia drivers which caused the problem  (which have not changed)

    After noticing a new version of the Nvidia Studio drivers had been released v441.12 I updated them - with no resolution to the cpu rendering problem

    there followed many days of annoyance at the situation, but at least I could work for a while using IRAY before Daz Studio began to contantly use cpu rendering

    simply quitting daz studio and reloading it would return to using the Gfx card for IRAY rendering (for a while)

    However, this past few days simply, quitting and reloading DazStudio did not fix the problem

    Daz Studio would immediately use cpu rendering even on the empty scene with full system resources available

    Not even rebooting would resolve the issue, hence my earlier comment

    Even using the release version of Daz Studio v4.12.0.86 the cpu problem was happening exactly as with the beta version

     

    I have now removed the Nvidia Studio drivers (v441.12) and reinstalled older Nvidia Studio drivers (v431.86) and for the past hour IRAY has been working as it should do

    Only time will tell if this has truly solved the problem

    in which case we will have to wait for a new version of the Nvia Studio drivers

    I noticed that  yesterday there was a new version of the gameready drivers released (v441.20)

    I expect that the Nvidia Studio version will be released in due course, with the cpu problem resolved

     

    I applogise for pointing the finger at the DazStudio beta, but logic dictated it should be so

    in this case logic was wrong

    neither I nor Mister Spock are perfect

     

  • Faery_LightFaery_Light Posts: 22

    Since the Face Transfer that is included in DS does not have all the bells and whistles of the original retail version, it would be nice if the restriction on how many you can save would be lifted. :)
    Some of us can't afford to retail set but might make more products so we could afford it if that restriction were gone.

     

  • Richard HaseltineRichard Haseltine Posts: 100,839
    Faery_Light said:

    Since the Face Transfer that is included in DS does not have all the bells and whistles of the original retail version, it would be nice if the restriction on how many you can save would be lifted. :)
    Some of us can't afford to retail set but might make more products so we could afford it if that restriction were gone.

    There are only two differences between the free and purchased license - number of saves and the watermark.

  • Faery_LightFaery_Light Posts: 22

    Richard. thanks for that information. 
    I just thought the retail version would have more bells and whistles.
    If I ever get the money to get the retail so there are no limits, I will because I like using it. :)

  • LeanaLeana Posts: 11,694
    Wildman oS said:
    Leana said:

    Richard meant is that Iray is not developped by Daz, nvidia provides the various versions as some kind of "black box component" to Daz and Daz only writes DS code to use that component.

    But yes, the new nvidia drivers are probably part of the problem. It wouldn't be the first time nvidia broke something related to iray when releasing new drivers, and needed to relased a new version of either the drivers or iray to fix that.

    There's no such thing as "Daz beta drivers".
    The DS beta probably included a newer version of Iray than the version you used previously though, and it's possible that version has problems with the drivers you use. That would be something for nvidia to fix as they develop both Iray and the drivers, and then if that requires a fix in iray Daz will have to create a DS version with the new iray version once they have it.

    Thank you for the clarification, although I think you misunderstood my comment

    Yes, my error I should have written Daz beta 'application', not Daz beta drivers

    Here was my dilema:

    Nvidia Studio drivers 431.86 + DazStudio beta 4.11.0.383 (or whatever version was immediately prior to 4.12.1.16) Works fine for me, no noticeable problems

    Nvidia Studio drivers 431.86 + upgrade to Daz Studio beta 4.12.1.16 << As soon as this DAZSTUDIO beta update was installed THEN the cpu rendering began

    This would suggest it is that which has changed that has caused the problem, not that which has remained the same

    therefore the new Daz Studio beta application and not the Nvidia drivers which caused the problem  (which have not changed)

    After noticing a new version of the Nvidia Studio drivers had been released v441.12 I updated them - with no resolution to the cpu rendering problem

    there followed many days of annoyance at the situation, but at least I could work for a while using IRAY before Daz Studio began to contantly use cpu rendering

    simply quitting daz studio and reloading it would return to using the Gfx card for IRAY rendering (for a while)

    However, this past few days simply, quitting and reloading DazStudio did not fix the problem

    Daz Studio would immediately use cpu rendering even on the empty scene with full system resources available

    Not even rebooting would resolve the issue, hence my earlier comment

    Even using the release version of Daz Studio v4.12.0.86 the cpu problem was happening exactly as with the beta version

     

    I have now removed the Nvidia Studio drivers (v441.12) and reinstalled older Nvidia Studio drivers (v431.86) and for the past hour IRAY has been working as it should do

    Only time will tell if this has truly solved the problem

    in which case we will have to wait for a new version of the Nvia Studio drivers

    I noticed that  yesterday there was a new version of the gameready drivers released (v441.20)

    I expect that the Nvidia Studio version will be released in due course, with the cpu problem resolved

     

    I applogise for pointing the finger at the DazStudio beta, but logic dictated it should be so

    in this case logic was wrong

    neither I nor Mister Spock are perfect

    According to the thread listing iray updates in DS, the latest update of DS beta did include a new version of Iray, so that could have introduced the problem with the beta. I don't see how it could have affected the release version though... Did you have problems with the release version with the old drivers?

  • cimenroller2cimenroller2 Posts: 76

    Why am I still getting this error?

    face transfer failed to generate try a different source image.

  • marblemarble Posts: 7,500
    edited November 2019

    Update on the CPU fallback issue. I'm using the current Beta (4.12.1.16) with NVidia Drivers 441.12 and my GPU is a GeForce 1070 with 8GB of VRAM.

    I was tinkering with skin shaders using Altern8 and trying different tones, etc., when I noticed that the IRay preview has suddenly dropped to CPU (I have a loud cooler in my CPU so it is unmistakeable). However, on checking GPU-Z it is clear that I had NOT run short of VRAM (see attached screenshot). So if it is not VRAM causing the fallback, what is it? By the way, these drivers seem better than the previous version because I have been able to render past the first frame of an image series which wasn't possible with the previos drivers.

    I tried some of the suggested workarounds like switching the render engine to CPU for a render then switching back to GPU but the only remedy seems to be to exit DAZ Studio and restart. I do hope they (DAZ or NVidia) fix this soon, it is taking all the fun out of working with DAZ Studio.

    fallback.jpg
    678 x 1280 - 164K
    Post edited by marble on
  • saneinvividualsaneinvividual Posts: 1
    edited November 2019

    concerning Iray and random CPU-Fallbacks:

    I can safely trigger a CPU-fallback within 1 minute by loading a G8 character and then randomly *spam-load-and-unload* various clothes. (viewport being in Iray-Mode...obviously)

    I am 100% sure that I am not over my VRAM budget. It is not an out-memory-fallback. My MSI Afterburner is set up to trigger an alarm if the GTX 1070 memory usage is above 6 GB. The only way to get DAZ to render with Iray on the GPU again is: save, restart DAZ, reload scene, continue.

    HARDWARE: i7 2600K, 32 GB DDR3 1600Mhz, GeForce GTX 1070 8 GB

    SOFTWARE: Windows 10 1903 18362.329, DAZ Studio 4.12.1.16 64 bit, Nvidia driver 441.12 tested 'standard' and 'studio' drivers

    edit: I can confirm the following Nvidia Driver versions all trigger this bug, It took me longer on older versions but that could be random:

    • 430.86-desktop-win10-64bit-international-nsd-whql
    • 431.86-desktop-win10-64bit-international-nsd-whql
    • 441.12-desktop-win10-64bit-international-nsd-whql
    • 441.12-desktop-win10-64bit-international-whql

    nsd-whql = "Studio" driver / whql = "Standard" driver

    log:

    2019-11-16 21:18:06.236 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating lights.2019-11-16 21:18:06.236 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating object flags.2019-11-16 21:18:06.236 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating caustic portals.2019-11-16 21:18:06.236 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating decals.2019-11-16 21:18:06.236 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Allocating 1-layer frame buffer2019-11-16 21:18:06.251 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Using interactive scheduling, caustic sampler disabled2019-11-16 21:18:06.251 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering with 1 device(s):2019-11-16 21:18:06.251 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : CUDA device 0 (GeForce GTX 1070)2019-11-16 21:18:06.251 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering...2019-11-16 21:18:06.251 Iray [VERBOSE] - IRAY:RENDER ::   1.9   IRAY   rend progr: CUDA device 0 (GeForce GTX 1070): Processing scene...2019-11-16 21:18:06.283 Iray [INFO] - IRAY:RENDER ::   1.2   IRAY   rend info : Initializing OptiX Prime for CUDA device 02019-11-16 21:18:06.283 Iray [VERBOSE] - IRAY:RENDER ::   1.2   IRAY   rend stat : Geometry memory consumption: 81.816 MiB (device 0), 0.000 B (host)2019-11-16 21:18:06.392 Iray [VERBOSE] - IRAY:RENDER ::   1.2   IRAY   rend stat : Texture memory consumption: 2.683 GiB for 153 bitmaps (device 0)2019-11-16 21:18:06.392 Iray [INFO] - IRAY:RENDER ::   1.2   IRAY   rend info : Importing lights for motion time 02019-11-16 21:18:06.392 Iray [INFO] - IRAY:RENDER ::   1.2   IRAY   rend info : Initializing light hierarchy.2019-11-16 21:18:06.392 Iray [INFO] - IRAY:RENDER ::   1.2   IRAY   rend info : Light hierarchy initialization took 0.000s2019-11-16 21:18:06.392 Iray [VERBOSE] - IRAY:RENDER ::   1.2   IRAY   rend stat : Lights memory consumption: 196.000 B (device 0)2019-11-16 21:18:06.392 Iray [VERBOSE] - IRAY:RENDER ::   1.2   IRAY   rend stat : Material measurement memory consumption: 0.000 B (GPU)2019-11-16 21:18:06.392 Iray [VERBOSE] - IRAY:RENDER ::   1.2   IRAY   rend stat : PTX code (329.709 KiB) for SM 6.1 generated in 0.001s2019-11-16 21:18:06.392 Iray [VERBOSE] - IRAY:RENDER ::   1.2   IRAY   rend stat : Materials memory consumption: 520.566 KiB (GPU)2019-11-16 21:18:06.439 Iray [INFO] - IRAY:RENDER ::   1.2   IRAY   rend info : JIT-linking wavefront kernel in 0.042s2019-11-16 21:18:06.455 Iray [INFO] - IRAY:RENDER ::   1.2   IRAY   rend info : JIT-linking mega kernel in 0.020s2019-11-16 21:18:06.455 Iray [INFO] - IRAY:RENDER ::   1.9   IRAY   rend info : CUDA device 0 (GeForce GTX 1070): Scene processed in 0.205s2019-11-16 21:18:06.455 Iray [INFO] - IRAY:RENDER ::   1.2   IRAY   rend info : CUDA device 0 (GeForce GTX 1070): Allocated 25.050 MiB for frame buffer2019-11-16 21:18:06.455 Iray [INFO] - IRAY:RENDER ::   1.9   IRAY   rend info : CUDA device 0 (GeForce GTX 1070): Allocated 1.107 GiB of work space (1343k active samples in 0.000s)2019-11-16 21:18:06.455 Iray [INFO] - IRAY:RENDER ::   1.9   IRAY   rend info : CUDA device 0 (GeForce GTX 1070): Used for display, optimizing for interactive usage (performance could be sacrificed)<span style="color:#FF0000">2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.2   IRAY   rend error: CUDA device 0 (GeForce GTX 1070): an illegal memory access was encountered (while launching CUDA renderer)</span>2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.2   IRAY   rend error: CUDA device 0 (GeForce GTX 1070): Failed to launch renderer2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.9   IRAY   rend error: CUDA device 0 (GeForce GTX 1070): Device failed while rendering2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [WARNING] - IRAY:RENDER ::   1.9   IRAY   rend warn : All available GPUs failed.2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [WARNING] - IRAY:RENDER ::   1.9   IRAY   rend warn : No devices activated. Enabling CPU fallback.2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [WARNING] - IRAY:RENDER ::   1.9   IRAY   rend warn : Re-rendering iteration because of device failure2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.9   IRAY   rend error: All workers failed: aborting render2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.9   IRAY   rend error: CUDA device 0 (GeForce GTX 1070): an illegal memory access was encountered (while de-allocating memory)2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.9   IRAY   rend error: CUDA device 0 (GeForce GTX 1070): an illegal memory access was encountered (while de-allocating memory)2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.9   IRAY   rend error: CUDA device 0 (GeForce GTX 1070): an illegal memory access was encountered (while de-allocating memory)2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.9   IRAY   rend error: CUDA device 0 (GeForce GTX 1070): an illegal memory access was encountered (while de-allocating memory)2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.9   IRAY   rend error: CUDA device 0 (GeForce GTX 1070): an illegal memory access was encountered (while de-allocating memory)2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.9   IRAY   rend error: CUDA device 0 (GeForce GTX 1070): an illegal memory access was encountered (while de-allocating memory)2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.9   IRAY   rend error: CUDA device 0 (GeForce GTX 1070): an illegal memory access was encountered (while de-allocating memory)2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.9   IRAY   rend error: CUDA device 0 (GeForce GTX 1070): an illegal memory access was encountered (while de-allocating memory)2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.9   IRAY   rend error: CUDA device 0 (GeForce GTX 1070): an illegal memory access was encountered (while de-allocating memory)2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.9   IRAY   rend error: CUDA device 0 (GeForce GTX 1070): an illegal memory access was encountered (while de-allocating memory)2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: CUDA device 0 (GeForce GTX 1070): an illegal memory access was encountered (while de-allocating memory)2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: CUDA device 0 (GeForce GTX 1070): an illegal memory access was encountered (while de-allocating memory)2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: CUDA device 0 (GeForce GTX 1070): an illegal memory access was encountered (while de-allocating memory)2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: CUDA device 0 (GeForce GTX 1070): an illegal memory access was encountered (while de-allocating memory)2019-11-16 21:18:06.486 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : CPU: using 8 cores for rendering2019-11-16 21:18:06.486 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering with 1 device(s):2019-11-16 21:18:06.486 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : CPU2019-11-16 21:18:06.486 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering...2019-11-16 21:18:06.486 Iray [INFO] - IRAY:RENDER ::   1.2   IRAY   rend info : Using Embree 2.8.02019-11-16 21:18:06.486 Iray [INFO] - IRAY:RENDER ::   1.2   IRAY   rend info : Initializing Embree2019-11-16 21:18:06.486 Iray [VERBOSE] - IRAY:RENDER ::   1.9   IRAY   rend progr: CPU: Processing scene...2019-11-16 21:18:07.376 Iray [VERBOSE] - IRAY:RENDER ::   1.2   IRAY   rend stat : Native CPU code generated in 0.506s2019-11-16 21:18:07.376 Iray [INFO] - IRAY:RENDER ::   1.9   IRAY   rend info : CPU: Scene processed in 0.887s2019-11-16 21:18:07.392 Iray [INFO] - IRAY:RENDER ::   1.2   IRAY   rend info : CPU: Allocated 25.050 MiB for frame buffer2019-11-16 21:18:08.533 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [WARNING] - POST:RENDER ::   1.0   POST   rend warn : renderer iray has no more devices available. Postprocessing falling back to CPU.2019-11-16 21:18:08.533 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [WARNING] - POST:RENDER ::   1.0   POST   rend warn : Postprocessing is running on the CPU, but Denoiser is requested. Denoising is not available on CPU.2019-11-16 21:18:08.548 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00001 iterations after 2.272s.2019-11-16 21:18:08.548 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering...2019-11-16 21:18:09.751 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00002 iterations after 3.464s.
    Post edited by saneinvividual on
  • Saxa -- SDSaxa -- SD Posts: 872
    edited November 2019
    marble said:
     

    I tried some of the suggested workarounds like switching the render engine to CPU for a render then switching back to GPU but the only remedy seems to be to exit DAZ Studio and restart. I do hope they (DAZ or NVidia) fix this soon, it is taking all the fun out of working with DAZ Studio.

     

    saneinvividual said:

    I can safely trigger a CPU-fallback within 1 minute by loading a G8 character and then randomly *spam-load-and-unload* various clothes. (viewport being in Iray-Mode...obviously)

     

    If one of you guys has a routine that (1) triggers drop to CPU and most importantly (2) the steps are reproducible by Daz tech support, then can you please send that in to support?

    4.12.0.86 continues to be rock solid after many long sessions, with all driver versions including 441.12 (which some RTX users seem to have had issues with).
    Whereas, Beta 4.12.1.16 continues to reliably drop to CPU.
    Using RTX2080Ti, win7 64, 64GB ram

    Presently my ticket for this issue is on hold status.  Awaiting dev-team input.
    Reproducing this issue for me is not that easy because it really is a bunch of texture spamming changes including panning/zooming over usually 10-15 minutes that triggers my drop to CPU.  
    So if anybody has the time to figure out and present a reproducible system of exact changes that DAZ can do to trigger this issue, that would be very helpful.

    Post edited by Saxa -- SD on
  • usahawansufi6c2usahawansufi6c2 Posts: 30
    I am still waiting for Daz to introduce multiple collision items... It's sad that you've only been able to collide with one item thus far.
  • hshqerror_6b3e477a63hshqerror_6b3e477a63 Posts: 1
    saneinvividual said:

    concerning Iray and random CPU-Fallbacks:

    I can safely trigger a CPU-fallback within 1 minute by loading a G8 character and then randomly *spam-load-and-unload* various clothes. (viewport being in Iray-Mode...obviously)

    ................................

    Hey,

    I had the same problem with 1080 GPU. My Asus Nvidia 1080ti OC (11 GB) didn't render at all. What I did was that I went to bios and enabled my processor (CPU I7-6700K) GPU which is Intel(R) HD Graphics 530. It was disabled by default. Now when I render a scene, taskmanager shows that Nvidia GPU is 100%, CPU about 20-30% and Intel GPU 0%. I dont have a  glue why it is rendering now. Driver version is 441.12 game.

    My Asus 43" 4k monitor is connected to Nvidia GPU. WhenI rendered a short test clip (image series 120x2500x2000, took over 2,5 hours) Windows task manager told that Dedicated GPU memory is 6.3/11.0 GP, GPU memory is 6.5/26.9 GB and shared GPU memory is 0.1/15.9 GB. I had both Crome and Firefox browsers open and Photoshop 2020 cc. 

    I also downloaded Intel sofware (Intel® Driver & Support Assistant; xxx.intel.com/content/www/us/en/support/intel-driver-support-assistant.html, replace xxx with www) and it updated my Intel GPU drivers. Microsoft apparently doesn't update them because my drivers where over 2 years old. If I remember correctly (not 100% sure) rendering started to work after I updated those drivers. My board is Asus Z170 Pro Gaming. 

    I hope this helps.

     

  • nonesuch00nonesuch00 Posts: 18,120
    hshqerror_6b3e477a63 said:
    saneinvividual said:

    concerning Iray and random CPU-Fallbacks:

    I can safely trigger a CPU-fallback within 1 minute by loading a G8 character and then randomly *spam-load-and-unload* various clothes. (viewport being in Iray-Mode...obviously)

    ................................

    Hey,

    I had the same problem with 1080 GPU. My Asus Nvidia 1080ti OC (11 GB) didn't render at all. What I did was that I went to bios and enabled my processor (CPU I7-6700K) GPU which is Intel(R) HD Graphics 530. It was disabled by default. Now when I render a scene, taskmanager shows that Nvidia GPU is 100%, CPU about 20-30% and Intel GPU 0%. I dont have a  glue why it is rendering now. Driver version is 441.12 game.

    My Asus 43" 4k monitor is connected to Nvidia GPU. WhenI rendered a short test clip (image series 120x2500x2000, took over 2,5 hours) Windows task manager told that Dedicated GPU memory is 6.3/11.0 GP, GPU memory is 6.5/26.9 GB and shared GPU memory is 0.1/15.9 GB. I had both Crome and Firefox browsers open and Photoshop 2020 cc. 

    I also downloaded Intel sofware (Intel® Driver & Support Assistant; xxx.intel.com/content/www/us/en/support/intel-driver-support-assistant.html, replace xxx with www) and it updated my Intel GPU drivers. Microsoft apparently doesn't update them because my drivers where over 2 years old. If I remember correctly (not 100% sure) rendering started to work after I updated those drivers. My board is Asus Z170 Pro Gaming. 

    I hope this helps.

     

    Yeah, I'm pretty sure Intel fixed multiple openGL/openCL driver bugs in all their integrated GPU drivers this year as after 2 years of no updates from Intel for my 7 year old Intel HD Graphics 4000 GPU the Intel Update Utility that runs in the background has done 2, maybe 3 updates in 2019.

  • mikmodmikmod Posts: 65
    saneinvividual said:

    concerning Iray and random CPU-Fallbacks:

    I can safely trigger a CPU-fallback within 1 minute by loading a G8 character and then randomly *spam-load-and-unload* various clothes. (viewport being in Iray-Mode...obviously)

    I am 100% sure that I am not over my VRAM budget. It is not an out-memory-fallback. My MSI Afterburner is set up to trigger an alarm if the GTX 1070 memory usage is above 6 GB. The only way to get DAZ to render with Iray on the GPU again is: save, restart DAZ, reload scene, continue.

    HARDWARE: i7 2600K, 32 GB DDR3 1600Mhz, GeForce GTX 1070 8 GB

    SOFTWARE: Windows 10 1903 18362.329, DAZ Studio 4.12.1.16 64 bit, Nvidia driver 441.12 tested 'standard' and 'studio' drivers

    edit: I can confirm the following Nvidia Driver versions all trigger this bug, It took me longer on older versions but that could be random:

    • 430.86-desktop-win10-64bit-international-nsd-whql
    • 431.86-desktop-win10-64bit-international-nsd-whql
    • 441.12-desktop-win10-64bit-international-nsd-whql
    • 441.12-desktop-win10-64bit-international-whql

    nsd-whql = "Studio" driver / whql = "Standard" driver

    log:

    2019-11-16 21:18:06.236 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating lights.2019-11-16 21:18:06.236 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating object flags.2019-11-16 21:18:06.236 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating caustic portals.2019-11-16 21:18:06.236 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating decals.2019-11-16 21:18:06.236 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Allocating 1-layer frame buffer2019-11-16 21:18:06.251 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Using interactive scheduling, caustic sampler disabled2019-11-16 21:18:06.251 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering with 1 device(s):2019-11-16 21:18:06.251 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : CUDA device 0 (GeForce GTX 1070)2019-11-16 21:18:06.251 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering...2019-11-16 21:18:06.251 Iray [VERBOSE] - IRAY:RENDER ::   1.9   IRAY   rend progr: CUDA device 0 (GeForce GTX 1070): Processing scene...2019-11-16 21:18:06.283 Iray [INFO] - IRAY:RENDER ::   1.2   IRAY   rend info : Initializing OptiX Prime for CUDA device 02019-11-16 21:18:06.283 Iray [VERBOSE] - IRAY:RENDER ::   1.2   IRAY   rend stat : Geometry memory consumption: 81.816 MiB (device 0), 0.000 B (host)2019-11-16 21:18:06.392 Iray [VERBOSE] - IRAY:RENDER ::   1.2   IRAY   rend stat : Texture memory consumption: 2.683 GiB for 153 bitmaps (device 0)2019-11-16 21:18:06.392 Iray [INFO] - IRAY:RENDER ::   1.2   IRAY   rend info : Importing lights for motion time 02019-11-16 21:18:06.392 Iray [INFO] - IRAY:RENDER ::   1.2   IRAY   rend info : Initializing light hierarchy.2019-11-16 21:18:06.392 Iray [INFO] - IRAY:RENDER ::   1.2   IRAY   rend info : Light hierarchy initialization took 0.000s2019-11-16 21:18:06.392 Iray [VERBOSE] - IRAY:RENDER ::   1.2   IRAY   rend stat : Lights memory consumption: 196.000 B (device 0)2019-11-16 21:18:06.392 Iray [VERBOSE] - IRAY:RENDER ::   1.2   IRAY   rend stat : Material measurement memory consumption: 0.000 B (GPU)2019-11-16 21:18:06.392 Iray [VERBOSE] - IRAY:RENDER ::   1.2   IRAY   rend stat : PTX code (329.709 KiB) for SM 6.1 generated in 0.001s2019-11-16 21:18:06.392 Iray [VERBOSE] - IRAY:RENDER ::   1.2   IRAY   rend stat : Materials memory consumption: 520.566 KiB (GPU)2019-11-16 21:18:06.439 Iray [INFO] - IRAY:RENDER ::   1.2   IRAY   rend info : JIT-linking wavefront kernel in 0.042s2019-11-16 21:18:06.455 Iray [INFO] - IRAY:RENDER ::   1.2   IRAY   rend info : JIT-linking mega kernel in 0.020s2019-11-16 21:18:06.455 Iray [INFO] - IRAY:RENDER ::   1.9   IRAY   rend info : CUDA device 0 (GeForce GTX 1070): Scene processed in 0.205s2019-11-16 21:18:06.455 Iray [INFO] - IRAY:RENDER ::   1.2   IRAY   rend info : CUDA device 0 (GeForce GTX 1070): Allocated 25.050 MiB for frame buffer2019-11-16 21:18:06.455 Iray [INFO] - IRAY:RENDER ::   1.9   IRAY   rend info : CUDA device 0 (GeForce GTX 1070): Allocated 1.107 GiB of work space (1343k active samples in 0.000s)2019-11-16 21:18:06.455 Iray [INFO] - IRAY:RENDER ::   1.9   IRAY   rend info : CUDA device 0 (GeForce GTX 1070): Used for display, optimizing for interactive usage (performance could be sacrificed)<span data-darkreader-inline-color="" style="--darkreader-inline-color:#ff3333; color:rgb(255, 0, 0)">2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.2   IRAY   rend error: CUDA device 0 (GeForce GTX 1070): an illegal memory access was encountered (while launching CUDA renderer)</span>2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.2   IRAY   rend error: CUDA device 0 (GeForce GTX 1070): Failed to launch renderer2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.9   IRAY   rend error: CUDA device 0 (GeForce GTX 1070): Device failed while rendering2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [WARNING] - IRAY:RENDER ::   1.9   IRAY   rend warn : All available GPUs failed.2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [WARNING] - IRAY:RENDER ::   1.9   IRAY   rend warn : No devices activated. Enabling CPU fallback.2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [WARNING] - IRAY:RENDER ::   1.9   IRAY   rend warn : Re-rendering iteration because of device failure2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.9   IRAY   rend error: All workers failed: aborting render2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.9   IRAY   rend error: CUDA device 0 (GeForce GTX 1070): an illegal memory access was encountered (while de-allocating memory)2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.9   IRAY   rend error: CUDA device 0 (GeForce GTX 1070): an illegal memory access was encountered (while de-allocating memory)2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.9   IRAY   rend error: CUDA device 0 (GeForce GTX 1070): an illegal memory access was encountered (while de-allocating memory)2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.9   IRAY   rend error: CUDA device 0 (GeForce GTX 1070): an illegal memory access was encountered (while de-allocating memory)2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.9   IRAY   rend error: CUDA device 0 (GeForce GTX 1070): an illegal memory access was encountered (while de-allocating memory)2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.9   IRAY   rend error: CUDA device 0 (GeForce GTX 1070): an illegal memory access was encountered (while de-allocating memory)2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.9   IRAY   rend error: CUDA device 0 (GeForce GTX 1070): an illegal memory access was encountered (while de-allocating memory)2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.9   IRAY   rend error: CUDA device 0 (GeForce GTX 1070): an illegal memory access was encountered (while de-allocating memory)2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.9   IRAY   rend error: CUDA device 0 (GeForce GTX 1070): an illegal memory access was encountered (while de-allocating memory)2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.9   IRAY   rend error: CUDA device 0 (GeForce GTX 1070): an illegal memory access was encountered (while de-allocating memory)2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: CUDA device 0 (GeForce GTX 1070): an illegal memory access was encountered (while de-allocating memory)2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: CUDA device 0 (GeForce GTX 1070): an illegal memory access was encountered (while de-allocating memory)2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: CUDA device 0 (GeForce GTX 1070): an illegal memory access was encountered (while de-allocating memory)2019-11-16 21:18:06.486 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: CUDA device 0 (GeForce GTX 1070): an illegal memory access was encountered (while de-allocating memory)2019-11-16 21:18:06.486 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : CPU: using 8 cores for rendering2019-11-16 21:18:06.486 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering with 1 device(s):2019-11-16 21:18:06.486 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : CPU2019-11-16 21:18:06.486 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering...2019-11-16 21:18:06.486 Iray [INFO] - IRAY:RENDER ::   1.2   IRAY   rend info : Using Embree 2.8.02019-11-16 21:18:06.486 Iray [INFO] - IRAY:RENDER ::   1.2   IRAY   rend info : Initializing Embree2019-11-16 21:18:06.486 Iray [VERBOSE] - IRAY:RENDER ::   1.9   IRAY   rend progr: CPU: Processing scene...2019-11-16 21:18:07.376 Iray [VERBOSE] - IRAY:RENDER ::   1.2   IRAY   rend stat : Native CPU code generated in 0.506s2019-11-16 21:18:07.376 Iray [INFO] - IRAY:RENDER ::   1.9   IRAY   rend info : CPU: Scene processed in 0.887s2019-11-16 21:18:07.392 Iray [INFO] - IRAY:RENDER ::   1.2   IRAY   rend info : CPU: Allocated 25.050 MiB for frame buffer2019-11-16 21:18:08.533 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [WARNING] - POST:RENDER ::   1.0   POST   rend warn : renderer iray has no more devices available. Postprocessing falling back to CPU.2019-11-16 21:18:08.533 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [WARNING] - POST:RENDER ::   1.0   POST   rend warn : Postprocessing is running on the CPU, but Denoiser is requested. Denoising is not available on CPU.2019-11-16 21:18:08.548 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00001 iterations after 2.272s.2019-11-16 21:18:08.548 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering...2019-11-16 21:18:09.751 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00002 iterations after 3.464s.

    I can confirm that on RTX 2080, Windows 7 x64 - all it takes is to change figure texture set once or twice while on iray preview and there is this error shown above. It makes at least this beta almost unusable.

  • stephenandersonstephenanderson Posts: 5

    OK. I just redownloaded the latest (4.12) onto a new machine. It may well be as fantastic as many seem to think, but, so far, I'm only frustrated that I can no longer centre my camera's pivot point on an object with Cntrl + Shift + A. Anyone PLEASE!?

  • L'AdairL'Adair Posts: 9,479
    edited November 2019
    stephenanderson said:

    OK. I just redownloaded the latest (4.12) onto a new machine. It may well be as fantastic as many seem to think, but, so far, I'm only frustrated that I can no longer centre my camera's pivot point on an object with Cntrl + Shift + A. Anyone PLEASE!?

    I don't do animation, so I've been holding off on going to the latest beta, so I can't test to see if the same happens on my computer.

    Question: Does anything happen when you use Ctrl+Shift+A?

    I suspect the answer is no, and if so, you can probably add that back in yourself:

    1. Open the Customize Dialog. (F3, or from the main menu, Window > Workspace > Customize)
    2. In the left column, scroll down to View Control and expand.
    3. Scroll down to Aim at Selection.
      • If you see Ctrl+Shift+A in the shortcut column, click on the Accept button and see if it now works.
      • If the Shortcut column is empty, right-click on the line.
        • In the popup menu, select Default Keyboard Shortcut.
          • Does Ctrl+Shift+A now show in the shortcut column? If so, click on Accept and see if it now works.
          • If Ctrl+Shift+A does not show in the shortcut column, select Change Keyboard Shortcut.
            • Now press Ctrl, Shift and A keys to set the shortcut. click on Accept and see if it now works.
              • If you get an error message stating the shortcut is being used by another action, you have the option to clear other uses and assign the it to this action. Change or not at your discretion. (It could come back to bite you, if Daz has changed this to something else.)
    4. If none of these result in the shortcut working again, file a bug report via the Contact Us page. (Make sure you're logged in here first.)
    Post edited by L'Adair on
  • RayDAntRayDAnt Posts: 1,135
    edited November 2019
    sylvie1998 said:

    @saneindividual:

    You are lucky, I just did a clean install of 441.28 STUDIO drivers (which are supposed to be more stable for professional 3D applications) and I get CPU fallback as soon as I switch to Iray viewport ON AN EMPTY SCENE:

    2019-11-23 16:49:31.075 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering...2019-11-23 16:49:31.076 Iray [INFO] - IRAY:RENDER ::   1.7   IRAY   rend info : Using OptiX version 6.1.22019-11-23 16:49:31.080 Iray [INFO] - IRAY:RENDER ::   1.7   IRAY   rend info : Initializing OptiX for CUDA device 02019-11-23 16:49:31.143 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.7   IRAY   rend error: "buildInputs[0].instanceArray", "numInstances" is non-zero, but "instances" is null2019-11-23 16:49:31.143 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.7   IRAY   rend error: optixAccelBuild( context,nullptr, &amp;opt,&amp;inst_input,1, get_address(m_d_scratch),tlas_size.tempSizeInBytes, get_address(m_tlas.data),tlas_size.outputSizeInBytes, &amp;m_tlas.traversable, &amp;bbox_desc,1) failed: Invalid value2019-11-23 16:49:31.144 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.15  IRAY   rend error: CUDA device 0 (GeForce RTX 2080 Ti): Scene setup failed2019-11-23 16:49:31.144 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.15  IRAY   rend error: CUDA device 0 (GeForce RTX 2080 Ti): Device failed while rendering2019-11-23 16:49:31.144 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [WARNING] - IRAY:RENDER ::   1.15  IRAY   rend warn : All available GPUs failed.2019-11-23 16:49:31.144 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [WARNING] - IRAY:RENDER ::   1.15  IRAY   rend warn : No devices activated. Enabling CPU fallback.2019-11-23 16:49:31.144 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [WARNING] - IRAY:RENDER ::   1.15  IRAY   rend warn : Re-rendering iteration because of device failure2019-11-23 16:49:31.144 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(304): Iray [ERROR] - IRAY:RENDER ::   1.15  IRAY   rend error: All workers failed: aborting render

    This is getting ridiculous.

    Did you try playing around with your instancing preferences under render settings? That error appears to be a case of Daz Studio (?) telling Iray to expect objects for instancing to be sent to it but then erroneously not sending any. I'd definitely recommend officially submitting this as a bug.

    Post edited by RayDAnt on
  • PadonePadone Posts: 3,688
    edited November 2019

    Just got 441.28 that also works better with blender 2.81 and everything seems to work fine here. Even tried animation and no memory leaks were found. My system worked fine with 431.86 too though. Specs in the signature.

    Post edited by Padone on
  • Saxa -- SDSaxa -- SD Posts: 872
    sylvie1998 said:
    I have finally found a combination of DAZ own products that reliably triggers this bug for me -- simply starting DAZ Studio and loading Babina 8 character (https://www.daz3d.com/babina-8) and panties and bra from the Lingerie Robe Set (https://www.daz3d.com/lingerie-robe-set-for-genesis-8-female-s) while Iray preview is enabled causes immediate CPU fallback. This does not happen in 4.12.0.86.

     

    Tried your Babina-Lingerie Robe test.
    Using 441.12 with RTX2080Ti on Win7Pro64.

    Did get drop to CPU too.
    My steps:
    (1) Open DS 4.12.1.16
    (2) Perspective view, toggle iray preview on (no panning/zooming needed)
    (3) Load Babina 8 HD
    (4) Load wearable set Lingerie (loads all 3 items)
    (5) delete the set of 3 items, and reload wearable set again.
    (6) Do this loading of wearable lingerie set a total of 4 times
    (7) On the 4th load of the lingerie set it drops to CPU

    Repeated this test 4 times.  Exact same result.
    Will add this to my support ticket now.
    Good find Sylvie.

     

  • marblemarble Posts: 7,500
    edited November 2019
    sylvie1998 said:
     

    1. There seems to be a driver bug in R440 branch (441.12, 441.28) which causes immediate CPU fallback on switching viewport to Iray preview for RTX card users and it affects both DAZ Studio versions (General Release and Public Beta). This does not happen with older driver versions (430.86, 431.86).

    I reported the driver bug to NVIDIA OptiX and Iray team, hopefully DAZ 3D can get around to fixing the second bug.

    TL;DR -- if you are using RTX card stay on NVIDIA 43x.xx drivers branch, and don't use public beta until this is fixed.

    I have a GTX 1070 and the drop to CPU when using the IRay viewport is a solid fault for me. I'm on 441.12 drivers. Also common is a drop to CPU when I change shaders (IRay shaders on skins or fabrics, etc.).

    Post edited by marble on
  • PadonePadone Posts: 3,688

    @marble One difference may be my 1060 is dedicated to rendering, I use the vega for windows and the viewport. So iray doesn't have to share resources with windows. I also use iray and blender together though for small renderings when I have to compare materials, and that works fine.

  • marblemarble Posts: 7,500
    Padone said:

    @marble One difference may be my 1060 is dedicated to rendering, I use the vega for windows and the viewport. So iray doesn't have to share resources with windows. I also use iray and blender together though for small renderings when I have to compare materials, and that works fine.

    I have a 970 which was used for the monitor and general Windows stuff until a few days ago. I saw most of the CPU fall-back problems while the 970 was installed. I removed it just in case it was perhaps the source of those problems. But it hasn't made a significant difference. 
     

Sign In or Register to comment.