My second-ever render in Poser 5! I did it primamry because my associate is reporting proplems with P5 crashing as soon as a render is attempted on my new set, as shown in the pic. Anybody have any ideas why P5 would crash on a dress like this? Some details: The dress is about 24,000 polygons, the shoes and flower are about normal for me. The dress CR2 is about 9 MB, _very_ heavy on morphs, like about 50 for the hip part. Mostly JCM and special operators to let it pose like this. The dress also has 7 "ghost" (groups without mesh) operators that work on the hip part- actually they aren't real ghost parts becaue I have Anton K style handles, first time I've used them. I couldn't duplicate the crash, which is why these questions. I tried it before and after th 4SR 4.1, and both P4 and Fireflty render. I have no ideas, I don't know much about P5. Anyway, I noticed all the JCM still works and the figure's Full Body Morphs still operate the matching ones in the dress - I though P5's no-crosstalk-allowed setup was supposed to stop that? In other words, it works as it should, not what I expected. I also used the P5 hair, Gee! This one is about the best of the bunch, IMHO. A lot of the styles are not my cup of tea. Render time on this (1200 x 1500) was about 15 minutes, is that about normal? I have Win 2K, 2 GB, 2.8 Mhz P4, I think my associate is using XP, though. P5 seems to save files faster than P4, anyway, maybe loads them faster, too. Gee!

Deja vu all over again. This sounds like something from 1-2 years ago.

I wonder if the crash is actually being caused by the hair, and not by the dress? Is your associate using the P5 hair, also?

Dynamic hair is a complete resource hog. For this reason, I stopped using it some time ago. It tends to limit the placement of other items in the scene.

Something To Do At 3:00AM 

She tried it without P5 hair, too, got a crash both ways. Yeah, I surely agree about P5 being a resource hog! I almost exclusively use P4, myself, too, this would render in seconds in P4, instead of 15 minutes.

That's part of the reason why I render in Vue Pro these days.

Something To Do At 3:00AM 

Just for a giggle perspective, here's a DAZ Studio rendition of Ingenue Vickie imported from my Poser4 runtime. It didn't crash, though. ;-) I'll have to see about hitting that link and filing a report...

It (DAZ Studio) just crashed when I try a render, even of the included Egyptian scene. She looks O.K. in preview, though. ;-) Oh, Well!

It's just the naked figure above, but I thought I wouldn't bother applying the nudity tag. I hope no one is offended. ;-)

"Starfleet? Did you get them?!" "What we got back didn't live long, fortunately..." Sorry, couldn't resist. Whenever I view mesh distortion of this kind, I'm reminded of the transporter accident from ST:TMP. I always have to turn off the sound not to hear that inhuman scream. Dang, it still sends shivers down my spine. Silly neurosis, I know. Sincerely, Bill

Tempt the Hand of Fate and it'll give you the "finger"!

I get a lot of crashes in P5 with dynamic hair too. Actually, I get a lot of crashes and hangups when using firefly at all. A render time of 15 minutes doesn't seem bad for that pic. For me, P5 is slower than P4 in just about everything. And here's a screenshot of SMV imported into DS. No trouble so far.

What exactly do you mean by crash?

Some neftis hair was causing weird behavior that went away when the hair was carefully reassembled (lots of material zones that were intermixed). The render would appear to freeze when prepping up for the render....however, it eventually made it through the render...if you gave it hours....

P5 is only a little slower on my machine than P4, except for a few situations (due to whatever the hair bug was)....so I use it over P4. I just wish they'd fix the problem with props that worked in p4 that look like crap in p5....arg.

Now DS is slow for me, so I've only loaded it once or twice.

eric

She said "lockup", I'm not sure exactly what she means by that, when DS crashes for me, for example, I get dumped back to Win 2K's screen, and the program closes. Win2K and XP are not supposed to totally lock up, being protected mode operating systems. Let me see if I can get her to comment here.

Aaack! Ingenue turned inside out!! L

Okay, here is what I've been experiencing. The dress works fine in P5 right up until I go to render it. Then P5 just locks up and does the "not responding" thing. It doesn't do that for anything else. I've slowly eliminated everything and narrowed it down to the dress. I bring in the dress and nothing else and it locks up. Weird. I have the dress installed in a seperate runtime that I've set up for all my V3, GV, IV, and SP stuff. The dress is the only thing that doesn't work when pulled from this runtime. However, I installed the dress to my old, bloated P4 runtime and it rendered fine in Propack. It also rendered fine in P5 suddenly, but only when pulled from the old P4 runtime. I'm going to try seeing if it will now pull from the new seperate runtime now that P5 can choose to reference it from the P4 runtime if it wants. I've noticed that P5 likes some obj's to be referenced in the old P4 runtime or P5's own runtime. Why is that? Anyone know? Anyways it's working now, finally. This is a relief, because I was hoping to make P5 friendly mat pose files with the node info in them and all that.

Ha! Great to hear it! My CR2s have the "short" file references in them (as below), I wonder if the long ones would work better seperate runtime? I have no idea... ;-) reflectionMap ":Cheongsam:Red-Pink-Lined.jpg"