DAZ started to fudge me over suddenly!

Daz repeatedly cancels renders, then renders the next time I click, then outputs a black image, then renders 7 frames in an image series without a problem; then fails and stops again. I watched it render today, where I normally just go do something else. Frame 1 renders fastish 1m30s(HD 250 iteration animation test), then frame 2 renders 6+ minutes, then normal again, then it gives up.

 

I have checked that I don't surpass the 8GB VRAM I have on my RTX3070(otherwise it would normally not let me switch to Iray in the viewport anyway). I have installed the latest NVIDIA studio driver; instead of the game driver. I have reinstalled DAZ and restarted the computer and so on and so forth. I have 32Gb RAM in my machine, and I can see that when Daz renders it sits comfortably @ 20Gb used and ~73% total, all other programmes running taken into account. My graphics card is nowhere near overheating. I do not have CPU fallback enabled, since that would just suck. I watch youtube videos while it renders most of the time, that is it. It rendered all night the past two nights without problems, but today it just went apeshit :-S If the save file was corrupt wouldn't it show up in the scene rather than result it failing to render?

 

Please help :-/

 

This is the log file output, last lines atleast:

2023-03-14 17:07:45.292 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating decals.

2023-03-14 17:07:45.294 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Using iray core convergence estimate.

2023-03-14 17:07:45.295 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Allocating 1-layer frame buffer

2023-03-14 17:07:45.296 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Using batch scheduling, caustic sampler disabled

2023-03-14 17:07:45.296 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Initializing local rendering.

2023-03-14 17:07:45.298 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Initializing OptiX for CUDA device 0

2023-03-14 17:07:45.406 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering with 1 device(s):

2023-03-14 17:07:45.406 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : CUDA device 0 (NVIDIA GeForce RTX 3070)

2023-03-14 17:07:45.406 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering...

2023-03-14 17:07:45.406 Iray [INFO] - IRAY:RENDER ::   1.4   IRAY   rend progr: CUDA device 0 (NVIDIA GeForce RTX 3070): Processing scene...

2023-03-14 17:07:45.406 Iray (Scene Access) : Retrieving geometry

2023-03-14 17:07:45.406 Iray (Scene Access) : Retrieving device geometry

2023-03-14 17:07:45.801 Iray (Scene Access) : Retrieving volumes

2023-03-14 17:07:45.801 Iray (Scene Access) : Retrieving textures

2023-03-14 17:07:50.848 Iray (Scene Access) : Retrieving device textures

2023-03-14 17:07:51.848 Iray (Scene Access) : Retrieving flags

2023-03-14 17:07:51.849 Iray (Scene Access) : Retrieving device flags

2023-03-14 17:07:51.849 Iray (Scene Access) : Retrieving lights

2023-03-14 17:07:51.849 Iray [INFO] - IRAY:RENDER ::   1.6   IRAY   rend info : Importing lights for motion time 0

2023-03-14 17:07:51.849 Iray [INFO] - IRAY:RENDER ::   1.6   IRAY   rend info : Initializing light hierarchy.

2023-03-14 17:07:51.857 Iray [INFO] - IRAY:RENDER ::   1.6   IRAY   rend info : Light hierarchy initialization took 0.008 s

2023-03-14 17:07:51.857 Iray (Scene Access) : Retrieving device lights

2023-03-14 17:07:51.857 Iray (Scene Access) : Retrieving section objects

2023-03-14 17:07:51.858 Iray (Scene Access) : Retrieving device section objects

2023-03-14 17:07:51.858 Iray (Scene Access) : Retrieving materials

2023-03-14 17:07:51.861 Iray (Scene Access) : Compiling custom code

2023-03-14 17:07:51.878 Iray (Scene Access) : Retrieving environment

2023-03-14 17:07:51.881 Iray (Scene Access) : Retrieving device environment

2023-03-14 17:07:51.883 Iray (Scene Access) : Retrieving backplate

2023-03-14 17:07:51.883 Iray (Scene Access) : Retrieving device backplate

2023-03-14 17:07:51.883 Iray (Scene Access) : Retrieving portals

2023-03-14 17:07:51.883 Iray (Scene Access) : Retrieving decals

2023-03-14 17:07:51.883 Iray (Scene Access) : Retrieving device decals

2023-03-14 17:07:51.884 Iray (Scene Access) : Retrieving motion transform data

2023-03-14 17:07:51.884 Iray (Scene Access) : Retrieving device motion transform data

2023-03-14 17:07:51.884 Iray (Scene Access) : Retrieving lens data

2023-03-14 17:07:51.884 Iray (Scene Access) : Retrieving device lens data

2023-03-14 17:07:51.914 Iray [INFO] - IRAY:RENDER ::   1.6   IRAY   rend info : JIT-linking wavefront kernel in 0.020 s

2023-03-14 17:07:51.914 Iray [INFO] - IRAY:RENDER ::   1.4   IRAY   rend info : CUDA device 0 (NVIDIA GeForce RTX 3070): Scene processed in 6.508s

2023-03-14 17:07:51.915 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.4   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3070): Not enough memory for kernel launches (0.000 B (401.871 MiB) required, 0.000 B available). Cannot allocate framebuffer.

2023-03-14 17:07:51.915 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.4   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3070): Failed to setup device frame buffer

2023-03-14 17:07:51.915 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.4   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3070): Device failed while rendering

2023-03-14 17:07:51.915 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [WARNING] - IRAY:RENDER ::   1.4   IRAY   rend warn : CUDA device 0 (NVIDIA GeForce RTX 3070) ran out of memory and is temporarily unavailable for rendering.

2023-03-14 17:07:51.960 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [WARNING] - IRAY:RENDER ::   1.4   IRAY   rend warn : All available GPUs failed.

2023-03-14 17:07:51.960 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.4   IRAY   rend error: Fallback to CPU not allowed.

2023-03-14 17:07:51.960 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.4   IRAY   rend error: All workers failed: aborting render

2023-03-14 17:07:51.960 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.4   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3070): [Guidance sync] Failed slave device (remaining 0, done 0).

2023-03-14 17:07:51.960 [ERROR] Iray :: Internal rendering error.

2023-03-14 17:07:51.969 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Device statistics:

2023-03-14 17:07:51.969 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : CUDA device 0 (NVIDIA GeForce RTX 3070): 0 iterations, 6.618s init, 0.045s render

2023-03-14 17:07:52.018 [INFO] :: Saved image: C:\Users\Antio\Documents\DAZ 3D\Studio\Render Library\Series\-:-

2023-03-14 17:07:52.786 [INFO] :: Finished Rendering

2023-03-14 17:07:52.818 [INFO] :: Total Rendering Time: 35.36 seconds

 

Comments

  • FishtalesFishtales Posts: 6,018

    According to that you are running out of Vram on the video card.

  • SofaCitizenSofaCitizen Posts: 1,564

    antiochethereal said:

    Daz repeatedly cancels renders, then renders the next time I click, then outputs a black image

    This means you have run out of video memory and as it cannot fallback to CPU it has no choice but to stop.

     

    I have checked that I don't surpass the 8GB VRAM I have on my RTX3070(otherwise it would normally not let me switch to Iray in the viewport anyway).

    Not true. There are settings, such as SubD levels which are applied differently between the Iray preview and proper render and so it is very possible to get an iray preview for something that will then exceed memory during rendering.

     

    I watch youtube videos while it renders most of the time, that is it.

    You should probably stop that if you are having trouble rendering since it will be reducing the available video card memory for Daz. Boot the machine up fresh. Set it to render and then leave it alone. If it still fails then use Scene/Camera Optimiser, adjust the SubD levels or do something else to make the scene fit in your card's memory.

  • PerttiAPerttiA Posts: 9,147

    8GB's of VRAM is very little nowadays for the latest DS with the latest drivers and relatively new assets on the scene.

    1. When you want to render, do not activate Iray preview at any point during that session. Use texture shaded insted.
    2. Browsers also use VRAM

  • Frames 1-6 render fine. Frame 7 stops it all. Nothing important happens in frame 7.

  • PerttiA said:

    8GB's of VRAM is very little nowadays for the latest DS with the latest drivers and relatively new assets on the scene.

    1. When you want to render, do not activate Iray preview at any point during that session. Use texture shaded insted.
    2. Browsers also use VRAM

    I am always careful with not having the iray preview activated, but it is a good tip. In the end I gave up and halved the sizes of the textures in the entire scene. It renders now atleast, but it still just stops suddenly. I didn't realize that one character I use (Gertha/Katheryn Winnick) was using 8k textures (37 of them). It is still weird that I could render at all though; because normally it just outputs a black screen. So I guess it was balancing between not having enough VRAM and having just enough to render.

     

    DAZ is plain weird sometimes. Just now I was setting up a character on a sofa, and added a smoothing modifier to the sofa. After that I chose the collision target, and then of course Daz crashed as per usual. After reloading and making a safe save before adding collision, I activated it, and this time it worked. BUT then when I wanted to position the character off of the sofa on the floor in front of it, all the joints are suddenly bugged. Bending the thighs now absolutely deforms the character and the scene is probably ruined. I hate this programme with all my heart, but have used so much time learning and bought so many assets for it, that I feel forced to keep using it. Otherwise I would've left this trashfire to burn out a long time ago.

  • antiochetherealantiochethereal Posts: 16
    edited March 2023

    While DAZ still has its quirks, especially while animating, I think I have found the largest single culprit I have had in the past 2-3 years when battling with VRAM. Windows 10 -.- I sat here thinking about it almost all week and have been trying to read about it online, to understand why the iRay memory assistant also gave me such wildly varying results, aside from the fact that I could sometimes render a scene and at other times not. I was running Windows 10 in 4K... I have now switched to 2K. Another scene I have battled with today, suddenly spit out 30 frames in 15 minutes where it usually takes double or triple that and shuts down frequently. Of course I will still run into problems sometimes with my meager 8 gigs, but right now I am just super happy I found a way to continue creating content without having to go out and buy a 3080/4080/3090/4090 card =D Sorry for the negativity!

    regards,

    Anti

     

    ps. Just thought I would leave this here in case someone else didn't check their Windows resolution when they first set their PC up lol

    pps. Yes I can feel a difference already looking at a 60 inch screen in 2K compared to 4K, it is a bit sharper somehow. Could also be because I am super tired after fighting with this [stuff] for a solid week.

    Post edited by Richard Haseltine on
  • Iray Memory Assistant can't actually see how much memory will be used, it has to guess based on the scene - unfortunately there is no simple relationship, as the data Daz Studio needs (things like morphs and joint setups) is not sent to iray, but Iray does get higher resolution versions of smoothed mesh (usually) and textures. I suspect that the changes in iray over the years may well have made Memory Assistant's estimates more unreilable rather than less, and of course we no loner get a definitive statement from Iray as to the memory used by a render.

  • I've been having some render crashes lately as well ( I have an iMac late-2015 with only 4GB of VRAM). Up to now, it's been fine, but wondering in getting an eGPU is something to consider.  Any thoughts?

    I do have an Intel processor and the current video card is an AMD Radeon R9 M395X.

  • teechurz_7c41d96282 said:

    I've been having some render crashes lately as well ( I have an iMac late-2015 with only 4GB of VRAM). Up to now, it's been fine, but wondering in getting an eGPU is something to consider.  Any thoughts?

    I do have an Intel processor and the current video card is an AMD Radeon R9 M395X.

    As far as I am aware there is no Mac driver for nVidia GPUs that is new enough to meet the minimum requirement for the current. or recent, version of Iray.

  • Yeah, I don't think any nVidias will work with Mocs.  I was thinking of an AMD eGPU but after doing a little research, I'm finding out that my system is too old to get am appreciable update using an eGPU.  They're all Thunderbolt 3 and my system is Thunderbolt 2.   There are workarounds, but they limit the effectiveness of the eGPU. Harrumph!

  • An AMD GPU would not be used by Iray in any event, that is nVidia or nothing when it comes to GPUs.

  • For anyone interested; I am also effectively testing the difference between using your computer while rendering in DAZ, and not. I have two identical computers with an i9/3070 8Gb and 32 GB RAM. One I do things like this and have 7 tabs open in Mozilla and Chrome. Editing video and so on while rendering. On the other one I only render. Same resolution, same frame amount, iterations, quality and ofc scene.

    The difference right now is that the one I am using for other stuff is @ frame 110/240(started at 1 out of 240) and the other one is at frame 113/240 (started at 241 out of 480). So not that big of a difference ^_^

  • Omfg. How much VRAM did Windows eat up in 4K!? Before I was limited to two people in an environment with few light sources. Now I can mash 5 people in there with 10 light sources and Raytracing! xD All 5 people are with grafts; but no clothes so far. On top of that I dialed every character down to Subd level 1 in rendering and saved the scene... I then reopened and started rendering... then found some errors and wanted to correct them... while in that process I also found out that all characters reverted to subd level 2 and I can STILL render xD that is just ridiculous and I have not halved textures or anything. I was sure I would be forced to do that.

Sign In or Register to comment.