Drai opened this issue on Apr 10, 2007 · 4 posts
Drai posted Tue, 10 April 2007 at 7:20 PM
Any ideas on this I would appreciate-- Thanks!
I've included pics to show what I mean, if I am not clear enough.
BeyondVR posted Tue, 10 April 2007 at 9:51 PM
Are you ray tracing shadows? I believe mapped shadows will cause this problem.
John
bagginsbill posted Tue, 10 April 2007 at 10:02 PM
There is a culling bug in Poser when using depth mapped shadows. However, you do not need to switch to ray-traced shadows. Simply enable shadow map caching. For some reason the bug is not evident when you use a cached shadow, only on a freshly generated shadow.
Enable shadow caching. Start a render - this one will be bad so you can abort it as soon as the shadow map is generated. Then start another render - this time let it go. As long as Poser is using the cache, it works fine. If you move lights, clear the cache, start a render, cancel it after shadow map is generated, then render as many times as you like.
You only need to clear the shadow map cache if you move something. You do not need to clear if you're changing light strength or material settings.
Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)
Drai posted Wed, 11 April 2007 at 8:54 AM
I am using ray-traced shadows, but I will also try out the shadow caching option too. I'll let you all know what happens.
Thanks for the advice.