FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: MattG on February 09, 2020, 07:37:58 pm
-
Hi,
After speaking to a few others it seems the latest GSX update from 6/7th Feb 2020 has a bug where GSX and Corul will not start with the sim and is missing from the addon drop down menu. I've tried running the update a number of times and it doesn't fix the issue. It seems like it's more of a lucky dip to see if it will load or not load at all. Sometimes it does, sometimes it doesn't.
If you could advise or look into it then that would be great. Or if you need me to do anything like provide logs etc then do let me know.
Cheers,
-
Same problem here since updating. Was fine before. Hope this gets fixed ASAP as its really annoying. Was working fine before the update. Glad its not just me getting this problem.
Wish I had held off updating . Also when it does start and you then restart Coualt after making changes to GSX it crashes. The Cualtl an Gsx menu disappears from the Addon menu
and you have to restart P3d. Its become totally unstable since the last update. Even tried reinstalling but no luck.
-
To confirm, exactly same issues for me. Once GSX disappears, I need to reinstall as it will not work after a sim restart.
Regards,
Keith
-
I Can confirm this as well. I did a post on this one earlier where the Menu disappears. YOu load p3d in default scenario and it works fine. As soon as you change aircraft the menu disappears. I had no SW changes over the past few months, other than updating FSDT yesterday. I dide howeber re-install VC++ 2005 library and seems to have fixed it
-
There's clearly a problem here with the latest update as GSX is currently virtually unusable in its current state. It also disables any FSDT airports you have installed when Cuoatl crashes.
there are now many posts on this problem and no response from the developer. Is he on holiday or something? The live update need to to be updated with a working version until the problem is solved.
Pity we cant roll back to the previous version as it would eliminate issues like this.
Someone said reinstalling VC++2005 library fixed the problem, could someone give a step by step instructions on how to do this as I don't have a clue how to do it. I have GSX and many FSDT airports installed that I can't use
because of this and i'm sure many others have too. This is extremely annoying.
-
Versus my previous Post from above that the re-install of the VC++ Libraries solved the problem. Nope: Yesterday I managed to fly KBOS to EIDW with GSX working fine. Today started P3d with default again - GSX is fine - changed airport to LTAC - GSX is still there - changed aircraft to PMDG 737 NGXU and bang - GSX disappears. I am at the end of my solutions here
-
I have the same issue, GSX not starting most of the time and showing as unregistered in Addon Manager. Tried Live Update but this did not solve the problem.
-
I'm sorry, but I cannot reproduce the problem.
GSX loads fine, and I can switch from an airplane to another with no issues, tried it now, switching from default A321 to PMDG 737-600, and back to default 737, and it always load normally.
-
It doesn't seem to be a virus protection issue as switching off real time protection does not solve the problem. Most of the time, Couatl is not launching, although I did get it to work a couple of time this morning but when I changed airport it stopped working (the airport cache did not load).
I have tried various aircraft (including the stock Cub) and various airports and most of the time I do not have GSX in the Addons menu and it shows as a trial product in the Addon Manager.
Any help would be appreciated as I do not want to reinstall (again) and then have to reinstall a lot of airport scenery.
I'm running the latest version of P3D client on Windows 10 with all updates installed. I have tried deleting my AppData/Local/Temp folder and this made no difference.
-
If Couatl simply doesn't start, then the most likely problem IS the antivirus.
We have updated it and, lots of antivirus if not properly configured ( by adding the whole Addon Manager folder to the antivirus Exclusions ), will block something they don't know "just" because it's new.
This happens a lot whenever we do an update, so users assume there must be a problem with it, but there isn't. It's just they antivirus blocking the file because it's new. After you configured the antivirus correctly, do as follows:
- Restart Windows
- Run the FSDT Live Update again.
-
I already had the whole c:\Addon Manager folder excluded. I'm never convinced that Windows pays attention to folder exclusions properly though!
I added the Couatl folder as well, rebooted and GSX worked with the default Cub at Gatwick. I changed to Rome LIRF and it was still working, then I switched the FSLabs A320 and it stopped. I rebooted and tried to load straight into LIRF with the FSLabs and it was still not working.
I'll try excluding the AppData\Roaming\Virtuali folder and see if that makes any difference and report back.
-
When you say "Gatwick" or "Rome LIRF", do you mean default sceneries ? If no, are these 3rd party add-on using SODE jetways, default jetways, GSX replaced jetways ?
I tried doing something similar to what you did, went to EGKK (default), switched to the default Cub, moved to LIRF (default), switched to the FS Labs A320, no problems.
-
They were 3rd party addon sceneries but I was having the issue with default airports as well. Virus protetcion does seem to be the problem and I think I have solved the problem by adding the AppData\Roaming\Virtuali folder as an excluded folder in the Windows virus protection settings. I have successfully loaded into one airport and changed to another and the airport cache and GSX loads.
NB this issue only came up for me today so it could be the latest virus definition that is the problem, I was using GSX happily yesterday morning with no issues.
Thank you for the prompt replies.
-
I have managed to fix the problem and no it's not related to any sort of anti-virus software.
In the following file: C:\ProgramData\Lockheed Martin\Prepar3D v4\add-ons.cfg I had entrires for the following:
FsDreamTeam Exclude
FsDreamTeam Addon Manager
I made a backup of the add-ons.cfg file and then removed the entries above and then re-numbered the packages so it was going in order: 1,2,3,4 (you get the idea).
I removed them because I already had them in the following area:
C:\Users\*yourusername*\Documents\Prepar3D v4 Add-ons\FsDreamTeam Exclude
C:\Users\*yourusername*\Documents\Prepar3D v4 Add-ons\FsDreamTeam Addon Manager
And in the above folders they have their own add-on.xml file.
Re-opened P3D and a message pops up asking if you want to activate the two addons. Said yes to both and GSX is working as normal. No idea what happened with the latest updates as this was all fine before I applied the update at the weekend (a number of times to see if it would fix it).
I can't say this will fix it for everyone as you will have to check your own files to see what is happening.
-
I made a backup of the add-ons.cfg file and then removed the entries above and then re-numbered the packages so it was going in order: 1,2,3,4 (you get the idea).
You mean they were out of order before ? This is strange, since we don't touch that file, it's the sim that will handle the creation of all the section, when an add-on asks to be registered.
Have you used an external utility that handles add-ons ?
-
I'm not 100% sure but I think it was a virus protection issue for me, as everything was working fine until this morning and the only thing that changed on my system was the virus definition file. I had run the most recent live update a couple of days ago and it did not cause me an issue as I was using GSX with no issues yesterday.
The virus protection behaviour seems to be a bit random as it was not stopping GSX all of time. In general, I feel that the virus protection industry is a bit of a scam and Microsoft make money charging developers to allow their programs to work!
-
I made a backup of the add-ons.cfg file and then removed the entries above and then re-numbered the packages so it was going in order: 1,2,3,4 (you get the idea).
You mean they were out of order before ? This is strange, since we don't touch that file, it's the sim that will handle the creation of all the section, when an add-on asks to be registered.
Have you used an external utility that handles add-ons ?
Hi,
No they weren’t out of order. I mean I put them back in order when I removed any mentions of FSDreamTeam.
I don’t use anything to manage the add ons.
-
I have managed to fix the problem and no it's not related to any sort of anti-virus software.
In the following file: C:\ProgramData\Lockheed Martin\Prepar3D v4\add-ons.cfg I had entrires for the following:
FsDreamTeam Exclude
FsDreamTeam Addon Manager
I don't have those entries in my add-ons.cfg.
-
I don't have those entries in my add-ons.cfg.
Which seemed to be the problem for me. I manually added those two folders by simply copying other addon-entries and redirecting the path to "...Addon Manager" and "...Exclude".
-
This is strange, I assure you that running GSX installer will result in both entries added to the add-ons.cfg file ( Prepar3d itself is doing this, under request from the GSX installer ) but, more importantly, the Live Update will never try to touch them.
-
This issue is a bit of a hit and miss. All my Sim files incl. FSDT and the virtuali one under users are excluded. Never had any problems until last update. Here is my scenario again.
5th attempt: Loaded SIM with default scenario - GSX is showing - no scenery cache loading - did it manually. Changed to LTAC with default aircraft again - reloaded airport cahe - then changed aircraft tp NGXU - and GSX was still present. There have been other occasions were this has not worked. At times it does not rebuild airport chache, wich it usually does. That doesn't explain though why the GSX menu disappears?!
-
GSX is showing - no scenery cache loading - did it manually
This is already not normal. What do you mean with "did it manually" ? The "Restart and rebuild the airport cache" option ?
-
Yes via the GSX dropdown. I thought I give that a try since I did not see it rebuild the Cache. The problem is not limited to PMDG. Had it on Aerosoft A330 as well
-
Yes via the GSX dropdown. I thought I give that a try since I did not see it rebuild the Cache. The problem is not limited to PMDG. Had it on Aerosoft A330 as well
As I've said, I cannot reproduce it in any way.
Try to wait a bit before switching airplanes, if you are on an airport that has many jetways, and GSX is still creating them when you switch airplanes, it might get stuck ( it shouldn't, we have code to prevent this, but you never know, each system is different... )
-
Folks, I don't currently have issues and have not yet installed the Feb 7th Live Update. Curious, I checked and found add-on.cfg files in two locations. The files are different in size and do not have duplicate entries.
The "addon.cfg" file in C:\ProgramData\Lockheed Martin\Prepar3D\ is 1KB and includes four(4) "Package.*" entries.
There are no references to any FSDT products in this file.
The "addon.cfg" file in C:\Users\...\AppData\Roaming\Lockheed Martin\Prepar3D v4\ is 6KB and includes twenty-six(26) "Package.*" entries.
The developer of the Lorby Add-On Organizer software explains the difference as follows: "There are two because there are two different kinds of add-on.xml "methods".
The file in \ProgramData\ contains...references to content that has been installed with the command line tools of P3D (and where the add-on.xml can be anywhere on your computer instead of \Documents\). It is only rewritten when an installer adds or removes one of those addons through the CLI.
The file in \AppData\Roaming lists those addons that are in the autodiscovery folder \Documents\Prepar3D v4 Add-ons\. It is rewritten every time something changes in that folder.
-
Tried all the suggestions here. nothing works. Just reinstalled it completely and still the same problem, if anything its worse.
As the problem cant be reproduced by the developer those of us having problems are stuffed. What we need is an option to use the previous version before all these problems started.
Why don't they put the previous version back in the live update so we can test.
Not only does it affect GSX but also any FSDT airport that you have installed so that's many products we may have paid for that we can no longer use.
Hope a solution is found soon as there clearly is a problem.
-
The "addon.cfg" file in C:\ProgramData\Lockheed Martin\Prepar3D\ is 1KB and includes four(4) "Package.*" entries. There are no references to any FSDT products in this file.
And this is strange, because the GSX installer ( NOT the Live Update ) is supposed to place the sections here, not in %APPDATA%
The file in \ProgramData\ contains...references to content that has been installed with the command line tools of P3D
Exactly, this is the way the GSX installer works: it ask P3D to add the sections themselves, only during installation. The Live Update will never, ever, touch this and none of our software is trying to access the add-on.cfg file directly. The ONLY time it's even changed, is when installing GSX with the full installer, and not directly, but by using P3D from the command line.
So, if you don't have the FSDT sections in the add-on.cfg under C:\ProgramData, it's can only be caused by one of this:
- You edited the file manually, for some reason.
- An external utility has changed that file.
- Another installer has corrupted it, because it tried to modify it directly ( we don't do that ), so the sections are missing.
- You uninstalled P3D entirely AND manually cleared all settings, by removing the %PROGRAMDATA%\Lockheed Martin and %APPDATA%\Lockheed Martin folders.
THIS will trigger the "Auto-Discovery" feature, which is when the sim finds you have an add-on.xml in the Documents\Lockheed Martin\Prepar3d V4 add-ons which is not referenced in either of the two add-on.cfg files (because you removed their folders in *addition* to uninstalling/reinstalling the sim), so it will ASK "Do you want to activate the add-on xxxx ?".
This is called Auto-Discovery and, if you reply Yes, it will re-create the missing sections for those add-ons in the %APPDATATA%\Lockheed Martin\Prepar3d V4\ADD-ONS.CFG file.
-
Why don't they put the previous version back in the live update so we can test. Not only does it affect GSX but also any FSDT airport that you have installed so that's many products we may have paid for that we can no longer use.
Hope a solution is found soon as there clearly is a problem.
That's the wrong approach to the problem. Since the update itself doesn't have any problems ( because if it did, it would affects many thousands of users, not just an handful ) and of course I already verified all correct files are online and works normally, we should understand why it doesn't work on YOUR system.
And again, I'm still fairly convinced is something related to the antivirus or similar security product ( like a firewall or anti-spyware ), which is blocking either the program itself or the Live Updater, preventing to update everything.
Or, it's blocking access to our own folders ( %PROGRAMDATA%\Virtuali and %APPDATA%\Virtuali ), which it's obviously wrong and will likely cause a crash on start ( or a failure to rebuild the airport cache ), and again, this is the fault of the antivirus.
Also, fact this happens ( to SOME users !!! ) every time we release an update to the executable, seems to confirm more and more it's caused by some external interference, antivirus/firewall/anti-spyware, etc.
The CORRECT approach of the problem, of course, would be that some affected user would contact me in private ( email or forum private message ), so we can arrange a Teamviewer session and I can see what's going on on their system. Waiting for your messages.
-
Hi Umberto,
When would it be convenient for you on a TeamViewer session to go through this?? After yesterdays flights which worked out fine from Ankara to Vienna, I opened my sim this morning, flying from UUEE to LYBE. GSX menu showed when changing airport, as soon as I changed to the AS A319 it disappeared again. As far as AV is concerned the entire SIM folder is excluded from AV plus the virtuali folder. under the APP section. I am going to add the LM folder under program data and program files plus any other Lm folders I can see to check if that makes a difference. I post back to you. Kind regards
Elmar
-
When would it be convenient for you on a TeamViewer session to go through this?? After yesterdays flights which worked out fine from Ankara to Vienna, I opened my sim this morning, flying from UUEE to LYBE. GSX menu showed when changing airport, as soon as I changed to the AS A319 it disappeared again. As far as AV is concerned the entire SIM folder is excluded from AV plus the virtuali folder. under the APP section. I am going to add the LM folder under program data and program files plus any other Lm folders I can see to check if that makes a difference. I post back to you. Kind regards
Did you also add the Add-on Manager folder to this? That might help if you haven't already done this.
-
Here is what I added:
T:\FSDT - C:\Users\ejweg\AppData\Roaming\Virtuali -- Documents/p3d addon folder - All LM folders in either program data/program files(86)/program files - C:\Users\ejweg\AppData\Roaming\Lockheed Martin - T:\P3d
C:\Users\ejweg\AppData\Local\Lockheed Martin: T:\Hifi for any active sky programs
That's just about all of them associated with my SIM.
The p3d documents/addon folder was previously not included - that may have made the difference?!
At the moment its working fine. When I completed this flight I will do another one from start and see what's happening.
Best regards Elmar
-
Here we go again:
Started SIM to default location with default plane - GSX present changed airport to EDDF GSX present - changed aircraft to Carenado - GSX is gone from the menu. Closed SIM. Restarted SIM with default location/aircraft - GSX menu present - then changed aircraft - GSX menu present - then changed airport to EDDF - no problem. Did this yesterday as well and appears that the sequence of it makes a difference.
As stated before: All SIM and their related pathways are excluded in the AV Defender scan - in fact I turned AV off all together - so AV is def. not the cause of it.
For some reason the switch seems to turn off GSX in the menu.
As stated yesterday - its an hit and miss item at the moment. I will also turn to log on in GSX to keep a file and forward next time
Kind regards Elmar
-
Have you tried what have been suggested in an earlier post, changing the Windows language to US English ?
-
We shouldnt have to change the language. It all worked pefectly before these latest updates, it s up to you to fix your program.
-
We shouldnt have to change the language. It all worked pefectly before these latest updates, it s up to you to fix your program.
It's obviously a TEST, how we are supposed to "fix" something that cannot be reproduced, other than asking to do tests to the few affected users ?
Of course, we haven't changed anything that has anything to do with language settings in the last update, and I DO NOT have my Windows set to US English so, clearly, the only possible way to even start to *begin* to understand what's going on, is by asking to TEST different things.
In addition to that, I asked several post ago for some of the affected users to contact me to have a remote assistance session but, so far, nobody has done that.
-
Umberto,
I am flying now, (and GSX again didnt work BTW). No menu appeared. All I did was to chose a plane and airport, I didnt swap anything.
Once I have finished I will willingly let you take a look remotely.
Keith
-
virtuali I am willing to remote with you and talk to you via discord if this is okay
-
Here we go again:
Started SIM to default location with default plane - GSX present changed airport to EDDF GSX present - changed aircraft to Carenado - GSX is gone from the menu. Closed SIM. Restarted SIM with default location/aircraft - GSX menu present - then changed aircraft - GSX menu present - then changed airport to EDDF - no problem. Did this yesterday as well and appears that the sequence of it makes a difference.
As stated before: All SIM and their related pathways are excluded in the AV Defender scan - in fact I turned AV off all together - so AV is def. not the cause of it.
For some reason the switch seems to turn off GSX in the menu.
As stated yesterday - its an hit and miss item at the moment. I will also turn to log on in GSX to keep a file and forward next time
Kind regards Elmar
I can reproduce the problem using the steps above.
I also have Win10 AV disabled via the registry.
Clean install of P3D & GSX/GSX2
Let me know if logs will help.
Dave.
-
I can reproduce the problem using the steps above.
Do you mean you tried exactly the same airport and the same airplane, or just any other airport/airplane combination ?
I also have Win10 AV disabled via the registry.
As explained so many times, you should NOT disable the antivirus. You should add the Addon Manager folder to the AV Exclusions, and it's probably best adding the whole simulator folder too.
-
Just had a TM session with moz2, which couldn't start GSX and, in his case, it was the antivirus ( Avast ), the Addon Manager folder wasn't added to the AV Exclusion list.
-
And after that the problem is still doing it had to restart my sim twice and its still doin it
-
And after that the problem is still doing it had to restart my sim twice and its still doin it
It was working when I was with you, that's a fact.
Your problem was just the Couatl didn't start, and it started immediately, on the first try, when I configured your antivirus correctly, and I switched airplane too, and it worked.
-
Okay the issues is when i load the fslabs a3xx couatl stops working
-
Okay the issues is when i load the fslabs a3xx couatl stops working
Already done that test, and it works fine here:
http://www.fsdreamteam.com/forum/index.php/topic,23050.msg154911.html#msg154911
-
Had no problems with any of fsdream products until I updated after the 7th Feb , now no GSX available. I know two other friends with the same issue.
Have added exception to antivirus rules and rebooted and updated fsdt products one more time. Will try P3d again in the morning and report back
-
See this post here:
http://www.fsdreamteam.com/forum/index.php/topic,23042.msg154923.html#msg154923
an user found what was causing it, and we might have a fix in the current Live Update.
-
New update 14.2.20 fixes the problem for me