3 Characters ok, 4 NOT?

edutzugaya

So i'm trying to learn the algoritm to which daz3d calculates the scene. I have a scene that has 4 characters on the same screen, complete with the interior environment. I tried to cut out moost of the "invisible" wall and props of the environment that is not shown on the screen, but i can't render with 4 characters for some reason. With only 3 and hidind the fourth, everything works flawlesly, it even doesn't go overboard and does not uses cpu (sometimes it happened when there were too many things there) But as soon as unhide the fourth character, daz remained at "CPU calculating scene .. something" ... waiting for like an hour and still was calculating, so didn't had patience anymore, and canceled, since it would obviusly be rendered by cpu and not gpu, and would take a day instead 1-2 hours. 

 

So what i'm asking is what does influence this behaviour so much? It feels like it's a mathematical progression, and becomes worse when a fourth character is added in the equation. It's like x^3 << x^4 so it takes so much more power. PC specs are: Ryzen 5 2600, 16Gbram, 6Gb gtx 1060.

Richard Haseltine

Is that with any one of the four hidden, or were you hiding a specific one?

LenioTG

edutzugaya said:

So i'm trying to learn the algoritm to which daz3d calculates the scene. I have a scene that has 4 characters on the same screen, complete with the interior environment. I tried to cut out moost of the "invisible" wall and props of the environment that is not shown on the screen, but i can't render with 4 characters for some reason. With only 3 and hidind the fourth, everything works flawlesly, it even doesn't go overboard and does not uses cpu (sometimes it happened when there were too many things there) But as soon as unhide the fourth character, daz remained at "CPU calculating scene .. something" ... waiting for like an hour and still was calculating, so didn't had patience anymore, and canceled, since it would obviusly be rendered by cpu and not gpu, and would take a day instead 1-2 hours.

So what i'm asking is what does influence this behaviour so much? It feels like it's a mathematical progression, and becomes worse when a fourth character is added in the equation. It's like x^3 << x^4 so it takes so much more power. PC specs are: Ryzen 5 2600, 16Gbram, 6Gb gtx 1060.

This tool tells you how much available VRAM you got, and how much your scene is using: https://www.daz3d.com/iray-memory-assistant

You actually can use less than 6Gb, because around 700Mb will be used by your system to show your desktop.

The good news is that you could hugely reduce the VRAM that anything takes. Some useful products are here: https://www.daz3d.com/forums/discussion/319396/very-useful-daz-products-imho-converters-lights-utilities-morphs-vram-optimizers-shaders-etc/p1

And in my signature you'll find some YouTube tutorials I've made about this (I've been rendering for 1.5 years with 2.4Gb of available VRAM xD)

heinzerbrew_f94794efff

Have you looked at your log file to see what errors you may have?

chris-2599934

TGFan4 said:

I've been rendering for 1.5 years with 2.4Gb of available VRAM xD

Don't worry, I'm sure your image will finish rendering soon!

barbult

https://www.daz3d.com/iray-memory-assistant provides only an estimate, and it is usually quite inaccurate. Don't rely on it.

LenioTG

barbult said:

https://www.daz3d.com/iray-memory-assistant provides only an estimate, and it is usually quite inaccurate. Don't rely on it.

Actually I've done many tests, and it had never been wrong by more than 60Mb in my case. I find that pretty accurate!

And by many tests I mean around 30. I loaded stuff, then I checked with GPU-Z how much VRAM Daz was actually using.

chris-2599934 said:

TGFan4 said:

I've been rendering for 1.5 years with 2.4Gb of available VRAM xD

Don't worry, I'm sure your image will finish rendering soon!

What do you mean? @chris-2599934

English is not my first language, I'm from Italy.
So, I meant that I have been using Daz for 1.5 years, not that I am still rendering one scene. But I guess you already know that, you just feel fun today.

barbult

When I owned the Iray Memory Assistant product, these were the problems I reported. They were not fixed during the time I owned the product. I returned it, because these issues made it useless to me for my scenes. If you do not use large HDRI images in Render Settings, and do not use products that use surface displacement subD (like most Martin J. Frost products), or geometry shells, etc., maybe you don't run into these issues. Other users reported additional issues. Take a look at this thread, if you want an overview of problems users reported.

1. It didn't take into account the GPU memory used by any HDRI in Render Settings, which can be quite large (Render Settings pane).
2. It ignored surface displacement SubD, which can require huge amounts of GPU memory (Surfaces pane).
3. It didn't properly handle some cases of Base vs. High Resolution with regard to Render SubD Level (Parameters pane).
4. It didn't seem to account for the memory used by textures on Geometry Shells.
5. The interface had problems with not being able to display enough digits and showed values like ",440,048" where the digit in the millions was not displayed. 

Anyway, I did not find it at all useful for predicting whether my scene would fit in GPU memory or not.