No liveries - Steam Install

[MarkW 1,490]

I just completed uninstalling all traces of the 777 and NGX per the sticky and I reinstalled to both Steam and FSX.  The aircraft work perfectly in both sims.  I have also download and installed some liveries using the Operations Center and they show as installed.  When I go to FSX-SE, I only see PMDG liveries (note that I have check the box that says show all variations).  The liveries are in the Aircraft folder and they are in the aircraft.cfg file.  Any ideas as to why they do not show up in the menu ?

[downscc 1,327]

Be sure you have PMDG 777 FSX-SE, for example, selected as the product. It's not hard to select the FSX variant instead of FSX-SE.

 

Look at your OperationsCenter.log file in \USER\AppData\Roaming\PMDG\PMDG Operations Center.  It should have the correct directory string for under Finding FSX:SE.

 

If you can't find anything obvious, please open a ticket at the PMDG Product Support portal.

[MarkW 1,490]

I fixed the problem (or more accurately worked around it).  You need to install the liveries in FSX not FSX:SE for them to show up in the list when running Steam, not sure why it works this way but it works.

[downscc 1,327]

I fixed the problem (or more accurately worked around it).  You need to install the liveries in FSX not FSX:SE for them to show up in the list when running Steam, not sure why it works this way but it works.

That's not the way it should work; otherwise, we'd see hundreds of posts on this problem.

 

Did you look at the OC log file?  You have a problem that you haven't fixed and unless fixed it is going to bite you.

[scandinavian13 5,192]

I fixed the problem (or more accurately worked around it).  You need to install the liveries in FSX not FSX:SE for them to show up in the list when running Steam, not sure why it works this way but it works.

 

As Dan mentioned, that's not how it's supposed to work. My bet is that you installed FSX, installed Steam, and then you deleted FSX? If so, this likely caused a registry error where things are pointing to the incorrect location, giving you the issues you're seeing.

[MarkW 1,490]

I did not uninstall FSX, I just installed Steam into another directory (not default).

[downscc 1,327]

I did not uninstall FSX, I just installed Steam into another directory (not default).

That's why I asked you to look in the log file to confirm that the OC knows where FSXSE is installed. It's really easy to do.

 

Regardless, if you're happy with your configuration then happy contrails.

[MarkW 1,490]

That's why I asked you to look in the log file to confirm that the OC knows where FSXSE is installed. It's really easy to do.

 

Regardless, if you're happy with your configuration then happy contrails.

 

It seems correct, here is the first part of the file.

 

===================== PMDG Operations Center v1.14.3 =====================

10:07:28.542   

10:07:28.542   Starting Ops Center

10:07:28.544   

10:07:28.546   Loading Settings

10:07:28.546   Finding FSX

10:07:28.547   Found FSX installation: F:\Flight Simulator X\

10:07:28.549   Finding FSX:SE

10:07:28.550   Found FSX installation: F:\Steam\steamapps\common\FSX\

10:07:28.552   Finding P3D

10:07:28.553   Failed to read registry value: 2

10:07:28.555   Checking if FSX is in Program Files

10:07:28.556   Nope!

10:07:28.558   Checking if FSXSE is in Program Files

10:07:28.560   Nope!

10:07:28.561   Checking if P3D is in Program Files

10:07:28.563   

10:07:28.565   Loading GDI+

10:07:28.565   

10:07:28.568   Command line: 

10:07:28.568   

10:07:28.570   Initializing

10:07:28.570   

10:07:28.571   Displaying Ops Center

10:07:28.571   

10:07:28.575   Window initializing

[downscc 1,327]

Thanks Mark, that looks good to me too.... now would you mind opening a trouble ticket and explain how you must install liveries to FSX to see them in FSXSE and attach a copy of above's log file. I expect RSR will want to take a look at this since he loves fixing his code in the Operations Center to make it work with the latest changes Dovetail may have made.  Unless you've had FSX:SE for a couple of months or longer, I'd also mention about how long it's been since you downloaded and installed FSX:SE.

 

The support portal is here: http://support.precisionmanuals.com/Main/Default.aspx

On your first visit, you need to create a support account. Support accounts are separate from sales accounts.

 

I appreciate your time in doing this.

[MarkW 1,490]

OK will do.

[MarkW 1,490]

Thanks Mark, that looks good to me too.... now would you mind opening a trouble ticket and explain how you must install liveries to FSX to see them in FSXSE and attach a copy of above's log file. I expect RSR will want to take a look at this since he loves fixing his code in the Operations Center to make it work with the latest changes Dovetail may have made.  Unless you've had FSX:SE for a couple of months or longer, I'd also mention about how long it's been since you downloaded and installed FSX:SE.

 

The support portal is here: http://support.precisionmanuals.com/Main/Default.aspx

On your first visit, you need to create a support account. Support accounts are separate from sales accounts.

 

I appreciate your time in doing this.

 

Dan, I am not going to enter a ticket because this issue is not caused by the OC but by the way I have referenced aircraft in my FSX install from my Steam cfg.  Finally figured out why I was having problems.

[downscc 1,327]

 

 

Finally figured out why I was having problems.

 

Do you mean FSX-SE install and fsx-se.cfg?  It's confusing so our convention is to use FSX for boxed version and FSXSE (or -SE or :SE) for Steam version.  Which configuration file did you modify that changed the location of installed aircraft?

[MarkW 1,490]

In the FSX-SE.cfg I have referenced the simobjects from my FSX install using the full path.  This works for most aircraft and ai aircraft but not for PMDG and one other payware developer.

[sunnychew 0]

For me when i checked the log, this is what i get.

===================== PMDG Operations Center v1.14.3 =====================
02:25:43.898   
02:25:43.898   Starting Ops Center
02:25:43.898   
02:25:43.898   Loading Settings
02:25:43.898       Finding FSX
02:25:43.898           Failed to open registry key: 2
02:25:43.898       Finding FSX:SE
02:25:43.898           Failed to read registry value: 2
02:25:43.898       Finding P3D
02:25:43.898           Failed to read registry value: 2
02:25:43.898   Checking if FSX is in Program Files
02:25:43.898   Checking if FSXSE is in Program Files
02:25:43.898   Checking if P3D is in Program Files
02:25:43.898   
02:25:43.908   Loading GDI+
02:25:43.908   
02:25:43.908   Command line:
02:25:43.908   
02:25:43.908   Initializing
02:25:43.908   
02:25:43.908   Displaying Ops Center
02:25:43.908   
02:25:43.918   Window initializing
02:25:43.918   
02:25:44.018   Loading Settings Module
02:25:44.018   
02:25:44.018   Loading Module from file: c:\program files (x86)\pmdg operations center\Settings.dat
02:25:44.018   Loading Module
02:25:44.018   
02:25:44.018   Settings - Product Module Loading
02:25:44.018   
02:25:44.018   Settings - Checking product version
02:25:44.018   No GUID found!

 

I had my FSX uninstalled. Currently I am using FSX:SE. I am not able to see the livery manager at operations center.

Anyone can help?

[Mike777 163]

In the FSX-SE.cfg I have referenced the simobjects from my FSX install using the full path. This works for most aircraft and ai aircraft but not for PMDG and one other payware developer.

 

 

Hi, Mark,

 

If you are trying to save some space by having only one set of textures for each livery, instead of one set in FSX:MS and another set for FSX:SE, it is POSSIBLE that you can use the texture.cfg file to reference the textures in FSX:MS from FSX:SE.  I THINK the following will work.

 

This assumes you have the PMDG 777 itself installed in both versions of FSX, and that all of your actual addon livery textures are in FSX:MS.  It also assumes that you know how to add livery entries manually in the aircraft.cfg file.

 

All you would need in the FSX:SE aircraft folder would be a folder with the name of the livery, and one small texture.cfg file.

 

Here is the full texture.cfg file for a typical addon:

 

-----------------

[fltsim]

fallback.1=..\texture.vc

fallback.2=..\texture.common200LR

fallback.3=..\..\..\..\Scenery\Global\texture

fallback.4=..\..\..\..\texture

 

-----------------

Here is a modified version that adds a line at the top referencing the texture you want in FSX:MS. 

-----------------

[fltsim]

fallback.1=[FULL PATH TO TEXTURE IN FSX:MS]

fallback.2=..\..\PMDG 777-200LR\texture.vc

fallback.3=..\..\PMDG 777-200LR\texture.common200LR

fallback.4=..\..\..\..\Scenery\Global\texture

fallback.5=..\..\..\..\texture

 

I don't think the OC will be able to handle this sort of aliasing, so you will probably have to ignore it as far as liveries in FSX:SE are concerned.  But it should still work fine for installing new liveries in FSX:MS.

 

Mike

 

 

 

 

I had my FSX uninstalled. Currently I am using FSX:SE. I am not able to see the livery manager at operations center.

 

Anyone can help?

 

Hi, Sunny,

 

It looks to me like there is something missing in the Windows registry.  If you compare your log to Mark's log, above, you will see that his shows that the OC found both versions of FSX and yours did not.

 

Did you install the FSX:SE (Steam) version before you uninstalled the FSX:MS (Boxed) version?  If so the OC may be confused because it is looking for the FSX:MS version.  Also, how did you uninstall FSX:MS?  

 

Mike