Linked mesh problems

Crocodilum

Hello!

I've read this topic Linked Mesh Bug, but I have quite the same bug, a crash, and another weird behavior.

Here's my process. It's quite simple. My goal is to use several card faces, and only one image card back. So, each card face would be a linked mesh, so I can rotate my card and see the back easily.

So, in the Setup, I have made a basic mesh on my card face. I create a linked mesh, then I rename the new created one into the card back.
Loading Image

1. First bug
Then, I cannot duplicate the bone or else Spine is crashing.

Here's the log:

Spine Launcher 3.5.01
Mac OS X x86_64 10.12
Java 1.7.0_51 Esoteric Software
64-bit Server VM
Up to date: Spine 3.4.02
Spine 3.4.02 Professional, JGLFW
Licensed to: *****, *****
ATI Technologies Inc.
AMD Radeon R9 M380 OpenGL Engine
2.1 ATI-1.44.68
Using customized hotkeys.
Started.
Sorry, an unexpected error has occurred:
java.lang.ArrayIndexOutOfBoundsException: 2
   at mv.a(SourceFile:153)
   at As.g(SourceFile:293)
   at Jy.a(SourceFile:544)
   at Jy.b(SourceFile:488)
   at Jy.a(SourceFile:461)
   at KI.Q(SourceFile:406)
   at Ln.a(SourceFile:3824)
   at gd.a(SourceFile:28)
   at en.a(SourceFile:181)
   at en.a(SourceFile:146)
   at com.badlogic.gdx.scenes.scene2d.ui.Button.b(SourceFile:123)
   at eP.b(SourceFile:91)
   at gf.b(SourceFile:89)
   at et.a(SourceFile:58)
   at ev.b(SourceFile:353)
   at p.b(SourceFile:96)
   at aq.b(SourceFile:91)
   at o.a(SourceFile:81)
   at ap.e(SourceFile:137)
   at ac.e(SourceFile:213)
   at ne.e(SourceFile:97)
   at ah.run(SourceFile:189)
   at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:251)
   at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:733)
   at java.awt.EventQueue.access$200(EventQueue.java:103)
   at java.awt.EventQueue$3.run(EventQueue.java:694)
   at java.awt.EventQueue$3.run(EventQueue.java:692)
   at java.security.AccessController.doPrivileged(Native Method)
   at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76)
   at java.awt.EventQueue.dispatchEvent(EventQueue.java:703)
   at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:242)
   at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:161)
   at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150)
   at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:146)
   at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:138)
   at java.awt.EventDispatchThread.run(EventDispatchThread.java:91)

What I did was I duplicated the slot instead, and it worked. I just had to create another bone, and drag my new copy slot inside. Tricky but it worked.
Loading Image

2. Second bug
Next, I went in the Animate mode, I just made a rotation on the card itself using the mesh. I know I could use scale, but not for what I intend to do in the future. For now I only use my first image, my card face, the '6'. Next step would be to swap image and show the back.
Loading Image

Then the weird behavior happens. I go on frame 5, the middle of my animation. And there, I want to switch my image.
And my animation is ruined because the new display image use its source mesh and replace the actual mesh.

Before:
Loading Image

After:
Loading Image

Once again, there's a trick, I just needed to do the image switch on another frame. Like frame 6. It creates a new weird mesh I didn't want, but it's ok, I just need to drag my key from the 5th frame on the 6th to replace it, then I can move all the keys from the 6th to the 5th. If you still follow, cool :p

Loading Image

Crocodilum

Nate

Can you try in Spine 3.5-beta? You'll need to change to the Latest version and check Beta updates in your Spine settings. Don't save your projects with 3.5 until you are ready, as you won't be able to open them again with 3.4.

When you duplicated the slot, it duplicated the source mesh and linked mesh, so now you have 2 source meshes, each with a linked mesh. This isn't what you want.

I expect it is fixed in 3.5, which will be going non-beta in a few days. If it still happens, please post or email (contact@esotericsoftware.com) a project file and we'll get it fixed ASAP.

Crocodilum

Alright, it still crashes. I sent you my project.

And what about the 2nd bug?

Nate

I didn't see a crash duplicating the slot in 3.5.08-beta. I did see a crash duplicate the bone, which has been fixed in 3.5.09-beta. Thanks! 🙂

BTW, you might want to move your attachment visibility keys that show the card back to about frame 5.4. You can do this by holding shift while dragging the keys. You can zoom in the timeline to be more accurate.