a520345203

我真的很生氣。

1.可以請貴公司先針對你們輸出的 JSON檔做一個統一嗎?不然就算再多的新功能但是系統不支援新版JSON寫法一樣沒有用。

2.或者你們匯出時選擇舊版本匯出。

3.舊版本所匯出的JSON檔案 新版本應該要可以支援才對。指示修改一些指令的寫法不可能做不到。


讓新舊版之前不再有這麼多的隔閡,或許這才是用戶所想要的。並不是更多的功能而是對 WEB Engine 有更好的支援。
a520345203
  • Posts: 1

Nate

a520345203 wrote:1.可以請貴公司先針對你們輸出的 JSON檔做一個統一嗎?不然就算再多的新功能但是系統不支援新版JSON寫法一樣沒有用。
Can you please make a unified one for the JSON file you output? Otherwise, even if there are more new functions, but the system does not support the new version of JSON, it is useless.
When we add features to the Spine editor, we also add them to the Spine Runtimes. If you use the latest Spine editor, you need to update to the latest Spine Runtimes. If you use older Spine Runtimes, you should not use the latest editor. The editor and runtimes version must always match.
将功能添加到Spine编辑器时,我们还将它们添加到Spine运行时中。 如果使用最新的Spine编辑器,则需要更新到最新的Spine Runtime。 如果使用较旧的Spine运行时,则不应使用最新的编辑器。 编辑器和运行时版本必须始终匹配。
2.或者你們匯出時選擇舊版本匯出。
Or when you export, select the old version to export.
This is not possible, as the old Spine Runtimes may not have features in the newer Spine editor. If the old runtimes just ignore features, the skeleton will probably render incorrectly.
这是不可能的,因为旧的Spine运行时可能在新的Spine编辑器中没有功能。如果旧的运行时仅忽略功能,则骨架可能会渲染不正确。
3.舊版本所匯出的JSON檔案 新版本應該要可以支援才對。指示修改一些指令的寫法不可能做不到。
The new version of the JSON file exported from the old version should be supported. It is impossible to instruct to modify the writing of some instructions.
I'm not sure this translated correctly. An old Spine editor cannot possibly export JSON with new features that the old version doesn't know about.
我不确定此翻译是否正确。 旧的Spine编辑器可能无法导出旧版本不知道的具有新功能的JSON。

The JSON (and binary) data is for use with the version of the Spine Runtimes that matches the version of the Spine editor used to export the data. If you change the version of your Spine Runtimes, you should export your JSON data again from your Spine projects.
JSON(和二进制)数据与Spine运行时版本配合使用,该版本与用于导出数据的Spine编辑器版本匹配。 如果您更改Spine Runtime的版本,则应再次从Spine项目中导出JSON数据。

You should not try to use the same JSON with a newer or older Spine Runtimes.
您不应尝试将相同的JSON与更新或较旧的Spine运行时一起使用。

You should not delete your Spine projects and keep only the JSON, then later try to import the JSON data back into Spine. You can do that, but it is not a good workflow.
您不应该删除Spine项目并仅保留JSON,然后再尝试将JSON数据导入回Spine。 您可以这样做,但这不是一个好的工作流程。

You should not save your projects with a newer Spine editor, then export the data and try to import it into an older Spine editor. Sometimes this may work, but it isn't a good idea.
您不应该使用较新的Spine编辑器保存项目,然后导出数据并尝试将其导入较旧的Spine编辑器。 有时这可能有效,但这不是一个好主意。

Please do keep your Spine project files. Write a script to automate exporting all your project files if you change the version of your Spine Runtimes.
请保留您的Spine项目文件。 如果更改了Spine Runtime的版本,请编写脚本以自动导出所有项目文件。

Also, you should freeze your Spine editor version so it matches your Spine Runtimes. Don't let your animators use the latest editor when you are using older Spine Runtimes.
另外,您应冻结Spine编辑器版本,使其与Spine运行时匹配。 使用较旧的Spine运行时时,请勿让动画师使用最新的编辑器。

If you follow these guidelines, everything will work smoothly!
如果遵循这些准则,一切都会顺利进行!

I am sorry if my Chinese translations are not good.
对不起,我的中文翻译不好。
User avatar
Nate

Nate
  • Posts: 9993


Return to 中国Spine用户