FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: qf11bd on October 21, 2012, 10:15:28 pm
-
Hi,
I installed GSX yesterday to test it out at a few FSDT airports before I would purchase it. Nothing else was installed into FSX, just GSX. After booting up FSX and giving it a go, all was good. But after I restarted my computer and started FSX (was having performance issues), all my FSDT sceneries don't appear, and the addon manager has disappeared from the in-game FSX menu. I did try and download the standalone addon manager, but no luck. Next I repaired the FSX registry path and tried again...still no luck. I'm not sure if this is 100% GSX related, but it happened after installing GSX.
How am I able to get everything to appear in FSX again?
Thanks
-
I'm not sure if this is 100% GSX related, but it happened after installing GSX.
It's fairly sure it's NOT caused by GSX because, according to your description, it hasn't happened as soon as you installed it, because you were able to use it for a while. The problem happened only after you restarted your system.
This seems more like a problem with your MS VC++ 2005 runtimes, and they might be change between a reboot, meaning you already had a problem, but it won't manifest until you rebooted (it's very complex to explain, but is related to the fact those are Side-by-side libraries that can run together in memory, even different versions at the same time)
Try this, download the following file:
http://www.fsdreamteam.com/download/setup/bglmanx/4053/bglmanx.dll
and put it into the FSX root folder, overwriting the one that is already there and try if it works.
If it doesn't, try with this one instead:
http://www.fsdreamteam.com/download/setup/bglmanx/6195/bglmanx.dll
If one of these files works, then it's SURE your system had a corrupted version of the VC++ libraries, which the MS installers weren't able to fix.
-
Wow, what a quick response Umberto!
Thanks heaps, I will download them this afternoon and give it a go.
*EDIT* If there is a problem with the VC++ Libraries, is it an easy fix?
-
Downloaded both of those...neither work.
Any more ideas?
BTW, I have been using FSDT products for over a year now and have never had this problem when rebooting my computer, so I do believe it is something to do with GSX.
-
Downloaded both of those...neither work.
Any more ideas?
Surely you have a problem with MS VC++ libraries.
Try this:
- Go in the Windows control panel, and Uninstall ALL the instances of the Visual Studio 2005 redistributable runtimes. You might have more than one version: remove them all.
- Then, after removing everything related to VS2005, reinstall again these 3 files:
http://www.microsoft.com/downloads/details.aspx?FamilyId=32BC1BEE-A3F9-4C13-9C99-220B62A191EE&displaylang=en
http://www.microsoft.com/downloads/details.aspx?FamilyID=200b2fd9-ae1a-4a14-984d-389c36f85647&displaylang=en
http://www.microsoft.com/downloads/details.aspx?familyid=766a6af7-ec73-40ff-b072-9112bab119c2&displaylang=en
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=26347
AFTER installing all the runtimes, it could be useful running Windows Update and update everything, including the optional downloads.
BTW, I have been using FSDT products for over a year now and have never had this problem when rebooting my computer, so I do believe it is something to do with GSX.
It's not possible this was caused by GSX, since GSX installs and download the SAME bglmanx.dll file that all the other products install and download, and they are taken from exactly the same URL so, it's was just a coincidence.
We have recently updated the .dll, because this FIXED a loading problem for many users that had the VC++ libraries corrupted but, if your corruption was similar but different, maybe this update has broken things for you instead. If this is the case, it would have happened the same if you simply reinstalled any scenery, so it's NOT a GSX problem.
You might try installing GSX WITHOUT NETWORK connection. You'll get a message asking to use the version of the .DLL included with the installer (proceed pressing "Next" when prompted), which I believe it's slightly older than the one online, maybe that will work on your system.
-
Umberto, I have about 10 instances of C++ in my uninstall programs directory. Some a more recent than 2005, do I remove them still?
-
Start only with the 2005 versions first, as I've said in my previous message.
-
Thanks, am trying now.
-
Have uninstalled all C++ 2005 instances and reinstalled from the links you provided.
Still nothing has changed.
-
Any ideas Umberto?
-
you can activate the Simconnect diagnostic mode to see what's wrong with your install:
Open notepad, and copy the following text:
[SimConnect]
level=normal
console=1
RedirectStdOutToConsole=1
OutputDebugString=1
; file=c:\simconnect%03u.log
; file_next_index=0
; file_max_index=9
Save the file as SIMCONNECT.INI in this folder:
Documents And Settings\YOUR LOGIN NAME\Documents\Microsoft Flight Simulator X Files
At the next FSX launch, you should see a text window with diagnostic message, that should tell what's going wrong. Let me know what you are getting, so we can have an idea what's happening.
Only the first few lines are important: if the window scrolls too fast, you can use the "Pause" key on the keyboard to pause the scrolling. Post here only the first 10 lines or so of the diagnostic, but it's important you post the first 10 lines.
-
0.00000 SimConnect version 10.0.61259.0
0.83478 Exe Launch Failed: GetLastError=0x000036B1 Path="fsdreamteam\couatl\co
uatl.exe" CommandLine=""
0.90107 Exe Launched: Path="C:\Program Files (x86)\EZCA\EZCA.exe" CommandLine=
"" Version="1.1.5.0"
0.92055 DLL Failed to load. Check for missing dependencies.
0.92074 DLL Load Failed: Error=-3 Path="bglmanx.dll"
1.01319 DLL Loaded: Path="C:\Program Files (x86)\Microsoft Games\Microsoft Flig
ht Simulator X\ORBX\FTX_AU\FTXAA_YBCS\scenery\ObjectFlow_YBCS.dll" Version="1.0
.0.3"
1.20406 DLL Loaded: Path="C:\Program Files (x86)\Microsoft Games\Microsoft Flig
ht Simulator X\ORBX\FTX_AU\FTXAA_YMML\Scenery\ObjectFlow_YMML.dll" Version="1.0
.0.3"
1.20775 DLL Failed to load. Check for missing dependencies.
1.20792 DLL Load Failed: Error=-3 Path="PMDG\DLLs\PMDG_HUD_interface.dll"
1.21591 DLL Loaded: Path="C:\Program Files (x86)\SquawkBox\sbtrans10.dll" Vers
ion="<Unknown>"
1.22132 DLL Loaded: Path="C:\Program Files (x86)\SquawkBox\sbaicontrol10.dll"
Version="<Unknown>"
1.27093 DLL Loaded: Path="C:\Program Files (x86)\SquawkBox\sbmod10.dll" Versio
n="<Unknown>"
-
Your log clearly shows the problem is exactly what I've suspected: you have a problem with your MS VC++ 2005 runtime libraries, which is indicated by the following lines:
0.92055 DLL Failed to load. Check for missing dependencies.
1.20775 DLL Failed to load. Check for missing dependencies.
The missing dependencies are surely the MS VC++ 2005 runtime libraries, because our modules only depends from them and the Simconnect DLLs, but can't be a Simconnect problem, otherwise you wouldn't be able to start the diagnostic either.
I find difficult to believe that NONE of the 2 additional Addon Manager .DLL I've suggested to download worked, since each one is requiring a different version of the MS VC++ runtimes: it's very unlikely all versions are all corrupted!
In such cases, a possible solution is to REPAIR the FSX install. First try to repair the FSX SP2 (or Acceleration, if you have that one) installation. This doesn't require to reinstall any addon.
-
I will try the files again now after reinstalling VC++ 2005.
I have recently gone through the pain of repairing FSX, so I won't be doing that again (when I say recently, I do mean within the last week).
-
I just don't see how this can be happening out of the blue with out some sort of explanation. I've been running my PC the exact same for a long period of time with FSDT never experiencing these issues. You can be assured I will be a new customer of GSX once this problem has been fixed and retains after a simple computer shut down.
-
I just don't see how this can be happening out of the blue with out some sort of explanation.
It's possible a Windows update might have caused this. Or, another product using such libraries creating a problem with them, if you read all the technical explanations of how the side-by-side system works (this allows several versions of the *same* .DLL running at the same time), is so complex and cumbersome that I wonder if even Microsoft know exactly how it works or (more important) how to fix when something does wrong.
-
I have installed all the latest versions of Windows Update. None between the time of FSDT working and not working.
I've never had any of these issues with any other payware developer...you make spectacular sceneries, but the technical side seems to be slightly lacking in this regard. I am still not being able to fly around the numerous sceneries I have bought, which is quite a shame since there are quite a lot of them (KLAX, KLAS, KDFW, PHNL, KORD, KFLL, KJFK).
-
I have installed all the latest versions of Windows Update. None between the time of FSDT working and not working.
You asked what might have caused the *problem*, and I've replied a Windows update could have, NOT that running "Windows Update" could FIX this, because that might have been the cause in the first place. However, that's a problem in your system only because, obviously, I have all the latest Windows Updates too, and the problem doesn't appear.
I've never had any of these issues with any other payware developer...
That's just because you don't have other installed products that requires the MS VC++ 2005 runtime version that is not working on YOUR system. The Simconnect diagnostic message is very clear about this.
you make spectacular sceneries, but the technical side seems to be slightly lacking in this regard.
They work just fine but, and what you are experiencing is entirely external to any of our products. You can't expect they would still to work, if a part of the Windows libraries are not working for some reason, and you can't expect our products installer would be able to automatically fix EVERY possible case of Windows problem, we would be in the more lucrative system-repair utilities market instead flight simming...
As I've said already, you should try an FSX SP2 Repair, that might fix the problem without having to reinstall FSX or Windows or your addons.
-
You do a search on these forums for 'addon manager' and you can find a large amount of topics with this exact problem. How can it be a particular system issue if 20+ other people have had the same issue?
-
You do a search on these forums for 'addon manager' and you can find a large amount of topics with this exact problem. How can it be a particular system issue if 20+ other people have had the same issue
First, it's fairly obvious that, in a support forum, you would only read about problems.
And, "20+ people" it's basically nothing, compared several thousands of customers, having less than 0,2% of users with this problem, it's very well inside the statistical chance that an user might have missing/corrupted system libraries at some point.
And, of course, of those 20+ people, most of them solved by acting on their VC++ runtimes installation, and the rest fixed it either by repairing the FSX install, or reinstalled Windows.
I'll repeat it again: repairing the FSX SP2 install shouldn't be a problem and will not require reinstalling any of your addons.
-
I do apologise for my previous comment Umberto, I was just a bit annoyed after spending several hours reinstalling things. I have uninstalled all VC++ libraries and installed again. Just about to reboot and give it a go.
-
No change, what's interesting though is that FS9 FSDT sceneries still work perfectly fine.
If I have a spare moment today, I will try and repair FSX.
-
No change, what's interesting though is that FS9 FSDT sceneries still work perfectly fine.
They require the 2003 VC++ runtimes which, not being the complexity monsters the Side-by-side .DLL system is, are *way* simpler to diagnose and fix, it's basically boils down to being sure a couple of .DLL are present. Unfortunately, developing for FSX requires the 2005 runtimes minimum, otherwise Simconnect won't work.
-
Hmm I'll go for a repair tomorrow. I shall report back the results
-
try running FSX as admin
-
Sorry to jump in, but I'm having the excat same problem. You say to install the 3 files, but you have 4 links. I uninstall any vs++2004 and I installed the 4 files from the 4 links provided and still nothing. I also tried both dll files and that also didn't work. I'm not a computer expert, but I did check the dll.xml and the file looked good. I also checked the trusted section of the FSX.cfg file and everything looked good. Just so you know after installing GSX for a trial look, I had no problems with the popup about these files. I just clicked ok and FSX loaded. After loading FSX no addonmanager or GSX show in the menu. I also did the simconnect.ini and I did get the message indicating what you say about c++ being corupt or missinf files. I wnated to see what would happen when I clicked on the COUAT1.exe file and I got a message that said:
This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix the problem.I've tried everything you suggested from different posts that I've read and nothing works. I'm just reading this post this morning so I won't be able to try the FSX fix until I get home from work. Also so you know, I had FSX installed from a couple of years ago with Cloud9 and QW757 installed and addonon manager installed with no problems. When I installed GSX to try before I buy, that worked fine also. (At least for a while) I did start getting fatal errors when starting FSX so I uninstalled everyhing and reinstalled FSX and now I can no longer install my products that require the addonmanager. What happen to good ol days when you can install aircrafts, scenery, ect without having this addonmanager and products would work without problems. I was able to install QW757, but FSX would crash to desktop when tring to load aircraft from menu. The first message for trusting the qw757.gau file went ok, it was the second .gau that would send my FSX to desktop. I know this isn't the cause of addmanager or GSX to installing because It was not installing before I tried to reinstall the QW757. I also installed Cloud9 without no problems, I'm just not sure if it's working. I woild relly like to get the addonmanager installed and working so I can enjoy my products that require them. Right now I feel like I wasted money on these products because of they require the addonmanager to work. VS++2005 may or may not be the problem, but everything else on my computer works fine. I also had a problem installing my EJETS 175, 195, but I don't know if they require addonmanager.
One more thing. I do have different VS++ installed. VS++2008, VS++2010. After reinstalling the VS++2005 I updated windows as you suggested and it install a VS++2010 SP1 update.
I hope we get this issue resolved.
I'm running windows xp 32bit, so as far as I know I don't need to run as admin
Thanks,
Gabe
-
This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix the problem.
That clearly indicates the problem is caused by a problem with your VC++ 2005 runtimes redistributables, so it's nothing related to our application but, instead, it's our application which is a victim of a problem in your Windows install.
To get more proof, see here an example of an entirely unrelated program (an antivirus) which fails to start with exactly the same message:
http://esupport.trendmicro.com/solution/en-us/1056722.aspx
The proposed solution is exactly the same as we suggested, which means reinstalling the VC+2005 runtimes.
The issue is, you can have many versions of the 2005 runtimes, needed by different products, and you can even different versions of other VC++ runtimes (like 2008 or 2010) and there are even known issues of possible problems of newer versions (ex. 2008) causing issues with older versions like the 2005, which is needed both by all our products AND by FSX itself.
Sometimes, these problems are very difficult to fix without a Windows reinstall.
You should also try the solution I've already posted several messages before:
Download the following file:
http://www.fsdreamteam.com/download/setup/bglmanx/4053/bglmanx.dll
and put it into the FSX root folder, overwriting the one that is already there and try if it works.
If it doesn't, try with this one instead:
http://www.fsdreamteam.com/download/setup/bglmanx/6195/bglmanx.dll
If one of these files works, then it's SURE your system had a corrupted version of the VC++ libraries, which the MS installers weren't able to fix.
-
Ok Umberto, I think I tried it already, but I'll give it another try when I get home from work. Right now I removed all thta has todo with addonmanager, so I'll have to reinstall. Should I just install addonmanager alone or should I also try and install GSX, or QW757, ect.? I'm thinking just addonmanager. What do you think
If this doesn't work I really don't know how I'll be able to fix VS++2005. I'm running kaspersky antivirus and had turn off for download and install. I may have to try and contact them to see if anything with their program can be causing this problem.
I'll let you know how it goes. Just so you know, I have a lot installed on computer so a reinstall of windows is not a option right now.
-
Should I just install addonmanager alone or should I also try and install GSX, or QW757, ect.? I'm thinking just addonmanager. What do you think
I'm not sure if you read anything of my previous message. Where, exactly, I said to "reinstall the Addon Mananager", let alone "reinstall any addon that use it" ?
The problem is not the Addon Manager, the problem are the VC++ 2005 runtimes, which should have been very clear from my previous message, which pointed out to the discussion of the *same* error message you are getting, but on a totally unrelated product.
The ONLY thing I've said about the Addon Manager, was to try the alternative .DLLs that requires *slightly* different versions of the VC++ 2005 runtimes, hopefully they might work better, but I haven't said anything about reinstalling it. I've only said to download those files I've linked, and replace them in the FSX root folder. Nothing more than that.
Try that first and, if it fails, THEN we might discuss about the VC++ 2005 runtimes.
-
I read your messages. I don't think you understand what I said. Maybe I didn't say it right.
What I was trying to tell you is that right now I don't have anything install on fsx I don't have addonmanager, gsx, ect... I removed everything that has to do with it. That's why I was asking if I should install the addonmanager alone or install gsx which will also install addonmanager.
I know the problem is with VS++2005.
-
Did you try to run fsx as administrator?
-
I tried running as Admin, but my computer won't let me. I don't know if I can or need to, running Windows XP. I forgot what the message said I can check again tonight.
I have computer running as owner (I think).
Any suggestion on getting Windows XP to run as Adim
-
That's why I was asking if I should install the addonmanager alone or install gsx which will also install addonmanager.
Every product that comes with the Addon Manager, installs the Addon Manager too. The only need to separately download the Addon Manager, is to update it without downloading full installer, because it will update several support files for your installed products, but this doesn't have anything to do with the VC++ problem: the only files that MIGHT do a difference, are those .DLL I've suggested to download in replacement of the ones that comes with any product that installs the Addon Manager.
Of course, you have to try the .DLL replacement AFTER everything else is installed.
Just note that, if you did that, instead of uninstalling everything, it would have save you the time you spent uninstalling because, uninstalling everything related to the Addon Manager, won't fix any VC++ runtimes problem, because nothing related to this is caused by the Addon Manager and its related files.
I know the problem is with VS++2005.
Then why you uninstalled everything related to FSDT ?
Our installer don't do anything special other the launching Microsoft installer for those runtimes at the end. Which means, if the Microsoft installer is not able to automatically fix the problem you have in the runtimes installation, our installer will not either, since it doesn't do anything different than launching the Microsoft installer, which is the same you could download on the Microsoft site (vcredist.exe)
-
came home for lunch and reinstalled GSX. Tried 4055 of the dll and didn't work. I got a fatal error from FSX. 6195 dll also didn't work and also had a fatal error loading fsx.
I'm going back to work so I look into this later.
-
Still not working.
With a lot of people having this same problem (read from past posts), has anyone been able to determine exactly what files in VS++2005 are missing or corrupt. I would think that the makers of this product would have found out what the files are. If we would be able to determine what files in VS++2005 bad, then we may be able to fix the problem.
-
With a lot of people having this same problem (read from past posts)
Only one or two, including you, still have it unsolved. Everybody else fixed it either by removing every VC++ 2005 files, repairing FSX, or reinstalling Windows. Have you tried that ?
I would think that the makers of this product would have found out what the files are. If we would be able to determine what files in VS++2005 bad, then we may be able to fix the problem.
If the solution was just "fix a missing file", it's fairly obvious we would have indicated quite clearly long ago. The issue is, is not a matter of a "missing" or "corrupted" file, that's just the short explanation because I can't type the complete explanation in a short post.
The real issue is, those libraries have a system that, if a program needs a specific version, your Windows will instead supply a newer one, if it's available, on the premise it's forward compatibile and it's "better". Sometimes this works, sometimes it doesn't and, if it wasn't already so complex, it's even possible to run two versions of the same library at the same time in memory, which wasn't possible with old-style .DLL (these are not plain .DLL but are Side-by-Side .DLLs a newer form) and this is also sometimes working and sometimes not. There were issues with the VC++ 2008 runtimes that created a problem if ran together with the 2005 ones, for example. Microsoft has fixed this, but you might still have this offending version installed by some other program, even not-flight sim related.
That's why I said it's usually easier to repair the FSX installation, because it's just too complex trying to diagnose what's wrong, when something doesn't work, the diagnostic tool for Side-by-side provided by Microsoft is so complex that I don't think anybody figured it out how to use it. If you add the fact these libraries comes with many additional support files AND are referenced in the registry too, you'll understand why it's not possible to give an universal "fix", but it must be dealt with case by case.
You don't have to take my word for this, see this post by Pete Dowson on Avsim:
http://forum.avsim.net/topic/323009-simconnect-gone-mad/page__p__1909995#entry1909995
n my opinion the side-by-Side library system is the most diabolically convoluted system ever conceived and implemented by Microsoft and when it goes wrong it is fatal.
He's saying exactly the same thing: when something goes wrong related to WinSxS, it's almost impossible to fix it without reinstalling the whole OS. And the VC++ runtimes are of course SxS, like almost all Windows system libraries. This was a system created to fix the infamous "Dll hell", but it created an even worse one.
-
removing every VC++ 2005 files, repairing FSX, or reinstalling Windows. Have you tried that
Reinstalling Windows is not a option at this time, since the issue is only with addonmanager, although some aircfaft can't be installed. Already removed VC++2005 and reinstalled. I haven't tried a FSX fix yet, but I will, although FSX is a fresh install.
There were issues with the VC++ 2008 runtimes that created a problem if ran together with the 2005 ones, for example. Microsoft has fixed this, but you might still have this offending version installed by some other program, even not-flight sim related.
I did remove and reinstalled VC++2008, so I would think that I'd have the fixed Ver.. If there were issues with VC++2008 that would conflict with VC++2005, do you think if I remove VC++2008 without reinstalling would solve any problem. I really don't know much about computer so I don't know if VC++2008 is really needed on my computer. I do have VC++2009 and VC++2010 installed on my computer.
Can I leave GSX install when doing a FSX repair or should I remove it before doing a repair?
Thanks,
Gabe
-
do you think if I remove VC++2008 without reinstalling would solve any problem. I really don't know much about computer so I don't know if VC++2008 is really needed on my computer. I do have VC++2009 and VC++2010 installed on my computer.
It has been discussed in this thread that, a possible solution is to remove ALL VC++ runtimes, then reinstall GSX which will reinstall the one it needs. However, removing all those runtimes will probably require reinstalling them too, otherwise all other products that required them wouldn't work. But it would be probably better to reinstall the 2008 and 2010 runtimes using downloads from Microsoft.
Note that, even if you are using a 64 bit OS, we are only dealing with the 32 bit version of the runtimes, because they are used to run 32 bit apps.
Can I leave GSX install when doing a FSX repair or should I remove it before doing a repair?
Repair FSX doesn't usually require reinstalling any addon. It will probably enough to repair just the FSX SP2 (or the Acceleration pack, if that is what you installed), not FSX itself.
But before trying a repeair, try first removing all runtimes, then reinstall GSX, then reinstall (after having checked if GSX worked this way) all missing runtimes using latest downloads (32 bit) from Microsoft.
If you are worried about this, I could connect to your system with Teamviewer
http://www.teamviewer.com
After you installed it, send me your user id and session password using a Private Message.
-
But before trying a repeair, try first removing all runtimes, then reinstall GSX, then reinstall (after having checked if GSX worked this way) all missing runtimes using latest downloads (32 bit) from Microsoft.
Just to be clear when you say remove all runtimes... I would remove VC++2005,2008,2009,2010.
If I remove all runtimes, will I be able to get right back on internet to reinstall all runtimes without problems to computer?
If you are worried about this, I could connect to your system with Teamviewer
I would, but I'm really not Comfortable letting someone I don't know get into my computer.
No Offence, I hope you understand.
-
Just to be clear when you say remove all runtimes... I would remove VC++2005,2008,2009,2010.
2005, 2008 and 2010. Never heard of a 2009 version.
If I remove all runtimes, will I be able to get right back on internet to reinstall all runtimes without problems to computer?
I don't think any of the browsers requires them but, just to be on the safe side, download all the runtimes before starting.
If you are worried about this, I could connect to your system with Teamviewer
No Offence, I hope you understand.
No problem.
-
Never heard of a 2009 version.
Yeah, I thought I saw something, I'll check in about 1-1/2, when I get home. I'll let you know.
I don't know what time it is where your at, so I don't know if you'll be up to reply.
Yes, I will download all needed runtimes before I uninstall.
Thanks my freind, for trying to help. I hope we can get this issue fixed. After seeing GSX, I know want to get back on FSX instead of FS9, although I do like FS9 with all the addons.
Gabe
Hey Umberto, Your'e from Italy?
Some very nice countryside. I still remember being their with the family visiting some cousins. Traveled from Rome down the coast to Sicily. Visited some family, Then up to (I think it's called Ortona) which is my Dad's home town. Of course we saw everting else in between. My wife and daughter were their last year on a school trip. Just noticed the time and it looks like your time zone.
-
Sorry Umberto, my bad I must be going blind in my old age. :o I thought there was something 2009
Anyways, here's a screen shot. So just the C++ stuff gets un-installed and reinstalled?
I don't have tor worry about the MS SQL stuff or the MS VISUAL STUDIO 2010 stuff or the MS SDK stuff, ect., right?
Thanks for being patience with me. I really have no clue what some of this stuff does.
Gabe
P.S. what happened to the org. poster. qf11bd are you out there? Were you able to fix?
If so, please let us know.
-
Anyways, here's a screen shot. So just the C++ stuff gets un-installed and reinstalled? I don't have tor worry about the MS SQL stuff or the MS VISUAL STUDIO 2010 stuff or the MS SDK stuff, ect., right?
If you uninstall and reinstall everything, they should working again. It might be useful to run a Windows Update after that.
-
Ok I'm doing handstands, bouncing off the walls :D Not really.
Great news I finally got it to work. ;D
This is what I did in case anyone else needs to try.
After looking at a post from 2009, I tried what was suggested. With GSX installed I went into the WinSxS and deleted the simconnect 10.0.61259.0 folder and then did a reinstall of FSX SP2. By the way my folder also contains a 10.0.61637 as did the org. poster.
Now first of all when I went into the SP2 setup it gave the option to uninstall (even though I deleted the simconnect folder). after I went back into the setup for SP2 and did a install. Once the install was complete I got into FSX and addonmanager was their. I would suggest that anyone with this same issue try what I did
Exert from post: It should be possible to repair the SP2/Acceleration Simconnect version, without reinstalling the whole FSX, by removing the 10.0.61637.0 folder located under WinSxS, and then reinstalling Acceleration I don't have Acceleration so I just reinstalled SP2.
I will work with Acceleration as it worked for the person who had it.
Thanks
Gabe
-
Exert from post: It should be possible to repair the SP2/Acceleration Simconnect version, without reinstalling the whole FSX
That's interesting: in your case, the problem wasn't the VC++ runtimes but, instead, the only one other external dependency required by our products, which is Simconnect itself.
I haven't considered this, because this is a very rare case and, if your Simconnect was broken, any other FSX addon module would stop working. Maybe you haven't noticed it, either because you don't have any other 3rd party modules requiring Simconnect installed, or you don't have any other 3rd party module that requires the 10.0.61259.0, which is what we use (it's the latest version used by SP2 and Acceleration). A module requiring an older version (10.0.61637 in this case, which is the one that comes with FSX as shipped) wouldn't be affected by a corruption of the newest one.
-
I did try and install QW757, but that was also a addon that required addonmanager.
The QW757 would crash FSX when loading. I also tried loading my ejets emb 172 & 195. The airplane loaded fine, except the gauges were scrambled. Of course I knewthis airplane was SP2, but didn't think of SP2 being corrupt. OH well live and learn. Next person that has a problem with not seeing addonmanger in FSX menu, should maybe try this first.
3rd party module that requires the 10.0.61259.0, which is what we use (it's the latest version used by SP2 and Acceleration). A module requiring an older version (10.0.61637 in this case, which is the one that comes with FSX as shipped) wouldn't be affected by a corruption of the newest one.
I still don't understand why the simconnect folder read 10.0.61259. and the .dll was 10.0.6137. When I reinstalled SP2, It was also 10.0.61259 (folder) and 10.0.6137 (.dll). The only thing I did was, instead of using the previous SP2 that I downloaded. I downloaded the SP2 right threw FSX and saved it to disk, then install. Don't know if that made a difference or maybe the SP2 that I first downloaded got corrupt during download from internet. Well I'm going to check out the GSX trial when I get home, Before purchase.
Thanks again
Gabe
-
Okay thanks Umberto, all is fixed.