Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2018.4.X, 2019.3.X, 2020.1.X
Votes
8
Found in
2018.1.0b12
2018.1.4f1
2018.2.0b7
2019.3
2020.1
2020.2
Issue ID
1051422
Regression
Yes
[LW-SRP] Console spams "Converting invalid MinMaxAABB" errors when a Particle System with Lights is inspected
How to reproduce:
1. Open the attached project "case_1051422.zip"
2. Go to Graphics settings and set LWRP-HQ Render Pipeline Asset (If selections are missing, fix Packman errors or reopen the project)
3. Open Features/Jacky_VFX/Sparks scene
4. In Scene View, select Particle System GO
5. Observe the errors in the console
Expected result: No errors appear in the console
Actual result: "Converting invalid MinMaxAABB" errors are constantly thrown
Reproducible with: 2018.1.0b12, 2018.1.7f1, 2018.2.0b7, 2018.2.0b10, 2018.3.0a4 (96052d777ea1)
Not reproducible with: 2018.1.0b11, 2018.2.0b6 (random errors, couldn't access the LW-SRP assets)
Note:
- Errors are not thrown if Lights in the Particle System are disabled
- Errors are not thrown if Environment GO is disabled
- Errors are a bit different when in Game View
-
dgoyette
Mar 03, 2020 20:11
Despite it not being listed in the description, I have been told by QA that this issue still exists in 2019.1, .2, and .3, though it may take extra steps to manifest in those versions. So this is still an open bug in the latest production release of Unity.
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
- Animator with nested avatar root show missing properties in the Animation Window
- System.Threading.Task tasks cause stall when used in WebGL
- [Package Manager] Access denied when installing some packages
- SerializedProperty.DataEquals returns true for two strings that are different
- Prefab is glitchy when editing in Prefab Mode in a custom UI Environment
Resolution Note (fix version 2020.2):
Fixed in: 2019.3.15f1, 2020.2.0a8
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.0b9
Resolution Note (fix version 2018.4):
Fixed in: 2018.4.29f1