177
edits
State overlay system: Difference between revisions
Jump to navigation
Jump to search
m
→overlay file
Chris blues (talk | contribs) m (→Implementation) |
Chris blues (talk | contribs) m (→overlay file) |
||
| Line 28: | Line 28: | ||
</PropertyList> | </PropertyList> | ||
</pre> | </pre> | ||
Now you can put your items, which need to be set between the overlay tags. | Now you can put your items, which need to be set between the overlay tags. You only need to put properties in there, which differ from your default setup. | ||
Another rule of thumb is that you use the hierarchy of the property-tree's root. It speeded up my research by quite a bit, when I found out, it's possible to [[Howto:Create_animation_XML_files_from_Nasal|dump the PropertyTree]] with a nasal command. Open up the Nasal-console from the developer-menu and put in the following: <code>io.write_properties( path: "/home/myName/.fgfs/Export/PropTree.xml", prop: "/" );</code> | |||
Beware! This outputs the '''entire''' PropertyTree! This is several thousand lines long. You might want to dump only single folders of the PropertyTree by changing the <code>"/"</code> to sth like <code>"/controls"</code> or whatever folder you want to dump. Now you can simply delete everything from that file, that you don't need and copy&paste it into your overlay.xml. | Beware! This outputs the '''entire''' PropertyTree! This is several thousand lines long. You might want to dump only single folders of the PropertyTree by changing the <code>"/"</code> to sth like <code>"/controls"</code> or whatever folder you want to dump. Now you can simply delete everything from that file, that you don't need and copy&paste it into your overlay.xml. | ||