Search Issue Tracker
Fixed in 2022.2.X
Votes
1
Found in
2021.2
2021.2.7f1
2022.1
2022.2
Issue ID
1395253
Regression
No
Editor crashes when entering the Play Mode
Reproduction steps:
1. Open users attached project
2. Open Scenes/SampleScene
3. Enter the Play Mode
Expected result: Play Mode is entered
Actual result: Editor crashes
Reproducible with: 2021.2.13f1, 2022.1.0b9, 2022.2.0a5
Could not test with: 2019.4, 2020.3.29f1 (could not downgrade the project)
Stack trace:
0x00007ff79c6bd575 (Unity) scripting_object_get_class
0x00007ff79c6fa9e4 (Unity) StreamedBinaryWrite::TransferSTLStyleArray<ArrayOfManagedObjectsTransferer>
0x00007ff79c712082 (Unity) Transfer_ManagedObject<StreamedBinaryWrite,1>
0x00007ff79c6ec2cc (Unity) TransferField_LinearCollection<ReportScriptingObjectsTransfer>
0x00007ff79c669b56 (Unity) ExecuteSerializationCommands<JSONRead>
Note: seems to only reproduce on Windows
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
- Editor crashes on "MonoBehaviour::Transfer<GenerateTypeTreeTransfer>" when resetting package defaults in VR Template project
- Rotation tool Gizmo is stuck in the Scene View when unchecking/checking the "Orient" node in the VFX Graph and the Scene view is visible
- The Editor opens when the window is closed right after launch
- Frame Debugger's Hierarchy is not navigable when connecting it to the project built with the Volumetric Fog
- The number of SetPass Calls is increasing when attaching the Frame Debugger to the Player
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.0a16
The DX12 native plugin interface works as intended, although some details were unclear in the documentation. So we have added a few comments to the header-file IUnityGraphicsD3D12.h. Other than that, the errors seem to be related to use of Microsoft's DX12 graphics API in the native plugin code.