- 수정됨
Crash when changing to animate mode
I just started getting a crash when trying to change to animate mode.
The project file is at:
http://www.chrismweb.com/temp/dress_up_game.project
What happened:
One of the images/slots wasn't rendering in the runtime, but was identical to all others AFAIK. Checked skeleton.json- identical to the other "calf highlight". But, in the animations, all of them have an entry for it under "slots", like the hand (which actually gets changed out with another hand, so supposed to be there).
The entry:
"slots": {
"calf_R_1L": {
"color": {
"0": { "color": "ffffffff", "curve": "stepped" },
"3": { "color": "ffffffff" }
}
},
"hand L": {
"attachment": { "0": "dress up game/800x480/hand_L_cupped", "3": "dress up game/800x480/hand_L_cupped" }
}
BUT I don't actually change the color anywhere. I was trying to change the color in setup mode (all my graphics are white, and colorized in game, but they are hard to see, layered in spine).
So I deleted the graphic+ slot in spine, and re-added it. Now it crashes whenever I try to go to animate, with or without the 'calf_R_1L' "slot"/image in spine.
So I think it somehow got stuck thinking the calf file is supposed to be animated/ color animated, even when it doesn't exist?
Thanks for the detailed report Chris, we'll look into that ASAP. There is an update coming out within the next couple of days probably, hopefully we can have that fixed by then
Thanks Shiu.
Do you know if there is a way to edit the project and remove the item ('calf_R_1L') completely from it?
Thanks!
Hi, sorry about the delay, I just moved to another country.
There was a bug where deleting a slot when there were animations that had keys on the color or image change for that slot would cause a crash when switching to animate mode. This will be fixed in 1.0.9. This must have been what happened to your project. I've fixed your project, which is attached.
Thanks Nate!
Out of curiosity, which country did you move to? You were in Austria with Mario before?
The program is very helpful, thanks again!
Hey, it's crashing when switching to animate mode (I just used my original project, but with 1.09):
The error in the log is:
java.lang.ArrayIndexOutOfBoundsException: -1
at com.badlogic.gdx.utils.Array.get(Unknown Source)
at z.a(Unknown Source)
at gh.a(Unknown Source)
at com.esotericsoftware.spine.editor.Editor.b(Unknown Source)
at hc.changed(Unknown Source)
at com.badlogic.gdx.scenes.scene2d.utils.ChangeListener.handle(Unknown Source)
at com.badlogic.gdx.scenes.scene2d.Actor.notify(Unknown Source)
at com.badlogic.gdx.scenes.scene2d.Actor.fire(Unknown Source)
at com.badlogic.gdx.scenes.scene2d.ui.Button.setChecked(Unknown Source)
at com.badlogic.gdx.scenes.scene2d.ui.Button$1.clicked(Unknown Source)
at com.badlogic.gdx.scenes.scene2d.utils.ClickListener.touchUp(Unknown Source)
at com.badlogic.gdx.scenes.scene2d.InputListener.handle(Unknown Source)
at com.badlogic.gdx.scenes.scene2d.Stage.touchUp(Unknown Source)
at com.badlogic.gdx.InputMultiplexer.touchUp(Unknown Source)
at com.badlogic.gdx.backends.lwjgl.LwjglInput.processEvents(Unknown Source)
at com.badlogic.gdx.backends.lwjgl.LwjglCanvas$3.run(Unknown Source)
at java.awt.event.InvocationEvent.dispatch(Unknown Source)
at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
at java.awt.EventQueue.access$200(Unknown Source)
at java.awt.EventQueue$3.run(Unknown Source)
at java.awt.EventQueue$3.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
(when I click on animate- I updated the project in the above link)
The old project file will still have the error in it since it was saved with 1.08 not sure we can do anything about this. Maybe Nate can elaborate.
No, it's alright- I opened up the project he posted back, and it worked fine
I had figured it wouldn't matter since spine had been updated, and had thought it would be fixed on saving out.
Thanks!
Your project file got corrupted from the bug, so I had to recover the data in your project.