New Discovery!
- Thread starter gecko
- Start date
Frosty
SOH-CM-2022
Fellas,
I have experimented a little by adding the following key events to the events.xml in the root folder and adding some assignments in-game.
<FUEL_SELECTOR_SET Caption="Fuel selector (set)" Type="engine"/>
<FUEL_SELECTOR_CENTER Caption="Fuel Selector center" Type="engine"/>
<FUEL_SELECTOR_RIGHT_AUX Caption="Fuel Selector Right Aux" Type="engine"/>
<FUEL_SELECTOR_LEFT_AUX Caption="Fuel Selector Left Aux" Type="engine"/>
<FUEL_SELECTOR_RIGHT Caption="Fuel Selector Right" Type="engine"/>
<FUEL_SELECTOR_LEFT Caption="Fuel Selector Left" Type="engine"/>
<FUEL_SELECTOR_ALL Caption="Fuel Selector All" Type="engine"/>
<FUEL_SELECTOR_OFF Caption="Fuel Selector Off" Type="engine"/>
What I have learned is the following:
- So far, you cannot add your own categories. That is why I have filed these commands under "engine". However, you can re-assign existing commands by changing the ' Type="XXXX" ' to one of the existing categories. I now have my flaps -commands under the "surface" instead of the "general" category.
- Most Fuel Selector commands seem to work. But alas, I saw no animation (I tried adding a simple selector model, named and animated according to the SDK, to one of my models). However, strange things happened when I added a drop tank to the aircraft of choice in the UI:
Without droptank, all commands worked, except the _SET, _CENTER and both _AUX commands.
With droptank, the _CENTER command worked but all others did not - until I dropped the droptank. This leads me to believe that the droptank is coupled to the _CENTER command. The other commands that refer to an onboard fuel tank might be influenced by the settings in the aircraft.cfg. I have not yet experimented with an aircraft that has auxiliary tanks defined in the .cfg to see if these tanks are also accessible.
I have experimented a little by adding the following key events to the events.xml in the root folder and adding some assignments in-game.
<FUEL_SELECTOR_SET Caption="Fuel selector (set)" Type="engine"/>
<FUEL_SELECTOR_CENTER Caption="Fuel Selector center" Type="engine"/>
<FUEL_SELECTOR_RIGHT_AUX Caption="Fuel Selector Right Aux" Type="engine"/>
<FUEL_SELECTOR_LEFT_AUX Caption="Fuel Selector Left Aux" Type="engine"/>
<FUEL_SELECTOR_RIGHT Caption="Fuel Selector Right" Type="engine"/>
<FUEL_SELECTOR_LEFT Caption="Fuel Selector Left" Type="engine"/>
<FUEL_SELECTOR_ALL Caption="Fuel Selector All" Type="engine"/>
<FUEL_SELECTOR_OFF Caption="Fuel Selector Off" Type="engine"/>
What I have learned is the following:
- So far, you cannot add your own categories. That is why I have filed these commands under "engine". However, you can re-assign existing commands by changing the ' Type="XXXX" ' to one of the existing categories. I now have my flaps -commands under the "surface" instead of the "general" category.
- Most Fuel Selector commands seem to work. But alas, I saw no animation (I tried adding a simple selector model, named and animated according to the SDK, to one of my models). However, strange things happened when I added a drop tank to the aircraft of choice in the UI:
Without droptank, all commands worked, except the _SET, _CENTER and both _AUX commands.
With droptank, the _CENTER command worked but all others did not - until I dropped the droptank. This leads me to believe that the droptank is coupled to the _CENTER command. The other commands that refer to an onboard fuel tank might be influenced by the settings in the aircraft.cfg. I have not yet experimented with an aircraft that has auxiliary tanks defined in the .cfg to see if these tanks are also accessible.
Last edited: