If I uncheck "Light emitter" on the hair this happens when rendered. Why.

A bug? It's not just this hair that causes this, other *.hr2 hair also do it. At the moment I think only .hr2's do this not character cr2 hairs. More testing needed.

There is a bug where inf. lights don't work randomly and then work fine in a render. You might try to change out your lights for a lighting sphere/dome first for testing.

Hi ghostship2,

I belive that bug was fixed in version 0.427, (at least it's no longer happening to me.)

Spot and area lights are also affected the same way as infinite lights-

No Light No Problem!

Hey! When did "shadow catch only" start working in Superfly?

gotta ask this: how are you rendering and if you are using a GPU what GPU are you using? Currently I'm getting an Optix GPU crash when I use a pair of glasses prop in a scene. Only when Optix is used but I have checked with another user who has the same prop and they could not get the same crash.

All my images are GPU renders, GeForce GTX 1050, Intel i7-7700 CPU.

My hardware is getting old.

Cheers.

well, at least we know it's not an RTX/Optix problem.

Can you just load in the hair prop and get the same bug?

Sorry I don't own this prop myself. I'm guessing it is be 3Dream?

This is the hair I used "Georgia Hair for V4 M4 and La Femme - Poser by RPublishing, prae." Store link

Bennie Hair by the same vendor also does this

However I noticed when I did the HDR render that the hair was still visable after deleting all lights.

There is a very weak ambient setting in both these hairs, after setting ambient to zero the lighting is no longer affected by the "light emitter" switch.

ghostship2 posted at 10:27AM Mon, 15 March 2021 - #4414897

gotta ask this: how are you rendering and if you are using a GPU what GPU are you using? Currently I'm getting an Optix GPU crash when I use a pair of glasses prop in a scene. Only when Optix is used but I have checked with another user who has the same prop and they could not get the same crash.

Do you get a CUDA error in the notifications? I have one scene that does that reliably, and saw it a couple times in other scenes. After it arises, no GPU renders work until a reboot. I sent the one scene to support and they were only able to replicate it on one computer, it worked fine on the others. Not sure if they have figured it out yet.

I don't think that's related to the ambient materials issue here though.

@RoseHawk The ambient nodes are meant for things that glow or produce light. Hair does not do this and that makes that a bad hair shader to begin with.

@ChromeStar Yes, I got a CUDA error in the log and Poser needed a re-start for the GPU to work again. My RTX card is not running the monitor so I did not have to re-boot the system to get it to work. I'm not using my older card in Poser and that way I can surf the internet, play video games or watch a movie without disrupting a render.

I have to say that from time to time, I stumble upon a wrongly defined material, most of the time we can see a dashed line instead of a continuous line. The default GTX can handle this, but using the OptiX option results most of the time in a crash.