Ok, here's some more interesting findings:
This is the Vram situation when rendering an empty scene. Please note the engine runtime, geometry and unavailable ram usage:
This is the vram after adding a default cube to the scene and rendering:
The only difference between the two scenes is the geometry which went from 4 bytes to 5.9kb. The weird thing is the unavailable vram shot up from 1.1gb to 1.9gb. I cant wrap my head around this. Is Octane using some additional vram here and showing it as unavailable? Is windows upping its vram reserve just because im rendering a cube instead of an empty scene? No idea what's going on here.
Cinema4D Vram usage
Moderators: ChrisHekman, aoktar
Hi,
interesting, but please consider that it follows the Total available device memory, and in your case, there is a difference of ~800MB, so, 1.1 + 0.8 = 1.9.
I have done the same experiment here, and the difference between an empty scene, and a simple cube is only 1MB: ciao Beppe
interesting, but please consider that it follows the Total available device memory, and in your case, there is a difference of ~800MB, so, 1.1 + 0.8 = 1.9.
I have done the same experiment here, and the difference between an empty scene, and a simple cube is only 1MB: ciao Beppe
Hi Beppe, thanks for your reply.
What im trying to understand is how come you get 100mb difference while I get 800mb?
Between the empty scene and cube i dont run any other software that grabs vram and this test is quite repeatable.
Really confusing.
What im trying to understand is how come you get 100mb difference while I get 800mb?
Between the empty scene and cube i dont run any other software that grabs vram and this test is quite repeatable.
Really confusing.
Engine Runtine Data is always near 1GB at start...
Architectural Visualizations http://www.archviz-4d.studio