Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.2.0a18
2021.2.5f1
2022.1
Issue ID
1387211
Regression
Yes
Error is thrown when attempting to serialize System.Random
Reproduction steps:
1. Open the attached project "Case_1387211.zip" and load Scene "SampleScene"
2. Enter Play Mode
3. Observe the Console
Expected result: No errors are thrown in the Console
Actual result: The following error is thrown in the Console:
"SerializationException: Type 'System.Random' in Assembly 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' is not marked as serializable."
Reproducible with: 2021.2.0a18, 2021.2.5f1, 2022.1.0b1
Not reproducible with: 2020.3.24f1, 2021.2.0a17
Comments (1)
-
where-to-watch-ant-man-and-the-wasp-quantumania-free-online
Feb 17, 2023 17:05
This is something Microsoft removed from the base class libraries that Unity uses
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Resolution Note (2022.2.X):
Unfortunately, we no longer support the serialization of objects of type System.Random with the BinaryFormatter. This is something Microsoft removed from the base class libraries that Unity uses - with an update to newer base class libraries Unity picked up this behavior.
There is a good bit of discussion around this topic here: https://github.com/dotnet/runtime/issues/27429 (including some possible work arounds).