Search Issue Tracker
Duplicate
Votes
8
Found in
4.3.0f1
Issue ID
573522
Regression
Yes
Mesh renderer with a mesh filter and a cloth renderer causes crash
To reproduce:
1. Import repro.unitypackage with Unity 4.3 - Unity crashes
The package contains a prefab with a disabled mesh renderer and a cloth renderer and a mesh filter. Removing either of these stops the crashing.
The crash can also occur when a parent gameobject has a mesh renderer+filter and a child gameobject has the cloth renderer
Does not crash with version 4.2.2f1
Comments (2)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Monkey Fritz
Dec 17, 2013 07:53
yup, just came across this today myself.
Only already running the latest version. Trying to save a prefab that has one child object with a mesh filter and mesh renderer, and another child object that has a cloth renderer crashes every time.
Removing the mesh filter I was able to save the prefab, then add the mesh filter back to the prefab in the inspector and bypass the crash.
But then Unity crashed any time I tried to save the scene.
gtjuggler
Dec 11, 2013 19:06
Came across this today and can confirm it's blocking our upgrade from 4.2 to 4.3.