FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: drego22 on November 11, 2017, 04:07:12 am
-
Hello, I am sending this message due to not being able to get the Selection menu to popup when I hit ctrl+F12 or Coualt menu. I ran the updater several times, and I updated the Add on Mgr. and still nothing! Please help me resolve this horrible issue. Thank you in advance!
Andre Chambers
-
I've also this problem for a few days now. In Add-ons menu I don't have GSX or Couatl menu. I've even reinstalled GSX completely but the problem persist. Also GSX stays in trial mode even when I put in registration serial in Addon Manager for GSX.
-
I've also noticed that with GSX installed I am getting simmconect error after p3d loads up.
-
I've also noticed that with GSX installed I am getting simmconect error after p3d loads up.
If you are getting a Simconnect error (which one ?), it clearly shows the problem is not GSX, but Simconnect itself, so GSX it's just affected by it and, most likely, many other addons won't work correctly until you fix this Simconnect problem.
They are *usually* caused by other 3rd party products using very outdated versions of Simconnect, so your sim is stuck with the old ones.
-
I am getting message: "Flight simulator X SimConnect Error has been detected, restarting connection". But now I found out that apparently this isn't happening because GSX but it is happening because of FS Real time, but strangely not always. Sorry that I accused GSX for this error. But I still don't have Couatl and GSX menu in Add-ons, also it seems I can't register GSX. It stays in trial mode. A week ago everything was working fine and lately i didn't install any new addons except Envshade and I've ran FSDT Live Update now and then.
-
I received news about the new update (v2.2) and its new feature allowing a third cargo door for aircraft and proceeded to install the new update from the download from GSX's website. I am using FSX and I have been battling this issue as well. After the install, during my first session of FSX, GSX worked flawlessly and I fiddled around with the new feature. On the next FSX run, the GSX and coautl context menus were missing from the Add-on menu.
My troubleshooting so far, in sequential order:
- Checked FSX's 'Trusted' section to see if coautl.exe and bglmanx.dll are present and this was true.
- Uninstalled and reinstalled FSUIPC to see if the issue was caused by FSUIPC.
- Deleted all entries associated with GSX in FSX.cfg and then uninstalled and reinstalled GSX.
- Rebooted my PC.
- Uninstalled GSX since the problem still persists.
- Made a decision to roll back to version 1.9 and this gave me no issues but at this point it was too late to go back as I was now missing the new feature (mentioned above) that I got fond of already.
- Decided to use FSDT Live Update to update GSX rather than the installer downloaded from the website.
- After all this, the problem still persists.
-
After the install, during my first session of FSX, GSX worked flawlessly and I fiddled around with the new feature. On the next FSX run, the GSX and coautl context menus were missing from the Add-on menu.
If Couatl/GSX menus appeared initially, but it didn't on the 2nd run, and this happens even after a reboot, the most likely cause is the antivirus blocking Couatl.exe.
- Configure the antivirus to exclude the whole Addon Manager folder from scanning:
- Run the FSDT Live Update again.
-
Just did this but it is still not working
-
Then there might be a problem with your VC++ libraries, some of them might be missing or corrupted. Try to download them from here:
https://www.microsoft.com/en-us/download/details.aspx?id=53587
Download BOTH 32 and 64 bit versions, install both of them.
-
Then there might be a problem with your VC++ libraries, some of them might be missing or corrupted. Try to download them from here:
https://www.microsoft.com/en-us/download/details.aspx?id=53587
Download BOTH 32 and 64 bit versions, install both of them.
I appreciate your quick response. I have installed these and it is still not working. I did some more troubleshooting:
- I ran FSX. In the Add-on menu, Addon Manager was present. I tried to manage GSX from the Addon Manager and saw that GSX was in trial mode. I tried to activate it but got the same issue as was said earlier.
I've also this problem for a few days now. In Add-ons menu I don't have GSX or Couatl menu. I've even reinstalled GSX completely but the problem persists. Also, GSX stays in trial mode even when I put in registration serial in Addon Manager for GSX.
I navigated to couatl.exe in the Addon Manager folder in ProgramFiles(x86) and ran it. I did the following right after:
- toggled UAC on and off while monitoring processes in task manager
- toggled couatl.exe to Run as Administrator
I observed that there was no improvement while doing this. However, Coautl's Scripting Engine process flashed for a second in Task manager each time I clicked on the executable.
FSX was running during my troubleshooting
-
Ah...finally some useful results to pin down the issue. I after looking around for an error describing why couatl was not running, I found a file called Couatl.err in my %appdata% folder. The error message contained in it read:
couatl v3.2 (build 3868)
panic log started on Mon Nov 13 22:04:15 2017
problem raised by engine or unspecified addon
Traceback (most recent call last):
File "<string>", line 1, in <module>
ImportError: No module named wx
Application aborted because of a Python error
{}
Can someone please tell me what this error represents so I can continue to pin down the cause of the error and resolve this issue?
By the way, everyone else that has this issue on this thread, have you resolved the issue yet?
-
I have same error in Couatl.err as you. And no, I haven't resolved this issue yet. I also tried to install VC++ libraries from that link, but I get error for both 32 and 64 bit version that I already have another version of this product installed. Maybe it has something to do with my Windows, because i use Insider Preview builds and maybe GSX stopped working when my system was updated to build 17035. But I don't remember exactly if this issue started at that point. 8)
-
I have same error in Couatl.err as you. And no, I haven't resolved this issue yet. I also tried to install VC++ libraries from that link, but I get error for both 32 and 64 bit version that I already have another version of this product installed. Maybe it has something to do with my Windows, because i use Insider Preview builds and maybe GSX stopped working when my system was updated to build 17035. But I don't remember exactly if this issue started at that point. 8)
Same here.
-
I have same error in Couatl.err as you. And no, I haven't resolved this issue yet. I also tried to install VC++ libraries from that link, but I get error for both 32 and 64 bit version that I already have another version of this product installed. Maybe it has something to do with my Windows, because i use Insider Preview builds and maybe GSX stopped working when my system was updated to build 17035. But I don't remember exactly if this issue started at that point. 8)
Same here.
Hm, apparently we can pin down the cause of this issue to windows insider preview and wait for next build this Wednesday or Thursday and maybe the issue will gone. ::)
-
Hm, apparently we can pin down the cause of this issue to windows insider preview and wait for next build this Wednesday or Thursday and maybe the issue will gone.
Yes, this was already discussed in this thread:
http://www.fsdreamteam.com/forum/index.php/topic,16676.msg119344.html#msg119344
The OP has exactly the same issue and the same "No module named wx" error, and it could be fixed only by removing the Windows Beta and restoring the official one.
We can only hope that Microsoft will fix this, because it seems to be happening entirely outside our control.
-
Sorry to say but i'm running regular W10 and have the exact same issues - both GSX and airports refuse to remain installed despite numerous install /reinstalls. Add on Manager say the're all installed and active.
I've wasted two days trying to fix this. It's driving me nuts!
-Dean.
-
Sorry to say but i'm running regular W10 and have the exact same issues
Are you sure you have the "exact same issue" ? Meaning, you have THIS specific error in the error log ?
ImportError: No module named wx
Application aborted because of a Python error
-
No, sorry Umberto, I have no error log.
Any other suggestions greatly appreciated.
-Dean.
-
No, sorry Umberto, I have no error log.
Do you have a Couatl.LOG file instead ? Not having an Couatl.ERR file is normal, if you have logging enabled in the GSX Settings, because that option will log everything to the Couatl.LOG file instead.
-
I will enable it the next time it makes an appearance :)
-Dean
-
Umberto,
So I install my last FSDT AP - CYVR. Sure enough GSX returns - I know straight away because I see 'Regenerating cache......' appear at start. The buildings appear and 'Trial period has start...' appears.
Now....I go to GSX Menu / Settings. Enable log / Save.
I return to P3D and...Kapow!... I have no buildings, 'Your Trial has ended..', GSX is no longer in the menu and 'Coult Restart' is unresponsive.
I restart but have no GSX menu again.
Log attached.
-Dean.
-
Now....I go to GSX Menu / Settings. Enable log / Save.
I return to P3D and...Kapow!... I have no buildings, 'Your Trial has ended..', GSX is no longer in the menu and 'Coult Restart' is unresponsive.
Nobody ever reported such issue when JUST enabling logging. That looks like something related to antivirus, as if it has denied access to the folder. Or, possibly, some kind of permission problem on your hard drive.
Try this:
- Restart Windows
- Remove this folder
%APPDATA%\Virtuali (this will clear all your airport and airplane configurations so, you might want to backup it somewhere first)
- Reinstall GSX
-
Reinstalled GSX after deleting virtuali folder. Restart P3D......no GSX in menu.
I have no AV on this W10 PC, only Defender. I have excluded the coutl and GSX folders.
-
Reinstalled GSX after deleting virtuali folder. Restart P3D......no GSX in menu.
So now it has changed ? Before, you said it started normally, then it crashed after enabling logging. Now it doesn't even start ? Or, is started on the first launch of the sim after the installation, then it didn't came out on the first restart of the sim ?
-
No, I did not say it started normally. The only time GSX will bring itself 'back to life' is after a new AP is installed, and then only for the first P3D session. If, during the first session, you force the sim to reload by either changing location or selecting a different AC, then GSX and coutl will fail to load.
Umberto, I appreciate you are dealing with numerous posts with people having the same 'disappearing GSX' issue or similar issues, but the fact remains - with the previous version we were all happy simmers enjoying your great program. And that is it - if it wasn't such a good addition to the sim experience, I would have ditched it many aggravated hours ago. I don't recall the last time, other than when i've been beta testing, I've spent the best part of three days trying to get an FS add-on to function correctly.
And please, with respect, don't tell us how it runs without issue on your Development machine. Try installing 75% of the ORBX Catalogue, the new FTX Central, 50% of Aerosims work, all of UK2000's airports, all of Fly Tampa's, plus other smaller fish - 29Palms, justflight etc... PLUS three or four Study level aircraft. If members of your Team don't have at least some of these products then they are of little use. Sure, get each build working on your test rig with a vanilla install of each Sim, but then get your guys to break it anyway they can. That's their sole function. Whilst I also appreciate that not everybody may exhibit this issue, there has to be commonality somewhere.
It is your, and your Teams responsibility to ensure your product will function alongside others. Of course, I appreciate it is impossible to test every possible scenario, and as an experienced Beta tester myself, albeit a few years ago now, I know bugs will always creep through. Though in this case, logic would seem to tell us that if a group of people have a fully functioning piece of software and the only variable that changes is a next build - no AV settings changed or Permissions altered, then the error surely is something in the build; it was rather substantial, no?
Perhaps you could supply a link to v2.1 with a non-functioning auto update, that will at least give us our scenery and a working GSX back. i haven't made a flight in four days! :-)
Best of luck in tracking this down.
-Dean.
-
Hm, apparently we can pin down the cause of this issue to windows insider preview and wait for next build this Wednesday or Thursday and maybe the issue will gone. ::)
Win 10 build 17040 came out yesterday. Has the issue been resolved for you?
-
The only time GSX will bring itself 'back to life' is after a new AP is installed, and then only for the first P3D session. If, during the first session, you force the sim to reload by either changing location or selecting a different AC, then GSX and coutl will fail to load.
Ok, now your description is different again, and I'm starting to understand. It seems you have two problems at the same time: not starting on the 2nd session, and a problem with restarting in-game.
Umberto, I appreciate you are dealing with numerous posts with people having the same 'disappearing GSX' issue or similar issues, but the fact remains - with the previous version we were all happy simmers enjoying your great program
We are discussing a problem you are reporting, and I cannot see ANY difference in the number of "disappearing GSX" reports with this version. Like any other executable that runs with the sim, there are countless or reasons why it might "disappear", they are *always* caused by external causes, either conflicts with other addons and by other non flight-sim related software like antivirus/firewall or by issues with Windows.
There are so many different ways the program might not start but, the end RESULT would always LOOK simular, and it will be "GSX disappearing".
It's just that now, for some reason, it's happening to you, so you are assuming there must be a problem with the new version, or an increase in the likelihood of its disappearance with this version, which is not the case.
And please, with respect, don't tell us how it runs without issue on your Development machine. Try installing 75% of the ORBX Catalogue, the new FTX Central, 50% of Aerosims work, all of UK2000's airports, all of Fly Tampa's, plus other smaller fish - 29Palms, justflight etc... PLUS three or four Study level aircraft
I won't install anything from OrbX, because they never cared to reply to any of my request of cooperation about fixing all the issue their products cause to our sceneries (and so many others). But I have all the Flightbeam airports installed and several PMDG planes so no, it's just wrong assuming we test with just vanilla sim.
Sim, but then get your guys to break it anyway they can. That's their sole function. Whilst I also appreciate that not everybody may exhibit this issue, there has to be commonality somewhere.
It is your, and your Teams responsibility to ensure your product will function alongside others
It obviously does but, I hope you don't expect we could *fix* others problems.
If some developer, for example, insist linking against OUTDATED version of Simconnect, or doesn't respect (like we do, of course), the LM recommendation that a P3D add-on SHOULD be compiled using the VC++ 2015 redistributable runtimes (like we do), otherwise conflicts might happen, while we keep seeing other addon modules installing all different versions, what are you expecting we do ?
Perhaps you could supply a link to v2.1 with a non-functioning auto update, that will at least give us our scenery and a working GSX back. i haven't made a flight in four days!
Since the problem is surely not GSX, having a previous version won't help at all.
There's a KNOWN issue that we are trying to track it down, which is related to the new Windows Insider Preview version. At this time, there's no way to run GSX with it. We are setting up a test system with a Preview version, and we'll hopefully understand why, but it might take a while.
If you are not running the Windows Insider Preview, I'm afraid this is way to difficult to troubleshoot on the forum so, it's best we'd have a Teamviewer session, so I can check your system directly. PM me to arrange this.
-
Hm, apparently we can pin down the cause of this issue to windows insider preview and wait for next build this Wednesday or Thursday and maybe the issue will gone. ::)
Win 10 build 17040 came out yesterday. Has the issue been resolved for you?
No, the issue still remains with a new build.
-
No, the issue still remains with a new build.
Right now, there's no way to run the software on any Windows Insider Preview build. The last version that works, it's the latest official version, which is the 16299 build.
We have identified the reason of the problem, and we'll surely release a fix before the Insider Preview will become official, but in the meantime, your only options are:
- Revert to the latest official build.
OR
- Wait for us to release a fix.
-
No, the issue still remains with a new build.
Right now, there's no way to run the software on any Windows Insider Preview build. The last version that works, it's the latest official version, which is the 16299 build.
We have identified the reason of the problem, and we'll surely release a fix before the Insider Preview will become official, but in the meantime, your only options are:
- Revert to the latest official build.
OR
- Wait for us to release a fix.
Thank you very much for all of your answers and the solution. I'll wait for a fix, because I need insider preview for other SW testing purposes. 8)
-
Thank you very much for all of your answers and the solution. I'll wait for a fix, because I need insider preview for other SW testing purposes.
Try running the FSDT Live Update now, we released an update now that should work with the Windows Insider preview.
-
Thank you very much for all of your answers and the solution. I'll wait for a fix, because I need insider preview for other SW testing purposes.
Try running the FSDT Live Update now, we released an update now that should work with the Windows Insider preview.
Yeaaaa... Kudos, it does work now. Thank you. 8) :) 8)
-
Sorry to say but the update didn't work for me.
Umberto, I sent you a PM earlier today. I really would like to get this resolved asap.
Thank you.
-Dean
-
Thank you very much for all of your answers and the solution. I'll wait for a fix, because I need insider preview for other SW testing purposes.
Try running the FSDT Live Update now, we released an update now that should work with the Windows Insider preview.
I can say that my issue has been fixed with the new update. Thanks for the superb support.