Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2019.2.0a7
2019.3.0a1
2019.3.0b4
2020.1.0a1
Issue ID
1184820
Regression
Yes
[Graphics General] DivideByZeroException error is thrown on enabling "Animate Cross-Fading" in LOD Group
DivideByZeroException error is thrown on enabling "Animate Cross-Fading" in LOD Group
Steps to repro:
1. Create a new project.
2. GameObject > 3D Object > Cube > Add LOD Group Component.
3. Change Fade Mode to CrossFade.
4. Change the LOD Percentage scale.
5. Enable Animate Cross-Fading checkbox.
Actual Result:
DivideByZeroException error is thrown in the console.
Expected Result:
No error in the console.
Reproducible in:
2020.1.0a6, 2020.1.0a4, 2019.3.0b4, 2019.2.0a7.
Working Fine in:
2019.2.0a6.
Environment:
Windows & Mac 10.14.
Stack trace:
DivideByZeroException: Attempted to divide by zero.
UnityEditor.LODGroupEditor.DrawRenderersInfo (System.Single availableWidth) (at <2c7108252b3f412abf2ec8c94fb7c234>:0)
UnityEditor.LODGroupEditor.OnInspectorGUI () (at <2c7108252b3f412abf2ec8c94fb7c234>:0)
UnityEditor.UIElements.InspectorElement+<>c__DisplayClass53_0.<CreateIMGUIInspectorFromEditor>b__0 () (at <2c7108252b3f412abf2ec8c94fb7c234>:0)
UnityEditor.UIElements.Tooltip:SetTooltip(Single, Single)
Comments (2)
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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
krisventure
Jul 13, 2020 14:08
This bug is also present still in Unity 2020.1.0b15.4110 (the latest available beta version).
krisventure
Jul 13, 2020 06:02
This bug is still present in 2019.4.3f1 LTS, along with an unreliable LOD group behaviour such as inconsistent switching between LODs, eg. LOD0, LOD1 and LOD2 all appear correctly at the correct distances when in Editor's Scene view but only LOD0 and LOD2 appear correctly when in PlayMode, with LOD1 getting culled. Also inconsistent results when pressing "recalculate bounds".