The upper and lower blocks in this image were rendered from the same PZ3 loaded into Poser 5. The upper used the "P4" rendering system, default settings; it agrees with the way I built the scene, and agrees with how it looked in true P4. The lower block is the new impressionistic Firefly Render, again all defaults left as is. Notice the sexy curve on the left of the case, and the stylish omission of unnecessary clutter and details in the rest of the scene. Salvador Dali would be proud!

Is it draft mode or production mode for firefly? Draft mode has definite issues! I hope CL still has the receipt for firefly. They should get at least a partial refund for it!

I set it in production mode. Didn't try draft mode. Weird, eh?

Hey, that's great! Cool how it eliminates all those unnecessary details. Very clean looking.

Quite impressive, indeed! :0) BTW, I do not think that CL can get a "refund" for the firefly renderer*. I am not 100% sure, but I do not think the normal "laws" apply in this case. I think the best they can hope for is bug fixes/patches or, if they decided to pursue it, possibly some form of legal recourse due to its "less than adequate" performance. Of course, that should all be described in the agreement that CL signed with the company that produced the firefly renderer. If anyone has any insider info on this, it would be an interesting topic to discuss. (* I understand the "refund" comment may have been a joke, but I like to try to figure these types of things out.)

Maybe they could just be killed.

I believe Firefly is Curious own in-house technology. Bill

how about spending some more time playing with the settings instead of complaining about something you don't know yet how to use properly. Rob

A while back a construction friend of mine complained that having bought one of the new nail guns he was most disappointed with it. He then produced it from his tool box and I was surprised to see how beaten up the top of it was. I asked if I could try it. Upon plugging it in and driving a few nails my friend said "Goodness what's that noise?"

Its probably best to learn how to use a new tool before condemning it. Its very possible that your old method of working will require adaption"

LOL, Phil, Rob, its obvious that those "spot the difference" pictures never played a big part in your childhood developments. Lets hope that renderer tweaking isn't going to be a factor on whether entire scene elements appear or disappear in P5. ockham, most of the stuff that seems to have gone in the firefly render looks like they are bitmap images on squares. A look at the material shading tree may shed some light on whether P5 has done anything unusual in converting them to the new material format. Bill

I used to love spot the difference & where's Waldo too :)

For what we know this could be just hardware related. I have tried to reproduce two bugs re[ported on this forum and haven't been able to get them. When we have so many driver combinations it is very possible that it might not be Curious Labs fault at all. I'm very impresed of what I have seen so far from Poser 5, worth every peny.

yeah what systems are these bugs showing up on & what systems haven't seen the bugs? be interesting to know which processors have the most problems with poser5, my money is on Athlons being the "problem child" sorry to all those who use those processors if I'm wrong. Rob

all you guys missed the boat on this...take a close look at that pic....he has the GAIN set way too high...no wonder everythin is gone

So you're saying he should switch to TIDE, or ARM & HAMMER? I guess everyhting comes out in the wash.

Actually, at least one bug has been reported by several people - polygons not rendering properly in firefly draft mode. There's several posts about this. I included an example in one post and have some pictures on my web site showing different rendering types on different pictures, a few showing missing pieces. My specs: XP Pro, 512MB of RAM, 1.7Ghtz CPU, over 2GB swap space available. Installed P5 over P4.

Attached Link: http://www.renderosity.com/viewed.ez?galleryid=238876&Start=1&Artist=Catharina+Przezak&ByArtist=Yes

Been a while since I've heard of a processor specific problem at the application level. Unless it was something to do with one of Intel's FPIV bugs or something.

Looking at some of the later threads regarding the missing polygons in FireFly draft mode, I think unchecking the "remove backfacing polygon" box in the render options may work. Still waiting for P5 here in the UK, but this looks to me like the draft mode renderer is misinterpreting some of the the polygon windings, or more technically screwing up the vector cross product calculations. Bill