19,185
edits
TRAM setup assistant: Difference between revisions
m
better to use {{finish}} so that we get the banner at the top; adding cat for status of tool
Paradox-01 (talk | contribs) mNo edit summary |
m (better to use {{finish}} so that we get the banner at the top; adding cat for status of tool) |
||
| Line 1: | Line 1: | ||
{{finish}} | |||
==Requirements== | ==Requirements== | ||
This program works with XSI generated DAE files. It's meant to create complete new TRAMs. For minior tweaking of XML animation files you would use a simple text editor. | This program works with XSI generated DAE files. It's meant to create complete new TRAMs. For minior tweaking of XML animation files you would use a simple text editor. | ||
==Data generation== | ==Data generation== | ||
| Line 11: | Line 10: | ||
* use the attack library to get the important data and fill in the rest by hand | * use the attack library to get the important data and fill in the rest by hand | ||
* drag and drop an existing animation (XML or ONI) to fill all fields, then apply changes if you need to | * drag and drop an existing animation (XML or ONI) to fill all fields, then apply changes if you need to | ||
===Normal animations=== | ===Normal animations=== | ||
| Line 17: | Line 15: | ||
Besides that, any attack and non-attack move that isn't a throw can be made in mode "normal animation or attack". | Besides that, any attack and non-attack move that isn't a throw can be made in mode "normal animation or attack". | ||
===Combined TRAM and OBAN creation=== | ===Combined TRAM and OBAN creation=== | ||
| Line 32: | Line 29: | ||
In XSI generated DAE files, the desired x position (analog for y) are inside the child tag of <source id="pelvis_translation_X-anim-output"> whereas only the first value of the array is of actual interest. That's so because the other values are calculated from that values plus the relatives values from the reconverted TRAM*.xml file. That's not elegant but easy as the TRAM holds heights and velocities for each frame. The DAE file contains only keyframes. | In XSI generated DAE files, the desired x position (analog for y) are inside the child tag of <source id="pelvis_translation_X-anim-output"> whereas only the first value of the array is of actual interest. That's so because the other values are calculated from that values plus the relatives values from the reconverted TRAM*.xml file. That's not elegant but easy as the TRAM holds heights and velocities for each frame. The DAE file contains only keyframes. | ||
===Throw source animation=== | ===Throw source animation=== | ||
Mode: "throw source" | Mode: "throw source" | ||
===Throw target animation=== | ===Throw target animation=== | ||
Mode: "throw target" | Mode: "throw target" | ||
===Combined TS and TT creation=== | ===Combined TS and TT creation=== | ||
| Line 58: | Line 52: | ||
In this mode, also the source-target relations (TT teleport and throw distance) can be calculated by reading both DAE files at once. | In this mode, also the source-target relations (TT teleport and throw distance) can be calculated by reading both DAE files at once. | ||
[[Category:Completed modding tools]] | |||
[[Category: | |||
[[Category:Windows-only_modding_tools]] | [[Category:Windows-only_modding_tools]] | ||