UniqueID Invalid on Aircraft/Editing Acft.cfg File

[Randy Tyndall 1087023]

I originally posted this in the FSInn Help Forums, but no had answered the original poster's post from June 2009 and did not respond to mine either. Here is a copy of the warning I get when I start the FSInn Control Panel:

 

 

Warning: UniqueID Invalid on Aircraft

Title : Arizona Express Airlines Beech B1900D

dirname : PMDG EXPRESS B1900D

aircraftfltsim : fltsim.3

acheavy : 0

IDModel : B03894AB

IDTexture :

acVers : 2

acEngine : 5

UIManufacturer :

UIType :

UIVariation :

CSLACICAO :

CSLALICAO :

CSLACDESC :

CSLGeoWingAera :

CSLEmptyWeight :

CSLGroundAlt :

CSLGroundAngle :

 

Error Description :

 

 

This warning did not occur with the original "PMDG" livery that came with the purchased aircraft as I flew it online several times, but every "after purchase" add-on livery (2D cockpit, VC cockpit, and VC/Cabin Cockpit) displays this warning on FSInn startup, even if startup occurs from the desktop.

 

I also have the PMDG B737NG-600/700/800/900 added-on and several add-on liveries for each 737 series. None of these aircraft/liveries generate this warning.

 

Please note: I can "see" the aircraft livery on my screen in FS9 (in this example, the Arizona Express Livery) and the aircraft appears to function normally. However, in the Flightplan tab of FSInn aircraft identification does not appear when I start to fill in my proposed flightplan. I have to fill that information in. I do not know what other aircraft or ATC "see" as far as my aircraft type when I do this.

 

I started a similar thread in the PMDG Customer Support Forum but it too has no responses and I really suspect the issue is an FSInn one or at least one shared between FSInn and PMDG. I had hoped between both forums I wouldl find a resolution that the Original Poster does not appear to have gotten.

 

Here are the particulars of my system:

 

Windows XP Media Center Edition, SP3

FSInn 1.3

CoPilot 1.7

FS2004, A Century of Flight, v9.1

 

Page 16 of the FSInn manual does briefly mention that "If an aircraft has a wrong configuration file an error report will be generated", but it does not explain what the user's attempts to resolve that report should be. Is it as simple as editing the acft.cfg file to something thhat FSInn recognizes?

 

Any help will be immensely appreciated.