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

2456730

Comments

  • bobrodobrobobrodobro said:

    Why mty librarry looks like this

    Something went wrong with the instalaltion - how did you install? Can you open the products if you double-click them? Can you find them in the Content Library pane, under Daz Studio Formats ior Poser Formats depending on the file type?

  • Okay, something happened after this latest update, my Iray is not working at all anymore... I can open simple character and rendering works but if I add some hair for example, Iray is not working and rendering isn't working either... My GPU is NVIDIA GeForce RTX 3060 Ti with latest driver (522.30). Any ideas how I should start solving this issue?..

  • Please bring back the MAKE PANE or PANE GROUP UNDOCKABLE.

    It's a real trouble to use 2 screen with different resolution, the second screen is very hard to fit correctly. It was working so much better before you remove this option.

    Thanks in advance

  • jz3dxjz3dx Posts: 0

    My Iray has been having a lot of issues with Hair assets more specifically OOT hairs. It will crash everytime I turn Iray on.

    I always get this error

    DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio4 Public Build\libs\iray\libiray.dll"

  • jz3dx said:

    My Iray has been having a lot of issues with Hair assets more specifically OOT hairs. It will crash everytime I turn Iray on.

    I always get this error

    DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio4 Public Build\libs\iray\libiray.dll"

    This issue is being investigated.

  • Tooning32 said:

    Please bring back the MAKE PANE or PANE GROUP UNDOCKABLE.

    It's a real trouble to use 2 screen with different resolution, the second screen is very hard to fit correctly. It was working so much better before you remove this option.

    Thanks in advance

    My understanding is that the feature was removed as it was in gernal very bug prone, it was added in very early builds when the docking was over-zealous but was then left in when that was resolved.

  • Richard HaseltineRichard Haseltine Posts: 98,323
    edited November 2022

    ramisundqvist said:

    Okay, something happened after this latest update, my Iray is not working at all anymore... I can open simple character and rendering works but if I add some hair for example, Iray is not working and rendering isn't working either... My GPU is NVIDIA GeForce RTX 3060 Ti with latest driver (522.30). Any ideas how I should start solving this issue?..

    You may want to roll back to the 517 drivers anyway, as the newer drivers (so far) have an OpenCL bug that breaks dForce. I don't know if it will help with your issue.

    Post edited by Richard Haseltine on
  • ImagoImago Posts: 4,980
    edited November 2022

    Richard Haseltine said:

    Tooning32 said:

    Please bring back the MAKE PANE or PANE GROUP UNDOCKABLE.

    It's a real trouble to use 2 screen with different resolution, the second screen is very hard to fit correctly. It was working so much better before you remove this option.

    Thanks in advance

    My understanding is that the feature was removed as it was in gernal very bug prone, it was added in very early builds when the docking was over-zealous but was then left in when that was resolved.

    I use two monitors too and that option is basilar for my workflow... I really hope this is just temporary and it will return soon.

    Post edited by Imago on
  • Richard Haseltine said:

    ramisundqvist said:

    Okay, something happened after this latest update, my Iray is not working at all anymore... I can open simple character and rendering works but if I add some hair for example, Iray is not working and rendering isn't working either... My GPU is NVIDIA GeForce RTX 3060 Ti with latest driver (522.30). Any ideas how I should start solving this issue?..

    You may want to roll back to the 517 drivers anyway, as the newer drivers (so far) have an OpenCL bug that breaks dForce. I don't know if it will help with your issue.

    I did roll back to the 517 but it didn't make any difference... Here is piece of log:

    2022-11-08 20:39:08.534 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Using iray core convergence estimate.
    2022-11-08 20:39:08.535 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: No device specified or usable
    2022-11-08 20:39:08.535 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering...
    2022-11-08 20:39:08.535 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: No worker to render with: aborting render
    2022-11-08 20:39:08.538 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Using iray core convergence estimate.
    2022-11-08 20:39:08.538 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Allocating 1-layer frame buffer
    2022-11-08 20:39:08.541 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Using interactive scheduling, caustic sampler disabled
    2022-11-08 20:39:08.541 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: No device specified or usable
    2022-11-08 20:39:08.541 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering with 0 device(s):
    2022-11-08 20:39:08.541 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering...
    2022-11-08 20:39:08.542 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: No worker to render with: aborting render
    2022-11-08 20:39:08.542 [ERROR] Iray :: Internal rendering error.

     

  • JB007 said:

    Is the 4090 fully supported in this beta with a new Iray / Cuda?

    Iray works, dForce does not.

    3000 series users can rollback to driver 517.xx, but 4090 users cannot because card is not supported in driver versions prior to 522.25.

    From NVIDIA 526.47 Game Ready driver Release Notes, listed under Known Issues:

    [Daz Studio] Application crashes after updating to latest driver when trying to run simulation [3838022]

    When that issue moves to the Fixed Issues section (should happen in the next driver release hopefully), dForce will be working again for all cards.

    Also, Iray performance on 4090 should be further improved after CUDA 12 (and subsequent OptiX) release.

  • f7eerf7eer Posts: 122

    ramisundqvist said:

    Richard Haseltine said:

    ramisundqvist said:

    Okay, something happened after this latest update, my Iray is not working at all anymore... I can open simple character and rendering works but if I add some hair for example, Iray is not working and rendering isn't working either... My GPU is NVIDIA GeForce RTX 3060 Ti with latest driver (522.30). Any ideas how I should start solving this issue?..

    You may want to roll back to the 517 drivers anyway, as the newer drivers (so far) have an OpenCL bug that breaks dForce. I don't know if it will help with your issue.

    I did roll back to the 517 but it didn't make any difference... Here is piece of log:

    2022-11-08 20:39:08.534 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Using iray core convergence estimate.
    2022-11-08 20:39:08.535 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: No device specified or usable
    2022-11-08 20:39:08.535 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering...
    2022-11-08 20:39:08.535 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: No worker to render with: aborting render
    2022-11-08 20:39:08.538 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Using iray core convergence estimate.
    2022-11-08 20:39:08.538 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Allocating 1-layer frame buffer
    2022-11-08 20:39:08.541 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Using interactive scheduling, caustic sampler disabled
    2022-11-08 20:39:08.541 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: No device specified or usable
    2022-11-08 20:39:08.541 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering with 0 device(s):
    2022-11-08 20:39:08.541 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering...
    2022-11-08 20:39:08.542 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: No worker to render with: aborting render
    2022-11-08 20:39:08.542 [ERROR] Iray :: Internal rendering error.

    I get something similar, but here is where the error starts:

    2022-11-08 07:19:50.362 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.12  IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 2080 Super): Kernel [8] (ShadowEvalSr      ) failed after 0.009s
    2022-11-08 07:19:50.362 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.12  IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 2080 Super): an illegal memory access was encountered (while launching CUDA renderer in <internal>:951)
    2022-11-08 07:19:50.363 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.12  IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 2080 Super): Failed to launch renderer
    2022-11-08 07:19:50.363 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 2080 Super): Device failed while rendering
    2022-11-08 07:19:50.363 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [WARNING] - IRAY:RENDER ::   1.5   IRAY   rend warn : CUDA device 0 (NVIDIA GeForce RTX 2080 Super) is no longer available for rendering.
    2022-11-08 07:19:50.364 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [WARNING] - IRAY:RENDER ::   1.5   IRAY   rend warn : All available GPUs failed.
    2022-11-08 07:19:50.364 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: Fallback to CPU not allowed.
    2022-11-08 07:19:50.364 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 2080 Super): an illegal memory access was encountered (while initializing memory buffer)
    2022-11-08 07:19:50.364 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: All workers failed: aborting render
    2022-11-08 07:19:50.364 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 2080 Super): [Guidance sync] Failed slave device (remaining 0, done 0).
    2022-11-08 07:19:50.364 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 2080 Super): an illegal memory access was encountered (while de-allocating memory)
    2022-11-08 07:19:50.364 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 2080 Super): an illegal memory access was encountered (while de-allocating memory)
    2022-11-08 07:19:50.364 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 2080 Super): an illegal memory access was encountered (while de-allocating memory)
    2022-11-08 07:19:50.365 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 2080 Super): an illegal memory access was encountered (while de-allocating memory)
    2022-11-08 07:19:50.365 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 2080 Super): an illegal memory access was encountered (while de-allocating memory)
    2022-11-08 07:19:50.365 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 2080 Super): an illegal memory access was encountered (while de-allocating memory)
    2022-11-08 07:19:50.365 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 2080 Super): an illegal memory access was encountered (while de-allocating memory)
    2022-11-08 07:19:50.366 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 2080 Super): an illegal memory access was encountered (while de-allocating memory)
    2022-11-08 07:19:50.366 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 2080 Super): an illegal memory access was encountered (while de-allocating memory)
    2022-11-08 07:19:50.366 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 2080 Super): an illegal memory access was encountered (while de-allocating memory)
    2022-11-08 07:19:50.366 [ERROR] Iray :: Internal rendering error.

    It looks like the first few errors are descriptive of what's happening, and the last few errors represent ungraceful handling of the first few errors.

    DAZ Studio 4.21.1.13 (Current beta release)
    GPU: NVIDIA GeForce RTX 2080 Super
    Driver: NVIDIA display driver version: 517.40

    I reverted to DAZ Studio 4.21.0.5 (current general release), and renders work great.

  • I've seen this beta  Public buold 4.21 +beta+ is getting a lot of troubles with OOT hairs, I can confirm Emilia and Lainey hairs won't work either on my machine. Just updated this morning and when I loaded later two Gen3 females with those hairs the render will crash. 

    Render goes smooth on the 4.21 version

     


    2022-11-08 20:33:58.294 Iray (Scene Access) : Retrieving device lens data
    2022-11-08 20:33:58.387 Iray [INFO] - IRAY:RENDER ::   1.3   IRAY   rend info : JIT-linking wavefront kernel in 0.080 s
    2022-11-08 20:33:58.387 Iray [INFO] - IRAY:RENDER ::   1.3   IRAY   rend info : CUDA device 0 (NVIDIA GeForce RTX 3090): Initializing volume acceleration structures took 0.000 s
    2022-11-08 20:33:58.387 Iray [INFO] - IRAY:RENDER ::   1.2   IRAY   rend info : CUDA device 0 (NVIDIA GeForce RTX 3090): Scene processed in 5.369s
    2022-11-08 20:33:58.404 Iray [INFO] - IRAY:RENDER ::   1.2   IRAY   rend info : CUDA device 0 (NVIDIA GeForce RTX 3090): Allocated 747.737 MiB for frame buffer
    2022-11-08 20:33:58.408 Iray [INFO] - IRAY:RENDER ::   1.2   IRAY   rend info : CUDA device 0 (NVIDIA GeForce RTX 3090): Allocated 1.969 GiB of work space (2048k active samples in 0.004s)
    2022-11-08 20:33:58.408 Iray [INFO] - IRAY:RENDER ::   1.2   IRAY   rend info : CUDA device 0 (NVIDIA GeForce RTX 3090): Optimizing for cooperative usage (performance could be sacrificed)
    2022-11-08 20:33:58.481 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.3   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): Kernel [8] (ShadowEvalSr      ) failed after 0.018s
    2022-11-08 20:33:58.481 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.3   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while launching CUDA renderer in <internal>:951)
    2022-11-08 20:33:58.481 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.3   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): Failed to launch renderer
    2022-11-08 20:33:58.482 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.2   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): Device failed while rendering
    2022-11-08 20:33:58.482 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [WARNING] - IRAY:RENDER ::   1.2   IRAY   rend warn : CUDA device 0 (NVIDIA GeForce RTX 3090) is no longer available for rendering.
    2022-11-08 20:33:58.482 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [WARNING] - IRAY:RENDER ::   1.2   IRAY   rend warn : All available GPUs failed.
    2022-11-08 20:33:58.483 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.2   IRAY   rend error: Fallback to CPU not allowed.
    2022-11-08 20:33:58.483 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.2   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while initializing memory buffer)
    2022-11-08 20:33:58.483 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.2   IRAY   rend error: All workers failed: aborting render
    2022-11-08 20:33:58.483 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.2   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): [Guidance sync] Failed slave device (remaining 0, done 0).
    2022-11-08 20:33:58.483 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.2   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
    2022-11-08 20:33:58.484 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.2   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
    2022-11-08 20:33:58.484 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.2   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
    2022-11-08 20:33:58.484 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.2   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
    2022-11-08 20:33:58.484 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.2   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
    2022-11-08 20:33:58.484 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.2   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
    2022-11-08 20:33:58.484 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.2   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
    2022-11-08 20:33:58.484 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.2   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
    2022-11-08 20:33:58.484 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.2   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
    2022-11-08 20:33:58.485 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.2   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
    2022-11-08 20:33:58.485 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.2   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
    2022-11-08 20:33:58.485 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.2   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
    2022-11-08 20:33:58.485 [ERROR] Iray :: Internal rendering error.
    2022-11-08 20:33:59.367 [INFO] :: Saved image: C:\Users\RenderMachine\AppData\Roaming\DAZ 3D\Studio4 Public Build\temp\render\r.png
    2022-11-08 20:33:59.531 [INFO] :: Finished Rendering
    2022-11-08 20:33:59.564 [INFO] :: Total Rendering Time: 12.74 seconds

  • rupaolrupaol Posts: 18

    Since the last update of the BETA version I can no longer render regardless of scene size. Before the update the renders were quicker on the BETA than on my 4.15 installation but now it only leaves a black screen. I tried to update the NVIDIA drivers both to game ready and to studio version without luck. 

    Is there any way to roll back to the previous version of the BETA relaese or do I have to wait for either a new BETA or an update GPU driver? I am using a 3060 card.

  • rupaol said:

    Since the last update of the BETA version I can no longer render regardless of scene size. Before the update the renders were quicker on the BETA than on my 4.15 installation but now it only leaves a black screen. I tried to update the NVIDIA drivers both to game ready and to studio version without luck. 

    Is there any way to roll back to the previous version of the BETA relaese or do I have to wait for either a new BETA or an update GPU driver? I am using a 3060 card.

    I use the DAZ install manager, you can get there the 4.21 version (not the beta) it works great for me. 

  • f7eerf7eer Posts: 122

    rupaol said:

    Since the last update of the BETA version I can no longer render regardless of scene size. Before the update the renders were quicker on the BETA than on my 4.15 installation but now it only leaves a black screen. I tried to update the NVIDIA drivers both to game ready and to studio version without luck. 

    Is there any way to roll back to the previous version of the BETA relaese or do I have to wait for either a new BETA or an update GPU driver? I am using a 3060 card.

    Just use what is the current general release. It was the beta before the last (bad) update to the beta.

  • rupaol said:

    Since the last update of the BETA version I can no longer render regardless of scene size. Before the update the renders were quicker on the BETA than on my 4.15 installation but now it only leaves a black screen. I tried to update the NVIDIA drivers both to game ready and to studio version without luck. 

    Exactly which driver versions were those?

    Is there any way to roll back to the previous version of the BETA relaese or do I have to wait for either a new BETA or an update GPU driver? I am using a 3060 card.

  • rupaolrupaol Posts: 18

    It is 522.3 Studio drivers.

    The reason why I do not want to upgrade my "normal" installation yet is because I am in the middle of a project and I can not risk any issues with any functionality. Hence why I run the 4.21 in parallell even though the newer version seems to render quicker. When it works...

  • rupaol said:

    It is 522.3 Studio drivers.

    Those certainly cuase issues in dForce and there have been reports of render issues. If you can, try the 517 drivers.

    The reason why I do not want to upgrade my "normal" installation yet is because I am in the middle of a project and I can not risk any issues with any functionality. Hence why I run the 4.21 in parallell even though the newer version seems to render quicker. When it works...

  • rupaolrupaol Posts: 18

    I'm more worried abot rendering than dForce but I will give it a try. Thanks.

  • rupaolrupaol Posts: 18

    The same issue remais after installing 517 drivers unfortunately. 

    Back to the questions, is there any way to roll back to the previous BETA or is the installation files for that version avaliable somewhere?

  • barbultbarbult Posts: 23,530

    rupaol said:

    The same issue remais after installing 517 drivers unfortunately. 

    Back to the questions, is there any way to roll back to the previous BETA or is the installation files for that version avaliable somewhere?

    You can roll back if you saved the previous DIM installer zip files for the application and associated plugins. Daz does not make prior versions available.You can submit a help request to Daz and ask for the files, but Daz might not comply. Nobody other than Daz can make those older versions available legally.

  • JoltrastJoltrast Posts: 199
    edited November 2022

    Unfortunately I've recently had to use Daz Central to install as DIM would crash on me, so no install files and a forced upgrade. 4.21 is almost unusable for me. It won't load scenes and often leaves traces of itself in task manager when it quits. Honestly, I can live without G9 until this version works. It did work fine for about a week, now it's almost useless, ironically while I'm in the middle of a project.

    Post edited by Joltrast on
  • IceCrMnIceCrMn Posts: 2,122
    edited November 2022

    NVidia says they have fixed that broken driver and released a new version this morning. Game ready version only though.

    I'm still using Studio driver 517.40 with both the public beta and the general release with one of the OOT hair shaders being the only problem for me so far.

    I'm running an RTX 3060 12GB.

    I'll leave the GPU driver beta testing to others.

    Once I see reports of the driver working I'll have a look at it and decide if I need it.

     

    edit:
    If you are using one of the new RTX 40xx series cards I understand you will need driver version 522.25 at minmum to support your card.
    In that case, you are unlukly enough to need to wait for nVidia to release a working driver. Which maybe the new one released today.

    Someone with one of those careds will need to test it to see if it works.
    I still use the RTX 30xx series card, so I can use the older drivers.

    Post edited by IceCrMn on
  • IceCrMnIceCrMn Posts: 2,122

    rupaol said:

    The same issue remais after installing 517 drivers unfortunately. 

    Back to the questions, is there any way to roll back to the previous BETA or is the installation files for that version avaliable somewhere?

    The current General Release (4.21.0.5) is the last beta (4.21.0.5).

    There's literally no difference between them except that one has beta in the name and one doesn't.

    Once a Public Beta has been tested to the point that no show stopper problems remain , it becomes the next General Release.

  • VividImaginatorVividImaginator Posts: 38
    edited November 2022

    Nope.

    The last NVIDIA game ready driver 526.86 (released on 11/10/2022) does not fix the Dforce issues.

    I get the following errors:

    Daz Beta 4.21.1.13:

    2022-11-10 11:57:43.558 [WARNING] :: ..\..\..\src\dzopenclkernelfactory.cpp(32): Open CL notify: Unknown error executing clFlush on NVIDIA GeForce RTX 3090 (Device 0).

    ...
    2022-11-10 11:57:43.559 [WARNING] :: ..\..\..\src\dzdynamicsengine.cpp(3293): ERROR: clFinish (-36)
    2022-11-10 11:57:43.592 [WARNING] :: ..\..\..\src\dzopenclkernelfactory.cpp(32): Open CL notify: Unknown error executing clFlush on NVIDIA GeForce RTX 3090 (Device 0).

    Daz Beta 4.21.05:

    2022-11-10 11:41:54.952 [WARNING] :: ..\..\..\src\dzopenclkernelfactory.cpp(32): Open CL notify: Unknown error executing clFlush on NVIDIA GeForce RTX 3090 (Device 0).

    ...
    2022-11-10 11:41:54.953 [WARNING] :: ..\..\..\src\dzdynamicsengine.cpp(3293): ERROR: clFinish (-36)
    2022-11-10 11:41:54.992 [WARNING] :: ..\..\..\src\dzopenclkernelfactory.cpp(32): Open CL notify: Unknown error executing clFlush on NVIDIA GeForce RTX 3090 (Device 0).

    Yeah, the same Dforce error using the last two Daz Studio Betas.

    Also, Daz Beta 4.21.1.13 and NVIDIA Game Ready Driver 526.86 can't render most OOT hairstyles; that seems to be a Daz Beta issue (not NVIDIA.)

    I'm not sure if it is the same Dforce error we get with the previous Nvidia drivers or if it is a new one... I guess I better check...

    Yeah, it is the same error:

    2022-10-30 19:31:35.394 [WARNING] :: ..\..\..\src\dzopenclkernelfactory.cpp(32): Open CL notify: Unknown error executing clFlush on NVIDIA GeForce GTX 1070 Ti (Device 0).
    2022-10-30 19:31:35.395 [WARNING] :: ..\..\..\src\dzdynamicsengine.cpp(3293): ERROR: clFinish (-36)
    2022-10-30 19:31:35.446 [WARNING] :: ..\..\..\src\dzopenclkernelfactory.cpp(32): Open CL notify: Unknown error executing clFlush on NVIDIA GeForce GTX 1070 Ti (Device 0).

    The last NVIDIA Game Ready Driver 526.86 released on November 10 2022 does not fix dforce errors. Stick to NVIDIA Studio Drivers 517.40 and Daz Beta 4.21.0.5!

    Post edited by VividImaginator on
  • rupaolrupaol Posts: 18

    After a lot of trial and error I have finally found out that it is indeed an issue with the OOT hair assets. I did not recognized it first as it seems as it does not help removing the asset from the scene. Daz has to be restarted in order to completely clear the textures I guess. 

    In any event, my problem i s solved as long as I do not use OOT hair assets.

  • beregarberegar Posts: 269
    edited November 2022

    Is there any particular reason why my ground plane grid now dissapears if I'm not moving the viewport? It just shows the grey background?

    Edit: unless the viewport background now is identical in color to the grid... hmm I never remember where to change the background color since it is in some completely obscure place

    Edit2: found it but it wasn't the reason for disappearing grid

    grey.png
    993 x 744 - 5K
    Post edited by beregar on
  • f7eerf7eer Posts: 122

    Richard Haseltine said:

    rupaol said:

    It is 522.3 Studio drivers.

    Those certainly cuase issues in dForce and there have been reports of render issues. If you can, try the 517 drivers.

    The reason why I do not want to upgrade my "normal" installation yet is because I am in the middle of a project and I can not risk any issues with any functionality. Hence why I run the 4.21 in parallell even though the newer version seems to render quicker. When it works...

    There are two separate newish problems:

    1. The dForce problem was introduced in nVidia driver 522.30, is known by nVidia, and a fix has not been released by nVidia yet. The workaround is to roll back to driver 517.48 or earlier.

    2. The render problem with OOT hair was introduced in DAZ Studio 4.21.1.13 (Current beta release), and fails with both nVidia drivers 522.30 and 517.40. The workaround is to roll back to DAZ Studio 4.21.0.5 (current general release).

    When I render a scene which contains OOT hair, I get the following errors:

    2022-11-08 07:19:50.362 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.12  IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 2080 Super): Kernel [8] (ShadowEvalSr      ) failed after 0.009s
    2022-11-08 07:19:50.362 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.12  IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 2080 Super): an illegal memory access was encountered (while launching CUDA renderer in <internal>:951)
    2022-11-08 07:19:50.363 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.12  IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 2080 Super): Failed to launch renderer
    2022-11-08 07:19:50.363 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 2080 Super): Device failed while rendering
    2022-11-08 07:19:50.363 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [WARNING] - IRAY:RENDER ::   1.5   IRAY   rend warn : CUDA device 0 (NVIDIA GeForce RTX 2080 Super) is no longer available for rendering.
    2022-11-08 07:19:50.364 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [WARNING] - IRAY:RENDER ::   1.5   IRAY   rend warn : All available GPUs failed.
    2022-11-08 07:19:50.364 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: Fallback to CPU not allowed.
    2022-11-08 07:19:50.364 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 2080 Super): an illegal memory access was encountered (while initializing memory buffer)
    2022-11-08 07:19:50.364 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: All workers failed: aborting render
    2022-11-08 07:19:50.364 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 2080 Super): [Guidance sync] Failed slave device (remaining 0, done 0).
    2022-11-08 07:19:50.364 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 2080 Super): an illegal memory access was encountered (while de-allocating memory)
    2022-11-08 07:19:50.364 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 2080 Super): an illegal memory access was encountered (while de-allocating memory)
    2022-11-08 07:19:50.364 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 2080 Super): an illegal memory access was encountered (while de-allocating memory)
    2022-11-08 07:19:50.365 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 2080 Super): an illegal memory access was encountered (while de-allocating memory)
    2022-11-08 07:19:50.365 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 2080 Super): an illegal memory access was encountered (while de-allocating memory)
    2022-11-08 07:19:50.365 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 2080 Super): an illegal memory access was encountered (while de-allocating memory)
    2022-11-08 07:19:50.365 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 2080 Super): an illegal memory access was encountered (while de-allocating memory)
    2022-11-08 07:19:50.366 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 2080 Super): an illegal memory access was encountered (while de-allocating memory)
    2022-11-08 07:19:50.366 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 2080 Super): an illegal memory access was encountered (while de-allocating memory)
    2022-11-08 07:19:50.366 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(377): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 2080 Super): an illegal memory access was encountered (while de-allocating memory)
    2022-11-08 07:19:50.366 [ERROR] Iray :: Internal rendering error.

    This problem only occurs with the new beta version Daz Studio, and fails with both new and old nVidia drivers. Seems like a Daz problem, not an nVidia problem.

  • VividImaginator said:

    Nope.

    The last NVIDIA game ready driver 526.86 (released on 11/10/2022) does not fix the Dforce issues.

    Of course it doesn't -- the issue is still listed under Known Issues in release notes. If you read those it would have saved you the trouble you went through to test it.

    All in all, yet another botched product launch by NVIDIA:

    1. Overpriced card (2400 EUR here)
    2. Cheap 12VHPWR power adapters with a built-in fire hazard
    3. Abysmal driver support -- random TDR crashes in Windows and in some games (sometimes unrecoverable requiring hard reset), OpenCL broken in Daz Studio (despite NVIDIA claiming that Studio Driver is certified for Daz Studio among other apps), geoshells flickering again when zooming/panning in Iray Preview, mouse cursor becoming visible over your crosshair in Mass Effect Andromeda, Chromium based browsers rendering some pages with epilepsy inducing flicker and element repositioning. Workaround? Disable hardware assisted GPU scheduling and hope it helps.

    On top of that, fixes for the bugs I reported directly be it drivers, CUDA, NVJPEG, installer, keep getting delayed.

    This is a repeat of the 2080 launch -- we won't have stable drivers and Iray that can fully use 4090 until at least March 2023.

    Don't know about all of you, but this is the last straw, and the last NVIDIA card for me.

  • IceCrMnIceCrMn Posts: 2,122

    Is anyone else seeing high CPU temperatures recently while rendering or using iray preview?

    When I say high , I mean over 90C-100C.

    See this thread for more info.

    https://www.daz3d.com/forums/discussion/603371/iray-viewport-render-causing-cpu-gpu-temps-to-soar-and-crash-daz-studio-after-new-nvidia-drivers

    Disabling CPU use in Advanced Iray settings fixes it, but I'm not able to track down the cause.

    ADM Ryzen 7 3800XT

    Studio driver 517.40

    Windows 10 Info

    Edition    Windows 10 Pro
    Version    21H2
    Installed on    ‎9/‎18/‎2021
    OS build    19044.2251
    Experience    Windows Feature Experience Pack 120.2212.4180.0

    Recent OS updates

    KB5019959

    KB5020687

    ---

    Don't know if this is a Studio, GPU driver, or Windows 10 update issue.

Sign In or Register to comment.