How to reduce VRAM usage? How much VRAM does a scene need?

LenioTG

marble said:

Richard Haseltine said:

Switching off visibility certainly should prevent the emsh from being sent to Iray - hiding it via surface settings, however, won't.

That surprises me. The reason I stated using IRay planes was because the render was still dropping to CPU no matter how many items I "turned off" (switched the little eye icon to closed).

I actually have the same experience! Is this maybe because everything you see while Daz is open remains in your VRAM?
When I close Daz Studio, the VRAM usage drops suddenly, and if I saved the scene with some elements hidden, when I load it it's not loaded into the VRAM

Richard Haseltine

kameneko said:

marble said:

Richard Haseltine said:

Switching off visibility certainly should prevent the emsh from being sent to Iray - hiding it via surface settings, however, won't.

That surprises me. The reason I stated using IRay planes was because the render was still dropping to CPU no matter how many items I "turned off" (switched the little eye icon to closed).

I actually have the same experience! Is this maybe because everything you see while Daz is open remains in your VRAM?
When I close Daz Studio, the VRAM usage drops suddenly, and if I saved the scene with some elements hidden, when I load it it's not loaded into the VRAM

I don't think that would work - Section Planes don't reduce the amount of scene geometry, in fact they add another polygon. Also, as far as I know and woudl expect, when you use a Section Plane the entire scene (including the bits to be hidden) must be passed to Iray so it can work out waht to chop; that may be done by a pre-process stage, and then discarded before the render process starts, but even that sounds unlikely as you can have the plane allow the camera to see through but block light and reflections as if it was normal.

kenshaw011267

I have that camera.  I have no idea if it changes VRAM usgae. What it does is drastically change render times. It clearly changes the amount of ray tracing that iRay does.

marble

kenshaw011267 said:

I have that camera.  I have no idea if it changes VRAM usgae. What it does is drastically change render times. It clearly changes the amount of ray tracing that iRay does.

I thought the way it might affect VRAM is by eliminating the need to load textures of objects that are beyond the plane. I might well be misunderstanding the whole thing though.

LenioTG

kenshaw011267 said:

I have that camera.  I have no idea if it changes VRAM usgae. What it does is drastically change render times. It clearly changes the amount of ray tracing that iRay does.

Interesting, thanks! :)

Anarkia333

Vous oubliez une seule solution... xD

Rendu avec seulement 1 G8, après l'autre. Et assemblage sur Photoshop.

Facile, rapide et réduit la VRAM.

Hylas

Richard Haseltine said:

Switching off visibility certainly should prevent the emsh from being sent to Iray

Are you sure? Items with smoothing modifier still react to meshes that are switched off, which kinda makes me think that the information is needed for rendering. I could be wrong of course.

Richard Haseltine

Hylas said:

Richard Haseltine said:

Switching off visibility certainly should prevent the emsh from being sent to Iray

Are you sure? Items with smoothing modifier still react to meshes that are switched off, which kinda makes me think that the information is needed for rendering. I could be wrong of course.

The adjustments are done by DS, Iray gets only the final result of all the modifiers rather than the modifiers themselves. That is one of the reasons there is no simple relationship between the size of a scene in working memory and the amount of GPU memory it will need.

Anarkia333

J'ai essayé cet optimiseur uniquement par Divise texure Bt 2, c'est un STUPID Tools...

Le résultat est partout mauvais, proche, et très loin.... Le diviseur fait un idiot fonctionne mal....

C'est une MAUVAISE période pour nous avec GPU, normalement 8go de VRAM c'est sympa en 2012!!! Nous sommes en 2021 et encore 8go ou 12go... Il nous faut 24 ou 36go minimum, ce sera le marché normalement. Donc, cet optimiseur n'est pas une fente pour une belle scène avec une résolution élevée ou G8, le même G3 est mauvais...

Seule solution, faire le rendu un par un corps... Ou optimiser manuellement uniquement la texture que vous voulez.....

Pour Windows ou Android, de nombreux outils viennent tout le temps, optimisez par 100 !!! Oh oui tout le temps c'est fini par BUG.... si le développeur ne fait pas optimiser l'outil, ce sera une raison, alors oubliez l'outil idiot magique pour avoir un rendu à 5 minutes et non 1h... Juste idiot fonctionne.

Nous avons besoin de HRDI 16h, texture 4k ou 8k, minimum pour un rendu sympa en 2021, si vous faites simplement une scène pour le web, soo 8go c'est Oki uniquement... Le résultat en 2K est horrible, bump est horrible, SSS oh mon dieu...

See the difference with 4k normaly and 2k, see the stupid result, and now imagine 8k or 16k....

And see the result with a far wood, and blurry with camera, result is strange, new Bump effet hasardous... Soo creaor make works with a define resolution, we can't come and divide by 2 or more, result will be strange and idiot all time...

Wee need to waiting for to have normaly GPU with 24go... No other true solution.