Crash when using shadow maps and light shafts
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 7.8k
- Forks
- 1.2k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 49
Description
Release Type: Official Release
Version: 4.0.0.1-beta03-1036
Platform(s): Windows
Describe the bug
Using a directional light with a large shadow map in combination with a point light also having a large shadow map causes a crash.
To Reproduce
Steps to reproduce the behavior:
- Create a new game
- Enable light shafts in the graphics compositor
- Set the shadow map size of the initial directional light to x2
- Setup a light shaft with a point light, set the shadow map size also to x2 and enable it. Usually it now crashes. If not, a third point light with an enabled shadow map definitely will.
The attached Stride project should cause the crash on open.
VolumeLightCrash.zip
Expected behavior
Not a crash. If this is a resource limitation an error log would probably be nice.
Log and callstacks
nullref.txt
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open the attached VolumeLightCrash.zip project and reproduce the crash using the directional and point-light shadow-map settings described. Start with nullref.txt and the light-shaft/shadow-map rendering path; done means the project no longer crashes, or reports a clear resource-limit error instead.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100