All of sudden, not enough Vram

I have often used the poduct Glowing Beach by Polish, a gorgeous scene in its own rights. Until recently, I could load up to three figures on it, 8.1 male and/or female with hair, anatomical parts and swimming attire and run it in sun-sky render settings without any sort of additional tweaking. Now, it looks like whenever I try to load one of these figures in that scene, even after removing all the candles, the boat and the tent with table settings etc, iRay just gives me the double finger. When the render is kicked in, here is what comes up in the log:

--------------

2022-07-01 15:44:29.900 Iray (Scene Update) : Updating LPE labels

2022-07-01 15:44:29.901 Iray (Scene Update) : Updating geometry

2022-07-01 15:44:29.901 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating geometry.

2022-07-01 15:44:29.902 Iray (Scene Update) : Retrieving geometry

2022-07-01 15:44:29.902 Iray (Scene Update) : Updating motion transform data

2022-07-01 15:44:29.902 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating motion transforms.

2022-07-01 15:44:29.902 Iray (Scene Update) : Updating section objects

2022-07-01 15:44:29.902 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Importing scene graph.

2022-07-01 15:44:35.049 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Auto instancing compression ratio 1.15 (Full instancing compression ratio 1.15)

2022-07-01 15:44:35.050 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Importing geometry for motion time 0

2022-07-01 15:44:37.119 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Geometry import (3 triangle objects with 59 M triangles, 0 fiber objects with 0 fibers (0 segments), 3 triangle instances yielding 59 M triangles, 0 fiber instances yielding 0 segments) took 2.069 s

2022-07-01 15:44:37.119 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating section objects.

2022-07-01 15:44:37.119 Iray (Scene Update) : Updating materials

2022-07-01 15:44:37.119 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating materials.

2022-07-01 15:44:37.730 Iray [INFO] - MATCNV:RENDER ::   1.0   MATCNV rend info : found 539 textures, 0 lambdas (0 unique)

2022-07-01 15:44:37.740 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Emitter geometry import (15 light sources with 46269 triangles, 1 instance) took 0.002 s

2022-07-01 15:44:37.740 Iray (Scene Update) : Updating volumes

2022-07-01 15:44:37.740 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating volumes.

2022-07-01 15:44:37.740 Iray (Scene Update) : Updating environment

2022-07-01 15:44:37.741 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating environment.

2022-07-01 15:44:37.741 Iray (Scene Update) : Updating lens data

2022-07-01 15:44:37.741 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating lens.

2022-07-01 15:44:37.741 Iray (Scene Update) : Updating lights

2022-07-01 15:44:37.742 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating lights.

2022-07-01 15:44:37.742 Iray (Scene Update) : Updating instance topology

2022-07-01 15:44:37.742 Iray (Scene Update) : Updating flags

2022-07-01 15:44:37.742 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating object flags.

2022-07-01 15:44:37.743 Iray (Scene Update) : Updating backplate

2022-07-01 15:44:37.743 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating backplate.

2022-07-01 15:44:37.743 Iray (Scene Update) : Updating portals

2022-07-01 15:44:37.744 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating caustic portals.

2022-07-01 15:44:37.744 Iray (Scene Update) : Updating decals

2022-07-01 15:44:37.744 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating decals.

2022-07-01 15:44:37.753 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Using iray core convergence estimate.

2022-07-01 15:44:37.753 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Allocating 1-layer frame buffer

2022-07-01 15:44:37.762 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Using batch scheduling, caustic sampler disabled

2022-07-01 15:44:37.762 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Initializing local rendering.

2022-07-01 15:44:37.768 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Using OptiX version 7.3.0

2022-07-01 15:44:37.770 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Initializing OptiX for CUDA device 0

2022-07-01 15:44:38.167 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering with 1 device(s):

2022-07-01 15:44:38.167 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : CUDA device 0 (NVIDIA GeForce RTX 3060)

2022-07-01 15:44:38.168 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering...

2022-07-01 15:44:38.168 Iray [INFO] - IRAY:RENDER ::   1.17  IRAY   rend progr: CUDA device 0 (NVIDIA GeForce RTX 3060): Processing scene...

2022-07-01 15:44:38.168 Iray (Scene Access) : Retrieving geometry

2022-07-01 15:44:38.168 Iray (Scene Access) : Retrieving device geometry

2022-07-01 15:44:39.034 Iray (Scene Access) : Retrieving volumes

2022-07-01 15:44:39.034 Iray (Scene Access) : Retrieving textures

2022-07-01 15:44:50.074 Iray (Scene Access) : Retrieving device textures

2022-07-01 15:44:51.399 Iray (Scene Access) : Retrieving flags

2022-07-01 15:44:51.399 Iray (Scene Access) : Retrieving device flags

2022-07-01 15:44:51.399 Iray (Scene Access) : Retrieving lights

2022-07-01 15:44:51.399 Iray [INFO] - IRAY:RENDER ::   1.5   IRAY   rend info : Importing lights for motion time 0

2022-07-01 15:44:51.400 Iray [INFO] - IRAY:RENDER ::   1.5   IRAY   rend info : Initializing light hierarchy.

2022-07-01 15:44:51.650 Iray [INFO] - IRAY:RENDER ::   1.5   IRAY   rend info : Light hierarchy initialization took 0.249 s

2022-07-01 15:44:51.652 Iray (Scene Access) : Retrieving device lights

2022-07-01 15:44:51.652 Iray (Scene Access) : Retrieving section objects

2022-07-01 15:44:51.652 Iray (Scene Access) : Retrieving device section objects

2022-07-01 15:44:51.652 Iray (Scene Access) : Retrieving materials

2022-07-01 15:44:51.656 Iray (Scene Access) : Compiling custom code

2022-07-01 15:44:51.656 Iray (Scene Access) : Retrieving environment

2022-07-01 15:44:51.656 Iray (Scene Access) : Retrieving device environment

2022-07-01 15:44:51.656 Iray (Scene Access) : Retrieving backplate

2022-07-01 15:44:51.656 Iray (Scene Access) : Retrieving device backplate

2022-07-01 15:44:51.656 Iray (Scene Access) : Retrieving portals

2022-07-01 15:44:51.656 Iray (Scene Access) : Retrieving decals

2022-07-01 15:44:51.657 Iray (Scene Access) : Retrieving device decals

2022-07-01 15:44:51.657 Iray (Scene Access) : Retrieving motion transform data

2022-07-01 15:44:51.657 Iray (Scene Access) : Retrieving device motion transform data

2022-07-01 15:44:51.657 Iray (Scene Access) : Retrieving lens data

2022-07-01 15:44:51.657 Iray (Scene Access) : Retrieving device lens data

2022-07-01 15:44:51.670 Iray [INFO] - IRAY:RENDER ::   1.17  IRAY   rend info : CUDA device 0 (NVIDIA GeForce RTX 3060): Scene processed in 13.502s

2022-07-01 15:44:51.670 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.17  IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3060): Not enough memory for kernel launches (0.000 B (244.617 MiB) required, 0.000 B available). Cannot allocate framebuffer.

2022-07-01 15:44:51.670 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.17  IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3060): Failed to setup device frame buffer

2022-07-01 15:44:51.670 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.17  IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3060): Device failed while rendering

2022-07-01 15:44:51.670 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [WARNING] - IRAY:RENDER ::   1.17  IRAY   rend warn : CUDA device 0 (NVIDIA GeForce RTX 3060) ran out of memory and is temporarily unavailable for rendering.

2022-07-01 15:44:51.738 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [WARNING] - IRAY:RENDER ::   1.17  IRAY   rend warn : All available GPUs failed.

2022-07-01 15:44:51.738 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.17  IRAY   rend error: Fallback to CPU not allowed.

2022-07-01 15:44:51.738 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.17  IRAY   rend error: All workers failed: aborting render

2022-07-01 15:44:51.738 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.17  IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3060): [Guidance sync] Failed slave device (remaining 0, done 0).

2022-07-01 15:44:51.740 [ERROR] Iray :: Internal rendering error.

2022-07-01 15:44:51.970 [INFO] :: Saved image: L:\TEMP\render\r.png

2022-07-01 15:44:51.995 [INFO] :: Finished Rendering

2022-07-01 15:44:52.040 [INFO] :: Total Rendering Time: 2 minutes 35.44 seconds

2022-07-01 15:44:57.258 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Device statistics:

2022-07-01 15:44:57.258 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : CUDA device 0 (NVIDIA GeForce RTX 3060): 0 iterations, 13.903s init, 0.070s render

---------------

I tried updating my nvidia driver. I tried updating to the latest beta. I restart Daz with every attempt. I clicked the "default settings" button in the render settings, trying to go back to what used to work. It still doesn't work. The only way I found to get the scene to work was to reduce its textures with scene optimizer but I didn't use to need that. And the characters I am trying to load there are the same I used to load in that same scene, countless times. What should I do? All advice welcome O_o

(Hardware wise: I am running a RTX 3060 on a Ryzen 3700X, with 64 G's of RAM. My OS is W11 Pro.) 

 

 

Post edited by second_technician_rimmer_9571136c47 on

Comments

  • PerttiAPerttiA Posts: 9,505

    "Until recently"... Is that the same as until W11?

  • As recently as five days ago :)

  • PerttiAPerttiA Posts: 9,505
    edited July 2022

    Do the "3 triangle objects with 59 M triangles" belong to the Glowing Beach, that has been working, or are they something new?
    15 light sources with 46269 triangles, sounds a lot for (outdoor?) scene

    I'm still on DS 4.15, so I don't know what the DS 4.20 log should look like... There are some strange things there...

    One thing that could cause such change, is if the Iray compression settings were somehow changed, causing the textures use more VRAM

    Post edited by PerttiA on
  • Just to clarify, about your W11 question: I moved to W11 a month ago and I did try that scene after that. It still worked. 

    I just tried to re-render the same scene without a character. I kept the render settings that came with the scene, only lowering the horizon to get a gradient of blue sky (otherwise it'd be very white). It renders just fine. If I run the character alone wihtout the scene, it works fine as well. 

    I tried loading the scene and applying different settings for the suns/sky. The same 15 light sources remain, the triangles too, no matter what. I really don't see what they are...

    The texture compression threshold is still set between 512 and 1024. GPU is selected for both photoreal and interactive, canvasses are not ticked (I did play with those a few times in the last week on another scene but didn't leave them on after that). One thing I noticed is that the normals are huge on that product.

  • PerttiAPerttiA Posts: 9,505

    If you look at the scene with wiremesh preview, you can probably spot the item(s) with 59M triangles

  • edited July 2022

    I am going to try and hunt it down but I suspect the island itself. However, it's still strange that a scene which worked just fine with some people less than a month ago would suddenly fux up.

    I don't know if it matters, but the scene renders fine in iray preview. Only in a final render does it go tits up.

    Post edited by second_technician_rimmer_9571136c47 on
  • PerttiAPerttiA Posts: 9,505
    edited July 2022

    Have you looked at your log (Help->Troubleshooting->View Log File)?

    Sorry...

    If you attach your log to your message, there may be things that have an effect (do not copy the log to the message area)

    Post edited by PerttiA on
  • PerttiAPerttiA Posts: 9,505

    An idea came to mind... Maybe something was installed/updated/enabled 5 days ago that eats up VRAM, you could use the Task Manager or GPU-Z to see, how much VRAM is in use when DS is not running.

  • I will do both these things, catch the log and attach it in a post, and check thoroughly what could have been installed in the last week. Sorry I didn't reply within the hour, I was still fighting with it and something odd happened. I still can't, as I used to, load 2 or 3 characters in the scene, but I managed to load one G8.1F fully loaded with the default render settings provided with the scene. And that didn't work at all unti half an hour ago. The only noticeable thing I did other than this was to reboot and play 10 mn of farcry 6 to make sure that the vcard reacted normally for other things. It's late now here, eleven thirty in the evening, but tomorrow I will follow your advice and I'll post the logs in here for you to see.

    Thank you for helping me PerttiA!

  • vectorinusvectorinus Posts: 113
    edited July 2022

    PerttiA said:

    "... Maybe something was installed/updated/enabled 5 days ago that eats up VRAM, you could use the Task Manager or GPU-Z to see, how much VRAM is in use when DS is not running."

    5 days ago, I noticed that at the start of the Daz Studio, the line "connecting to CMS..." is visible for a very long time. I don't know what the CMS talked to the Studio about for so long, but after that there were complaints about poor rendering of heavy scenes, which just recently were rendered well.
    For example here:    https://www.daz3d.com/forums/discussion/576631/public-build-iray-not-working

    But now the "connecting to CMS..." is visible 1-2 seconds. So, what happened to the Daz Studio 5 days ago?

    Post edited by vectorinus on
  • edited July 2022

    *EDIT*

    I think I found my culprit. The render subd for this character (and I can't think of why!) was cranked up to 5. I never set them up so high myself, usually sticking with 2 or 3 at max. Now, I can render two figures and do that so much quicker. Whatever modification I made to the character during the week, it seems to have reset my subd. Are there precedents to this?

    Post edited by second_technician_rimmer_9571136c47 on
  • vectorinusvectorinus Posts: 113

    It's good that you found the cause of the rendering problem. I think you implicitly solved the "public-build-iray-not-working" topic as well. There was also mentioned an object with 186 M triangles in the log file. This is too high a number even for a powerful graphics card.

  • I read somewhere on the forums about turning a figure into a prop. Assuming that you can do this, body, outfit, hair and shells, will the resulting prop eat less resources at all?

  • felisfelis Posts: 3,682
    edited July 2022

    second_technician_rimmer_9571136c47 said:

    I read somewhere on the forums about turning a figure into a prop. Assuming that you can do this, body, outfit, hair and shells, will the resulting prop eat less resources at all?

    As I see it, no.

    The difference between a figure and a prop is the figure is rigged.

    In order to reduce ressources, you have to reduce geometry (e.g subD level), number of textures or texture size.

    If it is a dressed character, you can hide bones covered by clothing, then they won't load when rendering.

    Also, if you have a large scenary, you can use Iray section planes to limit what is sent to the renderer.

     

    Post edited by felis on
  • I'll have to work on using iray section planes then.

     

Sign In or Register to comment.