Search Issue Tracker
Fixed in 2017.2.0f3
Votes
8
Found in
5.6.1f1
Issue ID
911189
Regression
Yes
ParticleSystem throws Unsupported type MultiModeParameter error when editing after upgrading from 5.5.x
When upgrading project with particle system prefab from 5.5.x to 5.6.x, editing the particle system in 5.6.x throws Unsupported type MultiModeParameter error.
To reproduce:
1.Create new project using Unity 5.5.0f3
2.Create particle system in the hierarchy
3.Make it a prefab
4.Edit particle system settings from the hierarchy(do not press apply)
5.Open the project in Unity 5.6.x
6.Edit particle system in the hierarchy
Expected result: editing with no errors
Actual result: console throws Unsupported type MultiModeParameter error
Reproduced on: 5.6.1f1 5.6.1p1 2017.1.0b5
Notes:
Using text difference program you can see that prefabs created in 5.5.x and 5.6.x has opposite curve values, these values are opposite in all settings.
This is not a regression as the bug happens when upgrading from 5.5.x to 5.6.x.
Tested this on Win 10 and MAC OSX 10.
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
- "Debug Assertion Failed!" error when launching Windows Dedicated Server Player with Script Debugging enabled
- [Cinematic Studio][3D HDRP] Shader warnings thrown in the Console window when creating a new project with Cinematic Studio template
- Autoplay is triggered on Audio Assets when changing Asset Bundle tags
- Inspector Asset Bundle section has no indication for Variants, AssetBundle is written without a space, and Variant dropdown menu is available without setting the Asset Bundle first
- Graphics.DrawProceduralIndirect and Graphics.DrawProceduralNow silently dropped on DX12
martinamenegon
Jun 07, 2017 12:39
confirm: Unity 5.6.1
when editing particle system I get this error and particles stop simulating (need to press simulate again).
Zekio
May 31, 2017 18:33
I can confirm this is an issue, it seems to affect all the particle systems in a scene if the scene was serialized under Unity 5.5. Is there a known fix or workaround to this issue?
Wiliz
May 18, 2017 12:21
Unity 5.6 doesn't read the settings from particle systems made in Unity 5.5 correctly, which means that editing a scene in Unity 5.6 and saving it can result in loss of data. The issue is more serious than just getting an error message when editing the particle system.