8,288
edits
XML talk:TRAM: Difference between revisions
m
no edit summary
Paradox-01 (talk | contribs) mNo edit summary |
Paradox-01 (talk | contribs) mNo edit summary |
||
| Line 285: | Line 285: | ||
|<!--image--> | |<!--image--> | ||
|} | |} | ||
STRCOMrun_thw_fw_p and STRCOMrun_thw_fw_pl are identical. That means the engine picks the correct TRAM by using an unkown context, possibly this is similar or part of the distiction of "forward" (face-to-face) and "backward" (face-to-back). | |||
: '''Maybe the algorithm checks always tgt's rotation and relative position to src at the same time but for most cases only tgt's rotation (facing) is relevant.''' | |||
Also, STRCOMrun_thw_fw_p(l) routing to Thrown5 and Thrown6 shows that Thrown anim types might be used however we like. A src-tgt-anim-type-pairing might be simply a ''convention''. Well, someone could check the source code... | |||
==Variants== | ==Variants== | ||
| Line 291: | Line 297: | ||
* The variant (varient [sic]) pickup system is not clear yet: is a RIFCOM idle and a RIFNAT idle both possible? | * The variant (varient [sic]) pickup system is not clear yet: is a RIFCOM idle and a RIFNAT idle both possible? | ||
** Or do rightpistole, leftpistol, rightrifle and leftrifle variants count as subsets of combat? | ** Or do rightpistole, leftpistol, rightrifle and leftrifle variants count as subsets of combat? | ||
==What we know and not know== | ==What we know and not know== | ||