FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: fraz31383 on December 29, 2014, 01:06:14 am
-
Installed FSX:SE on day of release and have been trying ever since to get GSX to work but have had no success.
Apologies if I am being a stupid here and have missed something blindingly obvious, but I have read numerous posts and genuinely tried everything I can imagine to get GSX to work.
As it stands at the moment:
1) I have downloaded (with antivirus off) version 1.9.0.4 of the GSX installer on 24th December. I installed with the antivirus still off and excluded the 2 files (bglmanx.dll and Couatl.exe) mentioned in previous posts from antivirus scanning.
2) Simconnect is installed and have tried uninstalling and reinstalling this multiple times in case this is the problem.
3) Both Couatl and Add on manger are installed and present in the add on manager menu in FSX:SE and GSX shows as Active, however does not appear in the Couatl powered products menu.
4) Pressing CTRL + F12 does nothing within FSX:SE and the default key mapping has been left at default
5) I have checked Control Panel, Internet Options, Content, Publishers etc and Virtuali s.a.s is under trusted publishers but NOT under untrusted. I have removed this from trusted as advised in previous posts and then re-trusted during launch of FSX:SE.
6) GSX shows as installed under Programs & Features in Control panel and detects the correct FSX:SE folder upon launch of the installer.
Please if there is any advice you can offer to sort the problem, as GSX is my favourite add on and I don't really want to use FSX:SE without it!
Many thanks
P.S Also tried a clean install of FSX:SE but no difference. Have now (29/12/14) also tried the 1.9.0.5 full GSX installer but this doesn't solve the issue either.
-
3) Both Couatl and Add on manger are installed and present in the add on manager menu in FSX:SE and GSX shows as Active, however does not appear in the Couatl powered products menu.
If you have BOTH menus, you can discard all the issues about Simconnect, antivirus, security certificates, etc. Those are ONLY meaningful if the modules don't run, but if you have their menus, the modules are clearly running.
If I understand your issue correctly, you HAVE the Couatl menu, but you don't have any entry related to GSX under it. Are you sure you installed GSX using the full installer ?
The latest full installer is 1.9.0.5, BTW...
-
3) Both Couatl and Add on manger are installed and present in the add on manager menu in FSX:SE and GSX shows as Active, however does not appear in the Couatl powered products menu.
If you have BOTH menus, you can discard all the issues about Simconnect, antivirus, security certificates, etc. Those are ONLY meaningful if the modules don't run, but if you have their menus, the modules are clearly running.
If I understand your issue correctly, you HAVE the Couatl menu, but you don't have any entry related to GSX under it. Are you sure you installed GSX using the full installer ?
The latest full installer is 1.9.0.5, BTW...
Yes that is correct, have the Couatl menu but no GSX in the list. Yes I am 100% sure I used the full installer, I even downloaded version 1.9.0.5 from the GSX website earlier this morning just after my initial post.
-
Yes that is correct, have the Couatl menu but no GSX in the list. Yes I am 100% sure I used the full installer, I even downloaded version 1.9.0.5 from the GSX website earlier this morning just after my initial post.
I cannot say what it might be without having a look at your system. If you want to start a Teamviewer session, contact me with a PM to arrange it.
-
if the OP finds a solution please post back the results here.
having identical issues, fresh FSX SE install, GSX installs fine with no visible error. the addon manager and couatl are all showing in the menu bar. default key ctrl + f12 is not displaying anything. tried changing this as ive seen in a few posts but no go. nothing is visible, at least in the demo airports ive tried
I want you to take my money but this has baffled me. have orbx (all uk areas) and a few planes plus uk2000 airports installed, all work fine with no issue.
-
I just had a Teamviewer session with fraz31383, and found what the problem was in his case: probably due to some kind of strange registry situation, due to the fact he used a registry cleaner (that didn't seem to clean much), there were registry keys pointing to empty folders, in this case the folder that holds the scenery.cfg, so the GSX was still trying to read into the folder normally used by FSX, or by an FSX Steam Edition installed alone, but that folder wasn't there.
We'll surely have a proper fix to handle these unusual cases, probably in the next days or so, and it won't require to download new installers, because it will likely be an update of just the Couatl.exe program.
IN THE MEANTIME, you can check if you are in the same situation, if you look for this folder:
%PROGRAMDATA%\Microsoft\FSX
But there's none. If you don't have this folder, your issue is probably the same as fraz31383 so, AS A TEMPORARY solution, to have GSX working, do as follows:
1) Create the Microsoft\FSX folder under %PROGRAMDATA% ( It's usually C:\ProgramData )
2) COPY (don't move, copy! ) the scenery.cfg from the %PROGRAMDATA%\FSX-SE into this newly created folder
This scenery.cfg will be used by GSX only, and if you add a scenery in FSX Steam Edition, either manually, or using an installer, you must copy again the updated scenery.cfg from the FSX-SE folder to the FSX folder, so GSX will get to know about the newly added scenery.
This will be ONLY a temporary fix, to allow you to use GSX while we fix it properly.
-
many thanks, this has worked for me as a temp solution. much appreciated.
-
The fixed version of Couatl.exe is now online, so if you just re-run any FSDT installer, you'll get it, so there's no need for that temporary fix anymore.
-
The fixed version of Couatl.exe is now online, so if you just re-run any FSDT installer, you'll get it, so there's no need for that temporary fix anymore.
Thanks Umberto and thanks again for your time spent yesterday trying to sort the problem.
Frazer
-
Hi Umberto,
I switch to this thread from where I originally posted, when it seemed to be a Norton 360 problem (KIAH).
Before Christmas it seemed that I had solved my problem because as reported I did not download the addon manager but GSX only, started GSX, which then obviously got the addon manager by itself and when I started FSX, both cuatl and addon manager were then active in the FSX addon bar and both GSX and all Airports were working.
But when I was starting FSX I got a message, that reporting a conflict with the
Dynamic Link Library version 2,9,0,25 bglmanx.dll.
Accepting to use the Library made GSX etc. running, not accepting, removed cualt and Addon Manger from the FSX bar and airports and GSX were not working.
This where I stopped testing, not testing the rest of my Cockpit hard and software, .because the problem seemed to be solved.
Today I started FSX, again I was asked, not to accept bglmanx.dll. By doing it, GSX worked, but my GoFlight instruments, as far as connected to the FSX PC (some are linked through a second PC), are not working any more.
I was trying several times always the same result and found similar reports on a FSX forum.
So for a first attempt, shall I remove GSX again and all its components and download the new Addon Manager, start with it.
I will also check, if the mentioned FSX.cfg conflict exists in may case as well, which I can only do tomorrow earliest.
Sorry, bit confusing probably..
To make a long story short, do you recommend to delete the old addon manager and use the new one in any case ?
best regards
Bernd
-
Accepting to use the Library made GSX etc. running
That means the program works normally on your sytem.
not accepting, removed cualt and Addon Manger from the FSX bar and airports and GSX were not working.
That's normal too. If you don't run the modules, nothing will work.
Today I started FSX, again I was asked, not to accept bglmanx.dll. By doing it, GSX worked, but my GoFlight instruments, as far as connected to the FSX PC (some are linked through a second PC), are not working any more.
That seems to indicate that running those modules causes a conflict. I had a look to the GoFlight software, and installed it, and it doesn't cause any problems on my system, but I can't possibly know if the conflict happens only if you have a GoFlight hardware attached or not.
I've checked the GoFlight software, and it seems to require the VC++ 2012 runtimes. Our modules requires the VC++ 2005 runtimes, and this is made intentionally, because that's the same version FSX itself uses, so we tried to be more close to the FSX standard, in order to minimize conflict. Simconnect itself, used by FSX, uses the VC++ 2005 runtimes.
So, the most likely explanation, is the Windows Side-by-side system that allows two modules using two different runtime libraries to be running together in memory, is not working properly.
To make a long story short, do you recommend to delete the old addon manager and use the new one in any case ?
You can TRY running the GSX full installer and DO NOT install the Stand-Alone Addon Manager afterwards. This because the Addon Manager version that comes with the GSX installer is slightly different than the one that comes with the Stand-Alone Addon Manager, meaning it requires a different sub-version of the VC++ 2005 runtimes, one that hopefully works in your system.
If this fixes the problem, then you know you should always install GSX or a scenery installer, and never install the Stand-Alone Addon Manager, until you fix the problem, or you don't run other products that triggers the conflict.
-
IN THE MEANTIME, you can check if you are in the same situation, if you look for this folder:
%PROGRAMDATA%\Microsoft\FSX
But there's none. If you don't have this folder, your issue is probably the same as fraz31383 so, AS A TEMPORARY solution, to have GSX working, do as follows:
1) Create the Microsoft\FSX folder under %PROGRAMDATA% ( It's usually C:\ProgramData )
2) COPY (don't move, copy! ) the scenery.cfg from the %PROGRAMDATA%\FSX-SE into this newly created folder
This scenery.cfg will be used by GSX only, and if you add a scenery in FSX Steam Edition, either manually, or using an installer, you must copy again the updated scenery.cfg from the FSX-SE folder to the FSX folder, so GSX will get to know about the newly added scenery.
This will be ONLY a temporary fix, to allow you to use GSX while we fix it properly.
Hi again Umberto
I today decided to do a complete clean install of both my boot/Windows drive and the drive that I installed FSX onto, in the hope of preventing any future problems. However straight after installing FSX:SE I made GSX the first add-on I installed, used the latest installer etc from FSDT site, accepted permissions during FSX:SE splash screen/start up. Once the Sim was loaded Add On manager and the Couatl powered menu was there but no GSX?!
I came back to your post following our Teamviewer session and went through the temporary fix, however, where I expected NOT to find the %PROGRAMDATA%\Microsoft\FSX I infact DID. I therefore thought to myself if GSX is looking for %PROGRAMDATA%\Microsoft\FSX-SE (which was missing in this case), if I renamed "%PROGRAMDATA%\Microsoft\FSX" to "%PROGRAMDATA%\Microsoft\FSX-SE" would this work, and hey presto it did! Scenery libraries were rebuilt upon loading FSX:SE and GSX was now back where it should be in the Couatl menu!
Im not sure of the relevance or significance of this but thought I would share in case it helps anyone else out or if it assists you with potential future issues.
In addition, I went back into %PROGRAMDATA%\Microsoft\ and where I had renamed the original FSX to FSX-SE a newer FSX only folder had been regenerated?! Hope this might mean something to you or others out there but at the moment I'm happy as I now have GSX working... haven't installed any other add-ons though so hope I don't encounter any issues with those!
-
Thanks so far, I will try asap.
Additional information.
I also use the DX 10 fixer, until yesterday version 2.5.
Yesterday I updated to version 2.6, better I tried it. The procedure is to completely delete the previous version and then install the new one.
Starting the installation of version 2.6 I got the message, that either my rights (this was not the problem) or the path is not correct. As far as I understand it also the fixer uses VC++ (no idea which version).
I then switched back to version 2.5 (new installation), which worked without any problems.
As I did not make any changes at all in my systems, when Norton 360 refused to accept bglmanx.dll and addon.exe and I was asked by the FSX not to accept the Virtually software, I was asked through several questions which I, as already reported accepted.
Obviously this led to the problems I am facing now.
So either the addon manager or the microsoft/FSX logic, that tried to delete all links etc. your software had set, must have made certain changes, which cause the problems.
Is the information that the new installation of the 2.5 Fixer DX10 workes, the 2.6 version not, helpfull ?
Regards
Bernd
-
I came back to your post following our Teamviewer session and went through the temporary fix, however, where I expected NOT to find the %PROGRAMDATA%\Microsoft\FSX I infact DID.
This is NORMAL. The %PROGRAMDATA%\Microsoft\FSX-SE folder is created ONLY if you install FSX Steam after the regular FSX. If you install with no previous FSX version, the standard %PROGRAMDATA%\Microsoft\FSX folder is used, and no Steam-specific folders are used.
I therefore thought to myself if GSX is looking for %PROGRAMDATA%\Microsoft\FSX-SE (which was missing in this case)
No, it's not. Or, it shouldn't...
if I renamed "%PROGRAMDATA%\Microsoft\FSX" to "%PROGRAMDATA%\Microsoft\FSX-SE" would this work, and hey presto it did! Scenery libraries were rebuilt upon loading FSX:SE and GSX was now back where it should be in the Couatl menu!
This is wrong, and shouldn't happen. I can see the code here now, and when the Steam version is running, the %PROGRAMDATA%\Microsoft\FSX-SE path is used ONLY if BOTH the fsx_se.cfg AND the scenery.cfg files are found in their respective %APPDATA%\Microsoft\FSX-SE folders. BOTH must be present, if even one it's missing, the standard %PROGRAMDATA%\Microsoft\FSX path is used.
So, the only possible explanation, is you are using outdated Addon Manager and Coautl executables. Latest Addon Manager is 2.9.0.26 and latest Couatl.exe is build 2.0.0.2376. If you don't have these version, reinstall GSX again to get them.
-
Is the information that the new installation of the 2.5 Fixer DX10 workes, the 2.6 version not, helpfull ?
Only to prove/confirm the problem is something happening to the VC++ libraries, which we cannot obviously fix in every possible situation. All our installers runs the official MS installers for the VC++ libraries, but all these installers cannot fix a problem caused by a "newer" installer, because they would never do what they consider to be a "downgrade" of any files.
This means, if another product installs a newer but bugged or conflicting version of the libraries, it cannot be fixed by "just" running the correct MS installers, like we do anyway in our installers.
The only thing you can try from our site, is to run the Stand-Alone Addon Manager AS LAST of, if that doesn't work, run GSX installer AS LAST.
-
I hade the exact same problem as Fraz and the solution was to make a copy of the FSX folder in the %ProgramData% and named it FSX-SE.
I have not had Orginal FSX installed but i do have P3D v2 and a program called "migration tool" which is to simulate FSX for some addons in P3D.
I have unistalled GSX several times and downloaded the latest installer for it but i could get it to work until i tried the above.
Is there any way to change so that GSX use the %programdata%Microsoft\FSX instead? Reinstalling it dos not work.
-
Is there any way to change so that GSX use the %programdata%Microsoft\FSX instead? Reinstalling it dos not work.
Reinstall it now, we updated again the modules now, and now the FSX Steam edition running stand-alone should be detected more reliably. You can remove the copy of the folder you made now.
-
Is there any way to change so that GSX use the %programdata%Microsoft\FSX instead? Reinstalling it dos not work.
Reinstall it now, we updated again the modules now, and now the FSX Steam edition running stand-alone should be detected more reliably. You can remove the copy of the folder you made now.
Can confirm this is now the case on my system. Although I had not had a previous install of FSX disc version (had done a complete system re-install) the FSX-SE folder was created, however after re-installing GSX with the most up to date installer, this fixed the problem and the FSX-SE folder is no longer needed or present.
-
Is there any way to change so that GSX use the %programdata%Microsoft\FSX instead? Reinstalling it dos not work.
Reinstall it now, we updated again the modules now, and now the FSX Steam edition running stand-alone should be detected more reliably. You can remove the copy of the folder you made now.
Re-installed it and now it works without the FSX-SE folder.
Thanks for the help
-
I am still having the issue where GSX is saying it cant find the FSX-SE. I have downloaded GSX again today and tried to install with the same issue. My FSX SE game is creating the folders just called FSX in local, roaming and Programdata so not sure why I am having this issue :(
Just tried to install KLAX and it didnt get any errors but it was not added to the scenery.cfg file in the FSX folder in ProgramData, I am guessing because it was expecting an FSX-SE folder to be there.
-
I am still having the issue where GSX is saying it cant find the FSX-SE
This is not very clear. Are your referring to the GSX *installer* saying it cannot find FSX-SE ? Or something else ? In any case, what's the precise, exact, text of the message ?
-
Sorry yes the GSX Installer. Downloads the additional files ok, installs files correctly to the Steam location and then the error
C:\Users]\Name\AppData\Roaming\Microsoft\FSX-SE\dll.xml Error on line 0, position 0:
The system cannot find the path specified
Your C:\Users]\Name\AppData\Roaming\Microsoft\FSX-SE\dll.xml file has not been modified by this installer.
-
Sorry yes the GSX Installer. Downloads the additional files ok, installs files correctly to the Steam location and then the error
C:\Users]\Name\AppData\Roaming\Microsoft\FSX-SE\dll.xml Error on line 0, position 0:
This was already discussed here:
http://www.fsdreamteam.com/forum/index.php/topic,11252.0.html
-
Hi there,
I have read that link and no where does it solve my problem sorry (or I am blind ;D ). My problem is that I dont have an FSX-SE folder(s) but the installer (which I downloaded yesterday) still tries to find the the wrong named folders. All my Steam Edition folders are just called FSX as I dont have a boxed FSX installed.
If I create a blank FSX-SE folder and copy my dll.xml from the FSX folder then it updates that fine but the problem is that my sim is only looking at the folder called FSX and as such the dll.xml doesnt do anything unless I copy it across to the FSX folder.
All other addons from Orbx and Aerosoft etc and planes are installing fine and finding the correctly named FSX folders.
-
I have read that link and no where does it solve my problem sorry (or I am blind Grin ).
The error message was the same. Since, so far, you haven't said you don't *have* an FSX-SE folder to begin with, I could only assume that, you were in the same case, since the error was identical. Now that you said you don't have a folder, then the issue is different.
My problem is that I dont have an FSX-SE folder(s) but the installer (which I downloaded yesterday) still tries to find the the wrong named folders. All my Steam Edition folders are just called FSX as I dont have a boxed FSX installed.
The installer correctly recognizes BOTH:
- An FSX Steam DUAL installation, which means FSX with its own folders and its own registry keys, and FSX:SE under its own separate FSX-SE folders
- An FSX Steam SINGLE installation, which means no FSX installed, and FSX:SE using the FSX folder and registry keys.
Of course, it can only rely on your registry to find which kind of installation you have so, if the installer is looking into an FSX-SE folder, it can only means your registry keys are pointing there, perhaps as a result of a previous dual installation, and then a removal.
To confirm this, you can activate logging in the installer this way:
- Open a command prompt ( start -> CMD -> enter )
- go to the folder where you have the installer, for example:
CD c:\Users\Yourname\Desktop
Assuming you put the installer on the Desktop
- launch the installer (GSX, in this example) with this command:
gsx_fsx_setup.exe /log=install.log
This should hopefully create a file named install.log on your Desktop. If you have it, then send it to me ( via Email, please ).
-
OK thanks for the info will do that once I get home from work.
Cheers
-
OK thanks for the info will do that once I get home from work.
The log you sent me by email, confirms the installer is correct, and the problem is your registry keys which are not right.
You said you installed FSX:SE without FSX. In this mode, FSX:SE will use the FSX registry keys and FSX folders. Instead, if you install FSX:SE alongside an existing FSX installation, it will use the FSX registry keys and folders.
The issue is, on your system, the registry key for FSX:SE WAS present, and pointing to its own folder on Steam, so the installer correctly assumed a Dual installation, and would use all the specific FSX:SE folders for things like XML files and .CFG files. But this is not normal, because if you installed FSX:SE stand-alone, the FSX:SE registry key should not exists.
Perhaps you installed in Dual mode, then removed FSX ? In that case, probably the registry keys remained as if they were in Dual mode, you are likely supposed to uninstall AND reinstall FSX:SE too, after an FSX removal.
Note that, you could have proceeded with the installation, if you simply replied NO to the 1st request to install into FSX Steam mode, because the installer is smart enough to check the FSX folder then, and check if there's a Steam FSX installed there, so you still have a chance to install into Steam in "Single mode", even after your replied NO to a Steam "Dual Mode" install.
-
Hi there and thanks for checking that.
I had uninstalled FSX prior to installing FSX-SE and had used a registry cleaner to remove any traces afterwards but I am guessing it must have missed something along the way.
Have checked the HKCU and HKLM in the registry and it only mentions FSX-SE.
Oh well thanks again
-
I had uninstalled FSX prior to installing FSX-SE and had used a registry cleaner to remove any traces afterwards but I am guessing it must have missed something along the way.
The problem are NOT the FSX keys which were still remaining: the problem are the FSX:SE keys, which were created when FSX:SE was installed alongside FSX.
That's why I said that, after uninstalling FSX and cleaned the registry, you should have Uninstalled (and verified if the FSX:SE keys were removed) AND Reinstall FSX:SE, in order to give a chance to the FSX:SE installer to set the registry keys to be like FSX, which is what they are supposed to be on a Single installation.
Uninstalling FSX won't change the FSX:SE keys, because the FSX uninstaller doesn't know anything about them, and a registry cleaner won't (hopefully) touch something that is still installed.
Have checked the HKCU and HKLM in the registry and it only mentions FSX-SE.
And THAT'S the problem!
If you install FSX:SE stand-alone on a clean system, you are not supposed to see ANY FSX:SE keys, the registry keys will look like exactly as if were FSX, just the folders they points to, will point to the Steam installation, usually under Programs\Steam\Steamapps\common\FSX
-
Note that, you could have proceeded with the installation, if you simply replied NO to the 1st request to install into FSX Steam mode, because the installer is smart enough to check the FSX folder then, and check if there's a Steam FSX installed there, so you still have a chance to install into Steam in "Single mode", even after your replied NO to a Steam "Dual Mode" install.
That's exactly what I did. I replied No to the request to install into FSX SE. But when I check the values in the "Date modified" column for dll.xml and exe.xml it says 19/05/2015 for both. If these files were modified today by the GSX installer, wouldn't the "Date modified" reflect that?
Thanks,
Tony B.
-
That's exactly what I did. I replied No to the request to install into FSX SE. But when I check the values in the "Date modified" column for dll.xml and exe.xml it says 19/05/2015 for both. If these files were modified today by the GSX installer, wouldn't the "Date modified" reflect that?
Assuming you are looking at the *correct* XML files (which, if you replied NO to the question about installing into Steam, are under %APPDATA%\Microsoft\FSX and NOT FSX-SE! ), they would be modified only if the installation completed without errors, which ( as it seems from your other message ), doesn't seem the case, because you said you still said the error on about the XML files, and if there's an error, they are not being touched.
However, it wasn't clear from that message, if when you said you tried to reinstall a 2nd time, you replied NO to the question about installing into Steam, which is something you are adding now.
I can only confirm that:
If your FSX:SE registry keys are still there from a previous installation together with FSX, but you haven't uninstalled/reinstalled FSX:SE after removing FSX in order to give a chance to the FSX:SE installer to set the registry keys correctly ( and assuming the FSX:SE uninstall WILL remove the now obsolete FSX:SE registry keys, which is not certain, so better check and do it yourself if they aren't...), which is what is causing this problem, answering NO to the request to install into Steam will complete the installation correctly, and still recognizing FSX:SE properly.
We'll probably update the installer to double-check, and verify the existence of the folder containing the XML files, but that would just be an additional foolproofing to make the installer more resistance to non normal situations like yours.
The normal situation should be:
1) FSX:SE installed alongside FSX = separate registry keys and folder locations for config files under the FSX-SE registry and folder name
OR
2) FSX:SE installed stand-alone = use of the same registry keys AND folder locations as FSX
BOTH #1 and #2 are correctly handled by the installer.
Yours is a different case, which is FSX:SE installed stand-alone, with folders under FSX, but with FSX-SE-specific registry keys coming from a previous installation when FSX:SE WAS installed along side FSX, so the folders were probably missing (as a result of uninstalling it), but the registry keys were still there, so the real issue it's likely the FSX:SE uninstaller that doesn't clean up everything.
But again, we'll surely add this case too.
ANOTHER possible solution, would be simply removing the FSX-SE registry keys with REGEDIT, the "AppPath" key, under this section:
HKEY_CURRENT_USER\Software\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0
If you remove this entry (assuming you have FSX:SE with NO FSX installed, and FSX:SE installed/reinstalled when NO FSX was installed ), the installers will work just the same, and it's probably the best solution, because I think other installers might be easily fooled by this.