June 19, 20223 yr HI , i moved some folders with this software and others like Flightbeam has an option to move within there own software. Is anyone having succes with the above including all the liveries? Second thought. Fenix has symbolic link to liveries What about the Official folder in MSFS - its rather big , can we have symbolic link or more folders ? Thanks Michael Moe Edited June 19, 20223 yr by Michael Moe Michael Moe
June 19, 20223 yr The PMDG Operations center, that controls all the liveries for the PMDG 737, looks for the PMDG in the Community folder. It creates a new folder, pmdg-aircraft-737-liveries. Since the Operations Center looks for this file in the Community folder, the 737 must be active in the Community folder in order to add or subtract liveries. I use addon linker and the Operations Center uses the virtual link to access the file. It properly adds and subtracts liveries from the file that I store away from my actual community folder. No problem, just remember that the file must be active in addon linker in order to work properly. Joe Alferio i9-9900K + 2080 Ti | 1TB PCIe + 32GB RAM. Dell 24 inch monitor. Thrust master T16000 stick, throttles, and pedals. FSX and MSFS.
June 19, 20223 yr Just make sure that you choose a folder outside of your Community folder when you install the Fenix. It will put Fenix.exe and the rest of its supporting files and folders where you select during install, but will put the airplane itself and the liveries in your Community folder. After installation, you can use the linker to move them out of the Community folder to wherever you want. I picked my community folder initially during the installation and was moving the airplane, libraries, and the Fenix application in and out with the linker. This was causing problems with options not saving correctly when I changed them in the airplane. i9-10850K, ASUS TUF GAMING Z490-PLUS (WI-FI), 32GB G.SKILL DDR4-3603 / PC4-28800, GIGABYTE RTX5080 16GB WF OC 3 FAN running 3440x1440
June 19, 20223 yr Really anything with an installer I tend to keep in the Community folder directly. Avoids issues with config saving or livery installation (PMDG), and most importantly, makes updating much simpler. Intel i7-10700K @ 4.7 GHz | Nvidia RTX 3070 FE | 32GB DDR4 RAM
June 19, 20223 yr 3 hours ago, Joe Alferio said: The PMDG Operations center, that controls all the liveries for the PMDG 737, looks for the PMDG in the Community folder. It creates a new folder, pmdg-aircraft-737-liveries. Since the Operations Center looks for this file in the Community folder, the 737 must be active in the Community folder in order to add or subtract liveries. I use addon linker and the Operations Center uses the virtual link to access the file. It properly adds and subtracts liveries from the file that I store away from my actual community folder. No problem, just remember that the file must be active in addon linker in order to work properly. Joe Alferio In other words, what you are saying is, if you want to use the PMDG Operations Center to add/subtract a livery, you need to make sure you've moved the pmdg 737 folder and the pmdg 737 liveries folder back into your Community folder. Am I right? Rhett 7800X3D ♣ 96 GB G.Skill Flare ♣ Gigabyte 4090 ♣ Crucial P5 Plus 2TB
June 19, 20223 yr 1 hour ago, Mace said: In other words, what you are saying is, if you want to use the PMDG Operations Center to add/subtract a livery, you need to make sure you've moved the pmdg 737 folder and the pmdg 737 liveries folder back into your Community folder. Am I right? No, you can just leave both PMDG folders in your custom installation folder. Just make sure they are activated in the addon linker.
Archived
This topic is now archived and is closed to further replies.