Horde3D

Next-Generation Graphics Engine
It is currently 26.08.2019, 04:21

All times are UTC + 1 hour




Post new topic Reply to topic  [ 4 posts ] 
Author Message
PostPosted: 16.02.2013, 05:05 
Offline

Joined: 16.02.2013, 04:52
Posts: 3
I am having an issue where my shadows display incorrectly when the camera looks at them from the wrong angle/position.

Here are two screenshots, the first with the shadows rendered correctly, the second with the camera moved slightly.

Good:http://www.firecaster.com/shadow1.png
Bad:http://www.firecaster.com/shadow2.png

Things I have tried:

Switching to and from deferred/forward lighting.
Changing the Shadow Map Bias
Changing the Shadow Map Count
Adding/removing lights. Using only one light.
Changing the ShadowSplitLambda, not sure what that does but it didn't help.
Splitting up my giant triangles into smaller triangles.

Does anyone have any solutions? Or at least a name for what this problem is.


Top
 Profile  
Reply with quote  
PostPosted: 16.02.2013, 13:47 
Offline
Tool Developer

Joined: 13.11.2007, 11:07
Posts: 1149
Location: Germany
What radius did you use, maybe you suffer from numerical issues because of low floating point precision.


Top
 Profile  
Reply with quote  
PostPosted: 16.02.2013, 17:45 
Offline

Joined: 16.02.2013, 04:52
Posts: 3
the radius of the light is 40. I tried increasing it to 400 and I still have the same problem.


Top
 Profile  
Reply with quote  
PostPosted: 14.05.2014, 23:51 
Offline

Joined: 14.05.2014, 14:39
Posts: 1
I think I'm experiencing the same issue. It seems to be a problem with Renderer::calcCropMatrix.

I've got a test scene that is just a big box for a shadow receiver (with casting off) and several bush meshes lined up in a row. I've got a light with a 90 degree fov, radius of 13 and y of 2. Normally everything appears just fine:
ImageImage


But I've got a procedure that automatically combines all the meshes in a scene node into a single geometry:
Image


If I combine all the bushes in to a single mesh the crop matrix gets cut strangely and the shadow maps become much more expensive:
Image


If I move the combined mesh more towards the front or back of the light it starts to correct:
ImageImage


Rotating the light on any axis (y pictured) also causes the cut off to change:
Image



Commenting out the call to Renderer::calcCropMatrix in Renderer::updateShadowMap "fixes" it. I've tried fiddling around with it, but I've had no luck. Adjusting the light's FOV and radius doesn't have any effect.


Top
 Profile  
Reply with quote  
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 4 posts ] 

All times are UTC + 1 hour


Who is online

Users browsing this forum: Bing [Bot] and 2 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group