Loading...
> >

IRAY Stops working

KeikuKeiku Posts: 143
edited March 29 in Technical Help (nuts n bolts)

I'm having a new issue where IRAY both preview and render just stop working. It will initially work (some of the time) but then after making a few changes (such as applying makeup) it will stop. The amount of time it takes before I run into a problem isn't consistant. So far it seems limited to one file, but I cannot narrow down if any particular object is at fault. I have one shaped and textured character (8.1) with a dress, earings, necklace, hair, and shoes. That's all.

  • 5950x (no cpu fallback), RTX 3090, 64GB RAM
  • Both System and GPU memory NEVER hit any limits.
  • Running the latest NVIDIA Studio driver (also tried one version behind).
  • Tried running on a different system (laptop with 3080 16GB)
  • Latest version of Daz.
  • No recent Windows updates.
  • No system or program changes since things were last working.

I'm just not sure what the deal is. Here is what the log says (more complete log attached):

2024-03-29 14:25:40.835 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.27  IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): Tail kernel failed after 0.011s
2024-03-29 14:25:40.835 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.27  IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while launching CUDA renderer in <internal>:674)
2024-03-29 14:25:40.835 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.27  IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): Failed to launch renderer
2024-03-29 14:25:40.836 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.4   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): Device failed while rendering
2024-03-29 14:25:40.836 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [WARNING] - IRAY:RENDER ::   1.4   IRAY   rend warn : CUDA device 0 (NVIDIA GeForce RTX 3090) is no longer available for rendering.
2024-03-29 14:25:40.837 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [WARNING] - IRAY:RENDER ::   1.4   IRAY   rend warn : All available GPUs failed.
2024-03-29 14:25:40.837 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.4   IRAY   rend error: Fallback to CPU not allowed.
2024-03-29 14:25:40.837 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [WARNING] - IRAY:RENDER ::   1.4   IRAY   rend warn : Re-rendering iteration because of device failure
2024-03-29 14:25:40.837 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.4   IRAY   rend error: All workers failed: aborting render
2024-03-29 14:25:40.837 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.4   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
2024-03-29 14:25:40.837 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.4   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
2024-03-29 14:25:40.837 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.4   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
2024-03-29 14:25:40.837 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.4   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
2024-03-29 14:25:40.837 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.4   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
2024-03-29 14:25:40.837 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.4   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
2024-03-29 14:25:40.838 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.4   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
2024-03-29 14:25:40.838 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.4   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
2024-03-29 14:25:40.838 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.4   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
2024-03-29 14:25:40.838 [ERROR] Iray :: Internal rendering error.
2024-03-29 14:26:01.960 Iray [INFO] - TRAV:DATABASE ::   1.0   TRAV   db   progr: Updating scene.
2024-03-29 14:26:01.960 Iray [INFO] - TRAV:DATABASE ::   1.0   TRAV   db   progr: Updating scene took 0.000143 s.
2024-03-29 14:26:01.961 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Using no convergence estimate.
2024-03-29 14:26:01.962 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
2024-03-29 14:26:01.962 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
2024-03-29 14:26:01.962 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
2024-03-29 14:26:01.962 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
2024-03-29 14:26:01.963 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
2024-03-29 14:26:01.963 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
2024-03-29 14:26:01.963 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
2024-03-29 14:26:01.963 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
2024-03-29 14:26:01.963 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
2024-03-29 14:26:01.963 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
2024-03-29 14:26:01.963 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: No device specified or usable
2024-03-29 14:26:01.963 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering with 0 device(s):
2024-03-29 14:26:01.963 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering...
2024-03-29 14:26:01.963 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: No worker to render with: aborting render
2024-03-29 14:26:01.963 [ERROR] Iray :: Internal rendering error.
2024-03-29 14:26:05.534 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - OPTX:RENDER ::   1.34  OPTX   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2024-03-29 14:26:05.534 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - OPTX:RENDER ::   1.34  OPTX   rend error: Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2024-03-29 14:26:05.537 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.34  IRAY   rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error
2024-03-29 14:26:05.537 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - OPTX:RENDER ::   1.34  OPTX   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2024-03-29 14:26:05.537 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - OPTX:RENDER ::   1.34  OPTX   rend error: Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2024-03-29 14:26:05.538 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.34  IRAY   rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error
2024-03-29 14:26:05.538 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - OPTX:RENDER ::   1.34  OPTX   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2024-03-29 14:26:05.538 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - OPTX:RENDER ::   1.34  OPTX   rend error: Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2024-03-29 14:26:05.538 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.34  IRAY   rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error
2024-03-29 14:26:05.539 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - OPTX:RENDER ::   1.34  OPTX   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2024-03-29 14:26:05.539 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - OPTX:RENDER ::   1.34  OPTX   rend error: Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2024-03-29 14:26:05.539 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.34  IRAY   rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error
2024-03-29 14:26:05.540 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - OPTX:RENDER ::   1.34  OPTX   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2024-03-29 14:26:05.540 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - OPTX:RENDER ::   1.34  OPTX   rend error: Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2024-03-29 14:26:05.540 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.34  IRAY   rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error
2024-03-29 14:26:05.541 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - OPTX:RENDER ::   1.34  OPTX   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2024-03-29 14:26:05.541 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - OPTX:RENDER ::   1.34  OPTX   rend error: Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2024-03-29 14:26:05.541 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.34  IRAY   rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error
2024-03-29 14:26:05.542 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - OPTX:RENDER ::   1.34  OPTX   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2024-03-29 14:26:05.542 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - OPTX:RENDER ::   1.34  OPTX   rend error: Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2024-03-29 14:26:05.542 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.34  IRAY   rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error
2024-03-29 14:26:05.543 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - OPTX:RENDER ::   1.34  OPTX   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2024-03-29 14:26:05.543 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - OPTX:RENDER ::   1.34  OPTX   rend error: Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2024-03-29 14:26:05.543 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.34  IRAY   rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error
2024-03-29 14:26:05.545 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - OPTX:RENDER ::   1.34  OPTX   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2024-03-29 14:26:05.545 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - OPTX:RENDER ::   1.34  OPTX   rend error: Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2024-03-29 14:26:05.545 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.34  IRAY   rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error
2024-03-29 14:26:05.546 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - OPTX:RENDER ::   1.34  OPTX   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2024-03-29 14:26:05.546 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - OPTX:RENDER ::   1.34  OPTX   rend error: Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2024-03-29 14:26:05.546 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.34  IRAY   rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error
2024-03-29 14:26:05.547 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - OPTX:RENDER ::   1.34  OPTX   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2024-03-29 14:26:05.547 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - OPTX:RENDER ::   1.34  OPTX   rend error: Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2024-03-29 14:26:05.548 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.34  IRAY   rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error
2024-03-29 14:26:05.548 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - OPTX:RENDER ::   1.34  OPTX   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2024-03-29 14:26:05.548 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - OPTX:RENDER ::   1.34  OPTX   rend error: Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2024-03-29 14:26:05.548 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.34  IRAY   rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error
2024-03-29 14:26:05.549 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - OPTX:RENDER ::   1.34  OPTX   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2024-03-29 14:26:05.549 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - OPTX:RENDER ::   1.34  OPTX   rend error: Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2024-03-29 14:26:05.550 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.34  IRAY   rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error



 

txt
txt
log.txt
239K
Post edited by Keiku on
«1

Comments

  • crosswindcrosswind Posts: 6,986

    Warnings of "illegal memory" usually result from file corruption, driver issue, card failure and Daz asset problems (geometry, texture maps... etc.). Since you said the issue only happened to this very scene, you can try an "exclusive method" : save half of the Wearables as Wearable Presets, then delete them. Preview or render.

    1) If fortunatlely the issue is gone, the culprit must be in the "saved Wearable Preset. Then you delete all the rest and load the Wearable Preset back... and repeat the above steps.

    2) If unfortunately the issue persits, repeat the above steps till you find out the culprit.

  • Richard HaseltineRichard Haseltine Posts: 100,948

    Are you deelting content along the way or are you progressinvely adding more and more items? 24GB is a lot of memory but it will run out if there is enough data.

  • KeikuKeiku Posts: 143
    edited March 30

    Richard Haseltine said:

    Are you deelting content along the way or are you progressinvely adding more and more items? 24GB is a lot of memory but it will run out if there is enough data.

    I am deleting items one by one to see what might be causing a problem. I have been monitoring the memory and at no point does it rise above 12 GB.

    My original character file which only had the character and hair seemed fine. But even after deleting everything from my working scene file that had the clothing and accessories, I get intermittent IRAY stops. It seems they mostly occur after adding something into the scene, especially any jewelry. The inconsistancy makes it difficult to troubleshoot.

    I also reinstalled DAZ though, since I tried on two separate machines, I doubt that was an issue.

    Post edited by Keiku on
  • Richard HaseltineRichard Haseltine Posts: 100,948

    If the GPU has been dropped because of memory, and potentially for any other reason, DS usually needs to be restarted before it will be used again.

  • PerttiAPerttiA Posts: 10,024

    Richard Haseltine said:

    If the GPU has been dropped because of memory, and potentially for any other reason, DS usually needs to be restarted before it will be used again.

    And in serious cases the computer may need to be restarted 

  • KeikuKeiku Posts: 143
    edited March 30

    It's definately not memory, unless my hardware monitors are not reporting correctly. I have restarted Daz between tests. Although I have not restarted the PC between every test, but between a few.

    I created a new scene using the seemly working original file and re-added the clothing. Things work working fine until I applied a pose, then IRAY quit again. This time getting "no device" and "no worker" errors in the log. Then I restarted and did the same thing, this time IRAY kept working. Then I applied a shader, still working. Then a pose and IRAY broke again. GPU Memory reached as high as 8,526 MB, system memory reached 18,272 MB.

     

    Post edited by Keiku on
  • PerttiAPerttiA Posts: 10,024

    Three lines stand out from your log;
    E:/3D Artwork/!Daz Library/data/DAZ 3D/Genesis 8/Female/Morphs/guhzcoituz/New Black Cat/BC Head.dsf (1,1): Syntax error - expected '{' or '['
    \src\sdksource\fileinput\dzassetdaz.cpp(7934): Circular ERC!: P3D Amused with ERC ERC [DeltaAdd] > Katie : P3D Amused
    \src\sdksource\fileinput\dzassetdaz.cpp(7947): Unsupported formula: /data/Daz%203D/Genesis%208/Female%208_1/Morphs/P3Design/Every%20Day%20Emotions/P3D%20Amused.dsf

  • KeikuKeiku Posts: 143
    edited March 30

    PerttiA said:

    Three lines stand out from your log;
    E:/3D Artwork/!Daz Library/data/DAZ 3D/Genesis 8/Female/Morphs/guhzcoituz/New Black Cat/BC Head.dsf (1,1): Syntax error - expected '{' or '['
    \src\sdksource\fileinput\dzassetdaz.cpp(7934): Circular ERC!: P3D Amused with ERC ERC [DeltaAdd] > Katie : P3D Amused
    \src\sdksource\fileinput\dzassetdaz.cpp(7947): Unsupported formula: /data/Daz%203D/Genesis%208/Female%208_1/Morphs/P3Design/Every%20Day%20Emotions/P3D%20Amused.dsf

    I noticed things like that. I don't understand why the first line matters as that shouldn't even be used in the file. Everything is installed manually. I do notice sometimes Daz will ask to install files that I never used in the scene and that are installed in my custom libary. Not sure if that has anything to do with these issues, considering this has only occurred in the last few days.

    The second two would be part of the expression I applied. However in subsequent tests, I did not apply the same expression.

    New log attached, loaded up the problematic scene and made some changes until IRAY quit.

    txt
    txt
    log.txt
    628K
    Post edited by Keiku on
  • PerttiAPerttiA Posts: 10,024

    Keiku said:

    PerttiA said:

    Three lines stand out from your log;
    E:/3D Artwork/!Daz Library/data/DAZ 3D/Genesis 8/Female/Morphs/guhzcoituz/New Black Cat/BC Head.dsf (1,1): Syntax error - expected '{' or '['
    \src\sdksource\fileinput\dzassetdaz.cpp(7934): Circular ERC!: P3D Amused with ERC ERC [DeltaAdd] > Katie : P3D Amused
    \src\sdksource\fileinput\dzassetdaz.cpp(7947): Unsupported formula: /data/Daz%203D/Genesis%208/Female%208_1/Morphs/P3Design/Every%20Day%20Emotions/P3D%20Amused.dsf

    I noticed things like that. I don't understand why the first line matters as that shouldn't even be used in the file. 

    It doesn't matter, what is used in the scene, all the morphs you have installed for the base figure (Genesis 8 and 8.1 female) are read when a figure based on those is opened in DS, the dials for them are created and all the interdepencies created.
    The "BC Head.dsf" is corrupted and/or incomplete and you need to download and reinstall a working version or remove the morph.
    Circular ERC and Unsupported Formula in "P3D Amused" sound serious enough to uninstall.

  • KeikuKeiku Posts: 143

    PerttiA said:

    Keiku said:

    PerttiA said:

    Three lines stand out from your log;
    E:/3D Artwork/!Daz Library/data/DAZ 3D/Genesis 8/Female/Morphs/guhzcoituz/New Black Cat/BC Head.dsf (1,1): Syntax error - expected '{' or '['
    \src\sdksource\fileinput\dzassetdaz.cpp(7934): Circular ERC!: P3D Amused with ERC ERC [DeltaAdd] > Katie : P3D Amused
    \src\sdksource\fileinput\dzassetdaz.cpp(7947): Unsupported formula: /data/Daz%203D/Genesis%208/Female%208_1/Morphs/P3Design/Every%20Day%20Emotions/P3D%20Amused.dsf

    I noticed things like that. I don't understand why the first line matters as that shouldn't even be used in the file. 

    It doesn't matter, what is used in the scene, all the morphs you have installed for the base figure (Genesis 8 and 8.1 female) are read when a figure based on those is opened in DS, the dials for them are created and all the interdepencies created.
    The "BC Head.dsf" is corrupted and/or incomplete and you need to download and reinstall a working version or remove the morph.
    Circular ERC and Unsupported Formula in "P3D Amused" sound serious enough to uninstall.

    Well, both of those items are fixed. Still having IRAY stop. It's so very strange.

  • PerttiAPerttiA Posts: 10,024

    Are you by any chance over or underclocking your GPU or system?

  • KeikuKeiku Posts: 143

    PerttiA said:

    Are you by any chance over or underclocking your GPU or system?

    Stock clocks on everything. No setting changes (made by me, not sure about Microsoft) since it was last working.

  • TimberWolfTimberWolf Posts: 288

    Bit of a wildcard this one but by any chance do you have multiple decals in that scene?

  • KeikuKeiku Posts: 143

    TimberWolf said:

    Bit of a wildcard this one but by any chance do you have multiple decals in that scene?

    I am unsure what you mean by "decals". I don't believe I do. Just the character, hair, textures, clothing, and a chair. Although I've tested with just the character + hair + makeup and had some issues too.

  • TimberWolfTimberWolf Posts: 288
    edited March 31

    You'd know if you'd put decals in a scene - they're generally used for adding FX to objects; essentially a projection of a 2D image onto a mesh. They can be problematic if multiple decals are used.

    In that case I'm going to bet your hair is from Out of Touch (OOT). There is (was) an issue with the custom shader that can prevent Iray from working in its latest iteration. Check your product updates for a fixed version but in the meantime simply remove the map from the 'Transmitted Color' section of all of the hair materials surfaces *BEFORE* you try to preview in Iray. Once you've turned on the render engine it's too late...

    If it's not that I'm at a loss!

    Post edited by TimberWolf on
  • KeikuKeiku Posts: 143

    Hmm. It's a more complex hair, but not one by OOT (which I know has had problems before with different driver updates). The one I am using is: Elegant Hair for Genesis 8 and 8.1 Females by Toyen. If it only messed with IRAY preview I'd think it would be a matter of turning on the hair preview, but I cannot render either.

    After deleting the hair and messing around with it for a few minutes, I haven't had IRAY stop yet. So it may indeed be tied to the hair somehow.

  • TimberWolfTimberWolf Posts: 288
    edited March 31

    And that hair works fine for me. The issue is putting a map in the Transmitted Color parameter which causes Iray to fail until Studio is restarted. This hair doesn't have that map.

    The only thing I can suggest is, if practical, delete that saved scene file and start again. I've never come across it personally but I know various oddities have happened to other people which effectively rendered their various saved files unusable. I'm afraid I can't think of anything else, however remote, that could cause what's happening to you but it must be related to that scene.

    Post edited by TimberWolf on
  • KeikuKeiku Posts: 143

    Ok. Maybe it wasn't the hair. I started over by placing the hair on plain Genesis 8.1. Then I applied the character's material preset. Then the character preset itself. Then clothing, makeup, setup the scene. IRAY kept working. Then finally after just tilting the head, IRAY stopped. So I am back to square one and have no idea what's causing it.

    Strangely though, this time the log seems to indicate multiple stops, but I only saw it happen once.

    txt
    txt
    log.txt
    1024K
  • PerttiAPerttiA Posts: 10,024

    What are these?

    (1 triangle object with 2 M triangles, 1 instance yielding 2 M triangles; 17 fiber objects with 21941 fibers (877 k segments), 17 instances yielding 877 k segments)
    (6 light sources with 45716 triangles, 1 instance)

  • KeikuKeiku Posts: 143

    PerttiA said:

    What are these?

    (1 triangle object with 2 M triangles, 1 instance yielding 2 M triangles; 17 fiber objects with 21941 fibers (877 k segments), 17 instances yielding 877 k segments)
    (6 light sources with 45716 triangles, 1 instance)

    Maybe relating to the dforce dress or the hair? Not really sure.

    Just reinstalled my video driver. That didn't help either. Checked Sub-D levels, also didn't help.

  • PerttiAPerttiA Posts: 10,024

    The triangles are not in clothing or hair. At the beginning of your log there was even more of them, millions of triangles is taxing.
    Your light sources have 45716 triangles, which means you have 45716 separate lights in you scene - May be the reason why Iray stops working

  • KeikuKeiku Posts: 143

    Yikes. That's a lot of light sources. I see how that would be a problem. But it's just using the default HDRI at the moment. So where that all is coming from is anybodies guess. Switching to Sun-Sky and IRAY still breaks. So that is ruled out also. I checked to see if any surfaces had emissive properties. Some did that shouldn't have and I removed those. But IRAY still stopped.

  • felisfelis Posts: 4,338

    It sounds like there is too much geometry, so Iray gets stuffed.

    Try to select each object in turns in the scene tab. In the bottom of the scene tab is the node info. It tells how many verteces and faces each object has.

    If your node info isn't open, you can open it if you hoover over the middle of the bottom line of the scene pane. When the line turns yellow and a bit thicker in the middle, click it, and it will open the node info.

  • KeikuKeiku Posts: 143

    Assuming I am doing this right, total scene geometry is 421,249 polygons. Over 2 million verteces.

  • PerttiAPerttiA Posts: 10,024

    DS likes quads better, that is why the number of triangles is mentioned in the log.

    Start building the scene from scratch and check when you get problems.
    In your logs, it looked like you were deleting items from the scene, but didn't start DS again, that way stuff gets left behind in memory.

  • martin36martin36 Posts: 171
    edited April 12

    I had exactly the same problem as the creator of the thread. I upgraded from 4.14 to 4.22 and Iray stopped working with illegal memory error. I fixed this by downgrading to 4.21 which works perfectly, zero IRAY errors now. Problem is not in the hardware or drivers, problem is in DS software

    Post edited by martin36 on
  • Richard HaseltineRichard Haseltine Posts: 100,948

    martin36 said:

    I had exactly the same problem as the creator of the thread. I upgraded from 4.14 to 4.22 and Iray stopped working with illegal memory error. I fixed this by downgrading to 4.21 which works perfectly, zero IRAY errors now. Problem is not in the hardware or drivers, problem is in DS software

    and which driver(s) were you using?

  • KeikuKeiku Posts: 143

    I finally got it to work. Though I had to redo it all from scratch. It may very well be related to Daz version 4.22. However, it is still an issue I did not have until recently. One thing that I did discover was that my custom characters were defaulting to a Sub-D of 5. The only way to fix it was to change the maximum to 4 in the parameters settings.

  • Richard HaseltineRichard Haseltine Posts: 100,948

    The rogue SubD is probably a character that is being aplied and is linked to the render SubD level - if you click the gear icon on the slider and open Parameter Settings what, if anything, is listed under controllers in the lower half of the dialogue box? Are any of those shapes/characters applying as soon as you load the base figure?

  • KeikuKeiku Posts: 143

    More of my characters are loading in with a Sub-D of 5 now (although not all have caused an IRAY crash)
    I have discovered there is a controller "ERC [Add]>Genesis 8.1 Female: SubDivision Level" under the parameters for both SubDivision sliders. Does this have anything to do with this? This shows up on Genesis 3, 8, and 8.1 without any additional morphs being applied.

Sign In or Register to comment.