Right cmon guys, help me out here :op

This is my system:

ABIT IC7 MOTHERBOARD hyperthread enabled.
Pentium4 3Ghz cpu HT
Graphics= nvidia geforce 6800 ultra 256 meg
sound= SB Live 5.1
RAM= 3072MEG DDR
H/DRIVE= 1x200GIG & 1x120gig
ENVIRONMENT= WINDOWS XP HOME ADDITION SP2
PERIPHERALS= WACOM PEN TABLET, LOGITECH CORDLESS MOUSE.
DRIVES= ATAPI dvdRW & DVD ROM.
ViRtual Memory = MIN 1024 MAX. 4096
Processor scheduling = "Adjust for best performance of: PROGRAMS"
Memory Usage = "Adjust for best performance of: PROGRAMS"

I am trying to improve the capabilities of my machine to render poser5.

I have been pushing it and pushing it to the point where I am trying to render 7 version 3 characters in a scene with plenty of scenery, eg walls etc.

I am trying to render in poser 4 mode into a window of 1024 x 768 with 72 pixels per inch. with everything selected except shader nodes.

When I open the file and view task manager the ram used goes up to around 900 meg.

When I render the ram usage goes up to 1.82 gig then poser gives an out of memory warning :o(

This was when I had 2048 meg of ram.

So I bought another 1 gig stick of ram and now have over 3 gig.

Unfortunatly I am still getting the out of meory warning at the same place and it suggest allocating more memory to Poser ???

Any suggestions as to why poser wont utilize this extra 1 gig it now has available?

Thanks
MaRv

When opening the file

Message edited on: 11/12/2004 16:32

Umm. The "Out of memory" error can often be Poser's default: "I've just hit some sort of error. I don't have enough traceback to know what caused it so I'll call it a memory error". Perhaps, if you could post a screen-cap of the scene you're trying to render, and a cap of the render settings, some of the wizards here might have some ideas as to why it fails.. Cheers, Diolma

ViRtual Memory = MIN 1024 MAX. 4096 increase min to 2048.

Yeh, the virtual memory was on that before, and it didn't work, so I turned it down, LOL. Didn't make any differece though so I will change it back. I'll see if I can do some screen caps later and I'll post them :o)

same problem...help-me too! just one thing I don't know waht is that you guys mena when:' do some screen caps ' as English is not my mother language...:( someone before said somtehing about allocated memory for Poser (still using PPP with a pacht for memory from Curious Labs site) How do I do that? Do I have to make a special partition for Poser in my HD and then what? runnig with 1.5gb ram and got it too. poser runs extremely slow and freezes for nothing sometimes is like I have a old P2 with 10 mb of memory!

Sorry but for all 32 bit versions of windows the absolute limit to any program is 2 Meg, regardless of the amount of memory in the machine. Any program exceeding this limit will be unable to get more memory. So three options: - try it with a 64 bit version of windows, as far as I know there are no real experiences with this yet - render in layers, first render a background, put as a picture in the background and build it up this way - reduce requirements by using simpler models (reduced resolution) and/or smaller and less texture maps

Typo on last message. Should have read 2 Gig of course.

"Screen cap" = short-hand for "Screen capture". Many 2D paint applications have a facility whereby you can run the app in the background, run (eg Poser), then capture all or part of the screen as an image (which can then be posted here to allow us to see exactly what you are talking about). Paint Shop Pro certainly has this ability... Hope this helps, Cheers, Diolma

"Screen cap" = short-hand for "Screen capture".Right; Print screen! Thanks unhappily still not get exactly what jfbeute says about 'try it with a 64 bit version of windows, as far as I know there are no real experiences with this yet' what does you mean really with 32 or 64 bit?would you please be more exactly...? Like: 8bit 16 bit 32 bit color ?

About 64 bit Windows: Some of the latest processors (not the P4 I am afraid) are 64 bit processors instead of the usual 32 bit processors. Windows was traditionally written for the 32 bit processors. Nowadays a 64 bit version of Windows exits for thbose people that have the very latest processors in their systems. This overcomes the hard memory limit of 2 Gig per process (among many other things). For you this wouldn't be a solution as your processor isn't capable of 64 bit processing. 64 bit processing means thata in a single instruction 64 bit can be worked on in one processor cycle. This has nothing to do with screen resolution, width of the i/o pipe or the size of anything else in your computer, just the capabilities of your processor. Historically we went from 8 bit processing (the first computers, e.g. Apple II) to 16 bit processing (where computers really started, e.g. the original IBM PC) to where we are now 32 bit processing (when computers became useful, virtually every available computer). In the future (which isn't far away) we will all be used to 64 bit processing (currently available in main-frames and some rare PC like systems). Until then we have to live the current limitations.

Bugga!