Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

skeleton mesh‘s shape editor can’t save after restart main world editor! #1048

Closed
ghost opened this issue Jul 8, 2023 · 4 comments
Closed

Comments

@ghost
Copy link

ghost commented Jul 8, 2023

skeleton mesh‘s shape editor can’t save after restart main world editor!

condition:
1.mesh and animation from Mixamo and its .dae file

but its weird that in 3.10.1 ver‘s demo project the “soldier_rigged.DAE” can save after restart world editor(in 3.10.1),
And i can’t restore “soldier_rigged.DAE” to 4.0.3 ver‘s shape editor because can't apply animation it report error (general understanding of UX).
So i cant find a alternative workflow of animation of skeleton mesh for the 3.10.1 and 4.0.3

issue may connect to:
#1047
https://github.com/TorqueGameEngines/Torque3D/issues/1047#issue-1794787230

#1043
https://github.com/TorqueGameEngines/Torque3D/issues/1043#issue-1789218604

step and output info:
01

02

@ghost
Copy link
Author

ghost commented Jul 8, 2023

骨架网格体的形状编辑器在重新启动主世界编辑器后无法保存!

条件:1.来自Mixamo及其.dae文件的网格和动画

但奇怪的是,在 3.10.1 Ver 的演示项目中,“soldier_rigged。DAE“可以在重新启动世界编辑器(在 3.10.1 中)后保存,并且我无法恢复”soldier_rigged。DAE“到 4.0.3 版本的形状编辑器,因为无法应用动画它报告错误(对 UX 的一般了解)。所以我找不到 3.10.1 和 4.0.3 的骨架网格动画的替代工作流程

问题可能连接到: #1047 https://github.com/TorqueGameEngines/Torque3D/issues/1047#issue-1794787230

#1043 https://github.com/TorqueGameEngines/Torque3D/issues/1043#issue-1789218604

步骤和输出信息: 01

02

im sorry that i found before you can save info ,you should nav to the module make sure has two lines or fill two lines(not shown in the module properties in the 4.0.3 editor ):
before:
<DeclaredAssets Extension="asset.taml" Recurse="true"/>

after filled:
<DeclaredAssets canSave="true" canSaveDynamicFields="true" Extension="asset.taml" Recurse="true"/>

ps:i referenced from community project:FPSplayer https://github.com/Torque3DResources/FPSPlayer it may contents best-practice how-to somehow. recommend that take action after full systematically review it.
steps:

01
02
03

@Areloch
Copy link
Contributor

Areloch commented Jul 8, 2023

I've been trying to replicate this but not really having much luck.

To be sure I'm following along right, the steps would be:

  1. Have a character model imported in
  2. Add a new animation to it, click the save button
  3. Close the editor, then re-open it and the new animation is gone
  4. edit the DeclaredAssets define on the module the character model asset is in to have the canSave values as true
  5. Re-add the new animation, and it saves properly

If the above is all correct steps, Is it possible you can upload the shown art somewhere so I can try to replicate it this end? Also what version of T3D is it?

@ghost
Copy link
Author

ghost commented Jul 9, 2023

I've been trying to replicate this but not really having much luck.

To be sure I'm following along right, the steps would be:

  1. Have a character model imported in
  2. Add a new animation to it, click the save button
  3. Close the editor, then re-open it and the new animation is gone
  4. edit the DeclaredAssets define on the module the character model asset is in to have the canSave values as true
  5. Re-add the new animation, and it saves properly

If the above is all correct steps, Is it possible you can upload the shown art somewhere so I can try to replicate it this end? Also what version of T3D is it?

hi,i feel sorry, i can't restore it now too,even after i start a virtual mechine of win10.
thank your for time,but i actually encounter it in 3.10.1 and 4.0.3 and i don’t know why.
but one can have a try if encounter “can't save”,
thank community and i feel sorry about it.

@Areloch
Copy link
Contributor

Areloch commented Jul 10, 2023

No worries, sorry I couldn't be more of a help there.
Hopefully it doesn't come back up in the future and then neither of us have to worry about it :)

I'll go ahead and close this for now then, but if it crops back up again, feel free to make another issue report!

@Areloch Areloch closed this as completed Jul 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant