Search Issue Tracker
Fixed in 5.4.0
Votes
1
Found in
5.3.2p1
Issue ID
765519
Regression
No
[Shuriken] IsNormalized error messages in console when scaling particle system having collision module
Steps to reproduce:
1. Download and import attached project.
2. Open scene: main.
3. Inspect console.
Expected result: Empty.
Actual result: Bunch of "IsNormalized (normal, 0.001f)" errors appear.
Notes: Only reproduces when scaling vertical axis or scaled value is 0. Also only reproduces when simulation space is local and scaling mode local. Only reproduces when Collision mode is set to plane and has attached at least one plane.
Reproduced on: 5.4.0b3, 5.3.2p1.
Comments (8)
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
- Reflection Probe “Probe Scene Editing Mode:” text is barely visible
- [HDRP] Game view doesn’t refresh after changing Camera Background Type until mouse moves over it
- Some Shaders appear twice in Material Shader selection menu
- Editor freezes with a StackOverflowException when certain asset types are assigned to a managed component in a SubScene via AddComponentObject
- Scale Snapping with Gizmos does not work in the Scene view when Snapping and Absolute Grid Snapping are toggled off
Sam777
Oct 31, 2019 05:03
still appears on 2018.2.9f1
sama-van
Aug 14, 2017 17:04
Just had the same error under 2017.1.0f3
Mijail_Bitboys
Aug 12, 2017 17:56
This issue still appears on 2017.1 when scale particles with hierarchy option checked
jmguillemette
Aug 04, 2017 00:18
I can confirm that the latest patch release (2017.1.0p2) has this error still
Mijail_Bitboys
Jul 22, 2017 16:08
This issue is still not fixed. Unity 2017.1 patch 1
WinderDream
Dec 01, 2016 02:10
i found this issue. 5.3.5p6
MortePCAndVR
Jul 03, 2016 14:58
Confirmed this error reproduces on 5.3.5f1 collision mode plane with plane gameobject, and confirmed workaround success using world collision.
Jeremy-Borton
May 30, 2016 22:32
Thank you!!! My particle system had collision mode set to plane and after changing it to world the error disappeared.