Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2020.1.X
Votes
2
Found in
2020.1.0a20
2020.1.4f1
2020.2
Issue ID
1275179
Regression
Yes
Out of range [0;1] exceptions are thrown when Light Component Intensity value is lower than 3.79684775648568885e-38
Reproduction steps:
1. Open the attached project ("Test2020LightingBug.zip")
2. Open "SampleScene" scene
3. Enter Play mode
Expected result: No errors thrown in the console
Actual result: ArgumentOutOfRangeException is thrown constantly:
ArgumentOutOfRangeException: Specified argument was out of the range of valid values.
Parameter name: Red color (Infinity) must be in range [0;1].
UnityEngine.Experimental.GlobalIllumination.LinearColor.set_red (System.Single value) (at <fb900ccbd717476f91b221d941550640>:0)
UnityEngine.Experimental.GlobalIllumination.LightmapperUtils.ApplyColorTemperature (UnityEngine.Color cct, UnityEngine.Experimental.GlobalIllumination.LinearColor& lightColor) (at <fb900ccbd717476f91b221d941550640>:0)
UnityEngine.Experimental.GlobalIllumination.LightmapperUtils.Extract (UnityEngine.Light l, UnityEngine.Experimental.GlobalIllumination.DirectionalLight& dir) (at <fb900ccbd717476f91b221d941550640>:0)
UnityEngine.Experimental.GlobalIllumination.Lightmapping+<>c.<.cctor>b__7_0 (UnityEngine.Light[] requests, Unity.Collections.NativeArray`1[T] lightsOutput) (at <fb900ccbd717476f91b221d941550640>:0)
UnityEngine.Experimental.GlobalIllumination.Lightmapping.RequestLights (UnityEngine.Light[] lights, System.IntPtr outLightsPtr, System.Int32 outLightsCount, Unity.Collections.LowLevel.Unsafe.AtomicSafetyHandle safetyHandle) (at <fb900ccbd717476f91b221d941550640>:0)
Reproducible with: 2020.1.0a20, 2020.1.5f1, 2020.2.0b2
Not reproducible with: 2018.4.26f1, 2019.4.10f1, 2020.1.0a19
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2020.2):
Fixed with 2021.1.0a2.727, backported to 2020.1.12f1
Resolution Note (fix version 2020.2):
Fixed with 2020.2.0b10