Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Possible improvements to Cascaded Shadow Maps
See original GitHub issueI thought I’d post a couple improvements for CSM I was thinking about in case anyone is interested and wants to pick them up.
-
Render all shadow cascades to a single shadow map target to save on shadow map branching and texture uniforms. Reference here and here
-
Add option to provide a scene bounding box or bounding sphere to the CSM object so the shadow render bounds can always encapsulate the scene.
-
Remove or rename the
Frustumclass in the/csmfolder so it won’t eventually conflict withFrustumin core.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:10 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Is there any progress on this? It would be great to finally see CSM in the core!
I hope this is helpful https://doc.babylonjs.com/babylon101/shadows_csm in this playground there is a shadow (CSM) in one direction and shadow2 (normal shadowgenerator) in other direction https://www.babylonjs-playground.com/#IIZ9UU#40