Search Issue Tracker
Won't Fix
Votes
3
Found in
4.1.2f1
Issue ID
541127
Regression
No
VertexLit Point Lights cause a very visible 'pop' when entering the range of an object
To reproduce:
1. Open project BrokenVLights
2. Open scene VertexLightsAreBroken
3. Attach LightMover script to point light
4. Run
5. Lightning on object 'pops' when entering/leaving range
Comments (1)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Video preview in the Inspector freezes shortly after the first play and does not recover until paused and replayed
- MSB3277 conflicts between different versions of "System.Numerics.Vectors" when using DotNet 11.0
- "Cannot create Settings Providers for: CreateAllChildSettingsProviders" error is thrown in the Console after fixing PolySpatial visionOS package validation error after installing XR Interaction Toolkit VisionOS Sample
- "Unable to find style 'VideoClipImporterLabel' in skin 'GameSkin' " warning thrown when converting the Video Clip Inspector to a floating window in Play mode
- Unclear "Failed to start primary listening socket" error when launching the Multiplayer Play Mode second player and many Unity instances are running
Spellbound
Jan 07, 2014 01:20
This is so annoying, especially because lighting is the most fundamental element when working with realtime rendering and dynamic lighting is a requirement.
We worked around this issue by computing a custom point light falloff within our shaders. This is again not very optimized, because the "range" parameter is not directly accessible from shaders.