Search Issue Tracker
By Design
Votes
0
Found in
2018.1.0a1
2018.4
2018.4.23f1
2019.4
2020.1
2020.2
Issue ID
1256471
Regression
Yes
Range and direction of the Light component are not shown in the Game view when Gizmos are toggled on
How to reproduce:
1. Open the attached "GizmoGameView" project
2. Open the "SampleScene" Scene
3. Make sure that Gizmos are toggled on in the Game view
4. In the Hierarchy select "Directional Light" GameObject
Expected result: Range and direction of the "Directional Light" GameObject are visible in the Game view
Actual result: Range and direction of the "Directional Light" GameObject are not visible in the Game view
Reproducible with: 2018.1.0a1, 2018.4.24f1, 2019.4.1f1, 2020.1.0b14, 2020.2.0a15
Not reproducible with: 2017.4.40f1
Note: Reflection Probe is the only Light component which range is visible in the Game view when selected
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
- Mouse input is registered incorrectly in Custom RP when downscaling Render Target and rendering Overlay UI before final upscale
- Time.deltaTime is locked to the display's refresh rate when the built Player is moved to a Secondary Display and Windowed Mode is used
- Crash on RaiseException when importing a specific asset
- Crash on RaiseException when opening a specific project
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
Resolution Note (2020.2.X):
Handles drawn through OnSceneGUI are by design not drawn in the Game View. MonoBehaviour components are able to register a callback in managed code to override the gizmo drawing, however Light is a native component.
As far as gizmos are concerned, this is working as designed. It would be preferable to move gizmo drawing (for both Scene and Game views) into Editor code, which would avoid this issue and allow inheriting Editor classes to override gizmo drawing. Work is scheduled within SRP and Scene Tooling to add this functionality.