I've been away for a couple of weeks. Of course the first thing I did when I got back was check the CL site to see if SR 1 had been released. Lo and behold, it had!

So, what's the verdict? Does it work? Does it break anything when you install it?

Well, I don't know about neone else but SR1 didn't coz ne probs for me. Well, I'm a noob so I don't use a lot of features of P6 neway :) But it doesn't wreck anything:)

There were some complaints, and one person said it rendered his P6 unusable, but for the most part the consensus seems to be that it works. I've had no problems with it.

It's fixed certain aspects of the memory bug for me.....which is great.

Although one should note that the official position now is that the "memory bug" didn't exist -- but rather that P6 sometimes gave out-of-memory errors when it shouldn't have.

:/

From a programmer's point of view, that's a significant difference.

But speaking from an end-user's point of view -- that's a distinction without a difference. The functional effect is the same either way.

To me, it'll always be "the memory bug"......of unlamented memory.

So back to your question:

Yes, P6 SR1 works. And it works very well.

I'm at least 93.27% satisfied.

E-frontier did an excellent job.

P6 SR1? 5 stars. Or 4.85 stars rounded up.

Message edited on: 06/02/2005 15:18

I didn't have a chance to download it until Tuesday, but now my dsl connection is back again. I'm satisfied with the SR1, I'm even able to render the huge scenes I couldn't do before. Well, except for 2 of them, but I don't think that's a Poser 6 problem. Trying to render a scene with 10 Mike/Vicky's in it with clothes and all high res textures all over 2000x2000 (some up to 5000x5000) on a 1Gb machine just isn't a good idea at all. I'm wondering why these content creators even use 4000x4000 and larger textures sizes at all. So after rescaling the textures a bit, the scene just rendered fine.

Thanks for the reviews. I've installed it. (And it didn't re-install CP. Yay!)

But..."no memory bug"? The problem wasn't the "out of memory" error messages. It was the way P6 would nuke the whole file. There is no way error messages, legitimate or not, should do that.

I'm wondering, how do you get rid of CP in P6?

The same as in P5. The instructions are exactly the same.

Thanks, didn't know that.

I got a couple of messages when I tried to render a scene in P6 that mentioned not enough memory or something like that. I reduced the texture sizes and lowered the buckets and the scene rendered just fine. I've seen here on Rosity a screen shot of an out of memory message that someone got and the person said their file was "nuked". I never got that message...ever. The one I had was different. I never had a file nuked by the non-SR1 P6. I have wondered about all of this because it almost seems there were actually TWO DIFFERENT "memory bugs" instead of one. Just so everyone knows....I run Win2K and I've got 512MB of memory.

Just so everyone knows....I run Win2K and I've got 512MB of memory.

That's probably why you haven't experienced the memory bug. It affected mostly people with more than 2 Gb RAM (system and virtual). Though usually more RAM is better, in this case, it wasn't. :-/

One memory problem left for me. I have a not really big scene with 7 characters and only 2 of them in foreground with bigger texturesizes. The others use special lowsizeversions. 3 Charactes are lowpolygon too. I created a kind of cave where all happens inside. The cave mostly use P6 shaders for background. If I try rendering it, Poser tells me that I have not enough memory... Yes? Have 2 GB RAM + 4 GB swap. I save the file, close Poser, start Poser, reload scene. Wow, yet rendering without any trouble. What does that tells us? There is a memory problem left. Kind of memoryleak maybe. If I yet move characters and start rendering after it again...same information about not enough memory.

Thomas

randym77, I always suspected that it was a 2GB RAM problem. I tried duplicating it just playing around and never could get it to trip. I'm not making the leap to 2gb until there are more programs (programs that I use) that can actually make good use of the RAM. Well, off to do some prog for CAD. YIPPEEEE sarcasm at it's finest

Although one should note that the official position now is that the "memory bug" didn't exist -- but rather that P6 sometimes gave out-of-memory errors when it shouldn't have. What a relief! 8-|