XML talk:TRAM: Difference between revisions

m
Yes, Onisplit is able create the attack ring and extents for a long time. Somehow nobody cared to update the section.
m (Note why Excel macro needs update. Though who is going to use it anyway? ^_-)
m (Yes, Onisplit is able create the attack ring and extents for a long time. Somehow nobody cared to update the section.)
Line 3: Line 3:
*<strike>The Vago documentation is for v0.8 and is obsolete.</strike>
*<strike>The Vago documentation is for v0.8 and is obsolete.</strike>
*<strike>The part about Blender just says that it's theoretically possible to use the program for animations! Link to a modern tutorial please.</strike>
*<strike>The part about Blender just says that it's theoretically possible to use the program for animations! Link to a modern tutorial please.</strike>
*The part about extents says that Neo will have to make OniSplit calculate them automatically; doesn't it do that now?
*<strike>The part about extents says that Neo will have to make OniSplit calculate them automatically; doesn't it do that now?</strike>
:: Yes, it does. I compared a pure XML extraction against a round-tripped XML-DAE-extraction: The DAE companioned XML gets extracted with no attack ring and extents, so for this test XML and DAE can converted straight back to ONI file format and re-extracted as pure XML. '''Conclusion: OniSplit creates attack ring and extents from DAE data, IMHO the new attack ring and extents match the original data not perfectly but still pretty good.
*The "Excel macro" should be rewritten as stand-alone application. Also, its support for XSI should be dropped in favor of blender.
*The "Excel macro" should be rewritten as stand-alone application. Also, its support for XSI should be dropped in favor of blender.
*This talk page needs an updating too! The material should be incorporated into the article or deleted.
*This talk page needs an updating too! The material should be incorporated into the article or deleted.
8,306

edits