I have the bombshell hair and used it quite a lot in poser4, because it's a nice simple figure and conforms well - but now that i'm using poser5 it chrashes when I render it. The only solution I have found is to set it to poser4 render, but the new renderer is so much nicer. Does this happen to anyone else and, if so, what can be done about it?

I've had the same problem. Occasionally it will render, but the vast majority of the time it crashes the Poser 5 renderer.

The hair might be too complex in transmapping for the render settings in P5. Only thing I can think of. I would find it hard to believe that P5 couldn't handle it. Very odd. No idea myself. Sorry. Wish I could help.

I have had the same problem myself, and I would like to know how to fix the problem so that I can use it with Montana Skye.

Just a few mins before reading this, I was struggling with exactly the same problem. The render progress box just disappears half-way through and the render stops.

well, at least I know that it isn't just my computer so maybe there will be a patch or revision in the the works - and, I don't know what aspect of the hair the renderer doesn't like but it always chrashes at "adding objects" for me

I wouldn't expect anything from Cl right away. But then again you never know.

Re: My earlier message abour an hour ago. I've now had the opportunity to go back to Poser 5 and have tested the firefly render with several heavy duty renders which include the bombshell hair. I've had no problems whatsoever. Certainly for me the bombshell hair seems to render fine in Poser 5. Whatever the earlier issue for me was, it was not a consequennce of the bombshell hair.

caulbox, are you using SR2.1, and does anyone with 1.0 have this problem?

Yes I am, and I have no problems with Poser 5. Maybe my (over 512 meg) memory and Win98 could use an overhaul. What I experienced earlier was just a memory problem with Win98. I think you'll find there are thousands like me!

I just completely updated my computer from the processor on down about two months ago so i'm thinking that thats not the problem, not to mention that this seems to happen consistenly - regardless of what else is happening on my system. I wonder if it might be some option with the firefly renderer itself - texture filtering, draw shadows, etc...

Not only does my Poser 5 render the Bombshell hair, with smooth polygons on it makes it look like buttah!! I do have 2G of memory and XPHome. You may not need texture filtering-- I had less trouble when I turned that off and used raytracing instead of the the other shadow method. Still when I install new stuff, P5 will occassionally lock up on loading objects or finding textures. Best thing then is to ctl-alt-del and reboot. Emily

ok... the plot thickens. When I earlier gave it the heavy duty test, I'd loaded a pz3 with detailed characters, and substituted a hair figure for the bombshell hair. I tried several variations and experienced no problems whatsoever with the firefly render. The strange thing is that if I load this pz3 file again then the hair always seems to render without problems. However, I've now tried once more within Poser by simply loading a V3 and conforming the hair, and the render often freezes again :(

It might be a job for Correct Reference-- in FS, it makes sure the path in the cr2 and where your hair textures are are the same. Um, we are talking about a Vicki 3 nonloaded with morphs, right? A plain Vicki 3?? Emily

I've been using a V3 with substantial morphing, though all morphs are DAZ - and without the hair the same figure renders just fine. I'm running XP pro with a new P4 2.3 and 800 odd megs of RAM. I can't seem to figure this out, and even better I cant recreate the problem with anything but the bombshell hair...

One comment I would add, is that I usually use a v3 fully loaded with all morphs. However I am in the habit of always loading v3 figures with the hi-res tex re-sized to 50% of the original size and using no bump.

I know it's not the V3 figure, that renders just fine without the hair... I tried rendering the hair after removing all textures, transparancy, etc - leaving it just flat colors - and it still chrashed, so i'm figuring that it must be the hair figure itself...

Just an afterthought, cos I've had potentially very serious problems with imported libraries and V3 delta injections within poser. Are you loading V3 and the hair figure from the main Poser 5 Library, or from an imported runtime? There seems to be something akin to cross-talk which affects the DAZ delta injections between libraries. (I may say more about this later but I'm currently awaiting a reply from DAZ tech support, and I don't want to scaremonger)

Hm. I'm going to have to stress-test this, but I got the Bombshell Hair to render with the P5 Firefly renderer when I turned off all the optional checkboxes, including displacement mapping. (Actually, I rendered once with the P4 renderer, then tried Firefly with everything off; that worked.) I'll continue to try to run these, and see if this renders reliably.

still, not having any luck - even with all the options off - but iv'e really got to thank everyone for helping me figure this out

I'm beginning to think this is definitely a mapping problem. If you open the Obj in UVmapper, you'll see there's the easily identified Scalp material, and all the other materials are contained in a series of horizontal lines accross the screen. Apart from the Scalp, all the other materials use the same texture and trans maps. As a quick fix I therefore saved the object with the Scalp material asigned to a region and didn't export the materials. I then re-opened my newly saved Obj and asigned the Scalp region to a material, and then inverted the selection and assigned all the rest to a gestalt Hair material. I also edited the Cr2 (and MAT pose files) to include only these two regions. Whilst this now denies me the opportunity of subtle shades of colour between former existing regions it is acceptable, and the rendering has become absolutely problem free within seconds!

Still had absolutely no problems and almost instantaneous renders with the strategy above. I've now improved it slightly, to allow me some subtleties of highlight again, and so that the original cr2 and MAT poses may be used to test. My eysight isn't very good, but I struggle to see what if anything is selected within UVmapper when I select any of inner1, inner2, side1, or side3 ? The Scalp, Side2, and side4 selections are plain to see. There must be a rogue pixel or two being selected, and I'm wondering what if any great effect a couple of pixels might have on the final render (apart from crashing Poser?). Any UV experts help would be appreciated. This time I've followed the same stratagey but asigned the Scalp, Side2 and Side 4 as three new UV regions. However when I re-asigned them as materials, I made an arbitrary decision to include all the other rare pixels in the same material as Side2 (by selecting the material along with the default material and then re-asigning it as Side2. I can now use the original MAT files and cr2 again, and I can also highlight Side2 and Side4 independentally. A look in the materials room will of course reveal extraneous materials which were present in the cr2 and pose files, but I'll get round to editting them again, when I'm finally happy with the outcome. (its a simple matter to delete refs to unused materials) The hair still renders fine with these three materials (Scalp, Side2, and Side4) but the basic render now takes about a further 20 seconds to initialise.

Oh dear!.. I've now noticed that the hard to see material selections do indeed exist, and turning the transparency on/off in poser certainly validates that they are very important material groupings :( I'm no UV expert but at least I've now learnt that some selections only become visible in UVmapper after clicking and dragging the screen? Apols for any earlier misleading info about rogue pixels, but I'm happy anyway to continue with my 3 material fast rendering fix until someone offers a better solution.