Lens flares gets screwed up when using GI Probes and setting Bounce to 2 when calculating GI.
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/GitHub (please choose appropriate option)
Beta
Version: Version number and/or git branch
4.0.01-beta03
Platform(s): Does the problem occur on Windows, Android...?
Windows
Describe the bug
A clear and concise description of what the bug is.
Lens Flares get screwed after calculating GI from GI Probes. When calculating with Bounce more than 1.

To Reproduce
Steps to reproduce the behavior:
- Bring in Sponza.
- Setup 540 GI Probes for best quality.
- Directional light with shadow.
- Skybox light turned off
- Calculate GI with 2 Bounces.
- Move view around and see Lens Flare freak out near Lion Sconce.
Expected behavior
A clear and concise description of what you expected to happen.
Lens flares should behave normally.
Screenshots
If applicable, add screenshots to help explain your problem (use GitHub drag & drop)
Attached picture.
Log and callstacks
If any, please attach here any log or callstack (preferably in a .txt file using GitHub drag and drop)
Additional context
Add any other context about the problem here.
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
Reproduce the issue in the Sponza scene using 540 GI Probes, a shadowed directional light, disabled skybox lighting, and GI calculation with 2 bounces. Inspect the lens flare and GI Probe rendering paths involved when moving the view near the Lion Sconce. Done means lens flares behave normally after GI calculation with more than one bounce.
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
- Mostly clear
- Newbie friendliness
- 35/100