Search Issue Tracker
Fixed in 2017.3.0f3
Fixed in 2017.1.X, 2017.2.X
Votes
0
Found in
2017.1.0f3
Issue ID
930005
Regression
No
Particle UI stuttering when navigating up and down since enabling particle collision: Plane
Repro steps (original attached project):
1. Drag "MissilesCollision" prefab into the scene.
2. Make sure the Particle Editor is open
3. In the Particle Editor, expand the Collisions module and change the type to Planes
--
I've also attached a smaller project, Bug_01.rar. If you want to use this, the repro steps are:
1. Open Scene 1
2. Select the Particle System prefab instance in the scene, and open the Editor.
3. Change the Collisions module's type to Planes.
Observe error / UI messes up like in the screenshot above.
The following errors appear in the console:
NullReferenceException: Object reference not set to an instance of an object
UnityEditorInternal.EditMode.DoInspectorToolbar (.SceneViewEditMode[] modes, UnityEngine.GUIContent[] guiContents, Bounds bounds, UnityEditor.Editor caller) (at C:/buildslave/unity/build/Editor/Mono/Inspector/EditMode.cs:190)
UnityEditor.ModuleUI.GUIButtonGroup (.SceneViewEditMode[] modes, UnityEngine.GUIContent[] guiContents, Bounds bounds, UnityEditor.Editor caller) (at C:/buildslave/unity/build/Editor/Mono/ParticleSystemEditor/ParticleSystemModules/ModuleUIHelpers.cs:159)
UnityEditor.CollisionModuleUI.OnInspectorGUI (UnityEditor.InitialModuleUI initial) (at C:/buildslave/unity/build/Editor/Mono/ParticleSystemEditor/ParticleSystemModules/CollisionModuleUI.cs:230)
UnityEditor.ParticleSystemUI.OnGUI (Single width, Boolean fixedWidth) (at C:/buildslave/unity/build/Editor/Mono/ParticleSystemEditor/ParticleSystemUI.cs:190)
Notes:
- Not a regression, happens in 2017.1 and 2017.2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
Add comment