Sign in to follow this  
rsrandazzo

[02JAN16] COEXISTENCE FAILURE - Update 2

Recommended Posts

Captains,

 

At about 0900Z/02JAN, we replaced the FSX installers for the PMDG 777-200LR/F and the PMDG 777-300ER.

 

We swapped new installers in an effort to eliminate some false-positives being thrown by the installer's registry error check process.

 

What we are dealing with is that there is a condition in which FSX-SE users might have only FSX-SE installed on their machine, yet their registry shows installation data for both FSX-Retail and FSX-SE, and this data points to the same physical location on the drive.  This should be a major-no-no but was done intentionally by the Dovetail Team in order to simplify customer installations, I would presume.

 

This method worked marvelously for their goals, but since it makes a total, unmitigated mess of the registry for folks like us who support their platform- we are going through some teething as we try to bring you more robust tools that are able to accurately decode problem installations from valid installations.  Our hope is that by automating this process and refusing to install into circumstances where we know from experience that our product will not behave properly- we can reduce the amount of time FSX-SE users spend seeking solutions to installation problems.

 

Unfortunately- we underestimated a specific condition that should be quite rare, because DTG decided to make it a base-case...  So we are changing the detection logic in order to make it accept circumstances that just really shouldn't exist.

 

(If you are sensing that my sense of humor is somewhat flat- you are correct.  I don't like having our time wasted by the poor choices of others...)

 

I anticipate that we are probably going to update these installers a few more times over the next day or so until we find a good balance between allowing botched installations that we know will create support problems, and flagging the installation as impossible so that the user knows to fix the problems before proceeding.

 

This latest installer should get rid of the vast majority of false positives- but a few of you might still hit knee-knockers that we have to adjust for...

 

If you have been having problems with a "COEXISTENCE ERROR" being thrown by the FSX installers- please pull new copies and try again.  Report back and let us know if the problem sorted out for you- or if you still have trouble.

 

It is worth noting that we have made a few changes to the support tool function in the Operations Center.  You can check the support.txt file that it creates and get a good accurate readout on your registry entries...

 

Stay tuned, we will have more information for you as we develop the solution...

 

 

  • Upvote 4

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

The new installer has solved the problem for me. Thanks very much for both the 777 update and the prompt response to the installation issue. Happy New Year indeed!

Share this post


Link to post
Share on other sites

Thanks very much for the memory-reducing update! Sorry you are running into difficulties w/ the

Steam method of configuring the registry.

 

One thing that occurs to me is that in a single install, the installation could detect which

version is installed by looking at the files in the FSX top level folder, assuming both registry

entries point to the same location. I notice there is a file in my top level Steam folder

called FSXSEConfig.exe which is not in the top level of FSX Box. Most likely this file appears

in a single install of Steam.

 

I have a dual install and have run into no problems. You mentioned somewhere a missing flashing

light texture but my aircraft (an addon repaint) appears to be have normal working beacons and

strobes. Do people who downloaded the first installer released yesterday and are not experienc-

ing any problems need to reinstall using a newer installation file?

 

Thanks,

Mike

Share this post


Link to post
Share on other sites

I never had a chance to download the original installer, just this new updated one, and the installer ran perfectly fine! I just use standalone FSX:SE.

Share this post


Link to post
Share on other sites

Thats strange. I have both legacy FSX and FSX-SE installed on the same drive on my computer.

I already had PMDG removed from FSX legacy and had it installed only for FSX-SE.

 

For this update last night, I was able to remove PMDG from FSX-SE and re-install it back into FSX-SE only without any issues.

Share this post


Link to post
Share on other sites

If we already have the 777 and it's working fine, do we need to download and install this update?

Share this post


Link to post
Share on other sites

If we already have the 777 and it's working fine, do we need to download and install this update?

 

Did you read the update information in the other thread?

Share this post


Link to post
Share on other sites

Did you read the update information in the other thread?

 

I have just now. I had a lot of problems getting onto the forum this morning and couldn't even see some threads, of which that was one. It simply didn't show up in the list of threads. I'm guessing my problems are due to the sheer number of people accessing this particular part of the AVSIM forum at this time. But I just read it, so thanks. With that, I have a quick question. This coexistence problem - does it only affect owners of FSX:SE? I do not have that version of FSX, I own the retail version.

Robert, tell your guys to keep their chin up. One of these days you're going to release a big update and there'll be zero requests for help fixing problems because there won't be any problems. I know it's unlikely, but a computer nerd can dream, right? :)

Share this post


Link to post
Share on other sites

Sorry to report I'm still getting the 'coexistence failure' message using the latest 777 installer. I had FSX/FSX:SE side by side for a while, but removed FSX some months ago. I do have success with an older version installer, which I reinstalled and the 777-200 worked as it should. I then again uninstalled through CP and tried installing the latest version...no joy.

 

Old FSX folder deleted.

Ran two reg cleaners.

Deleted all the old PMDG related folders as suggested in other thread.

Any ideas?

Thanks for the update...here's hoping I can make use of it! 

Greg Gott

Share this post


Link to post
Share on other sites

Any news of the installer? I'm not feeling safe to download the new one while some people still reporting issues with the installation detection method. I love so much the product!

 

Sorry my bad english.

 

Greeting from Brazil!

 

Murillo Gumiero

Share this post


Link to post
Share on other sites

Any news of the installer? I'm not feeling safe to download the new one while some people still reporting issues with the installation detection method. I love so much the product!

 

Sorry my bad english.

 

Greeting from Brazil!

 

Murillo Gumiero

Murillo, please give the latest installer and give it a try. One report of a problem out of thousands of downloads is not reason for concern.

Share this post


Link to post
Share on other sites

Murillo, please give the latest installer and give it a try. One report of a problem out of thousands of downloads is not reason for concern.

 

I will download it right now, the product already runs great and I'm crazy to fly it with even greater smoothness. Looks like the main problem is with customers using FSX:SE, as long as I only use FSX Retail should not have any issues.

 

Thanks Dan!

 

Sorry my bad english again  :Tounge:

Share this post


Link to post
Share on other sites

Well, I maintain that the old installer has no problem locating, verifying, and installing without being fooled by my system's registry. So I'll just carry on flying the older version which rarely gave me trouble anyway.

 

Is it possible my system is the only one on the planet tricking the new installer? :wink: 

 

Perhaps a support ticket submission is in order...<shrug>

 

Greg Gott  

Share this post


Link to post
Share on other sites

Somewhere Robert Randazzo mentioned a bad flashing texture that was included in the first release

of version 7025. I can't find this mention anymore.

 

I noticed that the red beacon causes a bright red reflection on the engines. It isn't just a reflec-

tion - the inside facing engine covers turn red. Although I did not have any installation problem,

this problem was fixed by downloading the most recent installer, dated 1-2-16, 2:37 AM.

 

So it seems to me that everyone may need this newest installer.

 

Mike

Share this post


Link to post
Share on other sites

For FSX users: Are the Cabin Windows transparent, now? Can you see the interior of the cabin from the outside view? After the first Update, the cabin windows were not transparent. Maybe this issue was fixed with the last updated installer?! Can someone confirm this? 

Share this post


Link to post
Share on other sites

For FSX users: Are the Cabin Windows transparent, now? Can you see the interior of the cabin from the outside view? After the first Update, the cabin windows were not transparent. Maybe this issue was fixed with the last updated installer?! Can someone confirm this? 

as far as i know i believe that it is an issue that PMDG are digging through now, i saw somewhere here in the forum that the windows are not transparent  in the latest version and we expect a newer one on the way

 

saif salama

Share this post


Link to post
Share on other sites

For FSX users: Are the Cabin Windows transparent, now? Can you see the interior of the cabin from the outside view? After the first Update, the cabin windows were not transparent. Maybe this issue was fixed with the last updated installer?! Can someone confirm this? 

 

Was not able to install the first due to the issue on topic but the last one installed without a problem and all is fine for me including windows.

One of the ground units is missing on the 777-3 though but It doesn't bother me :)

 

Pawel Grochowski

Share this post


Link to post
Share on other sites

 

 


One of the ground units is missing on the 777-3 though but It doesn't bother me :)

 

What are you referring to here?

Share this post


Link to post
Share on other sites

What are you referring to here?

 

Close inspection revealed the problem with one texture "getting lost" when switching from 1 plug to 2 plugs.

 

7QCaWsh.jpg

Share this post


Link to post
Share on other sites

Just a note, Kyle, if you have a look at the changelog in the ops center, dates are showing 2015 instead of 2016 for the two most recent changes.

Share this post


Link to post
Share on other sites

I just downloaded the installers and am getting the Coexistence failure warning.  I deinstalled both the 737 and the 777 and removed references from the simobjects folder, sim folder, and the appdata folder.  The occurred when installing the 777.  about to try the 737 and see if I get the same issue.  What is next?

 

Here is the registry info from the support tool:

 

===================== PMDG Operations Center Support Package =====================
 
PMDG Operations Center v1.16.01
 
Installed product modules:
PMDG 737NGX - P3D v1.14
PMDG 737NGX - FSX:SE v1.14
PMDG 737NGX - FSX v1.14
PMDG 777 - P3D v1.14
PMDG 777 - FSX:SE v1.14
PMDG 777 - FSX v1.14
PMDG J41 - FSX:SE v1.14
PMDG J41 - FSX v1.14
Settings Module v1.-1546188227
 
 
--------Paths in use by the OC--------
App Path: c:\program files (x86)\pmdg operations center\
App Data Path: c:\users\eric\appdata\roaming\pmdg\pmdg operations center\
Config Path: c:\users\eric\appdata\roaming\pmdg\pmdg operations center\PMDG Operations Center.cfg
 
 
------Registry Reported Locations-------
HKCU\SOFTWARE\Microsoft\Microsoft Games\flight simulator\10.0\AppPath :E:\FSXSE\steamapps\common\FSX\
HKLM\SOFTWARE\DovetailGames\FSX\install_path :E:\FSXSE\steamapps\common\FSX\
HKLM\SOFTWARE\Lockheed Martin\Prepar3D vX\SetupPath :
 
 
------FSX-SE Co-Existence Check-------
FSX-SE Co-Existence Key is present and value is: 0
 
 
------Drive Path-------
FSX Path: 
FSX:SE Path: E:\FSXSE\steamapps\common\FSX\
P3D Path: 
 
 
--------Flags--------
Run as admin: 1
 
 
--------PMDG 737NGX P3D--------
Is Installed: 0
Installed Version: 
Variants
>>>PMDG 737-800NGX
Is Installed: 0
Aircraft Path: PMDG 737-800NGX
>>>PMDG 737-800NGX WL
Is Installed: 0
Aircraft Path: PMDG 737-800NGX WL
>>>PMDG 737-900NGX
Is Installed: 0
Aircraft Path: PMDG 737-900NGX
>>>PMDG 737-900NGX WL
Is Installed: 0
Aircraft Path: PMDG 737-900NGX WL
>>>PMDG P-8A Poseidon
Is Installed: 0
Aircraft Path: PMDG P8A Poseidon
>>>PMDG 737-600NGX
Is Installed: 0
Aircraft Path: PMDG 737-600NGX
>>>PMDG 737-700NGX
Is Installed: 0
Aircraft Path: PMDG 737-700NGX
>>>PMDG 737-700NGX WL
Is Installed: 0
Aircraft Path: PMDG 737-700NGX WL
Expansions
>>>PMDG 737-600/700 NGX
Is Installed: 0
Installed Version: 
 
 
--------PMDG 737NGX XSE--------
Is Installed: 0
Installed Version: 
Variants
>>>PMDG 737-800NGX
Is Installed: 0
Aircraft Path: PMDG 737-800NGX
>>>PMDG 737-800NGX WL
Is Installed: 0
Aircraft Path: PMDG 737-800NGX WL
>>>PMDG 737-900NGX
Is Installed: 0
Aircraft Path: PMDG 737-900NGX
>>>PMDG 737-900NGX WL
Is Installed: 0
Aircraft Path: PMDG 737-900NGX WL
>>>PMDG P-8A Poseidon
Is Installed: 0
Aircraft Path: PMDG P8A Poseidon
>>>PMDG 737-600NGX
Is Installed: 0
Aircraft Path: PMDG 737-600NGX
>>>PMDG 737-700NGX
Is Installed: 0
Aircraft Path: PMDG 737-700NGX
>>>PMDG 737-700NGX WL
Is Installed: 0
Aircraft Path: PMDG 737-700NGX WL
Expansions
>>>PMDG 737-600/700 NGX
Is Installed: 0
Installed Version: 
 
 
--------PMDG 737NGX--------
Is Installed: 0
Installed Version: 
Variants
>>>PMDG 737-800NGX
Is Installed: 0
Aircraft Path: PMDG 737-800NGX
>>>PMDG 737-800NGX WL
Is Installed: 0
Aircraft Path: PMDG 737-800NGX WL
>>>PMDG 737-900NGX
Is Installed: 0
Aircraft Path: PMDG 737-900NGX
>>>PMDG 737-900NGX WL
Is Installed: 0
Aircraft Path: PMDG 737-900NGX WL
>>>PMDG P-8A Poseidon
Is Installed: 0
Aircraft Path: PMDG P8A Poseidon
>>>PMDG 737-600NGX
Is Installed: 0
Aircraft Path: PMDG 737-600NGX
>>>PMDG 737-700NGX
Is Installed: 0
Aircraft Path: PMDG 737-700NGX
>>>PMDG 737-700NGX WL
Is Installed: 0
Aircraft Path: PMDG 737-700NGX WL
Expansions
>>>PMDG 737-600/700 NGX
Is Installed: 0
Installed Version: 
 
 
--------PMDG 777 P3D--------
Is Installed: 0
Installed Version: 
Variants
>>>PMDG 777-200LR
Is Installed: 0
Aircraft Path: PMDG 777-200LR
>>>PMDG 777F
Is Installed: 0
Aircraft Path: PMDG 777F
>>>PMDG 777-300ER
Is Installed: 0
Aircraft Path: PMDG 777-300ER
Expansions
>>>PMDG 777-300ER
Is Installed: 0
Installed Version: 
 
 
--------PMDG 777 XSE--------
Is Installed: 0
Installed Version: 
Variants
>>>PMDG 777-200LR
Is Installed: 0
Aircraft Path: PMDG 777-200LR
>>>PMDG 777F
Is Installed: 0
Aircraft Path: PMDG 777F
>>>PMDG 777-300ER
Is Installed: 0
Aircraft Path: PMDG 777-300ER
Expansions
>>>PMDG 777-300ER
Is Installed: 0
Installed Version: 
 
 
--------PMDG 777X--------
Is Installed: 0
Installed Version: 
Variants
>>>PMDG 777-200LR
Is Installed: 0
Aircraft Path: PMDG 777-200LR
>>>PMDG 777F
Is Installed: 0
Aircraft Path: PMDG 777F
>>>PMDG 777-300ER
Is Installed: 0
Aircraft Path: PMDG 777-300ER
Expansions
>>>PMDG 777-300ER
Is Installed: 0
Installed Version: 
 
 
--------PMDG J41 XSE--------
Is Installed: 0
Installed Version: 
Variants
>>>PMDG J41
Is Installed: 0
Aircraft Path: PMDG_JS4100
 
 
--------PMDG J41--------
Is Installed: 0
Installed Version: 
Variants
>>>PMDG J41
Is Installed: 0
Aircraft Path: PMDG_JS4100
 
 
--------Browser Helper Objects--------
 
C:\Program Files (x86)\Internet Download Manager\IDMIECC.dll
 
C:\Program Files (x86)\TechSmith\Snagit 10\SnagitBHO.dll
 
C:\Program Files (x86)\Norton 360\Engine\22.5.5.15\coIEPlg.dll
 
C:\Program Files (x86)\Java\jre1.8.0_31\bin\ssv.dll
 
C:\Program Files (x86)\Bluetooth Suite\IEPlugIn.dll
 
C:\Program Files (x86)\Google\Google Toolbar\GoogleToolbar_32.dll
 
C:\Program Files\Logitech\SetPointP\32-bit\SetPointSmooth.dll
 
C:\Program Files (x86)\Java\jre1.8.0_31\bin\jp2ssv.dll
 
C:\Program Files (x86)\Java\jre1.8.0_31\bin\jp2ssv.dll
 

 

Eric Fields

Share this post


Link to post
Share on other sites

Don't  know  why  you uninstalled  the ngx  for  no need  to  do that,  send  a support  ticket  in  as explained  in the first post of  this  thread

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this