Apart from this P8 has been almost 100% stable.
haven't seen this error message before in prior versions of poser though.
Love esther

you are out of memory 

you should save your work and quit soon

Hm. I wonder if it has a memory leak.

Using IL? Try setting the Render Settings to Separate Process in the Preferences under the Render Tab.

 okay, thanks.
BTW I am looking forward to Sr1 as some of my old content (poses) isn't showing up.  I first started out in poser 4 as a newbie and I put all my content into one giant "bloated" runtime.  I have many more external runtimes, but the poser 4 runtime seems problematic for Poser 8 - perhaps because it is huge, or perhaps because it is inside my poser 5 folder which is inside my PoserAll folder.  Anyway I emailed SM and they say they are working on the problem.
Love esther

 actually I still get that new error message so I think it is unrelated to that render check box thingy.
Love esther

 Jus tried loading same things into poser 7 - no error messages.
Love esther

I have been getting this error too (alot) , with or without the seperate proccess checked ,
and the task manager shows P8 is using 500mbs to 1gb  out of my 4gb ?
sometimes you get to save your work (as the message suggests) sometimes it just crashes to desktop :(
I have it also say it cant load a texture because its run out of memory and in that case it was only using 500mbs out of 4gb ??
Also P8 uses 40% of CPU all the time no matter how long you leave it sitting doing nothing :(

Dynamic clothing is faster :)  but rerunning a simulation sometimes removes body morphs

I hope this is addressed in the 1st SR :)

My system is Dual core P4 3ghz , with 4gig ram , win XP pro , ATI HD 4850 512mbs

I think there might be a memory leak somewhere, I have it minimised right now not doing anything & it's memory usage is still creeping up, it started at 38Mb & while I've been typing this it's crept up to 154Mb & still rising.

When the screen is maximised it's constantly running the processor at 50% but that goes to nothing when it's minimised. Roll on SR1. :D

 Same issue here...I only managed to get one thing to render (and sure, it was fast...but 9 out of 10 times I got the memory error or it wouldn't load the textures...boo!), and when it did - it only rendered HALF the picture.  Didn't give me any errors on that one, just...stopped.

I've reloaded the file in Poser 7 and its rendering away merrily now. I'm sure it will take longer this way, but at least I'll have something to show for it when I'm done.

Guess they don't call it the "Bleeding Edge" for nothing...LOL!

I'm kind of glad I'm not the only one this is happening to.  Now regardless of what I load in P8 I get that error, the textures won't load and I crash.  :(

My experience with P8 so far is that ti seems less tolerant to file paths and I know it is less tolerant and does not allow capital letters in extensions (the later has been reported to SM support). Try changing  search to deep.

Regarding the file paths make sure they are complete and correct. Easiest thing to do is open the file in a text editor and search on the letters .jpg to find them all. Had some older content where the reference did not include :runtime:textures: in the file paths and they worked in P7 and then PPro, that do not work correctly in P8.

If like me you have a large runtime you might not want to check every file by hand, Correct Reference & Correct Reference Pro will do the job in pretty quick time although the free version doesn't work with compressed files.

www.hogsoft.com/content/index.php

I've been using Poser 8 for about 4 days now and I'm also getting the memory error. Most times I can't save...I click ok on the error box and a few seconds later Poser crashes. This is happening on subsequent rendering (ie: the 1st render is fine, but by the 2nd or 3rd, I get the error message). Needless to say, I've been saving my scenes before every render.

Also, after the 1st or 2nd render, the library starts to stall. When I navigate to a runtime folder and open it, many of the content folders fail to populate (the question mark never changes to the number of files, so I can't get to the content). The only way I've seen to fix this is to close Poser out completly and re-open.

Now, I am on an older system with Win XP Home and with little harddrive space (until my newer computer gets fixed)...however, I've used Poser 6 on this system for over 3 years and have never had this problem.

Poser 8 renders a heck of a lot faster than Poser 6, though, so I'll keep using it. But it would be nice if it didn't crash from memory issues all the time. ;)

tell SM tech support about it, they need to know. I've reported it, but the more people do it, the more clear it get's that this is a bug and needs to be fixed.

You better take screen shots and keep a tally of what was in your scene at the time of death and your render settings. You will be asked what they were I'm sure.

Quote -
Also, after the 1st or 2nd render, the library starts to stall. When I navigate to a runtime folder and open it, many of the content folders fail to populate (the question mark never changes to the number of files, so I can't get to the content). The only way I've seen to fix this is to close Poser out completly and re-open.

Now, I am on an older system with Win XP Home and with little harddrive space (until my newer computer gets fixed)...however, I've used Poser 6 on this system for over 3 years and have never had this problem.

Poser 8 renders a heck of a lot faster than Poser 6, though, so I'll keep using it. But it would be nice if it didn't crash from memory issues all the time. ;)

I'm on a quad-core 3gb ram system (Vista Home Premium) and I get the dodgy library after a while of playing with different scenes or renders. Sometimes closing and then re-opening P8 doesn't always work for me as I still get libraries with question marks, no matter how many times I hit refresh, so I end up restarting Windows then restarting P8. The library is a nice idea, I just wish it worked better/all the time.

Quad Core
4 Gig DDR2
1.5 Terrabyte HD
Nvidia chipset
Nvidia graphics card

 i find with the question marks on libraries (I'm on a mac) if you just sit back and wait sometimes eventually they slowly disappear and become normal folders.
Love esther

Hello

I read a lot of post about the  memory problem, but nothing about the solution!
anybody can resolve this problem?

Hi Karayo29,

I got a little help from Bagginsbill at another thread but for some dumb reason I can not find the thread anymore. It is under my user name but I'll be damned if I can find it again.

Anyway, something that Bagginbill said that helped a little was"I bet your min shade rate is set to .5 or less. BIG mistake".
So, when I went to render a picture that had been giving me a LOT of trouble again, I first set my preferences in Auto then switched to Manual and chose "Aquire Settings From Auto" then - still in the manual render screen - I went down to the setting for Min Shade Rate and bumped it up from .5 to 1 and low-and-behold I was finally able to get through a high uality render and save it before Poser 8 crashed trying to go back to the Pose window.

My knowledge is limited so I am not really sure what I was doing by adjusting the Min Shade Rate but it worked.

I am still getting crashes and just finished submitting a help message at Smith Micro with ALL my sytem specs included. Hope I get some help.

I will post to this thread if anything significant comes of it.

 I have a scene, it is a very big scene, but it will render in poser 7.  In poser 8 I get that message and I saw that thread to which you refer so I tried setting the min shading rate to 1.5 and then even higher but it didn't help.  Still crashes at render and sometimes on loading the scene - seems random which one.
Love esther

OK everyone. I have been corresponding with Smith Micro and have learned that P8 has a known issue with having more than one runtime that starts with the same name.
What this means is that if you, like me, imported your p7 runtime using the "add library" option and you now have both a Poser 7 library and a Poser 8 library it will cause problems.
The tech at SM said the following:

"There is a known issue in which Poser 8 experiences problems if there are is more than one runtime that begins with the same word. In this case, you have two runtimes that begin with the word "Poser" (Poser 7 and Poser 8). The engineers are working on a fix for this, but a temporary workaround is to change the names of the directories so that the directory containing the Runtime folder does not begin with the same word as any other one.

So, for example, you can rename your C:Program Filese frontierPoser 7 folder to C:Program Filese frontierA Poser 7. That way, one runtime is named "A Poser 7" and the other is named "Poser 8" so that both runtimes don't begin with "Poser". You will need to re-link your "A Poser 7" runtime back into the Poser 8 library, but after doing so, that should hopefully resolve your issue."

 or you can wait for the next SR they just told me - I have 100s of runtimes starting with the word poser.  I would run out of alphabet and some of my old pz3s probably wouldn't open anymore.
Love esther

I'm not going to rename my runtimes because SM messes up things. Renaming is a bad thing, as estherau already stated. I did that once (after a crash), did name all of the runtimes as before and now all of my poser file backups are worthless.

I'll wait for SR2 to see of that fixes it. Since I'm using Dimension3D's XL, I'm not getting the " you are out of memory you should save your work and quit soon" anymore. I've switched off the P8 linrary completely, that seems to help a lot. The not found texture error I've bypassed since Poser Pro already, by copying (not moving) the textures that cause problems into the P8 folders.

 really?  that fixed it?  How do you switch off the library?
Love esther

 I keep getting please locate "No_Map" error message

 haven't seen that one - yet

Quote -  really?  that fixed it?  How do you switch off the library?
Love esther

Start stop P8 library
Flex On/Off by Dimension3D

http://www.renderosity.com/mod/freestuff/index.php?user_id=288865

Simple instructions. Easy to revert if you want to remove it from your system

FYI, I don't see what some of the Win people see on my Mac which I know you are on. They claim even if the lib is idle it is chewing up resources. Granted I have it off using this tool as I now use XL to as a P8 library replacement

 thanks - well I succumbed and just this  minute bought the XL script.  so now I will try turning off the library and see what happens  I suppose.  thanks for link.
BTW have you tried D3D other script for manipulating lots of objects at once. it says untested on mac but doesn't say it definitely won't work??
Love es

 okay I loaded in the files as per instructions on the flex script and it says this in the readme "In the library palette, there will be an additional menu bar with "Start" and

"Stop" to activate the flex library and to turn it off again."
but now all I see instead of my previous library window in poser 8 is a blank white library window and no on and off button.
Love esther

 nope I see I did something silly.  should work now.

 this XL library thing looks very nice.  nice big thumbs and fonts.  Works quickly.  very happy so far.
Love esther

Now go to window and deselect libraries or press shift+ctrl+b and the start menu with the 'adverts' should be gone also, giving your parameter menu more room or you can place another menu where the library used to be. Personally I prefer the parameter menu getting more room, it's way to small by default, the library get's in the way.

 good idea aeilkema! thanks.

Quote -  this XL library thing looks very nice.  nice big thumbs and fonts.  Works quickly.  very happy so far.
Love esther

Curious, I am on 10.6.1. On your system the display order of the thumbs is left to right or up and down?

Thanks. the thumbs on Windows are left to right and then wrap to the next row. Just like the previous versions of poser. On Mac's it is down then wraps to the right. I have reported the bug in the wxpython Mac package to SM, but wasn't sure I was the only one with this problem.

FYI, another correspondence with Smith Micro:

I wrote:

"BTW, I have another issue with P8... When I try to change the background color via DisplayBackground Color ... I get a black background regardless of what color I choose. Say I choose white ... I get black. Then I can not even go back to the difault dull grey. It stays black until I close Poser and re-open it. What is causing that?"   Smith Micro wrote:

"My apologies for the trouble that you are experiencing. You're right, there is a known issue with selecting the color from the Display > Background Color menu. The engineers are aware of this and are working on it.

In the meanwhile, you can do the same thing but avoid this particular issue by:

1. selecting the Color tool, clicking on the background, and selecting a color, or

2. go to the Material Room and click on the Advanced tab. Select the Background as your active object, and change the color from the BG Color node."

Quote -  I keep getting please locate "No_Map" error message

You get that when who or what created the file didn't do it properly (several incorrect variations were covered by P7SR2).

The correct form is NO_MAP, but ":NO_MAP" and "NO_MAP" should be accepted.

Quote -  I keep getting please locate "No_Map" error message

 It is because vendors don't check their Poser file scripts with CRPro for getting their work right. They don't have a clue that lines like  :NO_MAP or "NO_MAP" always have to be   NO_MAP    - so it's not a Poser bug.

After loading your items that give you the error message check the specific files for it. You have this error in Vue and other software too if you don't correct the files.

edit: oops. nruddock was faster.