Hi all,

Just finaly got my Poser 7 to run properly after many alterations, thanks to you peeps in my other threads.

I have a new issue now, i just spent 2 hours setting up a scene with a few DM props and 2 characters. i took a couple of renders in firefyy to see what lighting was needed (size 800x800) everything looked great, so i thought i would change a couple of poses before i started adding some localised light, upon re rendering poser decided i didnt have enough memory to load the textures and proceded to close without saving...aaarrrggghhhhhh @#%$

Now i have just bought a brand new pc just so i could do more with poser as my old pc was arcaic.

This new pc is a Pac-Bell intell duo 2 quad 2.4Ghz Q6600, 8mb cache, 3 gig DDR2, 500 gig HD (400 spare) and an Nvidia GeForce GS 1500mb card.

How can i run out of memory ?????? please some one tell me, is it a cache thing ? if so can i empty it between renders.

Surly i dont have to guess all my lighting etc and hit render once hoping i dont have to HOPE i can render again if need be after any adjustments.

Please help me ;)

Regards,

Vale.

welcome to poser!! this phenomenon is what keeps us all poser addicts!!

this is why this is the home of all the nekkid vickies,'cause if you add more than a nekkid vicky and try to render it in poser, you get that memory message.

now you can start haggling with poser as to what stays in that scene and what goes, or you could export it to Vue or carrera, and actually render it.

I have that free version of Vue.

Is there a tutorial around on how to export a scene from Poser and load it into Vue and render it?  I've tried looking at Vue and the interface freaked me out completely and I uninstalled the program,  LOL

If there was a tutorial around that showed how to import a Poser scene and render it, I'd give it another go.

hahahah cheers vince, that fills me with confidence ;)

I dont have Vue or Carrera but if i did can i carry on adjusting my scene within these programs or is it still hit amd miss in poser ?

Surly this memory thing can be empited ? i can do 2 maybe 3 renders depending on content and its fine, its only after lots of adjusting and rendering it runs out of memory, now when it closes (crashes) and i restart i can do 2, 3, 4 full renders again untill its "full" so on that pretence surly i can empty this memory thing manually ? no ?

I am hooked mind ;)

There are lots of threads on reducing memory usage here. I saw one yesterday. This is the name of the game in Poser. We use BIG textures and it takes some experience to make things work. It does work though.

@Acadia:
About getting Poser scenes into Vue:

• start Vue, you'll get an empty scene.
• choose File->Open and browse for your .pz3 file.
• Vue will ask if it should import the entire animation (pz3 files usually contain 30 frames, so they're animations) or just a single frame. In case of a still image, import the single frame (usually frame 1).
• If Vue asks whether to enable reposing in Vue, don't enable it. It'll take loads of memory.
• Same for Poser shader trees, it'll take loads of memory, and when rendering, Vue will invoke Poser to render those parts. So you won't have any advantage of the Vue render capabilities.
• Import meshes as single groups.
• Enable "collapse identical materials".

I usually save out the individual objects as Vue .VOB objects, then start a new scene and recreate the imported scene by loading these VOB objects. VOB objects are far less resource intensive than hosted Poser objects.

Vue doesn't import camera settings, and since Vue uses a different coordinate system (z=up instead of y=up), you can't just copy the values from the main Poser camera. You'll have to set the camera position by hand (trial and error).

Materials might require some tweaking to render well.

Thanks so much :)

Some things that help in Poser 7:

• install a 64 bit OS (Vista 64 bit or XP Pro 64 bit)

• add more RAM (only useful if you install a 64 bit OS)

• NEVER use the automatic settings of the Firefly renderer. Switch to manual settings and tweak there.

• Don't use full quality texture filtering, it uses more RAM than fast filtering or no filtering. Setting the filtering quality for each and every texture map node is a royal pain, my TextureFilter script in freestuff can help.

• Use "Render in separate process"

• Last but not least (actually, the most important tip): SAVE BEFORE YOU RENDER. If the render fails, quit Poser, restart Poser, reload file, render again. A decent chance it'll render OK.

Theres a setting somewhere to dump the texture cache . I find it easier to save the scene , and restart Poser. Also check that you have lots of virtual memory available .

Look at your texture sizes too. I run most of the Daz stuff through a batch converter to  size them to 50% or even smaller . I then use those lower res images if its a background item .

you get a lot of 3000 x 3000 x 24 bit color images and memory goes fast.

You can try just minimizing Poser before rendering, it's quite a bit quicker than closing it and re-opening it and forces a lot of memory to clear.

For the record,  Carrara handles memory issues a lot worse than Poser 7.   It's just as much of a memory-hog, but  can't cope with anything more than 1.5Gb.   I  tried to build a scene in Carrara with Miki 2, Sydney and V4, but the third character was more than Carrara could deal with.  Poser 7 handled the same content without a hitch, because it can exploit twice as much memory as Carrara can.

In this particular case for Poser, I think pjz99's suggestion about minimising Poser before a renderi  is the best place to start, but reducing texture sizes, as per markschum, may eventually prove necessary.   Before that, it may be worth rendering the scene in segments and assembling it in PS, PSP, or an equivalent.   Another technique is rendering the scene without shadows and then rendering the shadows by themselves.   Again, that requires something like Photoshop to put the scene together.   Some people swear by that technique;   I tend to end up swearing at it, instead, but it may help.

Actually morgano that is not strictly true, the 6.1 update to Carrara has significantly improved its texture and memory handling abilities.

I have been able to cram an incredible amount of items/ figures into a scene(v4,v3,a3,sp3,m3,d3, all clothed and texured and with hair,stonemasons backstreets, mill dragon 2, that big ship by faveral etc) without Carrara Out of Memorying.

There was more in the scene but I cannot remember what else I stuck in, Oh yes apollo was in there and uzilte sports car. and still carrara kept going. it also rendered at very high quality settings with GI enabled.

Poser 7 can handle quite a lot. Right now I'm rendering a scene containing:

• 15 human figures with transmapped hair;
• interior with several pieces of furniture;
• a hires tree visible through the open door;
• several metallic objects with raytraced reflections;
• several glass objects with raytraced refractions;
• most materials have displacement mapping applied;
• skins have material nodes with SSS;
• 3 point lights with ambient occlusion and blurred shadows
• 1 IBL light with ambient occlusion as a fill light
• 1 infinite light without shadows, specular only

Most figures have their original texture maps, some of the 4096x4096 maps have been resized to 2048x2048.
Smooth polygons enabled
2 raytrace bounces
Min.shading rade 0.50
3 pixel samples.

The scene file is over 600 MB on disk.
Maximum memory usage in Poser itself, 2.5 Gb. Works in a 64 bit OS. Would also work on XP with the /3GB startup switch set (XP Home and XP Pro, but doesn't work for XP MediaCenter).
Rendering using separate process: the FFRender process uses 2.1 GB.

Acadia - Try & persevere with Vue if you can, it's really worth it. Don't be afraid of the interface, because you're so used to Poser it'll just take a little getting used to. It will become a breeze after time. Try rendering using Global Radiosity or Global Illumination, you'll love the realistic element it'll add to your work. It may take longer to render than in Poser but it's just in a different league.

If you come across any problems drop over to the Vue forum, we'll help you out there.

4/5/08

Is there a way to "exchange" XP Multimedia for XP Pro without doing a complete reinstall of XP Pro? I have no actual need for the Multimedia "features," but I would love to be able to use the /3 GB switch.

LMK

Hi all,

I have the same problem, middle in a render, it does EXIT.....??
and when I call it back, it's loads very slowly, never had the problem before....it does it sind two weeks or so....

At General preferences>render>
memory: Adaptive bucket size
Adaption threshold=0.375000
Memory limit buffer=28

At Render Settings
(auto Settings)
for the final Render, the slide is at "Final", some time with Smooth polgons on.

and sinds a day or 2 it loads very long 5 to 7 min.....? never had that before....and I allways have 'big' renders, with on problems....

I do this with a:
PC: mobiel AMD Athlon(tm) XP-M 2800+
Speed: 2.13 GHZ, 992MB
(not on line) can't do the up-dates...
so move the file with memory-stick...

help...!!

I'm thinking new install....??

Quote - You can try just minimizing Poser before rendering, it's quite a bit quicker than closing it and re-opening it and forces a lot of memory to clear.

Another trick is to switch your display preference to cartoon, minimize, and then maximize. This will dump the texture maps. I usually do this before rendering.

There are settings to only save 1 or none prior renders in cache, it's in edit/ general preferences/ under render. also there are settings to reload textures, or reuse shadow maps thats under render I don't know which uses less memory. Something else you might do is to empty your undo/redo cache its in edit/general preferences/document.

I have mine set to where I only save one prior render and I empty my undo/redo cache and I usually don't have any problems.

Hope this helps.

The render cache has nothing to do with memory usage, the prior renders are saved as uncompressed bitmap files on disk.
The undo/redo cache can be a culprit. I've set it to remember 5 actions instead of the default 100, and it sure saves quite a bit of memory.

Another thing I sometimes do when I am going to do something large is go into windows task manager and shut down the processes that are running that I don't need, there are lots of them that run all the time and take up memory that you don't need running.  Also do you have a large paging file?  I use an 8 gig paging file and that helps enormously, it gets used as ram sortof. thats actually a couple of paging files broken up on different drives.  It's best to set up your paging file on the drive(s) that does not have poser on it.

Okay, thanks for the tip(s), I'll test it.....;)

but...
can you explain this better: ~"Also do you have a large paging file?  I use an 8 gig paging file and that helps enormously, it gets used as ram sortof."~
I do not know of this 'paging file'....

and thanks for you'r time...;)

Yes, on your computer go to start/ control panel/ system/ advanced tab/ under performance click settings/ Advanced tab/ virtual mem click the change button/ select custom size and in the two boxs put 4000 and 4096 and save that setting.  Poser really needs that paging file. That's the largest paging file you can have on a single drive, if you have a second drive you can set another on that drive.

I almost forgott you have to restart your computer after you set up the paging file.

Here is some more really great info on setting up that swap (paging) file that I did not know when I posted here.

http://www.renderosity.com/mod/forumpro/showthread.php?thread_id=2735390

I´m not sure if you have the same probleme as I have just had sometimes but when I also got this message, and if I click ok as long I get this message, than Posers renders without any problemes. (Poser7) Try out ;-)

@ phantom3D: Thanks for all the tips.....I'll test it....

your tip about "virtual mem" was the best tip, all the time I 'run' on half the 'space'....very cool....!! now it is full power (sortof)....;)

(sorry from my poor englisch...;)**
**

@ Sivana: it does not work here...but thanks...;)

BenBischop:

You're welcome, I hope it works for you.

Your english is doing fine, I should learn to write your language at least as well.

Cheers,

Mike (phantom3D)

Thanks again for all your inputs, I have resized my page file to a standard recomendation of 1.5x my ram and i havent had any problems since. Just as a safe measure i also change texrture to cartoon and minimize before render.

I am sure there are many more little tweeks to learn but this has given me some stability to work with.

Also, thanks for the simple idea of saving my work. doh !!!!!!!!! i tried to save before but couldnt get it to work on upload...turns out i have to write .pz3 after the name......how stupid do i look, but there it is for anyone else that might be as simple as me ;)

Thanks again peeps.

x