XML:TRAM: Difference between revisions

m
→‎Excel macro: wording, linked to page for TRAM setup assistant
mNo edit summary
m (→‎Excel macro: wording, linked to page for TRAM setup assistant)
Line 836: Line 836:
====Excel macro====
====Excel macro====
[[Image:Animation_macro_v4.png|right|thumb]]
[[Image:Animation_macro_v4.png|right|thumb]]
For all TRAMs except overlays. [https://www.youtube.com/watch?v=vDTPYfvMf4M Demo vid here].
The Excel macro can be used to create any TRAM except overlays. [https://www.youtube.com/watch?v=vDTPYfvMf4M Demo vid here].


This Excel macro should be rewritten as .NET framework or .NET app because Excel is not freeware.
The macro should be rewritten as a .NET framework or application because Excel is not freeware. However, the tool was made with XSI in mind (for getting animation pair-based information). As XSI is mostly considered obsolete by the community, research for doing the same with Blender will be needed.
: There is a problem though. '''That tool was made with XSI in mind''' for getting (animation) pair based information.
: As XSI is out of date research for doing the same with blender will be needed.
: There was some development for an '''TRAM setup assistant''' in 2016 but drifted into inactivity since the community showed no sign of demand for an updated tool.
: By now there is a Blender script to create throw target adjustment data. So, instead of writing a new stand-alone app, at least the creation of header data might be better ported to the Blender script.


'''Usage:'''
There was some development of a .NET-based '''[[TRAM setup assistant]]''' in 2016, but the work drifted into inactivity since the community showed no sign of demand for an updated tool.
 
As of now there is a Blender script for creating throw target adjustment data. So instead of writing a new stand-alone app, at least the creation of header data might be better ported to the Blender script.
 
'''Macro usage:'''
* Put your files into the "input_and_output" folder.
* Put your files into the "input_and_output" folder.
* Disable macro security if you don't want to have to click on the "Enable Content" button every time.
* Disable macro security if you don't want to have to click on the "Enable Content" button every time.
* Close other worksheets before you run the macro.
* Close other worksheets before you run the macro.
* If you are not afraid of VBA code, you can enter the dev environment by hitting Alt+F11. If you want to extend the attack library with more screenshots and settings, search for "LibraryThrows", " LibraryAttack", "Picture", and "CBAttackHelp.AddItem".
* If you are not afraid of VBA code, you can enter the dev environment by hitting Alt+F11. If you want to extend the attack library with more screenshots and settings, search for "LibraryThrows", "LibraryAttack", "Picture", and "CBAttackHelp.AddItem".


===Run animations===
===Run animations===