• Editor

  • Spine editor and runtime version management

    engleski
Related Discussions
...

Sorry but I have no clue how to run JSON rollback :/
I downloaded Skeleton Viewer, imported there JSON from newer Spine version and no options are there to save it, change or so.
Similar, you gave link to the JSON roolback (spine-runtimes/JsonRollback.java at master) but all I can find is a wall of lines. Dont really know what to do with this to run JSON rollback. All is clear to the point: "Run the JsonRollback tool." because cant download it or run as exe or JAR like skeleton viewer.

I would be grateful for help ! 🙂

  • Nate

  • Objava #42
  • This post is in engleski

The rollback tool is inside Skeleton Viewer. Instructions from first post in this thread, run like this:

java -cp skeletonViewer.jar com.esotericsoftware.spine.JsonRollback input.json output.json

Though I'm not sure it's what you want, as it is for going from 3.4 to an older version. If you want to go from 3.5 to 3.4, you can probably just export to JSON and import data into 3.4.

3.5 export, 3.4 import works, thank you so much for help 🙂

Back to my problem with run JSON rollback in the Skeleton Viewer, it was that I dont know how to run this. "Run" for me is, speaking colloquially, just double click on the icon and run like all applications. Anyways, like I wrote above, your idea works

7 dana kasnije

  • NTTP

    • Objava #44
    • This post is in engleski

    Hey Guys I could really use some help.
    I updated to Spine version 3.5.3 not realizing that the developers I work with were using an older runtime (3.4.00)
    I now need to import all these animations back to version 3.4.00 but I am facing a problem and I could really use some advice.
    When I use a JSON exported from version 3.5.3 and try to import it to version 3.4.0 the animations come out rather bad. There are some huge glitches that appear and I am not sure how we can solve this problem.
    I tried to use the Skeleton viewer because I wanted to see if its roll back tool would be of any help however the Skeleton viewer doesn't run on my machine for some reason. It crashes on start up and I can't think of any solutions....I have downloaded java on my machine but I can't think of where I am going wrong or what I can do differently. PLEASE any advice would be really appreciated right now

    • Nate

    • Objava #45
    • This post is in engleski

    If the 3.5 JSON imports successfully into 3.4, then that is probably as good as it gets. The rollback tool was from 3.4 to 3.3, and even then it just makes changes to the JSON structure, it doesn't manipulate the actual animation data.

    I'm not sure why it looks wrong in 3.4. Unfortunately you will probably need to choose whether to fix it up in 3.4, or get the developers to move to 3.5.

    • NTTP

      • Objava #46
      • This post is in engleski

      Thanks so much for taking the time to reply to me.
      I have a few observations. Out of my 22 spine projects. nearly 13 were exported with minimal issues however 8 of them have a lot of glitches.
      Speaking of these 8 files that have glitches in them, sometimes when I copy paste the keyframes into a new animation the glitches disappear and the animation returns to how it was in version 3.5.3. However in some cases copying and pasting these keyframes results in an even weirder animation...
      Also in the animations that have glitches I can't seem to manually change the key frames. For example if i want to move an ik constraints position it just doesn't add a key frame and even though auto keyframing is ON and when I move to the next frame and return back to the previous one the changes that I make disappear.

      My hope lies in the skeleton viewer now and the roll back tool do you have any idea if others have faced this problem with the skeleton viewer, i.e crashing on startup i mean and is there a way I can open it to use the roll back tool?

      • Nate

      • Objava #47
      • This post is in engleski

      If Skeleton Viewer crashes, show the log.

      As I said, if the JSON imported, the rollback tool won't help. You could post or email your 3.5 JSON and we can look at what happens when it is imported into 3.4. contact@esotericsoftware.com

      • NTTP

        • Objava #48
        • This post is in engleski

        I've copy pasted the log. I am an animator so I don't know much about command prompt or if this is what you were asking for. And I shall send an email shortly thanks again

        C:\Users\DELL>cd downloads

        C:\Users\DELL\Downloads>java -jar skeletonviewer.jar
        com.badlogic.gdx.utils.SerializationException: Error parsing file: spineboy/spin
        eboy.json
        at com.badlogic.gdx.utils.JsonReader.parse(JsonReader.java:77)
        at com.esotericsoftware.spine.SkeletonJson.readSkeletonData(SkeletonJson
        .java:111)
        at com.esotericsoftware.spine.SkeletonViewer.loadSkeleton(SkeletonViewer
        .java:165)
        at com.esotericsoftware.spine.SkeletonViewer.create(SkeletonViewer.java:
        121)
        at com.badlogic.gdx.backends.lwjgl.LwjglApplication.mainLoop(LwjglApplic
        ation.java:149)
        at com.badlogic.gdx.backends.lwjgl.LwjglApplication$1.run(LwjglApplicati
        on.java:126)
        Caused by: com.badlogic.gdx.utils.GdxRuntimeException: File not found: spineboy\
        spineboy.json (Internal)
        at com.badlogic.gdx.files.FileHandle.read(FileHandle.java:136)
        at com.badlogic.gdx.files.FileHandle.reader(FileHandle.java:163)
        at com.badlogic.gdx.utils.JsonReader.parse(JsonReader.java:75)
        ... 5 more
        java.lang.NullPointerException
        at com.esotericsoftware.spine.SkeletonViewer$UI.render(SkeletonViewer.ja
        va:706)
        at com.esotericsoftware.spine.SkeletonViewer.render(SkeletonViewer.java:
        312)
        at com.badlogic.gdx.backends.lwjgl.LwjglApplication.mainLoop(LwjglApplic
        ation.java:225)
        at com.badlogic.gdx.backends.lwjgl.LwjglApplication$1.run(LwjglApplicati
        on.java:126)

        C:\Users\DELL\Downloads>

        Nate wrote

        If Skeleton Viewer crashes, show the log.

        As I said, if the JSON imported, the rollback tool won't help. You could post or email your 3.5 JSON and we can look at what happens when it is imported into 3.4. contact@esotericsoftware.com

        I have posted the log in the comment above and have emailed my files to the email above. Thanks again for all your help and I would really appreciate any help I can get in regards to solving this issue.

        • Nate

        • Objava #49
        • This post is in engleski

        Thanks, I've updated the Skeleton Viewer to 3.5.33, which should fix your problem. It won't help with your project files though. We'll look at those as soon as we can.

        • NTTP

          • Objava #50
          • This post is in engleski

          thanks so much for that and thank you for looking into the project files...

          perhaps I am being a bit impatient but one small thing. I cant seem to open the json roll back tool. here is the log that I get when I try to run the command line

          Microsoft Windows [Version 6.1.7601]
          Copyright (c) 2009 Microsoft Corporation. All rights reserved.

          C:\Users\DELL>V
          '▬' is not recognized as an internal or external command,
          operable program or batch file.

          C:\Users\DELL>java -cp skeletonViewer.jar com.esotericsoftware.spine.JsonRollbac
          k input.json output.json
          Error: Could not find or load main class com.esotericsoftware.spine.JsonRollback

          C:\Users\DELL>cd downloads

          C:\Users\DELL\Downloads>java -cp skeletonViewer.jar com.esotericsoftware.spine.J
          sonRollback input.json output.json
          Exception in thread "main" com.badlogic.gdx.utils.SerializationException: Error
          reading file: input.json
          at com.badlogic.gdx.utils.Json.fromJson(Json.java:702)
          at com.esotericsoftware.spine.JsonRollback.main(JsonRollback.java:56)
          Caused by: com.badlogic.gdx.utils.SerializationException: Error parsing file: in
          put.json
          at com.badlogic.gdx.utils.JsonReader.parse(JsonReader.java:77)
          at com.badlogic.gdx.utils.Json.fromJson(Json.java:700)
          ... 1 more
          Caused by: com.badlogic.gdx.utils.GdxRuntimeException: Error reading file: input
          .json (Absolute)
          at com.badlogic.gdx.files.FileHandle.read(FileHandle.java:144)
          at com.badlogic.gdx.files.FileHandle.reader(FileHandle.java:163)
          at com.badlogic.gdx.utils.JsonReader.parse(JsonReader.java:75)
          ... 2 more
          Caused by: java.io.FileNotFoundException: input.json (The system cannot find the
          file specified)
          at java.io.FileInputStream.open0(Native Method)
          at java.io.FileInputStream.open(Unknown Source)
          at java.io.FileInputStream.<init>(Unknown Source)
          at com.badlogic.gdx.files.FileHandle.read(FileHandle.java:140)
          ... 4 more

          C:\Users\DELL\Downloads>java -cp skeletonViewer.jar com.esotericsoftware.spine.J
          sonRollback input.json output.json
          Exception in thread "main" com.badlogic.gdx.utils.SerializationException: Error
          reading file: input.json
          at com.badlogic.gdx.utils.Json.fromJson(Json.java:702)
          at com.esotericsoftware.spine.JsonRollback.main(JsonRollback.java:56)
          Caused by: com.badlogic.gdx.utils.SerializationException: Error parsing file: in
          put.json
          at com.badlogic.gdx.utils.JsonReader.parse(JsonReader.java:77)
          at com.badlogic.gdx.utils.Json.fromJson(Json.java:700)
          ... 1 more
          Caused by: com.badlogic.gdx.utils.GdxRuntimeException: Error reading file: input
          .json (Absolute)
          at com.badlogic.gdx.files.FileHandle.read(FileHandle.java:144)
          at com.badlogic.gdx.files.FileHandle.reader(FileHandle.java:163)
          at com.badlogic.gdx.utils.JsonReader.parse(JsonReader.java:75)
          ... 2 more
          Caused by: java.io.FileNotFoundException: input.json (The system cannot find the
          file specified)
          at java.io.FileInputStream.open0(Native Method)
          at java.io.FileInputStream.open(Unknown Source)
          at java.io.FileInputStream.<init>(Unknown Source)
          at com.badlogic.gdx.files.FileHandle.read(FileHandle.java:140)
          ... 4 more

          C:\Users\DELL\Downloads>A

          • Nate

          • Objava #51
          • This post is in engleski

          You need to specify an input.json file that exists. However, for the third time, if your data imports into the older version of Spine, that is the best you can hope for. The JsonRollback tool will not help you because it does not fix up the data, it only changes the JSON structure so it can be imported. It's most likely that any problems you see after importing into an older version come from using features in the newer version that don't exist in the old version. No amount of changing the JSON can make the old version have these newer features.

          We got your email, thanks. I imported your JSON into 3.4 and was presented a warning saying some data was lost because Nonessential was not checked when the JSON was exported. I opened your .spine file with 3.5, exported to JSON making sure to check Nonessential, and imported the JSON into 3.4. Everything looks fine.

          Thanks for reviewing the spine project. Before emailing you the file I had checked non-essential data while exporting my file but It did not improve the results any.
          The file that I sent you had a defeat animation which when imported to version 3.4.0 is effected the most. At this point I guess this is the most I can hope for and I would have to manually correct the errors that I come across.
          None the less your feedback is really appreciated it really did help a lot so thank you 🙂
          I don't recall using any of the new features like the sheer tool etc to much but I should now spend more time fixing these animations manually than try to look for any other solution.
          Thanks again!

          Hey Nate Problem Solved!
          thanks again for looking into my issue had it not been for your feedback I would never have tired the following solution...
          When I was animating in version Spine version 3.5.3. I was setting up keyframes for the sheer tool through out my animation even though I was not using the shear tool... Figure 1 shows what my time-line looked like (I selected the shear tool filter so that only the shear key frames are visible).
          You see when I would add a key pose I'd select all the bones and add a key frame for rotate translate scale and also sheer regardless of if I needed all of these or not. You can see in Figure 1 the sheer settings remain unchanged throughout the timeline even though the keyframes are present.
          So Since I wasn't really using the sheer tool I just deleted these keyframes from my file and then exported a JSON with non essential data checked.
          Now when I import my animations in version 3.4.0 things look much better.

          Thanks again for your help with all this Nate.
          So to sum up...
          The issue I was facing was that my animations were not coming out buggy when exporting from spine 3.5.3 to spine 3.4.0 even Though I knew I had not used the sheer tool or any other features that had not been available in version 3.4.0. Though I had not used these features I had non the less set key-frames for them in my original file and that is what was causing my exported JSON to not run as it ought to in Spine 3.4.0.
          Deleting the keyframes for Shear did the trick in my case,
          I hope if anyone else faces the same issue they can find a solution here.

          just an observation;- Graphs tend to lose some of their data during all this. In many of my imported animations I've had to revert my graphs to liner or curve because they've automatically changed to stepped during this export/import process. Also some animations are still buggy however copying the keyframes and pasting them in a new/blank animation timeline fixes the bugs.

          Not sure why shear timelines were causing problems, since 3.4 has shear. It's also very strange about the curves, especially if not all of the curves were affected the same way. While importing newer JSON data into an older Spine isn't technically supported, though it can often work, I wouldn't expect these two issues to be a problem. At any rate, I'm glad you got it working!

          7 mjeseci kasnije

          Let's say I desperately want to use 3.6 but I'm stuck to 3.5 because we still have bugs in unity with 3.6 to solve. (they were saying something about their script unable to see when an animation ends if it's 3.6) Do you think that if I avoid using new features such as tint black, clipping, etc. but do use some of the abilities the editor has to offer sich as soft selection, animation preview in setup and so on I'll have problems?

          Maybe. It's not something we officially try to support, so you'd have to try it and see what explodes. I think it should work fine, as we didn't change the data formats much.

          You can definitely see when an animation ends. Ask them to post a new thread with their question, it is likely very easy to solve, just an API usage issue. Point them at: API Reference - Spine Runtimes Guide

          The link for the json rollback tool is dead. How do I roll back my json files?

          The rollback tool was to go from 3.4 to 3.3. If you are going from 3.6 to 3.5, you probably don't need it. I've fixed the link to the source file in the first post. The rollback tool is part of Skeleton Viewer, so you need to download Skeleton Viewer unless you want to compiled the source.

          Thanks for the fast reply! Much appreciated! 🙂

          5 dana kasnije

          I cant import .Json from 3.6.35 to 3.5.51
          Any help? Its just simple animations without Shear or bounding boxes.

          If you post the JSON, we can try to figure out what data in there is prevents it from importing into 3.5.51.