Jump to content

XML talk:TRAM: Difference between revisions

m
→‎Parts of page in need of updating: marking motion blur item as completed; a couple suggested changes to Paradox's words to try to clarify, please correct me if I'm wrong
m (→‎Parts of page in need of updating: marking motion blur item as completed; a couple suggested changes to Paradox's words to try to clarify, please correct me if I'm wrong)
Line 4: Line 4:
*<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>
*<strike>The part about extents says that Neo will have to make OniSplit calculate them automatically; doesn't it do that now?</strike>
*<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.
:: 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. '''--Paradox'''
*<strike>The "Excel macro" should be rewritten as stand-alone application. Also, its support for XSI should be dropped in favor of blender.</strike>
*<strike>The "Excel macro" should be rewritten as stand-alone application. Also, its support for XSI should be dropped in favor of blender.</strike>
:: That's the theory. Until OniX isn't going to be ... ahem ... a game changer, there will be probably no demand for this. A similar note was added on the non-talk page.
:: That's the theory. Until OniX is ... ahem ... a game changer, there will be probably no demand for this. A similar note was added on the non-talk page. '''--Paradox'''
*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.
--[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 00:12, 17 March 2021 (CET)
--[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 00:12, 17 March 2021 (CET)


Additionally to the updates, I'd say the TRAM page should be marked "complete" when ...
Additionally to the updates, I'd say the TRAM page should be marked "complete" when following things are done:
: ... following things are done:
* <strike>motion blur (mini tutorial?)</strike>
* motion blur (mini tutorial?)
* impact effects (mini tutorial?)
* impact effects (mini tutorial?)
* TRAM picking mechanism: it gets easier to this mechanism if we differentiate between pool construction and pool usage
* TRAM picking mechanism: it gets easier to explain this mechanism if we differentiate between pool construction and pool usage
* throw pair animation table
* throw pair animation table
* a simple tutorial to let a modder warm up with animations in Blender (it's okay if it rather resembles "round trip") since this page is about the file type itself (therefore: import and export)
* a simple tutorial to let a modder warm up with animations in Blender (it's okay if it rather resembles "round trip") since this page is about the file type itself (therefore: import and export)