8,018
edits
Talk:Mod Tool/OniTools addon: Difference between revisions
m
evil patrol paths ...
Paradox-01 (talk | contribs) m (weapon html ready, relative path not allowing xml to be seen wasn't correct, it's the file:/// in the link) |
Paradox-01 (talk | contribs) m (evil patrol paths ...) |
||
| Line 10: | Line 10: | ||
===New code snippets=== | ===New code snippets=== | ||
Latest MT addon attempt. Reducing complexity by dropping support for adding AE resources. Vanilla material only. | Latest MT addon attempt. Reducing complexity by dropping support for adding AE resources. Vanilla material only. | ||
Download link to the "shared" collection should only provided if Oni retail installation is found on client machine. | |||
<s>Draging and droping items from Oni Object Library into MT works with Firefox but not Google Chrome. Have to look into this.</s> | <s>Draging and droping items from Oni Object Library into MT works with Firefox but not Google Chrome. Have to look into this.</s> | ||
| Line 21: | Line 23: | ||
[[Image:ModTool_addon_Sledgehammer_ONCC_library.jpg|thumb|200px|right|Oni Object Library, character page]] | [[Image:ModTool_addon_Sledgehammer_ONCC_library.jpg|thumb|200px|right|Oni Object Library, character page]] | ||
The relative path | The relative path of the xml is transformed into an absolute path when dropped into MT. | ||
If the link doesn't begin with file:/// MT will add it. I removed it from html file so xml can be clicked and viewed. | If the link doesn't begin with file:/// MT will add it. I removed it from html file so xml can be clicked and viewed. | ||
Scratching together... | |||
x = done | |||
- = not needed | |||
{| class="wikitable" width="100%" | {| class="wikitable" width="100%" | ||
! - | ! - | ||
| Line 89: | Line 94: | ||
| x | | x | ||
| - | | - | ||
| | | x | ||
| | | | ||
<!-- | --> | <!-- | --> | ||
| Line 103: | Line 108: | ||
| - | | - | ||
<!-- | --> | <!-- | --> | ||
| | | x | ||
| | | | ||
| x | | x | ||
| | | x | ||
|- | |- | ||
| layer support | | layer support | ||
| | | x | ||
| | | | ||
| | | | ||
| Line 116: | Line 121: | ||
| x | | x | ||
<!-- | --> | <!-- | --> | ||
| | | x | ||
| | | | ||
| x | | x | ||
| | | x | ||
|- | |- | ||
| PPG interface | | PPG interface | ||
| | | x | ||
| | | | ||
| | | | ||
| Line 129: | Line 134: | ||
| x | | x | ||
<!-- | --> | <!-- | --> | ||
| | | - | ||
| | | | ||
| x | | x | ||
| | | - | ||
|- | |- | ||
| save in project | | save in project | ||
| Line 162: | Line 167: | ||
more ... later | more ... later | ||
flags, tvs, crsa, | flags, patrol path, tvs, crsa, sound, script objects (spawnable geometry) | ||
Partol paths are the trickiest. There's no easy way to show the connection from flag to another. It might be possible with multiple chains used for rigging but that's not very confortable to deal with. | |||
Idea: add ID property to each used flag. When a flag is clicked, a PPG opens with a button to show flag connections (one lose chain with many bones, old one is deleted). MT also opens/updates an apllication (have to look into writing command line apps first). I guess that's necessary to preview (and edit) the complete xml code as this would be to awkward to code directly in MT. The xml file is saved on change events. MT reads that xml when a patrol path flag is selected. | |||