Search Issue Tracker
Fixed
Fixed in 2022.2.0b10, 2023.1.0a13
Votes
1
Found in
2022.2.0b6
2023.1.0a8
Issue ID
UUM-12859
Regression
Yes
[2D] Changing values of "Platform Effector 2D" Component fields crashes the Editor when before the "Used By Effector" field value had been changed
How to reproduce:
1. Open the user’s attached “URP” project
2. Enter the Play Mode in the “Level” Scene
3. Select the “Player” GameObject
4. Enable, disable and re-enable the “Box Collider 2D → Used By Effector” value in the Inspector
5. Change the “Platform Effector 2D → Surface Arc” value in the Inspector
Expected result: Editor continues to work properly
Actual result: Editor crashes
Reproducible with: 2022.2.0a15, 2022.2.0b6, 2023.1.0a8
Not reproducible with: 2020.3.38f1, 2021.3.8f1, 2022.1.14f1, 2022.2.0a14
Reproduced on: macOS 12.3 (Intel)
Stacktrace:
#0 0xffffffff00000086 in (Unknown)
#1 0x0000010382929b in PlatformEffector2D::RecalculateContacts()
#2 0x0000010428e2b1 in SerializedObject::ApplyToFirstObject()
#3 0x0000010428fda7 in SerializedObject::ApplyModifiedPropertiesWithoutUndo()
#4 0x00000102835c37 in SerializedObject_CUSTOM_ApplyModifiedProperties(ScriptingBackendNativeObjectPtrOpaque*)
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
- Sahder errors in Player when "Strict shader variant matching" is enabled and the rendering path is set to "Deferred"
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
Resolution Note (fix version 2023.1.0a13):
Fix for this issue will be available on Unity 2023.1.0a13 and above
Resolution Note (fix version 2022.2.0b10):
Fix for this issue will be available on Unity 2022.2.0b10 and above