8,013
edits
TRAM setup assistant: Difference between revisions
m
cutscene TRAMs needs to be registered in TRAC
Paradox-01 (talk | contribs) m (1st March 2016 ?) |
Paradox-01 (talk | contribs) m (cutscene TRAMs needs to be registered in TRAC) |
||
| Line 36: | Line 36: | ||
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. | ||
====TRAC edits==== | |||
New animations must be added in TRAC even if they are just for a cutscene. | |||
chr_animate will execute a TRAM when called from developer console but it will fail when called from BSL if not registered in TRAC. | |||
===Throw source animation=== | ===Throw source animation=== | ||