Point lights with light probes causes warning and performance degradation.
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
Version: 4.2.0.2232
Platform(s): Windows
Describe the bug
When adding multiple Point lights to a scene with shadows on it will eventually throw warnings saying warning X3203: signed/unsigned mismatch, unsigned assumed
It seems like computing the lights sometimes removes the warnings but not consistently.
annoyingly I cant even share the project because it seems like at some point after rebuilding I cant create the problem anymore but it does sometimes come back when adding more lights.
To Reproduce
Steps to reproduce the behavior:
- create a new empty scene
- add 8 light probes in a box shape similar to the docs
- add point lights until when running the game the above error appears (it was not consistent for me when it popped up)
Expected behavior
Lights should not throw warnings when light probes are being used.
Screenshots
A view of the scene that used to throw the error:
Log and callstacks
Warning: shader_StrideForwardShadingEffect_a0e5bf768ffbbe8f4fb2385c6bc54cb3.hlsl(804,59-97): warning X3203: signed/unsigned mismatch, unsigned assumed
Warning: shader_StrideForwardShadingEffect_a0e5bf768ffbbe8f4fb2385c6bc54cb3.hlsl(804,59-97): warning X3203: signed/unsigned mismatch, unsigned assumed
Warning: shader_StrideForwardShadingEffect_f12b514f9b803faf5b7be898130d2229.hlsl(924,59-97): warning X3203: signed/unsigned mismatch, unsigned assumed
Warning: shader_StrideForwardShadingEffect_f12b514f9b803faf5b7be898130d2229.hlsl(924,59-97): warning X3203: signed/unsigned mismatch, unsigned assumed
the referenced files are here:
Shaderfiles.zip
Additional context
Linus in the Discord was the one who originally found the problem.
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
Start by reproducing the issue in a new scene with eight light probes and enough shadow-casting point lights, then inspect the generated shader files named in the log or Shaderfiles.zip. Confirm whether the signed/unsigned warning occurs consistently and whether it correlates with the reported performance degradation. Done means the light-probe scene runs without those shader warnings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- computer-graphics, game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100