Search Issue Tracker
Fixed in 4.5.2
Votes
16
Found in
4.3.3f1
Issue ID
588450
Regression
Yes
Mismatched serialization in the builtin class 'Mesh'
To reproduce:
1. Open attached project
2. Open MismatchError scene
Expected result: No error
Actual result: Error is thrown: Mismatched serialization in the builtin class 'Mesh'. (Read 295476 bytes but expected 295477 bytes)
Comments (35)
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
- Scrollbar is disabled in Adaptive Probe Volumes in Lighting window
- Disabled dropdowns in Lighting window are inconsistently expanded or collapsed
- “Frame Debugger On” text color not maintained across different Editor Themes in toolbar
- Rendering artefacts appear in the Game view window when maximizing/minimizing Inspector window and Frame Debugger is Enabled
- [MacOS] AdvancedDropdown in the Profiler is not scrollable even when not all options in the list are visible
Rene-Damm
Jun 16, 2014 15:48
This bug specifically affects meshes imported/created with 3.5.0 and loaded into Unity 4.x. 3.5.0 had a rather tricky bug in mesh serialization which was fixed in 3.5.1 but which requires a workaround serialization path in 4.x. This code path was missing a bool field thus leading to the error here (the mesh would still load more or less correct, though).
Fixed in 4.5.2.
Steven Walker
Jun 12, 2014 17:43
I am still getting these errors in 4.5.0f6 with no apparent solution or work around :/
EightBitNine
May 09, 2014 15:27
It now says voting disabled for resolved issues. WTF, how do you say that you "won't fix" something, but then say that its fixed? Did I just wake up in freaking OPPOSITE LAND?
deli73123
Apr 15, 2014 23:17
It seems like the people who run this Issue Tracker are extremely inconsistent in how they deal with errors.
I don't understand why they would even HAVE a "won't fix" option.
Marcurios
Apr 01, 2014 14:32
I'm glad i didn't buy Unity yet, cause i also have this error, and after searching for days on the net i could not find any fix for it, so now i have decided that i'm just going to use the Cryengine instead of a gameengine whose bugs won't get fixed.
kleinfb
Mar 27, 2014 03:41
Won't fix?? Is this a joke?
chiapet1021
Mar 17, 2014 20:57
Why has this issue been designated as "Won't Fix"? It seems to be a rampant error causing performance issues for many of us.
SnoozePouch
Jan 31, 2014 07:47
I am seeing a lot of these errors too since we moved to 4.3. A lot of things broken in 4.3, and even though they get marked as fixed, they are still present in 4.3.4 e.g. Does this mean that if one testcase results in no errors people just close the bug...?