1.) Where the %&^ is P6 SR1? Except for the major memory problem and a couple of other minor glitches, Poser6 is so almost there. It is SO FRUSTRATING having it crash all the time. 2.) Who are all these folks who say Poser 6 works perfectly on their system? Are they CL stockholders? Or ... ? 3.) And why, really, is Blackhearted holding his head in the MOTM photo? A), He is suffering for his art?; B), His brain is so big he has to keep constant pressure on his skull to keep everything in place?; C), The photographer simply thought it looked Cool?; D), I know, but I'll never tell.

3)it's either that a) years ago he accidently superglued his hand to his head and was too embarassed to get it taken care of or b) because he is going bald and doesn't want anyone to know. am I close?

1. Work perfectly? Not really but I get it to work if I take my time and don't get carried away with all the bells and whistles. I do not have a hot to trot super duper gaming machine with all the latest technology. Only a piddling 2.4 P4 cpu with 1 gig ram and an old Nvidia Gforce 4 mx 440 card with 64mbram.

Except for the major memory problem and a couple of other minor glitches, Poser6 is so almost there. Yep.

1. • nickedshield, I wish I could say the same. With 2 gigs ram and a FireGL 128, all I have to do is load 1 Mill figure, apply a texture and do a few lo-res software renders. After about the 3rd render, I can generally forget saving the scene (or doing anything else but exiting the program). I usually will get a nearly out of memory error (which apparently really means I am completely out of memory). The only way I can keep things working most of the time is to reboot after every render. Nice, eh? So when I come across a post (and I have come across a few) claiming that someone has had no trouble with Poser 6), I'm rather flabbergasted. How can that be?

XENOPHONZ, Poser 6 is such a pleasure to use, or it would be. That's why I find it so frustrating.

I have critized P6 rather hardly in former posts, but meanwhile i like it more and more, even if the bugs are still there. But i have rather complicated scenes, a lot of figures, background stuff, lights, and i think that people who are doing more portrait- and single figure pictures will rarely run into the memory bug. Furthermore it seems to me, that P6 works much better with scenes build up from the scratch in P6, but with scenes imported from P5. Another point: to work with P5 and P6 without too much frustration you should carefully read the manual-chapter or tutorials about the render-settings. Things like the 'minimum shader rate', 'pixel-samples' and so on have an enourmous effects on quality, speed an stability of the firefly-renderer. And there is a third thing: many characters like V3 use rather dirty tricks to 'abuse' the poser-data-structure in a way, that most likely wasn't planned from the developpers (or maybe planned, but then stopped, because they recognized that alle those inner morph-chains were too buggy). It must be a hell for the programmers to look for bugs in structures, that they would like to throw to the garbage, only to keep the very popular products from a competitor alive ;-)

claiming that someone has had no trouble with Poser 6), I'm rather flabbergasted. How can that be?

A couple of likely reasons.

One reason being that many people never attempt to push Poser very far beyond the basics. The memory issue is probably either rarely or never going to affect them.

Another reason derives from.....as indicated in the header of this thread........the mystery of myriad PC hardware/software combinations. Different systems might achieve distinctly different results -- results affected by a set of factors that no one can account for 100%.

A problem comes in when certain individuals that aren't experiencing the bug themselves act all self-righteous about the issue:

"Well......I'm running Poser 6 on a 20-year-old Tandy.....and I'm not having any problems. Must be something wrong with you..........."

I just want CL to get out the fix. Then we'll have it.

Well, I AM one without P6 problems so far... My PC is only an AMD Athlon XP 2500+, 1Gig ram, Radeon 9800 Pro graphic card, so it's clear I'm NOT a CL stockholder (I would like it...). For now, I find P6 much more responsive that P5, expecially when I choose to end prematurely a render - it has not shown the annoying habit of lock up the prog if I hit the "Cancel" button... :P

XENOPHONZ, Poser 6 is such a pleasure to use, or it would be. That's why I find it so frustrating.

I agree with you totally.

I've stated as much myself in several threads on the subject.

The GREAT potential of what P6 could be.......with just a little more help in the memory management department........

I have critized P6 rather hardly in former posts, but meanwhile i like it more and more, even if the bugs are still there. Same here. And that's the inherent contradiction of P6. The aggravating combination of joy and annoyance. Love the program.......hate the memory bug.

Got no problems either, unless I do a huge scene, then the rendering bug shows up. Got an AMD Athlon XP 2400+, 1Gb ram, Radeon 9600 Pro graphic card. I'm no CL stockholder either, but I do love P6 and I'm very happy with it and don't find it frustrating at all. I wouldn't be suprised if the major problems are with people using high end systems.

1. I have experienced almost no problems and have never seen the "out of memory" error. Toshiba Satelite A45-s120 (laptop) 2.6ghz, 1gig ram. I havent exactly been pushing the limits as far as renders, but i have had it open for several hours 8-12 (with periods in hibrination) doing mid level preview renders periodicly while working on texturing a model i am making. Just an observation, I dont know if there is a connection or not but it seems to me that every person i have seen complaining about the "out of memory" erro has said that they have 2Gig of ram. I only have 1 and everything seems to be running smooth. read the responses above and there are others with only 1Gig and no reported problems.

read the responses above and there are others with only 1Gig and no reported problems. It's worse with less memory. Currently, I've upgraded to 1.5G. I'll be jumping it up to 2G in a week or two.

It's obvious that enough people are experiencing this difficulty to acknowledge it as a genuine problem. It's not a figment of our imagination. Curious Labs has admitted that it's there. If you aren't having this trouble, then that's great. But many of us are.

Well, for me, Poser 6 works better out of the box than Poser 5 did. I got the "out of memory" error once, when I had been rendering one character over and over for about an hour (for reasons not related to Poser 6). I would have gotten the same error in Poser 5 had I been doing the same thing. My problem is that I need to sit down and figure out what everything does. There is enough new that I find some things quite confusing. No problems with the new hair (I never got dynamic hair to render in Poser 5 - froze the program every time so I gave up on it) or the cloth room (fingers crossed). I'm not excited about Jessi who just seems like another model wanna be, but the guy is pretty hunky. I'm seriously thinking of removing Poser 5 from my computer system and keeping Poser 4 (because of Vicky and her breathern) and Poser 6.

But I understand everyone is having a different experience. It was the same with Poser 5.

Message edited on: 04/14/2005 12:25

I'll be jumping it up to 2G in a week or two. Maybe then I'll be able to render a couple of scenes that are currently sitting on my hard drive -- unable to be rendered because of the memory bug.

Out of Mem error just once with one sided square, custom created texture for that square, SP3 from Daz, Ivey texture for SP3, Eastern Mil Dragon 2, Eastern Jewels for the EMD2, 4 custom spotlights. The file did not corrupt. Changed bucket size from 64 to 50, rendered file in about 50 seconds. I've made quite a few changes to the file and have not encountered the Out of Mem error again. AMD 3000+, Win2000, 512MB RAM, ATI Radeon 9600 Pro 256MB video card. I'm not a stockholder.

this did bring up an interesting peice of information though. The 2 times that I got the Memory bug (and I have 1gb ram BTW so it's not just the 2gb people) I was rendering a p5 scene that I deleted out a light dome and added a IBL AO light. After 2 attempts I gave up. Since then I've only rendered scenes that I've built from the ground up in P6. I wonder if anyone else has noticed something simular, or is it just a coincidence?

Jumping back in with a few questions: I don't know if this makes any difference or not but before installing P6 I was reading other threads about P5 issues and how it's best to make it happy by installing to it's own hard drive. Since I blew out my secondary drive I just waited for the new one. I don't know if not installing the complete package has any bearing. I did not install the Legacy stuff or the non-nude stuff. Yes I have run into the memory bug on a very complex scene but by following the suggestions on the error splash screen I was able to complete the render by changing some settings. I agree with XENOPHONZ that a memory fix would be most welcome. Then I could set up the scene, select my rendering options without worrying whether it will crash or not.

"Well......I'm running Poser 6 on a 20-year-old Tandy.....and I'm not having any problems. Must be something wrong with you..........."

Piffle! It's running on a ZX-81 here; sweet as a nut.

Attached Link: http://fnproductions.net/graphics/tutorial/poser6/

Thixen, I recently took one of my old P5 images and deleted all the lights and replaced them with 3 point lights in P6. Worked great. That said P6 runs like a pig most of the time! It works fine with 1 V3 a couple of props and 3 or 4 lights, which is pants to me because I usually like 3 figures usually in my scenes. System: Pentium 4, 3.4 Ghz HT, 1 Gig of RAM and a 256 Meg ATI Radeon X600 graphics card. thefixer poser coordinator

No major problems here and NO memory problems at all. I have done a couple of big scenes and have used some of the newer functions Ambient Occlusion, etc. Pentium 4/2.8 GHz 2.0 GB DDR SDRAM 128 MB NVIDA GeForce FX Go5700 Poser 6 seems to run as good or better than P5 for me on this machine -- hp PAvilion Notebook. Best Wishes, Rance

My repeated posts on this subject have three objectives:

1. To "encourage" Curious Labs along towards a solution.
2. To inform others about the problem.
3. To vent.

I've stated this little history before, and I'll repeat myself again in this thread (it bears repeating):

Over the last years, I have mentioned a few things here and there about P5's rendering problems. Ultimately, I was forced to do all of my rendering in Vue. Because P5 just couldn't do the job.

So.......P6 comes along. Hurray! Now I can render my scenes natively in Poser........

This issue has been brewing for a long time.

They need to fix it.

One would have to assume that they know that and are working on it. Yelling at them won't make it get here any faster.

One would have to assume that they know that and are working on it.

Yes, one would have to assume this. Especially as they've indicated that it's so.

Yelling at them won't make it get here any faster.

You are right -- it won't.

That's why I'm not yelling. I can't speak for others in this -- but I can speak for myself.

What I am doing is engaging in a reasonable disscussion about a very real issue. Not the faked-up problem that some seem to think that it is.

If the problem doesn't get talked about, then it's likely to be ignored.

Which would be just dandy for some of those individuals who aren't personally experiencing the pleasure of the memory bug. At least, those individuals with an utterly inexplicable attitude towards those of us that are.

When the memory bug goes away, then I'll praise CL for their good work. Just as they already deserve praise for about 95% of what they've done with P6.

Once the memory bug is gone, then it'll go up to 99% - 100%. In the meantime, the issue isn't going to go away.

One would have to assume that they know that and are working on it. Yelling at them won't make it get here any faster. Unless it'll cost them income, they have no reason to fix it. Hasn't this same glitch been around since P5?

BTW -- I have no desire to join the ranks of the chronic Curious Labs bashers. Nor will I. But one cannot ignore crashed renders and courrupted files. It's not my idea of fun.

"Unless it'll cost them income, they have no reason to fix it. Hasn't this same glitch been around since P5? "

It's more prominate in P6, and it's already costing them income in the fact that there are a lot of people who would of upgraded, but haven't yet because of this ohh I just wanted to add that I do have pretty good faith in CL's ability to fix this, and I think by doing so P6 will probably be the first Poser that can compete in the professional dept seriously and not just lie on the fringe.

Message edited on: 04/14/2005 14:35

What makes a problem more challenging to solve is when it occurs with irregularity and inconsistency. I am not saying the problem doesn't exist. This isn't an all or nothing kind of thing. But why it exists at varying levels on similar equipment makes it difficult to create a uniform solution. Or I would think so. I was not posting my experience to say that any of you didn't have the experience you did. As with Poser 5, the program seems to work differently from person to person, and it doesn't seemed particularly to matter if one is experienced or a novice, with new and high end equipment or older models. That is what is interesting to me. But it must be frustrating for those looking for fixes.

It's more prominate in P6, and it's already costing them income in the fact that there are a lot of people who would of upgraded, but haven't yet because of this Some of us had the silly idea that after all the problems with P5, CL would make more of an effort with P6. I suspect they made quite a few sales of P6. (A lot more than they deserved.)

Curious Labs must have some clue as to what is going on. They are the ones who announce that the problem existed. And as i recall they anounced that they had identified a memory problem, after they had given the go-ahead to make the "final" CDs. so when they said go, they believed that what they were releasing had no significant errors/bugs.

But it must be frustrating for those looking for fixes.

Yes, it is frustrating.

I didn't get from your post that you in particular were holding out an attitude towards those of us with the memory-usage problem......that is to say: those of us that dare to talk about it.

Unfortunately, some others do seem to have such an attitude.

Once we get past that little bump, then we can -- as you say -- begin to discuss solutions.

sigh

At the moment, the only "official" work-arounds are:

1. Upgrade your RAM (not an option for everyone)
2. Turn off texture filtering
3. Lower your max texture size
4. Reduce bucket size
5. Turn off other bells & whistles in Poser
6. End unnecessary processes in Windows to free up memory
7. Save & exit; save & exit; save & exit; save & exit;.............................

If anyone can add to this list -- it would be appreciated.

yp6 I agree with you.

You'd better do: 'SaveAs & Exit', if you don't want to loose your work ;-)

You'd better do: 'SaveAs & Exit'

Yep. Over & over again.

The process makes for a very efficient workflow.

;-)

1. Memory leaks are not easy to fix. I know first hand. 2. Who are you? A DAZ stockholder? ;) 3. It's heavy?

Curious Labs must have some clue as to what is going on. They are the ones who announce that the problem existed. And as i recall they anounced that they had identified a memory problem, after they had given the go-ahead to make the "final" CDs. IIRC, it was the bad character joint setup they knew about after they started printing CD's but before everything was shipped (though they didn't bother to mention it until users started pointing it out.) Of course, no problem! Just sign up for Content Paradox and we'll get you the fix as soon as you wade through all the advertising and put your serial number in a few times! (People resented it the first time, well you have to sign up now if you want your product to work right!)

FYI: Curious Labs loves you. They would never hurt you on purpose. :) BTW: There are plenty of people out there that won't upgrade to P6 because insert excuse. If it wasn't the memory bug it would be something else. It's unfortunate for them. They are missing out on all the fun. ;) Boy, I feel fiesty today. LOL...

to know if recent download purchasers (since the character joint fix was released) still had to go to CP for the fix. If they didn't, that would indicate the bogus Jesse joints weren't a marketing ploy to force people to sign up for CP...

The content updater (the full one) has now appeared on the Curious Labs website. Seems like they just take a little longer to change things there (took a couple of weeks before Poser 6 was added to the register list for me)

Boy, I feel fiesty today. LOL...

You? What's the world coming to........?

They are missing out on all the fun. ;)

I've already said this elsewhere, but I need to say it again here:

P6 -- even with the memory bug -- is worth.....no, MORE than worth.......it's price.

Buy it, or completely miss the boat.

I can't stress the good points of P6 enough. They are wonderful.

But this wonderful program is dragged down by a flaw at the end.

Get rid of that, and you've got what Poser should be.

The content updater (the full one) has now appeared on the Curious Labs website. Seems like they just take a little longer to change things there (took a couple of weeks before Poser 6 was added to the register list for me) The link takes you to Content Paradise...

personally I think it's a Beer and stale popcorn nazi conspiracy to me. What-cha thinl Xeno is it the Nazis ?? :D :p

Everyone suffers from the memory leak bug, some just don't use the program in a way that exposes it frequently or have systems that are more robust in dealing with it. But it exists and until it is fixed it is a major impediment to doing anything serious with P6.

CL may have released a less buggy version in P6 than they did in P5, but they still risk being tarred with the same brush unless they fix this problem soon. At the end of the day, the customer will not forgive them if the problems still persist in a few weeks time, particularly as CL knew about the bugs when releasing P6. That fact will come back to haunt them unless they fix the problems soon.

Frequent information updates from CL as regards progress of the fix will re-assure customers. Silence will only increase the speculation and anger.

personally I think it's a Beer and stale popcorn nazi conspiracy to me. What-cha thinl Xeno is it the Nazis ?? Nahhhh. This has nothing to do with the TOS. So it's unlikely to involve Nazis.

Just out of curiosity, has any one sent bug reports to CL when they've encountered the memory bug? They can produce a fix faster if they know what systems, what hardware, what the scene consists of, etc. When programming for AutoCAD a couple years ago, we'd get reports of "a button doesn't work". That's great, considering we'd made about 120 buttons and no one reported which one was working, it didn't do us a lot of good. The more they know, the easier it will be to fix.

I noticed where the CL link took you too late to stop the post, and couldn't find this threat again, but then I often loose the thread

"That's why I'm not yelling. I can't speak for others in this -- but I can speak for myself. What I am doing is engaging in a reasonable disscussion about a very real issue. Not the faked-up problem that some seem to think that it is. If the problem doesn't get talked about, then it's likely to be ignored." ____________________________________________________ "Yelling" is when you put things in caps or in bold letters, which you did. I don't think anybody thinks that this is "faked up problem". I can't recall a single person accusing anybody of complaining without just cause. Furthermore, nobody's ignoring this problem. But the memory problem has been talked about to death, this thread adds nothing new to the discussion, and more complaining isn't really going to help. I think there's a point at which complaining becomes counter-productive. It reaches its saturation point and there really isn't anything NEW to be said. And, not that you're one of them, but I am tired of hearing from people who have an axe to grind against CL and want to proudly proclaim that they're glad THEY didn't upgrade to P6 because (fill in the blanks). Who cares? I said this back in the middle of the Poser 5 brouhaha and I'll say it again today. This is a ridiculously cheap, amazingly powerful little piece of software that's being held together by spit and glue. But the company has never abandoned it. They've managed to find a way to keep it going, and we have to have a little patience and faith, and give them our support. If you want a higher order of perfection and sophistication for two-hundred bucks (or less), you're not living in the real world. There isn't even one piece of software that does this same kind of stuff for the same price. As of this writing, Daz Studio does NOT do animation. And I've been using Hash Animator since back in the old Amiga days, and it's always been as buggy as the jungles of the Amazon on a hot day. Really, if you want a smoother ride, go pay more and get Softimage. And in the spirit of contributing something USEFUL to the discussion, I haven't seen anybody mention this, but the corrupted file-saving aspect of the memory problem seems to be somewhat tamed by dropping your display down from 32 bit to 16 bit, or at least it has helped on my system. Your mileage may vary. -jjsemp (who's REALLY feeling fiesty today).

why do peploe defend a badly constructed program ? 1. get rid of content paradise it's offensive to have it shoved on you rather then have a choice to not want it. 2. poser6 is not much more then poser 5 very disapointed by that and the memory bug curious labs knew about but rushed to sell the product anyway before fixing it. 3. 6 I don't use because it's real slow or it gives an annoying memory error, whatever happened to speed? Another thing why can't they make this program access multiple runtimes?