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.

Still problem with the Livery Manager

Featured Replies

Hi, I have still a problem with the Livery Manager. When I install SAS with WL it shows up in the Installed Liveries tray. But when I install Airberlin (WL) it does not show up in the Installed Liveries tray and it removes the SAS entry also. When I start FSX ther are no airliner to choose. The default PMDG versions is still there. I did download the livery files yesterday. But I have re downloaded them agin today. For 900 WL and 800 (without WL) the liveries installs correctly which is strange. / Jonas

Jonas Lundgren

You're doing better than I. I've not been able to get the Livery Manager to work at all. When I click on "install liveries", there is no response. No problems shown in Event Viewer. I've only had CTDs, no completed flights yet. Perhaps I should uninstall the 737NGX & reinstall it. Dan "lensman" Davison

--
Dan "lensman" Davison
PMDG_T7_sig.jpgrs

I had the same problem also with the Norwegian livery (additional to the SAS, these are the only ones i installed). Jonas, the problem is here:1. (as mentioned under the PMDG 737NGX Issues Tracking Thread) the aircraft.cfg file is write protected. Click it right -> properties -> unmark write protect2. When the aircraft.cfg is rewritten with the new livery info (in my case Norwegian and SAS (no winglets)), the part called "ui_type=737-800NGX" is the same as the the PMDG house livery. So it does not show when choosing the airplane since there is an entry with the same name already. I renamed it to "ui_type=737-800NGX Norwegian" and then it can be seen in the aircraft menu. The same with the SAS livery, renamed it to "ui_type=737-800NG SAS" and it is visible. You can actually do this while FSX is running, just make sure you close and reopen the aircraft menu before checking after the changes. Dan,had the same problem - make sure you choose the type on the left side under "installed aircraft variants" fist e.g. 800NGX. Pressing the "selec livery to install" button after that will open an explorer window to chose the livery (unpacked, *ptp file) Hope that helps! Nico Andersson

  • Author

Hi, Thanx for the replay My aircraft.cfg is not write protected. Fore each of the installed livery did you creat a nw entry for the new lervries?

Jonas Lundgren

Now - i just installed the Norwegian (WL) and the SAS (no WL) liveries and both had this problem. Looks like bad luck actually since according to the forum other liveries show up correctly. So it just might be a problem with these two liveries.... And did not create a new entry, just rewrote an existing one... the "ui_type=" entry is a normal part of the livery entry. Nico

  • Author
Hi, Thanx for the replay My aircraft.cfg is not write protected. Fore each of the installed livery did you creat a nw entry for the new lervries?
I can see now that the installer does not creat new entries in the .cfg file. There are no [fltsim.x] sections for each new airliner installed. /Jonas

Jonas Lundgren

Have you checked also the end of the cfg file? The livery entries can be placed anywhere actually... Nico

  • Author
Now - i just installed the Norwegian (WL) and the SAS (no WL) liveries and both had this problem. Looks like bad luck actually since according to the forum other liveries show up correctly. So it just might be a problem with these two liveries.... And did not create a new entry, just rewrote an existing one... the "ui_type=" entry is a normal part of the livery entry. Nico
I installed more liveries and there is thes same problem. My problem is that the installer does not create the[fltsim.x] for each new arilainer added. /Jonas

Jonas Lundgren

does the installer create the folder with the textures then? If yes - it looks like the aircraft.cfg file is actually write protected... Nico

I have a similar problem, when I install one livery onto the 800 it's fine, but then if I try and install another, they both disappear. I've already set the CFG to not read only.

Rónán O Cadhain.

sig_FSLBetaTester.jpg

  • Author
does the installer create the folder with the textures then? If yes - it looks like the aircraft.cfg file is actually write protected... Nico
For me it does create the texture.SK folder under 80WL (the SAS livery) and I get the configuration file (FSX/PMDG/Aircraft). /Jonas
simply start the livery manager as an administrator, it works perfectly i have downloaded 5 a/c no problem
I allredy (hmm miss spelled?) run it as administrator. /Jonas
For me it does create the texture.SK folder under 80WL (the SAS livery) and I get the configuration file (FSX/PMDG/Aircraft). /Jonas I allredy (hmm miss spelled?) run it as administrator. /Jonas
Well I thougth I did but I did not do it. Thanx for the tips. But it is strange that it workd for 900WL and 800 without running it as administrator? /Jonas

Jonas Lundgren

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.