Rendering Issues

Has anyone else had issues with iRay scenes that worked perfectly well prior to the last couple of days?

I'm getting odd errors when I try to render, and I can't even view iRay in the viewport.

I've done nothing in terms of settings or anything, but the computer did update. Perhaps this means drivers updated ... but I'm just curious if anyone else has had this issue within this timeframe.

Comments

  • Richard HaseltineRichard Haseltine Posts: 107,932

    Do you mean error messages or errors in the output? What are they?

  • iqoniqmindiqoniqmind Posts: 16

    There were error messages pertaining to the Cuda cores having a memory problem.

    I installed the pre-May 21 driver and it fixed it, so either it was a driver issue, or the new driver installed ... wrong, I guess.

  • iqoniqmindiqoniqmind Posts: 16

    Richard Haseltine said:

    Do you mean error messages or errors in the output? What are they?

    I realized I didn't answer this properly. The errors were in the Log file, after the render had failed. It still would have kicked to CPU, but I've disabled that, so after the Cuda files failed, the render failed as well.

    Moreover, it wasn't just rendering. In the viewport, iRay wouldn't kick in either. It stayed "preparing the scene", without freezing the program or anything. It just wasn't working.

    But, installing the previous driver fixed it. I was just inquiring here, since I had presumed I wouldn't be the only one with this issue. But since it appears I was, perhaps it was just a bad install.

  • iqoniqmindiqoniqmind Posts: 16
    edited May 23

    I said all of that, then said it was fixed.

    And it is, in terms of iRay showing up in the viewport again. But now:


    2025-05-23 19:50:47.275 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(373): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: No device specified or usable
    2025-05-23 19:50:47.276 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering with 0 device(s):
    2025-05-23 19:50:47.276 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering...
    2025-05-23 19:50:47.276 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(373): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: No worker to render with: aborting render
    2025-05-23 19:50:47.276 [ERROR] Iray :: Internal rendering error.

    I have no idea what this even means, and I've never encountered it before.

    Post edited by iqoniqmind on
  • Richard HaseltineRichard Haseltine Posts: 107,932

    It's saying it can't find anything to render with, which makes it weird if it is in fact rendering.

  • iqoniqmindiqoniqmind Posts: 16
    edited May 24

    Richard Haseltine said:

    It's saying it can't find anything to render with, which makes it weird if it is in fact rendering.

    Yeah, it wasn't rendering - it was just allowing iRay to show up in the viewport, which it wasn't doing earlier. I'm back to rendering, but it feels as though I'm working with less memory now. WHile I can still render lighter stuff, I'm getting this error on scenes I used to be able to render just fine:

    2025-05-24 03:08:23.382 Iray [INFO] - IRAY:RENDER ::   1.15  IRAY   rend info : JIT-linking wavefront kernel in 96.160 ms
    2025-05-24 03:08:23.388 Iray [INFO] - IRAY:RENDER ::   1.5   IRAY   rend info : CUDA device 0 (NVIDIA GeForce RTX 3090): Scene processed in 2.914s
    2025-05-24 03:08:24.990 Iray [INFO] - IRAY:RENDER ::   1.2   IRAY   rend info : CUDA device 0 (NVIDIA GeForce RTX 3090): Prevent device timeout
    2025-05-24 03:08:25.191 Iray [INFO] - IRAY:RENDER ::   1.2   IRAY   rend info : CUDA device 0 (NVIDIA GeForce RTX 3090): Execute device timeout
    2025-05-24 03:08:30.789 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(373): Iray [ERROR] - IRAY:RENDER ::   1.15  IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while launching CUDA ior stack renderer in <internal>:319)
    2025-05-24 03:08:30.789 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(373): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): Failed to update ior stack
    2025-05-24 03:08:30.789 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(373): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): Device failed while rendering
    2025-05-24 03:08:30.789 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(373): Iray [WARNING] - IRAY:RENDER ::   1.5   IRAY   rend warn : CUDA device 0 (NVIDIA GeForce RTX 3090) is no longer available for rendering.
    2025-05-24 03:08:30.794 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(373): Iray [ERROR] - OPTX:RENDER ::   1.5   OPTX   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
    2025-05-24 03:08:30.794 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(373): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error
    2025-05-24 03:08:30.794 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(373): Iray [WARNING] - IRAY:RENDER ::   1.5   IRAY   rend warn : All available GPUs failed.
    2025-05-24 03:08:30.794 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(373): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: Fallback to CPU not allowed.
    2025-05-24 03:08:30.794 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(373): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: All workers failed: aborting render
    2025-05-24 03:08:30.835 [ERROR] Iray :: Internal rendering error.
    2025-05-24 03:08:30.946 [INFO] :: Saved image: C:\Users\18645\AppData\Roaming\DAZ 3D\Studio4\temp\render\r.png
    2025-05-24 03:08:30.947 [INFO] :: Finished rendering.

     

    I'm wondering if this is my card going bad! It shouldn't be doing so ... but ... just don't know what else it would be.

    Post edited by iqoniqmind on
  • felisfelis Posts: 5,744

    Have you tried monitoring your VRAM usage?

    It basically looks like you are running out of VRAM.

  • iqoniqmindiqoniqmind Posts: 16
    edited May 24

    Well, that's exactly what's happening, but I don't understand why it's happening.

    Remember, I was rendering these same scenes, exactly as they are currently set up, just last week. I personally changed nothing between now and then. I could render them back then, but now I cannot. That's the confusing part.

    The only thing that changed between now and then is that Windows updated, and my GPU's driver updated too. Then iRay stopped working, and I had to re-install an older driver to get iRay to work again. And now iRay works again, and I can render, but now the size of the scenes I can render has diminished.

    I think I might try to roll Windows back to last week, somehow, and see if that changes anything. I already rolled back the Nvidia driver.

    Post edited by iqoniqmind on
  • iqoniqmindiqoniqmind Posts: 16
    edited May 26

    How in God's name is this a real problem? For [goodness'] sake ... just beating my head against a wall here. DDU everything, reinstall drivers after driver, DDU it all again, reinstall, reinstall, google errors, reinstall ... this is crazy.

    There is no logical reason for there to be any problem whatsoever. Nothing in my scenes have changed, no hardware has been changed, I've over-optimized already optimized scenes to err on the side of caution. It's just silly. Sometimes iRay works in the viewport, sometimes it doesn't, sometimes I get hung on finding a device lens during the render process, sometimes it just flows smoothly to the black screen ...

    ... absolutely insane.

    Post edited by Richard Haseltine on
  • AlfRaMusicAlfRaMusic Posts: 100

    Rendering is also very choppy for me! The viewport only renders occasionally, and distance lights have no effect on the scene, not in Viewposrt and final render, as if no light is being emitted!

Sign In or Register to comment.