FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: jtbetteridge on July 07, 2016, 11:38:52 am
-
The other day I loaded a flight but when I pressed F12 I get an error mesage. GSX I have downloaded and installed the up to date files but they didn't load properly. I checked the path and it was pointing to a blank folder so corrected that and then the installation seemed to go OK, but F12 - no GSX and no coatl or GSX in the Addon drop down.
-
The other day I loaded a flight but when I pressed F12 I get an error mesage.
As I've already asked in the other thread: WHICH ERROR MESSAGE ? How do you expect we could even START helping you, with such non-descriptive report ?
-
The message was "Internal Error:An attempt was made to expand the "app" constant before it was initialized."
However, since that happened, I tried to follow your instructions to other people and reloaded GSX from the start. It seemed to load OK, but no there is no coatl or GSX in the addon drop down menu and nothing happens when I press Ctrl F12
In the addon menu FSUIPC and SODE are present.
Please let me know if you need more information?
Thank you
-
The message was "Internal Error:An attempt was made to expand the "app" constant before it was initialized."
You say "the message was", so this was the message you already posted in the thread here:
http://www.fsdreamteam.com/forum/index.php/topic,13985.msg103621.html#msg103621
However, since that happened, I tried to follow your instructions to other people and reloaded GSX from the start. It seemed to load OK
So you are NOT getting that error anymore ? Is the installer running fine now ? Does the program installed in the correct folder ? Because, from your LAST sentence here:
The other day I loaded a flight but when I pressed F12 I get an error message.
It seems you are INSIDE FSX and are pressing the ( not F12, but CTRL+Shift+F12, which the GSX default hotkey ) GSX hotkey, and you are getting an error.
I asked about THIS error, but you replied it with:
"The message was "Internal Error:An attempt was made to expand the "app" constant before it was initialized."
This is an error that can only appear while INSTALLING. But you said you got an error after pressing the (CTRL) F12 key!! They are two entirely different issue.
So, again, if what you said here is correct:
The other day I loaded a flight but when I pressed F12 I get an error message.
Which error is THIS one ??
Or, are you STILL getting the error from the installer AND a different error ( which one ? ) when pressing (CTRL) F12 ?
-
Hi
Yes, the message I got originally seemed to indicate that the path was incorrect so I followed your guide in the other thread and used the tool to correct the path. The message actually appeared when I tried to start GSX in FSXSE, not while installing. I installed GSX ages ago and it's been working fine until a day or two ago.
So then the GSX seemed to install OK, no warnings, no more error messages. Looking in the FSXSE folder there is the fsdreamteam folder with GSX inside
I started FSXSE and tried, but no GSX in the menu and pressing Ctrl F12 (I didn't mean F12) did not start GSX, just nothing at all.
So, what happens now is that when I have FSXSE running, and try to start GSX, nothing happens at all, no warnings, nothing.
-
The message actually appeared when I tried to start GSX in FSXSE, not while installing. I installed GSX ages ago and it's been working fine until a day or two ago.
I'm sorry, but if you are referring to THIS message:
"Internal Error:An attempt was made to expand the "app" constant before it was initialized."
It can ONLY appear when installing. It's an installer message. No chance to see it inside FSX.
I started FSXSE and tried, but no GSX in the menu and pressing Ctrl F12 (I didn't mean F12) did not start GSX, just nothing at all.
If with "no GSX in the menu", you are referring to the FSX "Addons" menu, are you missing:
- the GSX menu only
OR
- the GSX *and* the Couatl menu, but you have the Addon Manager menu
OR
- You are missing all 3 of them ?
-
I think we can forget that warning as it is no longer occurring anyway - I may have got the wording wrong possibly as I didn't write it down.
As far as the addon menu is concerned, the menu is there with only FSUIPC and SODE on the drop down. GSX, COATL and Addon Manager not present.
They were there the other day, and have been working fine until then!
-
GSX, COATL and Addon Manager not present.
Then it's not possible this would happen:
The other day I loaded a flight but when I pressed F12 I get an error mesage.
If if you don't have any of the 3 menus, it's clear that nothing related to GSX is running so, it's not possible you would see an error after pressing the GSX key!
If all 3 menus are not there, it's either the antivirus blocking them, which can be fixed as explained here:
http://www.fsdreamteam.com/forum/index.php/topic,13600.msg100771.html#msg100771
OR, your registry keys are STILL wrong, so the installer is not installing in the correct folders and not configuring the right DLL/EXE XML files, because the wrong registry keys for FSX are still there. This was already explained here:
http://www.fsdreamteam.com/forum/index.php/topic,13985.msg103575.html#msg103575
-
I'm telling you what happened.
GSX was present in the menu.
But when I pressed Ctrl F12 the warning came.
I've done the antivirus checks etc already. And in any case, if it was working fine before, why should it now stop working?
I will uninstall and start all over, and hope this fixes the problem.
I don't really understand your instruction fully for checking the registry keys. I have only FSXSE installed so please can you confirm that this source is exacly correct?
http://www.fsdreamteam.com/forum/index.php/topic,13985.msg103575.html#msg103575
-
But when I pressed Ctrl F12 the warning came.
Which warning ? If you are referring to this one:
"Internal Error:An attempt was made to expand the "app" constant before it was initialized."
Then no, you must confusing it with something else, because this error is an INSTALLER error. So, it must have been something else.
I have only FSXSE installed so please can you confirm that this source is exacly correct?
http://www.fsdreamteam.com/forum/index.php/topic,13985.msg103575.html#msg103575
Of course it's correct. It explains precisely how the registry keys should be when FSX:SE is installed alone.
-
OK, so I did exactly as instructed, including disable the antivirus, and still no GSX either by using hotkey or on the Addon Menu.
I have put FSX, coatl and bglmanx.dll in the exclusions list.
-
OK, so I did exactly as instructed, including disable the antivirus, and still no GSX either by using hotkey or on the Addon Menu.
This is again very confusing. You said:
But when I pressed Ctrl F12 the warning came.
WHICH warning ???
-
That was the original fault. It's not happening now and I can't remember the details.
What I can't understand is why, having uninstalled the GSX, then downloaded the new application and installed it, which all seems to go correctly, that GSX then doesn't work in FSXse?! I'm confused too.
I'm grateful for your help and sorry it's difficult!
What else can I try
-
That was the original fault. It's not happening now and I can't remember the details.
So what is happening now ? Nothing ? You are simply missing the GSX menu ?
What I can't understand is why, having uninstalled the GSX, then downloaded the new application and installed it, which all seems to go correctly, that GSX then doesn't work in FSXse?! I'm confused too.
A problem with antivirus is the most common cause for missing Add-on Manager or Couatl and GSX menus so, first try the following procedure:
- Go into Control Panel, Uninstall GSX and reply YES to the questions "Do you want to remove the Addon Manager ?" and reply YES to the question "Do you want to remove the Couatl script engine ?"
- TURN YOUR ANTIVIRUS OFF.
With the antivirus still disabled, reinstall GSX. Use the latest full GSX installer on our site.
- BEFORE launching FSX, configure the antivirus to exclude the following files from scanning:
YourFSXFolder\bglmanx.dll
YourFSXFolder\fsdreamteam\Couatl\Couatl.exe
- Now you can turn your Antivirus on, and launch FSX
- Note if FSX asks permission to run the Addon Manager and the Couatl programs, reply YES to both. PAY ATTENTION TO THIS.
- When FSX loads, check if you have BOTH the "Addon Manager" and the "Couatl powered products" under the "Addons" menu.
-
So what is happening now ? Nothing ? You are simply missing the GSX menu ?
Nothing. No GSX on the Addon Menu, only FSUIPC and SODE
I've followed those instructions exactly. No permission requests came up.
-
If I have done everything as above correctly, which I believe I have, what else can I try. Is there anyway that I can check the installation folders/files for example?
If SODE is working ok on the menu, and also ASN weather, then it implies that the GSX installation has gone wrong somehow?
-
Could you please try to download the full GSX installer now ? We just updated it.
-
OK. I'll do the whole routine including all the above advice re antivirus
-
OK, I downloaded it, it installed OK and I got the questions when FSXSE started, but then FSX crashed and I got a warning about a problem with the bglmanx.dll. Tried to start FSX again and it crashed see screnshot attached
-
OK, I downloaded it, it installed OK and I got the questions when FSXSE started, but then FSX crashed and I got a warning about a problem with the bglmanx.dll. Tried to start FSX again and it crashed see screnshot attached
I cannot open your attachement. Was it a screenshot ? If yes, why you sent an MS *Word* file ? Just sent the image. However, it's not really needed.
The bglmanx.dll error is a fake error, and it might appear the first time you trust an updated module.
Try to reinstall after a Windows restart.
-
I'm sorry, got the same error message and it crashed out when i said run with that file.
It says there's a problem with the bglmanx.dll and recommends running without it or disabling it.
-
I'm sorry, got the same error message and it crashed out when i said run with that file. It says there's a problem with the bglmanx.dll and recommends running without it or disabling it.
Doesn't happen and nobody reported it. Do exactly the opposite as the message suggests to do: ALLOW the program to run. And, as I've said, try to reinstall after a Windows restart.
And, be absolutely sure you don't have an antivirus interfering.
-
I did a allow, it crashed FSX. I'm reporting it.
Why don't you believe what I'm telling you
-
I did a allow, it crashed FSX. I'm reporting it.
Why don't you believe what I'm telling you
Why you think I don't "believe you" ?? I believe it's happening to you, but it's happening to you and you only, that's what I meant. The two proposed solutions:
1) Do exactly the opposite as the message suggests to do: ALLOW the program to run. And, as I've said, try to reinstall after a Windows restart.
AND
2) Be absolutely sure you don't have an antivirus interfering.
Will surely fix it.
-
I'm away for a few weeks so will try again when I get back, thanks.
-
Hello again
I've now done all of your instructions again; checked and confirmed the path is correct, uninstalled gsx, downloaded the new installer fromn the website, turned off the antivirus, installed, excluded the folders.....all as per your instructions.
Still no GSX on the menu.
Sorry. I would like more help?
Thanks
-
Still no GSX on the menu.
Are you still getting the error message you reported before, or you are just missing the Addon Manager and GSX menus ?
-
No error messages, just no GSX or addon manager on the menu
-
No error messages, just no GSX or addon manager on the menu
A problem with antivirus is the most common cause for missing Add-on Manager or Couatl and GSX menus so, first try the following procedure:
- Go into Control Panel, Uninstall GSX and reply YES to the questions "Do you want to remove the Addon Manager ?" and reply YES to the question "Do you want to remove the Couatl script engine ?"
- TURN YOUR ANTIVIRUS OFF.
With the antivirus still disabled, reinstall GSX. Use the latest full GSX installer on our site.
- BEFORE launching FSX, configure the antivirus to exclude the following files from scanning:
YourFSXFolder\bglmanx.dll
YourFSXFolder\fsdreamteam\Couatl\Couatl.exe
- Now you can turn your Antivirus on, and launch FSX
- Note if FSX asks permission to run the Addon Manager and the Couatl programs, reply YES to both. PAY ATTENTION TO THIS.
- When FSX loads, check if you have BOTH the "Addon Manager" and the "Couatl powered products" under the "Addons" menu.
-
I've done all that - no change I'm afraid
-
I've done all that - no change I'm afraid
You haven't replied to this step:
- Note if FSX asks permission to run the Addon Manager and the Couatl programs, reply YES to both. PAY ATTENTION TO THIS.
Of course, I assume you REALLY did all the steps, without missing a single one. Especially without missing THIS one:
- Go into Control Panel, Uninstall GSX and reply YES to the question "Do you want to remove the Addon Manager ?" and reply YES to the question "Do you want to remove the Couatl script engine ?"
If you haven't replied YES to both questions, then my previous question "Note if FSX asks permission to run the Addon Manager and the Couatl programs" becomes useless.
If you are not sure you done this, do it again. Be sure you DO reply YES to both question and note if FSX asks permission to run the Addon Manager and the Couatl programs.
-
Thanks.
I'm sure I did all those steps carefully.
I will do them all again to be absolutely sure!
One thing I am unsure about is the instructions on registry. You say:
"As I've said, the correct situation with ONLY FSX:SE installed is to have the FSX:SE key REMOVED:
- HKEY_CURRENT_USER\Software\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0
And the FSX registry key:
- HKEY_CURRENT_USER\Software\Microsoft\Microsoft Games\Flight Simulator\10.0
Pointing to the FSX:SE installation folder. This is a CORRECT registry for an FSX:SE installed with no FSX."
I did this, but I just checked in regedit and both files Flight Simulator\10.0 AND Flight Simulator - Steam Edition\10.0 are present. Is this wrong? I haven't done anything other than follow your instructions.
-
I did this, but I just checked in regedit and both files Flight Simulator\10.0 AND Flight Simulator - Steam Edition\10.0 are present. Is this wrong?
Yes, it's wrong. The error is the 10.0 folder, which shouldn't exists if you have ONLY FSX:SE installed and no FSX. You should remove the 10.0 folder only, no need to remove the whole key.
In any case, the *current* GSX installer is able to deal with the problem too, so if you are sure you are using the current full installer, it shouldn't be fooled anymore by this erroneous condition, so it's should be necessary to edit the registry. But I'd do it anyway, because that folder shouldn't be there, so it might confuse other installers.
-
Which 10.0 folder should I delete? the FSX one or the FSX - Steam one?
-
Which 10.0 folder should I delete? the FSX one or the FSX - Steam one?
From your previous message here, which quoted mine:
As I've said, the correct situation with ONLY FSX:SE installed is to have the FSX:SE key REMOVED:
- HKEY_CURRENT_USER\Software\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0
And from my previous reply, just to be sure you do it correctly:
You should remove the 10.0 folder only, no need to remove the whole key.
-
OK I did all that, reloaded GSX and when I started the FSX SE it looked good, asking permission to run the Addon Manager and Coatl programmes, which I answered yes. Then FSX crashed. Restart, and I get the following warning on an Error screen:
Flight Simulator has detected a problem with a third party software programme:
Name: bglmanx DLL
Version 3,0,0,17
Do you want to run this software (not recommended)
So I clicked "yes" because I know it's your programme, and FSX crashes again.
What next?
-
So I clicked "yes" because I know it's your programme, and FSX crashes again.
It's an error that appears randomly for many 3rd party modules, see a possible fix here:
http://fscaptain.proboards.com/thread/1523
Of course, in your case, the key will contain $ IgnoreFreeLibrary<bglmanx.dll>, but the solution doesn't change. Remove the key related to FSX.EXE in the HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers
-
There's nothing in that folder referring to FSX SE.
What seems to be happening though is the 10.0 folder keeps re-appearing in the other folder even after I've deleted it
-
What seems to be happening though is the 10.0 folder keeps re-appearing in the other folder even after I've deleted it
This seems to be caused by another addon that mistakenly tries to "fool" FSX:SE to look as if it was FSX, maybe to fix some other compatibility problem.
Unless, of course, you DO have BOTH FSX and FSX:SE installed so, as I've already explained in all my previous explanations, it's correct having both folders active, so you shouldn't remove anything.
-
No, I uninstalled FSX before installing FSX SE.
Could it be Active Sky Next? I installed SP5 about a week before I reported this problem to you?
Having said that, I went back and deleted the FSX SE\10.0 folder and then I just tried to start FSX SE without ASN strated and it crashed immediately. I restarted FSX SE and it came up with the bglmanx warning. So I then went and checked the registry and there was the FSX SE\10.0 folder again.
It seems that FSX Steam is relying on a FSXSE\10.0 path to launch.
-
It seems that FSX Steam is relying on a FSXSE\10.0 path to launch.
As I've said, you DO have BOTH FSX and FSX:SE installed. But in that case, the correct registry should be different: the FSX registry keys pointing to FSX and the FSX:SE registry keys pointing to FSX:SE
Under NO circumstances, BOTH registry keys should point to the same folder!
I'll repeat it AGAIN:
The correct situation with ONLY FSX:SE installed is to have the FSX:SE\10.0 key REMOVED:
- HKEY_CURRENT_USER\Software\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0 ONLY the "10.0" should be removed!
And the FSX registry key:
- HKEY_CURRENT_USER\Software\Microsoft\Microsoft Games\Flight Simulator\10.0
Pointing to the FSX:SE installation folder. This is a CORRECT registry for an FSX:SE installed with no FSX
If, instead, you have BOTH FSX and FSX:SE installed, the CORRECT registry should be:
the FSX registry key:
- HKEY_CURRENT_USER\Software\Microsoft\Microsoft Games\Flight Simulator\10.0
pointing to the FSX folder
and the FSX:SE registry key:
- HKEY_CURRENT_USER\Software\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0
pointing to the FSX:SE folder
-
I do not have both installed!
I uninstalled FSX following the instructions on Steam website in March before I installed FSX SE.
I have had GSX since 5 February 2013, and it was fine in the FSX system and then worked fine with FSX SE until the end of June.
Since then we've been having a long email exchange but it still doesn't work.
Maybe I haven't understood you correctly somewhere, but I've followed all your instructions carefully.
You keep referring to the registry, and it seems there must be something wrong there, but every time I delete the files you refer to they come back. When the FSX SE\10.0 folder is deleted, FSX SE just crashes out so maybe it should be pointing at that folder!? I'm sure you are right in what you are telling me, but it isn't working for some reason.
-
The other thing is that every time I start FSX SE now the warning about bglmanx.dll appears.
The fix you sent me didn't work because the path wasn't there - any other ideas, because it looks like FSX SE must be seeing GSX every time, but it's blocking that file..?
-
The fix you sent me didn't work because the path wasn't there - any other ideas, because it looks like FSX SE must be seeing GSX every time, but it's blocking that file..?
check if you are running FSX in any of the “Compatibility” modes, like XP or Vista or Windows 7/8, under Windows 10
No Compatibility mode should be enabled for the FSX.EXE file, which is how FSX defaults to.
-
can you help me by telling me how to check that?
-
can you help me by telling me how to check that?
Right-click on FSX.EXE, select "Properties"->"Compatibility"
-
OK I checked, and it's not running any compatibility modes.
Wondering why it keeps rejecting the bglmanx.dll? Surely there must be a key to the solution there do you think?
-
OK, so I've just been right back to basics again. Followed all of your installation instructions exactly, including checking the registry, uninstall, sort out the antivirus and then reinstall.
I used a clean download from the website. Installation seemed to go correctly, although a SODE dialogue box appeared, not sure what that was for.
Then started FSX SE and it crashed on start. So started it again and it came up with the warning about the bglmanx.dll. This now happens every time I start FSX SE and if I say run it, FSX SE crashes. So I say no, don't run it and FSX SE is fine, but no COATL or GSX in the addon menu.
So I checked the registry again and the FSX SE 10.0 folder has reappeared! It has a sub-folder FSX SE\10.0\Launch.
There must be something going wrong here but I've no idea what?
-
So I checked the registry again and the FSX SE 10.0 folder has reappeared! It has a sub-folder FSX SE\10.0\Launch.
That's because you probably installed FSX:SE when FSX was still installed. Even if you uninstall FSX, FSX:SE won't change its configuration, unless you reinstall FSX:SE too.
What's the value of the Co-Existence key in the FSX:SE registry ?
-
No,
as I said, I followed the instructions carefully, and uninstalled FSX before installing FSX SE!
I've got no idea what the registry reading you asked for is, where do I find that?
-
as I said, I followed the instructions carefully, and uninstalled FSX before installing FSX SE!
Installing or re-installing ? If you already installed FSX:SE once, when FSX was installed, the registry keys won't change and will remain as they were when you originally installed FSX:SE the first time, when FSX was present.
That's the only possible reason why your FSX:SE is still using the FSX:SE keys.
On a brand-new Windows install, that NEVER had FSX installed, FSX:SE will use the FSX registry keys. Its own keys will NOT use the 10.0 folder!
I've got no idea what the registry reading you asked for is, where do I find that?
In the same FSX:SE folder of the registry, the one that contains (and it shouldn't) the 10.0 key.
-
I can't see one.
Why can't I delete the FSX SE registry in full if it's not needed? It seems to be the focus of the problem.
And why the constant rejection of the bglmanx.dll?
-
Why can't I delete the FSX SE registry in full if it's not needed? It seems to be the focus of the problem.
Who said it's "not needed" ? The main key IS needed, what is NOT needed (and shouldn't be there), is the 10.0 folder inside of it, which shouldn't be there, if you installed FSX:SE when FSX wasn't installed.
And why the constant rejection of the bglmanx.dll?
Doesn't happen here. But until you fix your registry, anything can happen.
-
I've come to the conclusion that a full uninstall and reinstall is the only way ahead
-
I owe you an apology - despite having done my best, I have discovered residual FSX files which I've now completely removed from the PC. :-\ Despite searching before I hadn't found them, and used another programme to then complete the uninstall.
Hopefully this will now mean I can get a clean installation of FSX Steam and GSX will work again for me.
Thank you for your time over the past few weeks.