hi boys!!
i've a problem with a scene.
think 10gb vram on rtx 3080 go full!
but i've see this windows.
How do these values work?
have 32gb ram.
thanks
nico
out for ram and crash
Moderator: juanjgon
- Attachments
-
- 222.jpg (9.42 KiB) Viewed 5036 times
the question if You run out of RAM (system memory) or VRAM (video memory on Your card)
Fire up something like MSI afterburner and keep Your eye on usage of Your system resources.
once You get a clear idea of what is happening You have few options:
* in case of low RAM, system memory, simply turn off everything that You do not use in the background - like other software, even web browsers.. - You get the point.
* if that does not help, start optimizing Your scene - that's simply put the price of resources - You either buy better system or spend more of Your time optimizing files (which one is a better option it's up to You)
* if You run out of VRAM, You can do some things as well. Enabling OOC (out of core) would help, if You have some spare RAM (system memory). this functionality allows You to place part of Your scene, usually textures into system memory. You might loose some speed, like RTX boost, but at least You should be able to render (if You are still fitting into RAM).
* another option, again, to optimize. Lower resolution of Your textures, optimize meshes and so.
one thing to remember is that running close to the edge of VRAM could be a bit unstable, getting into OCC could have render speed impact.. so optimizations are always welcome as they improve every aspect of Your work, from simple navigation, refresh, stability to render times.
Fire up something like MSI afterburner and keep Your eye on usage of Your system resources.
once You get a clear idea of what is happening You have few options:
* in case of low RAM, system memory, simply turn off everything that You do not use in the background - like other software, even web browsers.. - You get the point.
* if that does not help, start optimizing Your scene - that's simply put the price of resources - You either buy better system or spend more of Your time optimizing files (which one is a better option it's up to You)
* if You run out of VRAM, You can do some things as well. Enabling OOC (out of core) would help, if You have some spare RAM (system memory). this functionality allows You to place part of Your scene, usually textures into system memory. You might loose some speed, like RTX boost, but at least You should be able to render (if You are still fitting into RAM).
* another option, again, to optimize. Lower resolution of Your textures, optimize meshes and so.
one thing to remember is that running close to the edge of VRAM could be a bit unstable, getting into OCC could have render speed impact.. so optimizations are always welcome as they improve every aspect of Your work, from simple navigation, refresh, stability to render times.
as for Your screenshot
RAM limit points to how much RAM You allow OctaneRender to use - and that's very much scene dependent and what You are doing with Your system and such. For instance if You allow 10GB to be use out of 32 You have. and Your browser uses 20GB..- most likely You run into issues before You even start rendering.. as preparation of the scene to fil 10GB card and flow over would probably be more than You have in total.. - so again, start looking into resource monitoring apps and see what You have and where You are hitting the wall.
as for headroom, this is simple parameter that controls how much space should be left in VRAM before scene data would start to go to RAM. as pointed before in the other comment, if You are too close to the edge, You might have stability issues, however if Your scene is pushed out of VRAM to RAM too fast, You might loose render speed, so it's a balancing act and it's scene dependent. Sometimes optimizing few textures and keeping less headroom could lead to rendering few times faster, than not optimizing and pushing part of the scene to out of core and then rendering few times slower..
hope it makes sense.
RAM limit points to how much RAM You allow OctaneRender to use - and that's very much scene dependent and what You are doing with Your system and such. For instance if You allow 10GB to be use out of 32 You have. and Your browser uses 20GB..- most likely You run into issues before You even start rendering.. as preparation of the scene to fil 10GB card and flow over would probably be more than You have in total.. - so again, start looking into resource monitoring apps and see what You have and where You are hitting the wall.
as for headroom, this is simple parameter that controls how much space should be left in VRAM before scene data would start to go to RAM. as pointed before in the other comment, if You are too close to the edge, You might have stability issues, however if Your scene is pushed out of VRAM to RAM too fast, You might loose render speed, so it's a balancing act and it's scene dependent. Sometimes optimizing few textures and keeping less headroom could lead to rendering few times faster, than not optimizing and pushing part of the scene to out of core and then rendering few times slower..
hope it makes sense.
thanks for explain.glimpse wrote:as for Your screenshot
RAM limit points to how much RAM You allow OctaneRender to use - and that's very much scene dependent and what You are doing with Your system and such. For instance if You allow 10GB to be use out of 32 You have. and Your browser uses 20GB..- most likely You run into issues before You even start rendering.. as preparation of the scene to fil 10GB card and flow over would probably be more than You have in total.. - so again, start looking into resource monitoring apps and see what You have and where You are hitting the wall.
as for headroom, this is simple parameter that controls how much space should be left in VRAM before scene data would start to go to RAM. as pointed before in the other comment, if You are too close to the edge, You might have stability issues, however if Your scene is pushed out of VRAM to RAM too fast, You might loose render speed, so it's a balancing act and it's scene dependent. Sometimes optimizing few textures and keeping less headroom could lead to rendering few times faster, than not optimizing and pushing part of the scene to out of core and then rendering few times slower..
hope it makes sense.
unfortunately I have already optimized everything to the maximum.
the resolution is not very high (2000x1000), the only thing left for me to replace are the instances of the trees that are very heavy.
Are you using Denoiser ?
IF yes then, increase GPU headroom (400-500 MB instead 300), Denoiser needs real VRAM, can't work with OOC (System memory).
Also Enable OOC checkmark.
cheers
IF yes then, increase GPU headroom (400-500 MB instead 300), Denoiser needs real VRAM, can't work with OOC (System memory).
Also Enable OOC checkmark.
cheers
--
Lewis
http://www.ram-studio.hr
Skype - lewis3d
ICQ - 7128177
WS AMD TRPro 3955WX, 256GB RAM, Win10, 2 * RTX 4090, 1 * RTX 3090
RS1 i7 9800X, 64GB RAM, Win10, 3 * RTX 3090
RS2 i7 6850K, 64GB RAM, Win10, 2 * RTX 4090
Lewis
http://www.ram-studio.hr
Skype - lewis3d
ICQ - 7128177
WS AMD TRPro 3955WX, 256GB RAM, Win10, 2 * RTX 4090, 1 * RTX 3090
RS1 i7 9800X, 64GB RAM, Win10, 3 * RTX 3090
RS2 i7 6850K, 64GB RAM, Win10, 2 * RTX 4090
have tested it:
1. enable OOC texture;
2. used 10GB RAM Usage Limit
3. GPU Head Room 1000MB
in attachments during rendering.
use denoise.

1. enable OOC texture;
2. used 10GB RAM Usage Limit
3. GPU Head Room 1000MB
in attachments during rendering.
use denoise.


- Attachments
-
- Cattura.PNG (5.56 KiB) Viewed 4949 times
Hi,
I have had this kind of issue by the past.
Decrease the OpenGL display value to minimum value in Layout and modeler (if launched or better quit modeler) and retry to render.
I have had this kind of issue by the past.
Decrease the OpenGL display value to minimum value in Layout and modeler (if launched or better quit modeler) and retry to render.
Work Station : MB ASUS X299-Pro/SE - Intel i9 7980XE (2,6ghz 18 cores / 36 threads) - Ram 64GB - RTX4090 + RTX3090 - Win10 64
NET RENDER : MB ASUS P9X79 - Intel i7 - Ram 16GB - Two RTX 3080 TI - Win 10 64
NET RENDER : MB ASUS P9X79 - Intel i7 - Ram 16GB - Two RTX 3080 TI - Win 10 64
thanks...i think the problem is this customer and his negativity charmepixym wrote:Hi,
I have had this kind of issue by the past.
Decrease the OpenGL display value to minimum value in Layout and modeler (if launched or better quit modeler) and retry to render.


