SetDirtyAndNotify causes null exceptions on GameObject delete #192
Comments
|
Thank you for your reporting! |
mob-sakai
added a commit
that referenced
this issue
Sep 6, 2024
github-actions bot
pushed a commit
that referenced
this issue
Sep 6, 2024
## [2.3.2](v2.3.1...v2.3.2) (2024-09-06) ### Bug Fixes * SetDirtyAndNotify causes null exceptions on GameObject delete ([706f022](706f022)), closes [#192](#192)
|
🎉 This issue has been resolved in version 2.3.2 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
github-actions bot
pushed a commit
that referenced
this issue
Sep 6, 2024
## [2.3.2](v2.3.1...v2.3.2) (2024-09-06) ### Bug Fixes * SetDirtyAndNotify causes null exceptions on GameObject delete ([706f022](706f022)), closes [#192](#192)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Sometimes when I delete on Initialization some GameObjects containing the SoftMask.cs component, I am getting null exceptions. Those are being casued by the call to MaskUtilities because those are not checking if the object still exists:
private void SetDirtyAndNotify() { SetSoftMaskDirty(); MaskUtilities.NotifyStencilStateChanged(this); }I solved it by just adding
if (isDirty || !this || !isActiveAndEnabled) return;before the MaskUtilities call, but there is probably some better way to solve it.Thank you for developing this asset by the way, it's super helpful, it's honestly crazy that Unity doesnt support this by default.
The text was updated successfully, but these errors were encountered: