If one has already successfully installed XMLTools simply skip any other installer that prompts you to install XMLTools. It's already done!

And how could this problem be resolved by removing the Red channel? How is it possible to remove the Red channel only anyway? Once I remove it in Photoshop, it switches the remaining channels to "Magenta", which cannot be converted through imagetool (throws an error). Note that the follow...

Not like that, no. All custom XML variables follow this format:

(L:MyCustomVariable,unit) where unit = bool, enum, or number

If that is the case I will not waste my time trying to supply content for P3D v4. It is not worth the time and expense for the limited return that the flight simulation market has today. What expense? VS2015 Express may be had for "free"... The SDK states that the VS2010 may be used, as w...

Use FSUIPC's Logging to see if there is an Event being fired continuously. This will block normal door operation because the number entry from the keyboard command is being blocked...

Nice Rob. I love the "Better On A Camel" livery... :)

UPDATE: I tried the trick of running a CMD Prompt in "Administrator Mode" and typing:

msiexec /i "C:\DATA\Prepar3D_v3_SDK_Setup_3.2.3.16769.msi"

but I still get the same silly error message!

Okay, this is beyond strange.

This is what I see when attempting to install Prepar3D_v3_SDK_Setup_3.2.3.16769...


Um, the last time I checked C:\ is a "local drive"! ;)

Rob, you are so naughty! ;)

You must "uninstall" the Prepar3D Client before running the Client .msi installer.

Or, if you insist on doing a full install of v3.1, then you must completely uninstall v3.0 first.

If you follow the very clear instructions to "Uninstall v3.0" first, your activation count will automatically be reset.

The top unit is COM1/NAV1 radio tuning.
The lower unit is COM2/NAV2 radio tuning.
The HSI uses only NAV1 for the CDI and GlidesLope.
(There is no "c" in glideslope). ;)

It appears that whoever scripted that G1000_config file mistakenly used double-slashes // for a "comment" instead of the correct <!-- comment --> or (* comment *) symbols.

Hello, Also, how do I access the various Vcockpit entries to show the different virtual cockpits. Example, the Mooney Bravo panel.cfg has two Vcockpit entries how do I access the 2nd one, if by default the 1st one is shown? No one answered your second question, or at least not specifically. You can...

They are identical in structure.