Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.0f1
2017.4.2f2
2018.1.0a1
2018.2.0a1
2019.1.0a1
Issue ID
1087099
Regression
No
Lights, who have their Render Mode set to Not Important, are not rendered when the Camera leaves the Light range
Steps to reproduce:
1. Open attached project "case_1087099-Light_Going_Out_Bug_Example.zip"
2. Try to move Camera on the Z-axis away from the center
Expected result: Light is still visible because Camera can still see light coming from "Point Light"
Actual result: Light goes out after camera moves away from "Point light" range.
Reproduced in: 2017.4.16f1, 2018.1.9f2, 2018.2.17f1, 2018.3.0b11, 2019.1.0a10
Note: Light is also not rendered on the surface if the surface is out of "Point Light" Light range. Unity assumes that light from light source (in this case "Point Light") won't leave Light range bounds, which is not true due to intensity being able to do so.
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
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
Resolution Note:
This issue has been identified as having low priority and has been closed without a fix. If the bug has no workaround and is blocking your production please feel free to reopen it with any additional information you might have. Sorry for the inconvenience this might cause.