Sure!
Since I used
Livery over MP, I think this is a very good explanation. However, there are a couple of things I struggled with:
1) In the howto, you use the 747 as an example. In the livery-xmls, there is (a) "<747-texture>Liveries/KLM.png</747-texture>" and in the models-xml, thie texture-prop is defined accordingly: (b) "<texture-prop>747-texture</texture-prop>". It took me a while to figure out that the XML-naming ist totaly free and that (b) defines the name to be used in (a). Most of the available aircrafts just use "livery". A small hint/explanation would be helpful to understand that this naming is free but has to match in both files.
2) In my first attempt, I forgot to add the .nas file. This resulted in a menue-item wich did not do anything at all.
3) As far as I can see, the howto does not give a hint on how to load the .nas file after it was generated. I added
- Code: Select all
<nasal>
<A310>
<file>Nasal/liveries.nas</file>
</A310>
</nasal>
to my -set.xml. Has this possibly been forgotten?
Without this entry, I see the same behaviour as in 2): A menu item without any reaction when clicking it.
4) The xml-parser does not like <model><model>...</model></model>. Example:
Aircraft/Models/A310-308.xml (the main model file):
- Code: Select all
<PropertyList>
.......
<model>
<name>Fuselage</name>
<path>Aircraft/A310/Models/Fuselage.xml</path>
<offsets>
<x-m> 0.0</x-m>
<y-m> 0.0</y-m>
<z-m> -0.35</z-m>
</offsets>
</model>
....
</PropertyList>
Aircraft/Models/Fuselage.xml:
- Code: Select all
<PropertyList>
...
<model>
<path>Fuselage.ac</path>
<animation>
<type>material</type>
<object-name>fuselage</object-name>
<property-base>sim/model/livery</property-base>
<texture-prop>texture</texture-prop>
<texture>Liveries/HF90.png</texture>
</animation>
</model>
...
</PropertyList>
This does not work because both files declare a <model> section inside each other. Removing the <model>-tag from fuselage.xml helped.[/list]
5) Maybe a "common errors" section could help. E.g.: "if your menu is visible but does not react on clicking, then your .nas or include section is wrong or the xml files are mixed up".
For the
Howto:Edit a livery, there´s just one remark but I´, not sure if this is a bug in the rembrandt-engine or an intended feature:
If the initial livery is declared like this:
- Code: Select all
<animation>
<type>material</type>
<object-name>fuselage</object-name>
<property-base>sim/model/livery</property-base>
<texture-prop>texture</texture-prop>
<texture>Liveries/HF90.png</texture>
</animation>
Then this single png (here: HF90.png) is not allowed to contain any full or partly transparent pixels. An alpha channel is ok as it is does not affect any pixels. For all the other .png loaded by clicking on one of the menu-items, alpha-pixels are ok. Same for the .png noted inside the .ac files: no problem here. Once the initial .png is "contaminated" with an alpha, all parts of the aircraft covered by this file look funny orange-green:
So: unless this is not fixed or declared a feature, a hint in the howto would help.
I hope this helps. Thank you for all the help and howtos!
Sascha