Animating a mesh suddenly stops working

alan mac

I'm having a problem with mesh animations. Transforming and keyframing vertices of a mesh works for a while, and then suddenly stops working. I'm no longer able to select or edit any vertices and have to restart Spine and re-open the project to get it to work again.

Oddly at the same time this happens I'm also unable to move keys on the timeline (I have to cut and paste instead of just moving frames with the mouse)

Any suggestions what I might be doing wrong?

I'm fairly new to Spine, so may be something stupid I'm doing. But it's done it several dozen times in the last two days and I can't see a pattern in anything I'm doing to cause it.

Any help appreciated! I've checked previous posts but can't see anything quite the same as this. I'm using version 3.5.42.

Thanks

Alan

alan mac

Nate

That is very strange, and a new one. Does pressing spacebar or escape to deselect help? Maybe Spine thinks you have a modifier key pressed. Can you try pressing and releasing both the left and right ctrl, shift, and alt keys? Does it happen in setup mode? Does it keep happening if you re-open the project without restarting Spine?

alan mac

Hi Nate,

Tried each of those suggestions but no luck.

It only happens in animate mode and only when I'm deforming a mesh. When it does happen it locks up all the meshes in a project, not just the one I'm working on.

If I just reload the project it stays broken, I have to re-start Spine to get it to work again. I've attached the project but I suspect it's nothing to do with this project in particular (I've had it happen on other projects and the previous version of Spine)

It seems to be happening more frequently now I have more than one deformable mesh.

I'm using the PC pro version on Windows 10 Pro.

I was hoping it was a common problem with an easy answer : (

Nate

We'll keep an eye out for it, but we run Spine a LOT and haven't seen this, so I'm not super hopeful. 🙁 Maybe there is some unique set of actions you take that we don't, and that triggers it? The fact that it stays after you reload the project means it's like some editor state that gets bad, rather than something in the project.

alan mac

I upgraded to 3.6.02 this morning and whatever it was that was causing it isn't doing it anymore!

Thanks!