AlexandraA

Noody! THANK YOU!!!! With the Java SE Development Kit 15.0.2 it works!
AlexandraA
  • Mesajlar: 2

Nate

warmanw yazdı:
We have updated JsonRollback in Skeleton Viewer 4.0.54-beta to support specifying a version of 3.8 to go from 4.0.xx to 3.8.99.
So that means we can go back from 4.x to any 3.8.x maybe even 3.7.x?
Sorry I missed this. Yes, you can. However, as of 4.0.68-beta we've made it easier: you can choose an older version when exporting JSON.



This is equivalent to using the JsonRollback tool, but is easier. Going back to an older version may still lose data and may still require manual fix up, such as deleting attachments or constraints that do not exist in the older version. Exporting to an older version is still not a recommended workflow, it is provided only to help recover work after from the catastrophic situation where a newer Spine version was used unintentionally.
Kullanıcı avatarı
Nate

Nate
  • Mesajlar: 11349

warmanw

Thank you, Happy tears.

Kullanıcı avatarı
warmanw

Kickstarter Backer
  • Mesajlar: 277

bilalmirza

Hello, I have around 300+ spine exports, And the project i need to update is very old, spine 3.x. I Don't think i'll be able to find all the spine projects.
I need to update it to 3.8.
Is there a way to change all the json files (assuming only changing the json will make it work).
Kullanıcı avatarı
bilalmirza
  • Mesajlar: 37

Nate

@bilalmirza The process is: run 3.8, convert JSON to a project (.spine), run 4.0, export JSON from the project.

You can write a script to do it. I recently posted more information and the commands here:
Spine-Unity 3.8 to 4.0 Upgrade Guide
Kullanıcı avatarı
Nate

Nate
  • Mesajlar: 11349

bilalmirza

Thanks! just what i needed.
Sorry I missed that post, my bad.

---

All files were converted via tool you mentioned. Everything works perfect except for 1 file. Any idea why it could be?
Bu mesaja eklenen dosyaları görüntülemek için gerekli yetkilere sahip değilsiniz.
Kullanıcı avatarı
bilalmirza
  • Mesajlar: 37

Nate

Great! I can't tell from the problem from the screenshot, sorry.

In 3.8 when a constraint is applied, it may revert the changes made to bones by a previously applied constraint. In 4.0 that has been improved, but means your skeleton may not look the same as in 3.8 if you were relying on the constraint revert behavior. If that is the case, it will look wrong in both the editor and at runtime. To fix it you just need to find the constraint that you don't want applied and set the mixes to 0.
Kullanıcı avatarı
Nate

Nate
  • Mesajlar: 11349

bilalmirza

Sorry, I wasn't able to work on this for a month, It seem like the problem is related to skins(maybe) and not constraints, Or maybe the export itself.
I've removed meshes, constraints and skins in the following image. The scarf is exported as the fan.
Bu mesaja eklenen dosyaları görüntülemek için gerekli yetkilere sahip değilsiniz.
Kullanıcı avatarı
bilalmirza
  • Mesajlar: 37

Nate

I'm afraid I can't make much sense of what is going on, as I'm not familiar with your project. Does it look right in the editor? Have you tried rebuilding the atlas? Does it look right in Skeleton Viewer?
Kullanıcı avatarı
Nate

Nate
  • Mesajlar: 11349

bilalmirza

It looks right in the editor, and the skeleton viewer. Atlas rebuild doesnt work. I guess the problem is in the runtime on cocos2d-x end.
Kullanıcı avatarı
bilalmirza
  • Mesajlar: 37

Nate

You'll need cocos2d-x to use the 4.0 runtimes if you are exporting from the 4.0 editor. If you are using the 4.0 editor to create an atlas for the 3.8 runtimes, you'll need to check Legacy output.
Kullanıcı avatarı
Nate

Nate
  • Mesajlar: 11349

bilalmirza

im on coocs2d-x 4.0. Spine v4 export crash, 3.7 crashes, and only one that works is 3.8 but with weird skin results mentioned above.
Kullanıcı avatarı
bilalmirza
  • Mesajlar: 37

Mario

The spine-cocos2dx runtimes crash, or the Spine editor crashes? You can not use an export from e.g. version 3.8 in a Spine Runtime of version e.g. 4.0. Please make sure the Spine Editor version you exported from and the Spine Runtimes version match. If that is the case, and the Spine Runtimes still crash, then please send us the exported files and we can see if there's a bug in the runtime.
Kullanıcı avatarı
Mario

Mario
  • Mesajlar: 2631

bilalmirza

This issue was fixed by removing cocos2d-x default sp runtime and using the spines runtime https://github.com/EsotericSoftware/spine-runtimes
Thanks Mario for helping me out!
Cheers
Kullanıcı avatarı
bilalmirza
  • Mesajlar: 37


Dön Editor