Search Issue Tracker
Duplicate
Votes
0
Found in
2019.1.9f1
2019.2.0b9
2019.2.0f1
2019.3.0a8
2020.1.0a1
Issue ID
1178532
Regression
Yes
Editor crashes with (Unity) WorldCollision when previewing a Particle System
How to reproduce:
1. Create a new project
2. Import the "case1178532_ReproPackage" Package
3. Add the "Brenntest" Prefab to the scene
4. Select "Brenntest/Dome_type1_1.0/Dome_1_frame_big/Pentagonburning (1)/WallFlameswithoutbaseScript" Game Object
Result: Editor crashes with (Unity) WorldCollision
Reproducible with: 2019.1.14f1, 2019.2.3f1, 2019.3.0b1, 2020.1.0a1
Not reproducible with: 2019.1.8f1, 2019.2.0b8, 2019.3.0a7
Last 5 lines of the Stack Trace:
0x00007FF6ACDBD090 (Unity) WorldCollision
0x00007FF6ACDBC5F7 (Unity) CollisionModule::Update
0x00007FF6ACD78129 (Unity) ParticleSystem::UpdateModulesPostSimulationIncremental
0x00007FF6ACD77CD9 (Unity) ParticleSystem::UpdateModulesIncremental
0x00007FF6ACD666B1 (Unity) ParticleSystem::Emit
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
This is a duplicate of issue #1168859