After approx. one week of working with P6, this is how I now evaluate the program.

Have you ever seen an elegant, beautiful thoroughbred racehorse limping around in a paddock? A racehorse that has the potential to fly......if only its leg can be healed?

Well.....that's the state of P6 in its initial release.

So long as the task doesn't put too much of a strain on that leg -- like in creating relatively simple scenes -- then you've got a first-class winner.

P6 has given us a greater potential for realistic renders than any previous version of Poser can hope to match.

P6's interface is as smooth as glass. Library organization is better than ever. Control function is slick and sweet.

P6's rendering capabilities exceed the older versions by several orders of magnitude. I've been playing around a lot with IBL AO -- its got a few rough spots: but they can be worked around. It sure beats the way that they used to have to do it back in grandad's day.........a couple of months ago.

The program is so well designed that you could just cry.

So......that lame leg?

No doubt about it -- the well-known memory bug is a real letdown in an otherwise rosy picture. A fly in the ointment. A pimple on the beauty queen's face.

It's quite discouraging to be riding a superb horse to victory, only to have him come up lame in the final stretch. And until Curious Labs comes up with a service release fix -- that's the situation with P6.

I've created several scenes that I can't render in P6. The memory bug kicks in every time. With 3 mil figures in a scene (2 V3's & 1 M3), plus clothes, hair, background props, and a textured room.....on an IBL firefly render -- P6 just can't do the job. It's a thing of wonder with lesser scenes. But it can't hack it on the big ones.

P6 chews right through my 1.5G of physical memory, and then bombs out of the render. I have to quit Poser without saving. I make sure to back up the .pz3 prior to attempting a render -- to avoid corrupting the file. Exiting Poser clears out the memory -- but it doesn't clear out enough RAM to render the scene.

I am going to upgrade my RAM to 2G, but all that will do is to ameliorate the problem somewhat. It won't fix it.

The renders that I can do are wonderful. Too bad that P6 can't handle the heavy lifting -- at present.

On the other hand, I fully expect that Curious Labs will get this thing fixed.

Soon, I hope.

In the meantime, I'll keep creating complex scenes in the belief that SR1 will enable me to actually render them.

CL needs to work on that leg.

Then this horse will be able to do what he was born to do.

Message edited on: 04/06/2005 15:09

word. ^_^

I have to say that I agree with every word you said Xenophonz! I couldn't have put it better myself! thefixer poser coordinator

Have to agree. I loaded up one of the Winter Queen sets, just that and nothing else, cranked the render settings up to maximum in the auto window, and P6 fell over with the memory bug. Not so good, really. Okay, I can get round it by turning down the render quality but I shouldn't have to on this 2Gb machine. Other than that, I really like it.

agreed as well...same deal...and I'm not even getting a DAZ mil dragon with temple to render... SSS seems to make it worse.

Well put, Xeno. :] Fish

I also agree.... It worries me that they are talking about a "Content" service release. How about a "functionality" service release ? Apart from the memory bug, I've encountered a couple of really kooky bugs so far in the 2 days that I have been using P6. I hope that they read the threads in this forum.

Agreed...I'll keep working in P5 till this gets sorted out. Also holding off installing till V5I gets the ability to import P6 Items.

Message edited on: 04/06/2005 17:13

its amazing to me that so many people do not exhibit these problems. What is the significant factor that allows one system to work and another to fail ?

Yeah, here's a few more. I've been able to work around them but they really should be addressed. Thumbnails disappear when going to the material room and re-appear when I refresh the library. Interface locks after a render after switching from another application. I have to switch to a different camera angle and then back to main. Luckily I know my shortcut keys. Again after switching back after a render, the scene sometimes goes blank in openGL mode. Workaround: Go to render settings and then go back - all is ok. Sometimes P6 doesn't want to make a thumbnail when saving to the library but I've seen this in Poser 4 and up. Sometimes I get an extra "application" in my taskbar which is the libary palette. Happens in P5 too. Interface locks when loading a figure and the face camera is being used. Not and issue with earlier Posers. I think that's it here ;)

Thanks, folks......

I recognize P6 for the splendid program that it is -- or rather that it can be -- once CL gets this memory thing taken care of.

What is the significant factor that allows one system to work and another to fail ?

I doubt that anyone can answer that question with any degree of accuracy. There are simply too many variables involved with PC's.

Of course, a quick answer would be that most likely around 87% or so of Poser users never attempt complex scenes. And therefore they never activate the bug.

It worries me that they are talking about a "Content" service release. How about a "functionality" service release ?

Yes, that concerns me too. Content releases are just dandy.......but I'd much, MUCH rather see this memory bug dealt with before they spend too much time fussing over Jessi's rigging.

I hope that they read the threads in this forum.

Me too.

Xenophonz is wise.

Has anybody experienced this one? When I do a render with Vicky 3 using occlussion lighting, sorry Jessie is too damned ugly right now, and like everyone one else hits the memory bug and get the, "Can't load texture file", Poser 6 replaces either the face texture, or parts of the face like lips or eyes with the texture it was using for the lighting. When you try to reapply the face textures, you still get nothing until you remove all textures from the figure and start from scratch? This has created some very bizzare renders. I have also found that by turning my bucket down to 10, I can usually bypass the memory bug. This also increases render time by three fold. I found this mysterious problem after rendering a scene for 13 hours and finally got to the head of the figure and about threw my keyboard through my lcd. The initial low res render came out very nice.

After two weeks of use I have regretfully concluded that poser will remain A very nice previsualization app to stage INDIVIDUAL FIGURES for render in ANOTHER PROGRAM!! in my case Cinema4DXL from Maxon. I love the Open GL previews and the cloth room is way faster. but i dont dare add 3 point lights( one rim one key and one fill) and render anything more complex than a nekkid vicky2. and god help anyone trying to render a detailed set peice like"RDL7" from sanctumart. even scene that will render are way too slow for me as i have been spoiled by C4D hybrid render engine and yes to HELL with jessie's stupid hands!!! fix the memory bug.

I don't know, I've been dealing with the render "bug" crap since Poser 5 (including SR4). The only Poser that could render even a relatively (2 or more figures) large scene was Poser 4. Are they actually going to fix it? That was 1 question I posed during the pre-release hype (asking for an actual answer).

Okay, so if we set up the scene in Poser then export to another program to render, which program renders the best with the least amount of headache? Vue? Bryce? DazStudio? Lightwave? Maya? Cinema4D? 3DStudio? Carrara? bB

Shade? Maybe that's why they threw it in? (haven't played with it yet...)

The Glue Factory is around the corner!!

Vue seems to work rather seamlessly...

Netherworks, I get a variation on the last error that you report. That is, if I load in a new figure with the Face Camera active, it points at the figure's feet. If I flick to Main Camera and back to Face Camera (Ctrl-m, Ctrl-=), it fixes it. Andrew

"The only Poser that could render even a relatively (2 or more figures) large scene was Poser 4."

Completely incorrect, I can have oodles of mill figures in one scene in P5. I do have 2 gigs of RAM, and a properly configured system though.

I'm a bit dissapointed in the New CL that they let so many bugs slip thru... They really need to handle the patching of this software well, to keep the goodwill that they have earned with all that is good about P6 (WHICH IS A LOT BTW.)

It's a tightrope though... If they release a patch quickly and it doesn't fix enough bugs, people will jump on em. If they wait too long to release a patch, people will jump on em. WHEN the patch creates new unforseen bugs, they will get screamed at... Oy it's gonna be rough.

Message edited on: 04/06/2005 22:18

Attached Link: http://www.renderosity.com/messages.ez?ForumID=12356&Form.ShowMessage=2202061

" "The only Poser that could render even a relatively (2 or more figures) large scene was Poser 4." " "Completely incorrect, I can have oodles of mill figures in one scene in P5. I do have 2 gigs of RAM, and a properly configured system though." I've got 3 GIGS of RAM and a properly configured system also. Are you using clothes, an environment (mine tend to be detailed, buildings, terrain, plants etc) global lighting?

and this is differant than the other 500 posts because? :)

Just wondering. ;)

fyi: Did y-all see that Steve from CL posted that they released the content fix. At least that part gives us stuff to chew on. P.S. This isn't meant as a "smart a$$" post. XENO, you have been incredibly possitive throughout the whole P6 release. Posters like you make the forums a good place to visit

Message edited on: 04/06/2005 23:10

*and this is differant than the other 500 posts because? :)

Just wondering. ;)*

I am a guy that tends to call 'em like I see 'em.

P6 deserves every bit of praise that it's gotten -- and then some. And Curious Labs deserves praise for producing such an excellent piece of software.

But a big, black horsefly perched on top of the delicious bowl of gourmet ice cream can't be ignored.

XENO, you have been incredibly possitive throughout the whole P6 release.

"Positive" is the preferred way to do things. Negative should only be used as a last resort.

Curious Labs deserves our support as they get these issues worked out. I believe that they will.

When they do, I will gladly point it out to one and all -- but I doubt that they'll need me for that. And I will point out that CL has been vindicated against its critics.

Posters like you make the forums a good place to visit

Thanks, LawnDartLawnDart.......and you likewise. You are one of the few that always seeks to be constructive. That's not an easy thing to do in this environment.

I am not exactly universally loved, but c'est la vie.

It's the price of doing business in the forums.

Keep up the good work, LawnDartLawnDart.........

And I'll keep calling 'em as I see 'em.

Even when that means fulsome praise for CL. Or for DAZ. Or for Renderosity.

Besides, it irritates the chronic critics whenever someone does that. And that's always a Good Thing.

mathman, Netherworks,

Re #20 this bug existed in P5, I reported it on the very first P5 release, but it was never addressed AFAIK.

I used P5, and I never saw that bug before. I have never had a problem with this in the past.

Please stop beating this dead horse over and over again..... Don't see the point in this at all, CL is aware of the problem and this issue has been discussed in a number of threads (were you have contributed to also) before. As for the content fix release, they've promised that right after the initial release of P6 already so it's about time they've released that one. Give them some time to fix the other problems.....

As for the content fix release, they've promised that right after the initial release of P6 already so it's about time they've released that one. Yeah, the 1st content fix is already out there for anyone willing to sign up for content paradise.

Please stop beating this dead horse over and over again.....

Oh, but the problem here is that the horse isn't dead. He's very much alive. And a fine animal, too.

He's just in need of some work on that leg.

"Beating" isn't what's going on here. "Coaxing" is more like it.

Don't see the point in this at all, CL is aware of the problem and this issue has been discussed in a number of threads (were you have contributed to also) before.

Yes, they are aware of the problem. And they are working on it. As I pointed out several times in this thread. ;-)

And yes......I have participated in several threads on the subject already.

I will continue to do so until such time as the problem is solved.

Thanks to Curious Labs for the content updater. Message edited on: 04/07/2005 10:59

This forum is for the discussion of issues related to Poser. I'd say that a major memory bug constitutes a legitimate topic of discussion.

I will continue to do so until such time as the problem is solved.

When the solution happens, then I will give full credit where credit is due.

Poser6 + Content Update
1GB memory system.

WindowsXP + Norton + Poser6 loaded = 290 MB peak
previous + 1 WinterQueen loaded = 440 MB peak

Render Auto Min shading Rate 1.25 = 655 MB peak
Render Auto Min shading Rate 0.10 = 1.7GB peak

Both render finish ok.
Are those numbers the same for you ?