Editor glitches when Spine Object selected

PeterBacall

Anyone else has this issue(?):
Every time I inspect a Spine Game Object in the Editor (that contains a Spine Mecanim or Spine Animation component), the screen/editor starts to aggressively glitch. At first I almost got a heart attack, thought my screen broke but it only appears when a Spine object is selected. Using MacBook Pro M1, latest spine runtime version, latest Unity (either 2022 LTS or 2023, both Silicon versions). Appears in any new/fresh projects too.

Harald

@PeterBacall Sorry to hear! This looks as if the skeleton's bone structure is overlaid over the wrong window. Does this occur with a new clean project with only the spine-unity runtime installed, when you open one of the Spine Examples example scenes? Or does it only occur with one of your own exported skeletons?

Could you please share a screenshot your Spine Preferences settings, located in Unity - Preferences - Spine? Does the situation change when you modify the Editor Bone Scale setting?

PeterBacall

Appears in clean projects. In the screenshots I'm using spine-unity 4.1 (updated 2023-08-21), Unity 2023.1.9.
Seems to appear in any Spine Examples scene.
Unfortunately modifying the Editor Bone Scale doesn't seem to help, not sure what it is supposed to change since the bones doesn't scale in the Editor, only the circles?
(see GIF at bottom)

Harald

PeterBacall Appears in clean projects. In the screenshots I'm using spine-unity 4.1 (updated 2023-08-21), Unity 2023.1.9.

That's very unfortunate then. We will investigate the issue, unfortunately we can't yet reproduce this issue on our end.

Unfortunately modifying the Editor Bone Scale doesn't seem to help, not sure what it is supposed to change since the bones doesn't scale in the Editor, only the circles?

Thanks for trying that out, you're right, it only changes the drawn circles but not the bones. It was just a quick guess which might have provided some more insights.

If anyone else has encountered such issues before or even has a solution to offer, please don't hesitate to let us know.

PeterBacall

Harald That's very unfortunate then. We will investigate the issue, unfortunately we can't yet reproduce this issue on our end.

I'm curious, did you test on one of the M1 chips? Using MacBook Pro or something else?

Should I file a bug report to Unity? Maybe something with their Editor

Nate

FWIW, since this looks like corrupt/fuzzy graphics, it may be a problem in Unity on the MacBook Pro M1 (or all Mac ARM).

PeterBacall

Just some extra notes/investigation: tested on my friends Macbook M1 Pro 14-inch, it had the same glitches. So M1 Max and M1 Pro confirmed...
I'm afraid if I file a bug report to Unity, they'll just take a glance at the project and say "it's because you have assets installed, contact them instead" etc (as they've usually done in the past). Not sure really where to go from here.

Nate

The best way to get Unity to listen is to cut the reproduction case down to the bare minimum: a project with Unity editor code that does only what is needed to cause the incorrect drawing.

We'll look into it further. Once Harald can reproduce it, he'll likely be able to say if we can implement a workaround.

Harald

@PeterBacall We have now pushed a potential bugfix for this issue.
New spine-unity 4.1 and 4.2-beta unitypackages are available for download:
https://esotericsoftware.com/spine-unity-download
Please let us know if the issue persists. Thanks for reporting!

For details see the following issue ticket:
EsotericSoftware/spine-runtimes2353

PeterBacall

Harald
Unfortunately, tried with a fresh project and it's still there 😕
Edit: FWIW, in Unity 2023.2 (beta) the glitches have become very rare in the inspector, but area instead visible in the Scene view. (They are visible in the Scene View in 2023.1 too, but more rare). Really weird

Harald

@PeterBacall Terribly sorry, the download links on the English spine-unity download page failed to update and were pointing to an older package. Could you please try again with the updated download link, the correct package date containing the fix is 2023-08-29:
https://esotericsoftware.com/spine-unity-download

PeterBacall

Harald
No worries! 2023-08-29 Doesn't seem to solve the glitches unfortunately :/

Harald

@PeterBacall Oh dear, sorry to hear. We can reproduce the issue on our end now at least. We will let you know once we've boiled the problem down to the problematic lines, we can then either hopefully provide a bugfix or report the bug to Unity.

Harald

@PeterBacall We could boil the issue down to a minimal reproduction project, it seems to be an issue with Unity. We have submitted a bugreport, hopefully it will be processed soon. We didn't receive a public ticket URL yet, but we will keep you informed as soon as we've received any updates from them.

PeterBacall

Harald

Really good to know, thank you for keeping me posted and for reporting to Unity! Hopefully they will fix it soon, cheers! 🍻

Harald

@PeterBacall Good news, we have just released new spine-unity 4.1 and 4.2-beta packages which should resolve the issue:
https://esotericsoftware.com/spine-unity-download
Big thanks go to user @Noeski here on this forum thread who discovered the fix!

PeterBacall

Harald

What an awesome timing and find @Noeski! Can confirm the issue is gone, thank you all! 🍻

Harald

FYI: Unity has created a public issue tracker ticket here:
https://issuetracker.unity3d.com/issues/visual-artifacts-appear-on-gameobject-and-in-the-editor-windows-when-gameobject-with-onscenegui-and-graphics-dot-drawmeshnow-is-moved-in-scene-view-on-macos
We've just informed them of the available fix (or workaround) and that if the checks are officially required that their docs should mention that.

Harald

Thanks for confirming, @PeterBacall, glad it's resolved!