Opened 12 years ago
Closed 11 years ago
#33 closed defect (fixed)
Error when extracting ONCC with TRAM
Reported by: | EdT | Owned by: | s10k |
---|---|---|---|
Priority: | major | Component: | Vago |
Keywords: | Cc: |
Description
According to paradox, when extracting ONCCred_hard_1 with TRAMREDCOMcomb_p you get error messages such as
Cannot find instance 'TRAMKONCOMthrow_rev'
Cannot find instance 'TRAMKONCOMthrow_rev'
Cannot find instance 'TRAMKONRIFturn_right'
Cannot find instance 'TRAMKONOKOlev18_ZomStand'
Cannot find instance 'TRAMKONOKOcorner_hide'
Cannot find instance 'TRAMKONPIScorner_hide'
The problem is that these TRAMS are listed in TRACkonokocore_animations, but were not in included with the Oni.
I noticed you are using the command -extract:dae -search level0_Final <output dir> -anim:TRAMREDCOMcomb_p <path_to_ONCCred_hard_1.oni>
In AETools I have been using this command:
-extract:xml <output dir> -anim-body:<path_to_ONCCred_hard_1.oni> <path_to_TRAMREDCOMcomb_p.oni>
Change History (8)
follow-up: 2 comment:1 by , 12 years ago
comment:2 by , 12 years ago
Yes that function should be moved. When you are on it maybe consider rearrange some more functions. Like:
XML, Levels, Characters, Objects, Textures, Misc
XML: xml <=> oni
Levels: dat <=> oni; oni => dae; xml master file => oni/dat
Characters: oni <=> dae; FILM dat => xml; ONCC oni + TRAM oni => dae + xml
Objects: M3GM oni <=> obj; M3GM oni + OBAN oni => dae; OBAN (cam) <=> dae
With that the user shouldn't confuse animations anymore cuz they are either part of Characters or Objects.
Also now that we have ..
-extract:xml <output dir> -anim-body:path_to_ONCC path_to_TRAM
the older function could be removed:
-extract:dae -search level0_Final output_dir -anim:TRAM path_to_ONCC
I find the combined export of dae and xml much more elegant.
Opinions?
comment:3 by , 12 years ago
Side note 1:
-extract:dae can't extract ONCC with alien animations (e.g. Barabus with Fury punch doesn't work)
-extract:xml can extract ONCC with alien animations
Side note 2:
-extract:dae need search folder and additional files: TRAC, TRMA, TXMPs
-extract:xml doesn't need those (xml export rulz! ^_^
)
comment:5 by , 12 years ago
Characters: oni <=> dae; FILM dat => xml; ONCC oni + TRAM oni => dae + xml
By "oni <=> dae" you mean "ONCC oni <=> dae" right?
btw should Vago ignore "Cannot find instance 'TRAMKONCOMthrow_rev'" kind of errors by default?
Talked with Neo too and seems indeed that extract:dae is deprecated. I will replace it with extract:xml.
comment:6 by , 12 years ago
I had a look at the wiki again. To be fully correct it would be "TRBS/ONCC oni <=> dae" for -extract:dae (character mesh without animation).
There's also a possibility to use -extract:xml for "TRBS oni <=> xml + dae". Can you allow this for Vago's Character tab, too?
I think the xml variant is great because it extracts all five 3D meshes of the TRBS. Latest high poly characters use that xml file also for import. So this would be a good addition here.
should Vago ignore "Cannot find instance 'TRAMKONCOMthrow_rev'" kind of errors by default?
I guess we won't see that error if you remove -extract:dae for Characters. :-)
There are a lot of commands in here, to avoid confusion let's look on this summary. I think we agree on those:
Delete: -extract:dae -search search_path output_path -anim:TRAM path_to_ONCC
Add: -extract:xml output_path -anim-body:path_to_ONCC path_to_TRAM
Keep: -extract:dae output_path path_to_TRBS/ONCC
Add: -extract:xml output_path path_to_TRBS
comment:7 by , 12 years ago
Owner: | set to |
---|---|
Status: | new → accepted |
comment:8 by , 11 years ago
Resolution: | → fixed |
---|---|
Status: | accepted → closed |
I think I've fixed all in the latest 0.9 version, if not re-open this.
Thanks all.
Hi seems Vago also supports that command using:
General > ONI to XML > Another TRAM > Convert
I wonder if you guys which use much more this conversions than me would prefer this to be moved for models or animations? (as ONI to XML)