Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Livery request: Lufthansa Cargo 777 Freighter

Featured Replies

Hi Kevin,

 

thank you very much for this great advice. This is really useful for archiving all the custom changes in liveries if a re-install inside the PMDG OPS center is needed in future.

 

 

 

 

So this is the reason why my NGX callsigns get "scrambled" after installing/changing a e.g. 738WL via the PMDG OPS center. There must be a "hiccup" in my FSX list you call "various state.cfg files". 

 

Is there a way to edit "state.cfg files" (I did not find according "state"-files in the FSX folders) in order to get it back in sync with the aircraft.cfg?

 

Thank you very much again for the great help! B)

Hi Claus,

 

Glad to help. I always wondered where FSX stored information about tail numbers and airline callsigns that you can edit in the FSX menu. Of course this assumes any new liveries will be added to the end ot the fltsim.x sections. The OC re-orders this section every time you add or delete a livery, but doesn't change the corresponding state.cfg file.

 

The state.cfg files are in a folder structure under where your fsx.cfg file is. On my PC that is:

 

C:\Users\Kevin\AppData\Roaming\Microsoft\FSX

 

There is a sub-folder called SimObjects and under that, a folder for every object installed. Thats where the state.cfg files are. It seems state.cfg files are only created when you use the aircraft in FSX. As well as tail number changes, etc it also records engine hour, presumably for the FSX logbook. I think the best thing to do would be to simply delete the file (or rename it) and let FSX create a new one. That should reset things.

 

Cheers

 

Kevin

ki9cAAb.jpg

  • Replies 47
  • Views 14k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • Or get this one here:   https://www.dropbox.com/sh/50ziykj8oqivpvh/sFmDVNRyB1   PMDG_777_200F_GEC.PTP   Comes with correct fonts, colours, 'Good Day, USA' title and SELCAL on the registration pl

  • http://library.avsim.net/download.php?DLID=181103 Have you seen this one?

  • Have you had a look at the link I posted. There's an AeroLogic (D-AALC) repainted located and if my eyes don't fool me, the registration plate has got the SELCAL.     I have already started workin

I think the best thing to do would be to simply delete the file (or rename it) and let FSX create a new one. That should reset things.

 

That is a real cool finding! :rolleyes:

 

I just tested it with my somehow (or apparently) corrupted NGX 738WL state.CFG file in ...\AppData\Roaming\Microsoft\FSX\SimObjects\PMDG 737-800NGX WL\state.CFG:

I removed the state.CFG file (renamed original for backup) and launched FSX.

Here a new (clean) state.CFG is created just in the moment you press "Details" inside the "Select Aircraft" menu. FSX then always adds a new entry to the respective state.CFG every time you click "Details" of an aircraft that is not listed yet.

It therefore seems to read the [FltSim.x] number from the respective aircraft.CFG file (inside "SimObjects" folder structure):

 

E.g. I lastly clicked "Details" of the PMDG Default 738WL as the sixth "PMDG 737-800NGX WL" and the lines

[FltSim.0]

atc_id=N738PM

atc_id_enable=1

were added as the sixth entry at the end of the new state.CFG file.

 

While my PMDG "aircraft.CFG" files are kept nice, clean and in a chronological [FltSim.x]-order, the "naturally grown" FSX state.CFG files have a chaotic order, some "duplicates" and even many "no shows"... At some point those lists must have lost their synchronity by adding and removing liveries.

 

So I took all my old/weird NGX state.CFG lists to synchronize them manually with the actual entries inside the PMDG aircraft.CFG files...

THIS SEEMS TO BE IMPORTANT, as the selected aircraft's callsign (as noted inside the state.CFG list) seems to be cruical for the choice of panel state files inside PMDG A/Cs...

 

My PMDG T7 state.CFG lists seem to be correct however.. B)

 

BTW:

The state.CFG list (in fact) makes a record of the total running time of the engines (individual engines) of the respective type (not by callsign).

Probably interesting for those who would like to see how many hours they have spent already with a certain A/C type while engines were running...

 

Here is my list of RIGHT engine running hours (in average 1% more than LEFT engine due to many engine start/shutdown cycles in relation to CRZ periods):

737-600: 49.390961 (Janet Airlines (URS Federal Services))

737-700: 80.226295 (Easy Jet (Retro))

737-700-WL: 159.422722 (Air Berlin, KLM)

737-800: 0.000575

737-800-WL: 503.992081 B) (Ryanair, Air Berlin, KLM, SAS, TUIfly, Copa, American Airlines)

737-900: 0.0

737-900-WL: 20.416422 (KLM)

777-200-LR: 6.114853 (Boeing, Emirates)

777-F: 230.789616 B) (TNT, Aero Logic, Lufthansa)

777-300-ER: 18.892507 (Emirates)

 

(Remark: FSX install of 2011-09-20)

Claus KUEPPER

 

 


THIS SEEMS TO BE IMPORTANT, as the selected aircraft's callsign (as noted inside the state.CFG list) seems to be cruical for the choice of panel state files inside PMDG A/Cs...

The registration is the key item that links them up.

ki9cAAb.jpg

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.