|
|
Out of virtual memory on TS 6.6?
About Truespace Archives
These pages are a copy of the official truespace forums prior to their removal somewhere around 2011.
They are retained here for archive purposes only.
Out of virtual memory on TS 6.6? // Roundtable
Post by davidjohnson // May 1, 2008, 11:22am
|
davidjohnson
Total Posts: 169
|
I am running out of virtual memory with WINXP, and I don't know why. I have an animation of 600 frames and about 200 each and everytime, it stops rendering and tells me I am out of virtual memory.
I went into XP and virtual memory and switched it to 4000, but it seems to still be happening. Any ideas? |
Post by v3rd3 // May 1, 2008, 6:37pm
|
v3rd3
Total Posts: 388
|
I found that scenes with a large number of objects (vertices) ran into the same problem and I did not find a specific fix for it. I ended up creating multiple files and creating smaller scenes and camera movement to match.
In some cases I rendered backgrounds from the scene and applied them to simple planes or cubes to get the look I was after.
I am still very much a 3d noob so I hope you get some other answers. I just wanted to make sure you didn't feel alone..... :D |
Post by davidjohnson // May 2, 2008, 1:41am
|
davidjohnson
Total Posts: 169
|
Thanks for that, at least it isn't just me. I have tried it on two different computers, same thing. I am trying to minimize background activity in XP and see if that helps. |
Post by transient // May 2, 2008, 2:10am
|
transient
Total Posts: 977
|
Maybe you could try rendering out to tga or another sequential format. Video files can get huge, and this may be why your computer isn't handling the data.
It's just a guess, but maybe worth a try. |
Post by Tiles // May 2, 2008, 2:39am
|
Tiles
Total Posts: 1037
|
That's my advice too. Render to a picture format. Not to a movie format. In that way you can render in portions, like 100 frames for one go. No problem when it crashes. Simply go on with the frame it crashed. Put your pictures together to a movie by using a video cut software then. There is Avid Free for example ... |
Post by v3rd3 // May 2, 2008, 4:43pm
|
v3rd3
Total Posts: 388
|
Just one other thought as well. If you are rendering video try doing it without any codecs. On a couple of occasions I successfully rendered to an uncompressed avi and then used Wax to open the file and render using codecs for compression. |
Post by davidjohnson // May 3, 2008, 9:13am
|
davidjohnson
Total Posts: 169
|
Everything I try is unsuccessful. I have tried the codec and uncompressed and I have tried image sequences. I think I have an old demo of TS7.0 that I never installed, I might try that and open the file just to render it out and see if that works. I just can't figure this thing out... |
Post by Steinie // May 3, 2008, 10:15am
|
Steinie
Total Posts: 3667
|
So you CAN render out 199 frames? Just do them in groups and combine later. What is stopping you? With your system that is the limit so work within the limit. The limitation should be addressed later and not stopping you from doing your project. |
Post by davidjohnson // May 3, 2008, 6:06pm
|
davidjohnson
Total Posts: 169
|
I did try that. I rendered out 1-200, then 200-400, then I had to go in increments of 25 for the last 400-600 - not sure why, but just frustrating. |
Post by trueBlue // May 3, 2008, 7:31pm
|
trueBlue
Total Posts: 1761
|
You might try rebooting trueSpace after a rendering session and start fresh where you left off. HTH |
Post by Tiles // May 3, 2008, 9:30pm
|
Tiles
Total Posts: 1037
|
Yup. Reboot your system to free the memory. Then do the rest. |
Post by jamesmc // May 4, 2008, 6:20am
|
jamesmc
Total Posts: 2566
|
This happened to me on my old system. Haven't got trueSpace installed on my new system yet (haven't found the serial number for it :D)
In fact the rendering would stop even sooner if recorded with V-Ray or Lightworks. If I had 200 or so frames, somewhere between 10-20 frames, the rendering would stop and state I was out of virtual memory. No amount of resetting the virtual memory or rebooting the computer would solve the problem.
Too many people have this issue for it not to be a hardware related bug, perhaps there is a commonality among users that experience this.
I'll try it again on this computer as the processor is intel rather than AMD. Perhaps it is how memory is handled? Who knows? |
Post by transient // May 4, 2008, 3:08pm
|
transient
Total Posts: 977
|
The vray memory leak is a bug, it seems to happen on stills as well depending on what you are rendering. I'm not sure about lightworks, but Dribble seems to be fine.
Dribble uses very little ram in the first place, and it gives all of it back to you afterwards. |
|
