Here's a thread about this problem. There's also a workaround that works for me.
www.renderosity.com/mod/forumpro/showthread.php

I think the problem you are encountering here is the third point from markschums post. Hongyu's corset does not have the morphs you applied to V4, so it doesn't conform properly.
You could use the "Morphing Clothes" utility from Dimension3D here in the marketplace to transfer the missing V4 morphs to the clothing.

After you posed the figure make sure you apply the magnetize pose that came with V4 to the clothing to transfer the joint control morphs.

I have to say that SR1 solved most of the issues I had (PC with XP PRO SR3). Only problem I had was one crash when refreshing the library (not reproduceable)...at last now I can work (play?) with P8.

Ali Larter was also in Final Destination I and II  (Clear Rivers)

You're right. I didn't mean to be rude....but the only effect was, that the textures in Battlefield 2142 had to be calculated again...

Quote - > Quote -

I updated the Flash component with the recommended version shortly after getting Poser8. My older Poser version works fine so I wouldn't blame the graphics driver (ForceWare 178.13).

That's not a very good assumption. The reason drivers get outdated is precisely because things change. (Not saying it's a problem; just saying that because your driver is fine with something older proves nothing.)

Yes, but I don't have a display problem. If my car is leaking oil, I do not start checking the headlights.

Just updated to nvidia forceware 190.62 and have the same memory issues, crashes while trying to refresh the library etc. These drivers are usually updated quite often because of some sophisticated functions used by some new games. I doubt that Poser uses these functions.

Quote - Guys, let's not confuse memory use climbing while idle with cannot load texture. These are separate issues.

I know the texture failure dialog says it could be out of memory. That's not the problem for those who see it instantly. It's because there were some bugs in dealing with file I/O (a few actually) and they've been fixed. Let's see if SR1 fixes it.

As to the climbing memory, this is normal, although it perhaps scares you. However, you've noted that most if not all the memory is given back when you minimize. It is also given back periodically. This is memory being used to cache messages going between the library GUI and Poser. It is a normal consequence of using modern "managed code" where the programmer is not responsible for memory management - the system is. This is how Flash works. Every once in a while, a garbage collector runs and gives the memory back. I watched this very carefully for hours and hours. It is not a bug when it is working as it is supposed to.

That's not to say it is impossible to consume all of memory doing nothing. There are any number of components that could be buggy in this area. I've seen graphics drivers do it, I've seen out-of-date versions of Flash and IE do it, lots of things that are under your control, not P8's control. Not saying you've done something wrong.

Sigh - I have to go on and on trying to explain these technical things. I'm sure I'm becoming boring/insulting again to somebody.

Understood. Here are some more observations regarding memory usage and release.

When I start Poser8 up and load the SA Kitty Mass Production Figure from the content package into an empty scene, Poser has allocated 270MB of memory, after 10min doing nothing (and I mean nothing!!!), it has increased to 285MB, after another 10min it has reached 303MB, then a minute later there was a slight drop to 278MB and starts rising again.  When I minimize the app and maximize it, I get something <20MB (now it's reached 60MB while I was typing).

So my cars has a consumption of 21 mpg (thankfully not when in idle), and Poser has a consumption of 1.5 mbpm (Megabytes per Minute)

I updated the Flash component with the recommended version shortly after getting Poser8. My older Poser version works fine so I wouldn't blame the graphics driver (ForceWare 178.13).

One more question: The problem with Poser crashing while trying to refresh the library has been reported already by someone, right? And the 1px artifacts at the border of a render.

Thank you Bagginsbill and Tyger_purr.

I just reported my memory leak problem to Smith Micro. Even if I load a blank scene and do nothing, memory consumption of the Poser.exe process increases by 30KB/sec. I usually leaave my PC alone during rendering (watching TV). So, when you get back after 30min or so and move the mouse, the "out of memory" error appears, because Poser allocated a lot of memory even if it's in idle mode after rendering.

With my previous Poser version, memory consumption stays constant when I do nothing (as expected).

EDIT: Just to give you some idea. During the time it took to report the problem and write this forum post, Poser memory consumption increased from 17MB to 73MB. When I minimize Poser, memory drops again to 17MB and starts increasing slowly but steady...

Cool tip! I had the same problem.
But the name of the file is LibraryPrefs.xml (at least on my system)

I also start to get frustrated:

• Library crashes Poser almost every time I try to update within Poser.
• "Cant load texture. Bad file" - message after rendering (without a problem) causes a crash.

EDIT: I think these are errors are mentioned here quite often and this should definitely have occured during beta testing as well.

Beautiful  dress...Thank you!

I had both behaviours: Poser disappearing instantly and the "Poser encountered an error" (or similar, I have a German version of WinXP Pro Sp3 8-) and the error details in the first post. This occured even if it was not a top level runtime folder.

I also installed the latest version of the Flash Player after I installed Poser 8.

Adobe Flash Player version 10.0.32.18

You could now adjust the transmap to compensate the distortion. It's a bit of try and error process.