Mike, I think this is FSX-SE related rather than a general OC problem. Livery export doesn't work with FSX-SE installs either.

PMDG already know about the livery export problem but maybe not about the GMC problem.

 

Hi, Kevin,

 

You are right that there is an export problem w/ FSX:SE.  I had downloaded the Singapore livery to FSX:SE only for the 300ER from PMDG using the OC.  It did not install the correct folders or entries in the FSX:SE 777 GMC folder.  BUT: I just looked in my FSX:MS 777 GMC folder, and sure enough the entry that should be in the same folder  in FSX:SE, is in FSX:MS instead, although there is no Singapore livery in the FSX:MS 300ER folder (since I didn't install Singapore to FSX:MS). 

 

Oddly enough, the FSX:MS GMC aircraft.cfg texture entry is pointing to the correct folder name for Singapore (SQ), even though other entries in that same file point to incorrect texture folder names. 

 

I received a reply on my ticket, and PMDG does know about the wrong folder name pointer problem.

 

Mike

Hi, Kevin,

 

You are right that there is an export problem w/ FSX:SE.  I had downloaded the Singapore livery to FSX:SE only for the 300ER from PMDG using the OC.  It did not install the correct folders or entries in the FSX:SE 777 GMC folder.  BUT: I just looked in my FSX:MS 777 GMC folder, and sure enough the entry that should be in the same folder  in FSX:SE, is in FSX:MS instead, although there is no Singapore livery in the FSX:MS 300ER folder (since I didn't install Singapore to FSX:MS). 

 

Oddly enough, the FSX:MS GMC aircraft.cfg texture entry is pointing to the correct folder name for Singapore (SQ), even though other entries in that same file point to incorrect texture folder names. 

 

I received a reply on my ticket, and PMDG does know about the wrong folder name pointer problem.

 

Mike

It can't just be a folder pointer problem, it must be more than that. I only have FSX-SE, installed in single mode with default file names and folders. Old addons install just like it was FSX. So the OC ought to point at the correct folders.

It can't just be a folder pointer problem, it must be more than that. I only have FSX-SE, installed in single mode with default file names and folders. Old addons install just like it was FSX. So the OC ought to point at the correct folders.

 

Yes, that is really odd.  You can see that the problem I found with the Singapore livery probably has to do with the OC not being programmed to find the 777 GMC folder in FSX:SE, even though it does find the 300ER folder in SE to install the livery.  And most installation problems with FSX:SE come from the changed folder names in a dual install only.

 

The wrong texture folder name problem in the GMC aircraft.cfg file is not specific to FSX:SE, however.  Most of the entries in both my FSX versions of that file point to the wrong folder name (e.g. texture= Virgin Australia instead of texture=VA).

 

One question:  Is it possible you have some remnant of an FSX:MS install in your registry that might be confusing the OC?

 

Mike

 

 

One question: Is it possible you have some remnant of an FSX:MS install in your registry that might be confusing the OC?

I don't think so. I worked hard to eradicate all of them. The main FSX registry entry looks just like it did with the DVD install but points to Steam. There is no other FSX location and the OC doesn't write to the default location either.

 

I have the 747, MD-11 and J41 all installed in steam with no problems. Ironically the J41 reports itself in the OC as the FSX-SE version although there's no such thing.

 

 

There is no other FSX location and the OC doesn't write to the default location either.

 

So it installs the livery for a 300ER but not the entries in 777 GMC?  If so, strange, because the OC did find the 777 GMC folder for my FSX:MS, just not the right one (in FSX:SE).  By the way, once the OC or an addon installer has found the top level FSX folder for whichever version, it should do OK for folders that are subfolders of FSX's main folder.  It's the appdata, Documents and Program Data subfolders that have the weird names.  At any rate we can't fix the OC, and your instructions should help anyone who reads this thread get it working right. 

 

One thing to consider is to repost your instructions in a thread with a better title, such as "300ER taxi camera fix/workaround" or something like that.  There must be many people w/ this issue.

 

Mike

The OC provides you with the locations that it has found for the different simulators in the log file here: ...\USER\AppData\Roaming\PMDG\PMDG Operations Center

 

Have a look to verify all looks as expected.

 

 

The OC provides you with the locations that it has found for the different simulators in the log file here: ...\USER\AppData\Roaming\PMDG\PMDG Operations Center

Have a look to verify all looks as expected.

 

Hi, Dan,

 

Thanks for pointing out the log file.

 

It doesn't appear to show what it does regarding installation of the entries in the 777 - GMC folder (the one for the taxi cameras).  I just installed Singapore from FSX:MS using the OC and downloading from PMDG.  It did a proper install, looking at all the entries.  It did not have the texture pointing problem I've found in older liveries in both FSX:MS & SE.   I can see the install of the livery in the 300ER folder, in the OC log file, but I don't see any reference to the 777-GMC folder at all.  Yet it did it correctly.

 

Mike

Well it was worth a look.  Sorry I don't have any insights, in fact now that I am pretty much all P3D I've forgotten that feature exists since it didn't migrate to the new platform.

 

 

Well it was worth a look. Sorry I don't have any insights, in fact now that I am pretty much all P3D I've forgotten that feature exists since it didn't migrate to the new platform.

 

At any rate, PMDG is aware of the issue.  I think they fixed part of the problem recently since the GMC aircraft.cfg texture entries now point to the correct texture folders; they used to be wrong. 

 

Mike

Hi, everyone,

 

Just received word from PMDG tech support that the new OC version now available should fix this problem.

 

Mike

Thanks for that Mike. Be good to see that working again.

Hi, everyone,

 

Just received word from PMDG tech support that the new OC version now available should fix this problem.

 

Mike

Hi Mike, is the updated OC working for you? I still have this problem after the update. Other things listed as fixed, such as livery export, work fine.

Hi Mike, is the updated OC working for you? I still have this problem after the update. Other things listed as fixed, such as livery export, work fine.

 

Hi, Kevin,

 

My dual install appears to be working OK.  I just did the following, all using the Op Center:

 

I chose Garuda Indonesia livery since I didn't already have it installed and almost certainly never did.

 

Installed Garuda Indonesia for 300ER SE (selecting ...300ER SE for the livery downloader view and then clicking on Garuda install).

Checked the 300ER & GMC Aircraft.cfg files, both folders.  GMC Aircraft.cfg has same title as 300ER for that livery w/ GMC added, is pointing to the correct livery name (texture.GA), GMC texture folder has correct name and points to correct livery name in 300ER folder. 

Loaded FSX SE and selected the Garuda Indonesia 300ER livery.  Clicking on CAM worked OK -- I have the two views of what appears to be the Garuda livery.  Ailerons move when commanded.  Only complaint is that when switching views, e.g. to overhead panel or external, the camera window is hidden although it must still be open as I have to click twice on CAM to get it to reappear.  Not a big deal.

 

Shut down FSX:SE, then using the OC, I performed the same steps, except for choosing ... 300ER FSX non-SE option.  Everything checked out same as in FSX:SE.

 

I didn't check to see if OC is still putting some settings in FSX:MS folder that should be in SE, since, as long as they are in SE where they should be, shouldn't be a problem.

 

Only thing I can think of is, with a single install like yours, are you supposed to select ...300 FSX:SE for the liveries, or regular 300 FSX?   And of course there's always a possibility of a registry issue.

 

Hope this helps!

 

Mike

With a single install I don't get the option to choose. However for the -300 it doesn't list it as the SE version. I wondered about that and the fact yours lists both might be a clue why it doesn't work for me. It may still be a bug with single installations.

 

I still don't see how the OC can correctly install the liveries for the -300ER but then decide not install anything for the GMC. I would have thought it was all part of the same process. I'll check again to see if it has installed any GMC folders in other locations instead.

 

Meanwhile I opened a ticket about it.