Bjoern
worst developer ever
Unique features (confirmed thus far as working) include:
1. VC selectable wing fences and inlet test vane.
Why not make this permanently selectable?
(Info for Milton; needs to be coded into the model.)
Code:
<PartInfo>
<Name>XF-92_Wing_Fences</Name>
<Visibility>
<Parameter>
<Code>
(A:TITLE, string) 'FENCES' sstr 0 > if{ 1 } els{ 0 }
</Code>
</Parameter>
</Visibility>
</PartInfo>
Will activate when "FENCES" is contained in the [fltsim.x] entry's "title=" line.
Code:
<PartInfo>
<Name>XF-92_Inlet_Vane</Name>
<Visibility>
<Parameter>
<Code>
(A:TITLE, string) 'INL_VANE' sstr 0 > if{ 1 } els{ 0 }
</Code>
</Parameter>
</Visibility>
</PartInfo>
Will activate when "INL_VANE" is contained in the [fltsim.x] entry's "title=" line.
So all you'll have to do is create multiple [fltsim.x] entries for each configuration and you can select them from the aircraft menu. Next advantage: Milton won't have to export three different models. Third advantage: With a bit of folder and config file path magic, you can even have slightly different flight dynamics for each one. without many redundant model files and textures. 125% efficiency!
There's one more major item that I would like to implement but it's beyond my skills. I imagine that I need to have a fairly competent coder, like Brian or Bjoern. We'll see if I can convince someone! For now I'll leave it at this.
If it's engine related shenanigans, I'd provide a more universally applicable approach SOMEDAY. I've got a UI template set up for an engine damage gauge, but it is configured for piston engines and still lacks most, if not all, systems interactions. One of these days, it's going to be adapted to jets and turboprops, so you can put it into any plane you want. However, the whole thing is on the backburner since most of my dev time is taken up by the A320 and Metro.