albertocano opened this issue on Apr 20, 2004 ยท 18 posts
albertocano posted Tue, 20 April 2004 at 10:37 AM
When i try to render a big number frames animation ( 200-300 frames) with high detailed characters and a environment full of objects in Poser 4 i get a memory error message in about frame 100. I think a have a enough powerfull machine ( Pentium 4 2800, Windows XP, 1G RAM memory, Ati Radeon 9600 pro). Why do this thing happen?, Do i need a more powerfull computer?
neilp posted Tue, 20 April 2004 at 10:44 AM
Poser 4 pro pack?
albertocano posted Tue, 20 April 2004 at 10:49 AM
No, only Poser 4
neilp posted Tue, 20 April 2004 at 10:50 AM
I lifted this directly from the Curiouslabs site Poser 4 FAQ. My computer freezes before it finishes rendering my animation. What do I do? This could be a video card driver issue. Make sure you have the latest drivers for your specific video card. You may also try reducing Hardware acceleration. Right-click the desktop > choose properties. The Display Properties control panel will open. Click Settings > Advanced > choose either Performance or the Troubleshoot tab. Adjust the Hardware acceleration slider to lower settings and test your Programs.
mateo_sancarlos posted Tue, 20 April 2004 at 11:00 AM
Alberto, what codec do you normally use for your animations?
albertocano posted Tue, 20 April 2004 at 11:04 AM
Thank you, ill do what you say
albertocano posted Tue, 20 April 2004 at 11:07 AM
Sorry Mateo i didnt see you, i use MPEG-3688 V3
albertocano posted Tue, 20 April 2004 at 11:08 AM
I mean MPEG4-3688 V3
SamTherapy posted Tue, 20 April 2004 at 11:09 AM
"a big number frames animation ( 200-300 frames) with high detailed characters and a environment full of objects" That's probably your issue. 1 GB of RAM ain't a hell of a lot if you're trying to do something really ambitious. A lot of detailed models and an environment full of objects is taxing enough on single frame renders.
Coppula eam se non posit acceptera jocularum.
MungoPark posted Tue, 20 April 2004 at 11:14 AM
This is probably a bug - Poser had a memory leak which apparently is fixed in P5 service release 4. Look at the read me. Probably no chance for PP4. I never could render big long animations neither in P4 nor in P5 until the service release.
albertocano posted Tue, 20 April 2004 at 11:15 AM
Not very ambitious is just an animation with one v3 in Retro Diner ( Daz3d environment).
albertocano posted Tue, 20 April 2004 at 11:18 AM
But i rendered longer animations but more simply than this
MungoPark posted Tue, 20 April 2004 at 11:19 AM
Yes, but this big V3 will add up over time very fast and if the memory is not cleaned up there is an end in view. With a normal V3 I could render on a machine with 1 gig memory from 100-300 frames then the end was reached. The same problem occurred when I rendered the same V3 in the same frame from Python and it had nothing to do with the movie
albertocano posted Tue, 20 April 2004 at 11:27 AM
So, the only solution is to make avis less than 100 frames and to join then with a video editor. Isnt it?
albertocano posted Tue, 20 April 2004 at 11:29 AM
And, what do you think about what Neilp answered In Re.4?
MungoPark posted Tue, 20 April 2004 at 11:37 AM
Try it - could help probably, But if it doesnt work render, it into single tiffs, in 100 frame batches and then join them later in a movie editor programm.
who3d posted Tue, 20 April 2004 at 1:23 PM
The "render to image files" solution is the best one I know of if you don't have Poser 5 SR4.1 (which as you've got Poser 4, you won't have).
If you render out to a sequence of image files then you can use the "Animation Palette" to select the range to preview and render. If you crash at frame 150 then set this to go from 151 to end when you reload, and rendering will resume at frame 151 :)
As a matter of interest, if you render to image files this way then you can fairly easily adjust small parts of your animation and only re-render the frames which have changed :)
Cheers,
Cliff
RealDeal posted Tue, 20 April 2004 at 11:20 PM
I would suggest you try rendering to a different codec; most computers have cinepak, try it at 100%. I used to get this a lot.