lior opened this issue on Dec 27, 2010 · 30 posts
lior posted Mon, 27 December 2010 at 7:33 PM
Hi 
After so many hours to get my final render, a few seconds after a message says I'm out of memory even after giving a limit of 3% instead of 25%(default dettings).
How to avoid this:"Out Of Memory"?
Thank you for your help 
ShawnDriscoll posted Tue, 28 December 2010 at 5:37 AM
Reduce the ecosystem some. Reduce the resolution of texture maps used on objects too far from the camera anyway to see them.
lior posted Tue, 28 December 2010 at 5:48 AM
Hi ShawnDriscoll,
After installing again Vue8, this message appears but before I hadn't this message after loading any .Vue file
Must I change my configuration instead of default settings ?
cbuchner1 posted Tue, 28 December 2010 at 6:13 AM
on a 32bit system, consider using the 3GB switch (procedure differs between Windows XP and later Windows versions)
I enabled the Vue binaries and renderer to be large address aware, meaning they can address the full 32bit 4GB memory range per process. There are tools for this, for example EDITBIN from the Microsoft Visual Studio package. The default setting allows applications to only address 2GB of memory.
I can now render larger ecosystems before my laptop runs out of memory.
On 64bit systems I have seen this error message when I ran out of swap space once (I had limited my swap space to a fixed size, which was not enough apparently)
lior posted Tue, 28 December 2010 at 8:58 AM
I'm in WinXP Pro SP3 with
...
I have a scene that impossible to give me the final render
A friend said: "you should re render the scene using the external standalone rendered, it will most likely render the scene without a problem for you"
So I did as he said but again:"Out Of Memory"
Impossible to get this final render
hobepaintball posted Tue, 28 December 2010 at 9:14 AM
Your second dialog is about your video card memory for use displaying in your view ports. Change this number to the amount of ram on your video card.
lior posted Tue, 28 December 2010 at 9:20 AM
Quote - Your second dialog is about your video card memory for use displaying in your view ports. Change this number to the amount of ram on your video card.
I did it and I wrote 512Mo instead of 128Mo but still impossible to get this final render
hobepaintball posted Tue, 28 December 2010 at 9:25 AM
The second message has nothing to do with your problem with final render. You are just trying to display more in the view port than the 128 standard limit can address. The final render out of memory can be addressed through lowering the resolution of materials or terrain resolution or lowering instances, or replacing objects with instances or using a lower resolution render, the options are limitless depending on where you are willing to comprimise
lior posted Tue, 28 December 2010 at 9:29 AM
A friend said: "you should re render the scene using the external standalone rendered, it will most likely render the scene without a problem for you" I did this but still impossible ...
hobepaintball posted Tue, 28 December 2010 at 9:48 AM
Will it render at one of the smaller sizes?
You could switch to custom and try eliminating subrays or lowering quality or eliminate depth of field calculations, if it features poser imports there are many sepaerate ways to optimize that. You could try hiding once of the complex items from render and see if the scene will render then, and if so there's where you can look towards for optimization
lior posted Tue, 28 December 2010 at 11:49 AM
Quote - Will it render at one of the smaller sizes?
You could switch to custom and try eliminating subrays or lowering quality or eliminate depth of field calculations, if it features poser imports there are many sepaerate ways to optimize that. You could try hiding once of the complex items from render and see if the scene will render then, and if so there's where you can look towards for optimization
Something I don't know how to do and I've never found any tutorial about this problem.Do you know links that would be useful to understand what you said?
A print screan would help me to understand?
Thank you for your help
ShawnDriscoll posted Tue, 28 December 2010 at 9:55 PM
Quote - Hi ShawnDriscoll, After installing again Vue8, this message appears but before I hadn't this message after loading any .Vue file
Must I change my configuration instead of default settings ?
That 128MB message is a whole other issue. It means that your video card has been told to use only 128MB (the default amount in Vue's display options) of its RAM. If you have more RAM on your video card, you can increase the amount to equal it. If you don't have the setting available in Vue to change this, edit your environment.xml file (found in Vue's Config folder) and change the line to
line to
(for 512MB video cards)
For huge scenes that use up system RAM to store while rendering, and the RAM usage still goes up more while rendering, well you are going to need more RAM and a 64-bit OS to render your scene.
Can you post a screenshot of just the bottom right view screen to show what is in your scene? I may have more ideas for you then.
lior posted Tue, 28 December 2010 at 10:56 PM
ShawnDriscoll posted Tue, 28 December 2010 at 11:02 PM
I don't se any problem memory-wise with that camera view. Are you animating the camera? Are you using Dynamic Population for any eco-system used?
lior posted Tue, 28 December 2010 at 11:39 PM
Quote - I don't se any problem memory-wise with that camera view. Are you animating the camera? Are you using Dynamic Population for any eco-system used?
No animated camera+Dynamic Population for all the ecosystems, that's to say for the Ground+the two terrains: 4 ecosystems in Dynamic Population
ShawnDriscoll posted Tue, 28 December 2010 at 11:47 PM
And as far as you know, there are no hi-def (hero) plants used in the eco-systems? They are pretty much lo-poly objects?
Do you have any objects/layers in the scene that you've made invisible? They can be deleted to free up system RAM.
And how long does Vue take to generate the dynamic eco-system when you click render? 5 sec? 10 sec? 1 minute? 10 minutes? 60 minutes?
lior posted Wed, 29 December 2010 at 12:23 AM
ShawnDriscoll posted Wed, 29 December 2010 at 1:19 AM
But during the actual render (I'm guessing GR lighting is being used), does the render bucket (do you see the render as it's being done by the way? or is this being rendered straight to disk or something?) move along nicely and then pause for a bit while some Dynamic population is being generated? Then the bucket continues on until it runs over another eco-system that needs populating?
Lots of questions here, I know. But is your terrain a fractal one and is its material using a fractal pattern? Might as well turn off the fractals for both if the terrain is covered by plants anyway. That will save on RAM a bit and speed up the render as well.
How many lights are in the scene? More than three? How many sub rays? Can your system render the Sample Vue scenes included without RAM errors?
Render to screen instead of disk so that you can see where the crash is happening. Also watch your resource value go down as it renders. You do not want to go below 7% while rendering. You need room to save the render afterwards.
lior posted Wed, 29 December 2010 at 3:23 AM
Quote - But during the actual render (I'm guessing GR lighting is being used), does the render bucket (do you see the render as it's being done by the way? or is this being rendered straight to disk or something?) Then the bucket continues on until it runs over another eco-system that needs populating?
Lots of questions here, I know. But is your terrain a fractal one and is its material using a fractal pattern? Might as well turn off the fractals for both if the terrain is covered by plants anyway. That will save on RAM a bit and speed up the render as well.
How many lights are in the scene? More than three? How many sub rays? Can your system render the Sample Vue scenes included without RAM errors?
Render to screen instead of disk so that you can see where the crash is happening. Also watch your resource value go down as it renders. You do not want to go below 7% while rendering. You need room to save the render afterwards.
I tried to render straight to disk but impossible
What do you mean by:"move along nicely and then pause for a bit while some Dynamic population is being generated?"
I load a procedural terrain, in 1024x1024 and I used a fractal =simple fractal.After loading my ecosystems, I made a copy= that's 2 say 2 simple fractal terrains.
I have not any light on the scene, excepted the sun.
Whitch subray?
ShawnDriscoll posted Wed, 29 December 2010 at 3:56 AM
See image for subrays. Try again using a standard terrain instead of a procedural terrain.
ShawnDriscoll posted Wed, 29 December 2010 at 4:02 AM
I'm tired and circled the subray on the right. I meant the subray setting on the left.
bigbraader posted Wed, 29 December 2010 at 6:12 AM
Try using the standalone renderer.
lior posted Wed, 29 December 2010 at 5:16 PM
Quote - Try again using a standard terrain instead of a procedural terrain.
With a procedural terrain, we have more possibilities to get the terrain you want!
Quote - Try using the standalone renderer.
What do you mean and how to do this
bigbraader posted Thu, 30 December 2010 at 5:24 AM
The stand-alone renderer is also known as the "external renderer".
I use it for almost all my final output. It's a stand-alone application that runs independent of Vue itself, once the render has started. You can work on other things in Vue or even close it, the render will continue to run in the background (unless you close THAT one).
It is much less ressource-intensive than the basic screen render, doesn't require any involvement of GPU and such.
I have the impression that many Vue users are sceptical to this option, but this is mainly due to "irrational" reasons (they don't "like it", they can't see what's going on etc. - some claim the outcome isn't predictable etc.). But I've used it very much, and the result is exactly as it would be if you rendered it to screen. Only that it will allow you to pull off renders that would crash your system otherwise.
Read the manual for more information.
lior posted Thu, 30 December 2010 at 3:21 PM
Quote - The stand-alone renderer is also known as the "external renderer".
I use it for almost all my final output. It's a stand-alone application that runs independent of Vue itself, once the render has started. You can work on other things in Vue or even close it, the render will continue to run in the background (unless you close THAT one).
It is much less ressource-intensive than the basic screen render, doesn't require any involvement of GPU and such.
I have the impression that many Vue users are sceptical to this option, but this is mainly due to "irrational" reasons (they don't "like it", they can't see what's going on etc. - some claim the outcome isn't predictable etc.). But I've used it very much, and the result is exactly as it would be if you rendered it to screen. Only that it will allow you to pull off renders that would crash your system otherwise.
Read the manual for more information.
It's exactly what I did to succed to get my final render !
lior posted Fri, 31 December 2010 at 1:21 AM
ShawnDriscoll posted Fri, 31 December 2010 at 1:24 AM
Ok. See you next year.
bigbraader posted Fri, 31 December 2010 at 5:26 AM
What and how was the solution - the subrays tip?
ShawnDriscoll posted Tue, 04 January 2011 at 3:34 AM
I just bought Martin's Winter Grasslands Mega Bundle today and gave it a try. His eco-systems are dense. Really dense. My RAM dropped to 80MB left (from 1.5GB initially) while rendering just a 800 x 600 GR-lit preview scene (camera facing the ground) even with Dynamic Population enabled.
His grasses look amazing though.
lior posted Tue, 04 January 2011 at 10:42 AM
Quote - I just bought Martin's Winter Grasslands Mega Bundle today and gave it a try. His eco-systems are dense. Really dense. My RAM dropped to 80MB left (from 1.5GB initially) while rendering just a 800 x 600 GR-lit preview scene (camera facing the ground) even with Dynamic Population enabled.
His grasses look amazing though.
Winter Landscape Here has very heavy ecosystems and .atm: this explains why it wasn't easy to get my final render.
