Attached Link: http://www.atomic-knights.de

I am a bit new to Poser 5. I have it for sometime but I sill use P4 because it's faster to handle. Today I wanted to try an scene I did with the Firefly render. In P4 this image takes about 5 minutes to render but P5 is busy for 45 minutes already and did not finish a single pixel. Is this normal ??

Generally, IMO, P5 is slower than P4. And, depending on what's in your scene, firefly can be MUCH slower. But I don't know about 45 minutes with absolutely no progress. I don't think that's normal, even for P5 firefly. But I could be wrong.

After two hours and countless shadow maps he finally started to put pixels on the screen. I think it's the Global Light Set from DAZ that needs so much time.

Curious labs should try and optimise the renderer. Two hours just to initialize is ridiculous, there must be some way to make it faster...

How many cr2's in the scene? Were they Millenium 3's, Like V3? How much high density hair or props? How many runtimes do you have associated with Poser 5? All these things effect render time. I don't usually use Gobal lights because shadow maps from lights can take forever. And I like dramatic spots better anyway. Two hours is long but not unheard of, my worst was about 4 hours. Three Unimesh figures took a little over an hour to render with the Poser 4 engine in P5. Forgot one more thing, how big is your hard drive and how many other drives are linked to it? Poser looks everywhere!!??!! for textures if it doesn't find them immediately. Emily

"How many runtimes do you have associated with Poser 5? All these things effect render time." hmm... Just wondering how runtime directories have anything to do with render speed? They shouldn't have anything to do with each other since Poser re-reads them every time you switch...it doesn't store them in memory. At least I don't think it does. After all, if it did, there'd be no reason to re-read on every switch.

I don't know how or why, but I did notice a huge slowdown when I added my fifth Runtime. On the other hand, when I use the smallest RUntime-- the one with fairies and PT's-- it renders as fast as Poser 4. Not as much lag in actual posing either but not as drastic a change. This is why I added my fifth runtime-- oit only contains what I might use for the Aldara Project at Rdna-- so I thought it would be quickr. No such luck. Maybe if I deleted a Runtime. . . Over half an hour to boot the damn thing, my fault, I didn't half to buy out every store.LOL. Emily

How can you have more than one runtime ? We are talking about the runtime directory, do we ?

The Global lighting pack at CL does not work well with P5, period. The lights in it are hacked to take advantage of certain undocumented fatures in P4, and truly are set up to take full advantage of the P4 rendering engine, not firefly, which can actually accomplish the same effect with fewer lights and smaller shadowmaps. One of the quirks about the light set is that it causes P5 to create shadow light temp files, usually in the ImageIO and prefs folders in the runtime, that for some reason choke the daylights out of Poser 5. I'm sorta hoping someone will create a set specifically for P5, but, in the meantime, I'm experimenting myself, and have found some success using three sets of three lights each, with a combination of depth mapping and raytracing. They render much quicker. (also, be sure to delete all the lights form the scene before you add the daz lights!!!! P5 still has bugs in the lighting engine, and I'm praying hard they fix them with sr4)

err, stupid me That should be the Gloabal Lighting Pak at DAZ does not work well (being nice, it should read at all) with P5. preview, girl, preview!!!