FSDreamTeam forum
Products Support => GSX Support MSFS => Topic started by: disco79stu on October 09, 2023, 09:09:04 pm
-
Since the latest update (and I ran the updater several times now) on sim start GSX won't work and when I try to open the window it just briefly flashes and won't stay open (see video).
Restarting Couatl takes care of this issue, GSX then runs fine. But it doesn't start quite right...
https://www.youtube.com/watch?v=Ub_DbEbcLbI (https://www.youtube.com/watch?v=Ub_DbEbcLbI)
Edit: log attached. seems to just stop while adding facilities (whatever that is)
-
Solved it by reordering apps in the exe.xml, moving couatl to the lowest spot.
-
Belay that, the issue is back. Can‘t make sense of it tbh.
Will try to switch back to fsuip based autostart.
-
From the log which ends while it was getting Navdata data from the sim, it's possible that the sim took more than usual to reply, and if you open the menu while it's still getting the data, it won't work.
Either wait a bit more before opening the menu (and exit a session with the GSX Toolbar icon Inactive), or disable all other add-ons that have modules in the exe.xml (this is obviously for troubleshooting reasons), because one of them might be causing this and fact you seemed to have noticed a difference when changing the loading order, seems to confirm this.
-
From the log which ends while it was getting Navdata data from the sim, it's possible that the sim took more than usual to reply, and if you open the menu while it's still getting the data, it won't work.
Either wait a bit more before opening the menu (and exit a session with the GSX Toolbar icon Inactive), or disable all other add-ons that have modules in the exe.xml (this is obviously for troubleshooting reasons), because one of them might be causing this and fact you seemed to have noticed a difference when changing the loading order, seems to confirm this.
okay, thanks. I will try to play around with add ons, only strange thing is that it never was an issue before. and waiting didn't solve it either (I waited over 2min), plus I use fenix2gsx which usually responds quite quickly and do its thing. but it's not anymore, since GSX somehow doesn't start properly. so it use to work, now it doesn't. but I will keep troubleshooting. cheers.
-
It's all the same with all other add ons removed.
Log stops at
Facility add LFVX LFVX
Sim was shut down with GSX taskbar icon inactive.
-
I have exactly the same problem, only in the last few days. Uninstalled and downloaded everything again for a fresh install, problem is still there. Can restart the couatl and it works for departure, but on arrival at destination I get more error messages about the script causing it to run slow so end up restarting again. Have upgraded to 2.8.0 today and problem is still there.
-
Also the Same
-
Same problem for me as well.
-
Still having the issue.
Log appears stuck at a random airport while "adding facilities" each time (right now for example "Facility add EKRN Bornholm").
-
Just wanted to note I am also having this same problem. Just started recently, have had no issues with GXS previously.
-
Other than confirm I can't reproduce the problem in any way, it's always best to provide a log.
-
Where are the log files located?
-
Other than confirm I can't reproduce the problem in any way, it's always best to provide a log.
Here's another log, just happened again.
-
Where are the log files located?
C:\Users\youruser\AppData\Roaming\virtuali
-
Where are the log files located?
C:\Users\youruser\AppData\Roaming\virtuali
Thank You, but I have no no log files in that folder. Is there an option that has to be set in GSX first?
-
Yes, of course.
Please take a look in the manual or at least in the settings‘ troubleshooting tab, it‘s all well described and layed out for you.
-
Again, your log only shows for some reason the program got stuck while receiving Navdata which, again, I can't reproduce.
This issue might be caused by either:
- Too much traffic over Simconnect, so the request we are getting got stuck because the sim was spammed by too many add-ons requesting data.
- Having exceeded the maximum Simobject limit, which cause Simconnect to break and not returning data anymore.
Also, I noticed something strange in your log, which is the atc_id of the airplane in the airplane.cfg file:
ATC_ID read from aircraft.cfg is _
That is, is not missing, but is set to a value that is clearly wrong, as it was intentionally set like this. Before in the log, the ATC ID is like this:
ATC_ID read from Simconnect is D-HYAJ
The problem is, in a recent update, we read the ATC ID from both sources, giving preference to the aircraft.cfg file, because the ATC ID in the Configuration tab of the airplane selection menu will be the one reported by Simconnect so, if we need to find an airframe-specific GSX CFG file or recognize the airplane variant (for example in the PMDG integration), we need to know the "real" atc_id of the airframe, the one that doesn't change.
But in your case, it seems you changed it to the underscore ( _ ) character, which is not required, since the one in the airplane selection page will take precedence, but this way you are confusing GSX.
This shouldn't have any effect on your problem, which is clearly something external to GSX and affecting Simconnect at large but, it will prevent the ability to recognize your airframe.
-
hm, that is strange. I never manually modified anything in this regard, at least not that I know of. I do have some configs in the Airplanes folder for my LH-fleet so they use ULDs, but other than that I can't recall modifying anything with an editor.
D-HYAJ is a helicopter I sometimes fly (HPG H145) but I don't use GSX in those cases.
Usually, I only fly the Fenix, no other Airliner.
Is there something you would suggest to "reset" this?
-
Is there something you would suggest to "reset" this?
I think the problem is in this extra livery:
FNX320_VOLOTEAECNOS
Which seems to have set that strange atc_id for some reason. Variation liveries should always include some atc_id, so their airframe could be detected.
-
Is there something you would suggest to "reset" this?
I think the problem is in this extra livery:
FNX320_VOLOTEAECNOS
Which seems to have set that strange atc_id for some reason. Variation liveries should always include some atc_id, so their airframe could be detected.
okay, thanks, I'll pass this on to the creator(s) of those liveries (VA-internal) as it seems to be the case for all of their liveries.
-
so I corrected the aircraft.cfg and created a new log.
happened again @LEPA just now.
please see another fresh log attached.
-
... and here's a log from when I then restart Couatl (thus making GSX work perfectly normal again). maybe this helps, idk.
-
Again, your log only shows for some reason the program got stuck while receiving Navdata which, again, I can't reproduce.
-
Again, your log only shows for some reason the program got stuck while receiving Navdata which, again, I can't reproduce.
ok. thanks for taking a look at it.
I removed it from exe.xml and let it start via fsuipc, which doesn't produce the error.
-
Hi,
I'm now getting the same issue on my end. Open up the menu and it immediately closes.
Looking to see if this is a one time fluke.
UPDATE: A reload of MS2020 has corrected the issue.
-
Hello,
Same issue for me after installing the last update. I have to restart couatl manually. I used before to start MSFS and couatl in administrator mode, but the issue is still there, being this mode unabled or not.
I noticed that this issue occurs mainly when the PMDG 737 is launched first. And that GSX is correctly launched after I come back to the main menu and select another aircraft like the Fenix.
So, something has changed since the last update (I'm not saying that GSX is the main culprit...), as some users are reporting here. Btw, il's not a great deal having to restart couatl manually.
Daniel.
-
In my case, it depends on which aircraft I'm in. It works fine for Fenix and FBW A320ies but Horizon/LatinVFR A319 has the above mentioned issue. The error message reads:
Using aircraft data from aircraft.cfg file
Airframe-specific GSX.CFG file for N822UA not found in C:\FS20\Community\zLVFR-A319-FBW-Compatibility\SimObjects\Airplanes\A319ceoIAE, using a default GSX.CFG file
Airframe-specific GSX.CFG file for N822UA not found in C:\Users\...\AppData\Roaming\Virtuali/Airplanes\A319ceoIAE, using a default GSX.CFG file
and then loads a really long list of airports (I parked in KPHL).
What's the issue with the default GSX.CFG file? Are there specific a/c cfg files required for GSX?
Thanks,
chris
-
In my case it's only with the Fenix and I don't get any cfg errors in the log, just stops loading the data.
Again, when I let Couatl autostart through fsuipc, not the exe.xml, I don't get the issue at all.
-
In my case, it depends on which aircraft I'm in. It works fine for Fenix and FBW A320ies but Horizon/LatinVFR A319 has the above mentioned issue. The error message reads
What makes you think that is an error message?
It's just reporting that, since you haven't made an airframe-specific airplane profile, it will use the default one, that's it. It is what it will say in most of the cases, and it's there just to provide some help in case you TRIED to create an airframe-specific profile, but for some reason it doesn't seem to work, so those lines are there to help you if it recognized the file.
Don't try to interpret the log and, instead, always provide the actual file (ZIPPED and ATTACHED to a post), so we can check it.
-
Hi,
I have the same problem. The GSX Window disappears immediatly. Even if I restart couatl.
Here is my err file.
Thanks
-
I have the same problem. The GSX Window disappears immediatly. Even if I restart couatl.
You posted an .ERR log dated Oct. 22nd so, if you enabled logging, the .ERR file is not used anymore, and the file used is the Couatl.LOG instead, so you should post that one, because from the .ERR file, I could see you were using an outdated version, but I can't see if it's still outdated now, without checking the file that is being used now.
-
Thanks for your answer.
I got no .log file and I can't open gsx.
-
I got no .log file and I can't open gsx.
https://www.fsdreamteam.com/forum/index.php/board,73.0.html
-
Hi,
Here is the log file.
Thanks.
-
The same issue here
Follows log file
-
New rig, windows 11, msfs and gsx pro clean install. Same thing happening to me, we need a solution for this please.
-
rebooted pc and it worked
-
This is what fixes it for me every time.
%APPDATA%\Virtuali\Couatl_MSFS.ini file if it shows:
logFile=Couatl.log
useAirportCache=0
I just remove useAirportCache=0 then save and GSX works again.
I have to check the file every time before starting flightsim to make sure GSX works which is kind of annoying.
-
This is what fixes it for me every time
The useAirportCache=0 line is not the problem, because this is how it's supposed to be, this is how it is by default, and it won't make any difference even if the line is not there in the first place.
I think the real issue that is making you *think* editing the file has fixed this for you, is the other line, the logfile line. Since there's no path, the log file will be created in the current working folder for the Couatl engine. But the current working folder might change if you have the Couatl engine started automatically by the sim (normal case) or if you start it manually, so it might be better to set a path for it, so it will never change.
However, since you not always need log, and the airportCache is disabled by default, you might just remove the Couatl_MSFS.INI file.
-
And this Flashing/open/Close problem seems to continue day after day - weeks after weeks and no fix. I'm start to be very frusrated. Yestarday everything works like charm and today not although I tryed to start Couatl from my Taskbar many times. Flash and disappeared. Oddiest thing is GSX works very well many month after it's published. All updates what You provided to us works well, too buty now we are sunk into swamp of the some kind darkness.
I dont't see any sense to start and re-start sim all time that I can mayby get a some programs working. It's Your job to fix it. Mayby You are put a one bit's a little bit awry.
I tryed a clean intall GSX (as a few other person here, too) without help. I have not time to sit all day behind my screen and try GSX working.
Yestarday GSX works - nothing than day changed 5.11 to 6.11 Sunday to Monday and today no joy... >:(
-
And this Flashing/open/Close problem seems to continue day after day - weeks after weeks and no fix.
Of course, it doesn't happen here, and it doesn't happen to most users.
One user I helped on Discord who had this problem, made the mistake of manually copying the whole fsdreamteam-gsx packages to its Community folder, and this caused the issue, because the simulator used the manually copied folders, while the FSDT Updater and the GSX code only works on the Addon Manager copy, relying on the fact it's LINKED to the Community folder, which is how we install it.
As soon the user removed the manually copied folders he made, and RELINK in the FSDT Installer, the problem was fixed.
-
Yes - could be that but I'm not moving or copying anything anywhere. All packages are there where they always are been as I bought and installed GSX Pro August 2022. All works ok many month but after 2 or 3 updates ago the problems started and continue way as i told to You.
I use Addon Manager airports and Libraries only. GSX is it default folder and it's here since August 2022.
Well - I don't really understand about why someone is manually moved anything - what's the point?
-
Yes - could be that but I'm not moving or copying anything anywhere.
I just reported what happened to another user, and in that case, it was expected to cause that. I cannot possibly be sure if that's your case.
Well - I don't really understand about why someone is manually moved anything - what's the point?
A possible reason might be having the Community folder on an external USB drive not formatted in NTFS, which doesn't support Symbolic link so, the user might have decided to copy the folders there manually, to get around that limitation, which wouldn't work, since the GSX code expect all its files to be in the Addon Manager folder.
If that's not your case (but please, check *again* if your gsx packages in the Community folder are real folders or Shortcuts. They *must* be Shortcuts ), please provide your log according to these instructions:
https://www.fsdreamteam.com/forum/index.php/topic,26924.0.html
-
Community folder is fsdreamteam-gsx-pro Shortcuts.
Here is 2 zip.file -> Coutatl + exe
-
I don't see anything in your log which suggests the menu didn't open. You made several different operations in GSX, so the menu must have worked. Could you please clarify exactly at which step it stopped to work, assuming this is what happened ?
-
Hi
One flight, it woks, one flight it doesn't.
Today, it didn't.
I click on Gsx, the window is open less than 1 second.
Here is the log.
Thanks
-
Today, it didn't. I click on Gsx, the window is open less than 1 second.Here is the log.
Your log shows the simulator just closed before you did anything. Note that, from GSX point of view, the simulator "closed" might just mean it "closed communications", which can be caused by having reached the maximum number of objects in the sim or by too many addons connecting to it. But of course it might just be it really closed.
-
Thank you for your answer.
What can I do to have less object ?
-
What can I do to have less object ?
Most likely, you have too high AI settings, coupled with a too dense airport, so you surpassed the maximum limit of objects in a scene (officially documented as 1000), after which Simconnect no longer responds correctly to commands, causing all sort of malfunctions.
The easiest way to reach the limit is to use AI traffic, especially with AI Injection. But it IS possible to reach it even without it, if the airport is detailed enough.
What you CAN do from GSX to mitigate the problem ( not fixing it, only Asobo can really fix it, by allowing more than 1000 Simobject in a scene ), is:
- Disable the "Ground Clutter" option in GSX. This will only be effective for default airports that had their jetways replaced by GSX.
- Lower the Passenger Density slider in GSX. This will reduce the number of passengers visible at any given time, which will affect the overall number of Simobjects in a scene.
But the most effective way to deal with the Simobject limit, is reducing the AI Density. If the AI traffic product has an option to disable Ground Services for AI, that's the most effective way, because each AI could generate extra 5-6 objects as ground services so, 100 AI airplanes could add 500-600 Simbojects and, if you add the airport objects, and the Jetways, it's very easy to surpass the max Simobject limit.
-
I don't see anything in your log which suggests the menu didn't open. You made several different operations in GSX, so the menu must have worked. Could you please clarify exactly at which step it stopped to work, assuming this is what happened ?
1. To do a Flightplan using SimBrief.
2. Import the Flightplan to Navigraph Chart addon.
3. Check the Flightplan that everything is as it should be.
4. Start Flight Simulator 2020 (Steam version) via desktop shortcut.
5 Hoping best that GSX Pro works at this time (a small prayer somewhere upside)
6. After Sim is started I select an airport I want to leave to according my flightplan
7. Push Fly Now and wait as the airport is loaded.
8. After that if everything is gone ok now I can see a GSX Pro Menu open and I know I can continue my started flight
9. I load a real time and real weather + AI Traffick.
10. But if the GSX Menu not open I try to start a Couatl manually - wait a little bit and try again until I understand that this not work today and take heading to the GSX forum to crying my destiny with this randomly working addon..
This is about what I do in general. Today I got GSX to working as I re-started sim at once.
-
What can I do to have less object ?
But the most effective way to deal with the Simobject limit, is reducing the AI Density. If the AI traffic product has an option to disable Ground Services for AI, that's the most effective way, because each AI could generate extra 5-6 objects as ground services so, 100 AI airplanes could add 500-600 Simbojects and, if you add the airport objects, and the Jetways, it's very easy to surpass the max Simobject limit.
Thank you for your answer but what is surprising is that I fly whithout trafic.
-
Umberto,
Something strange. In my \AppData\Roaming\virtuali folder.
I found couatl.bak
I never touched this file.
I renamed it to couatl.exe and my GSX started working fine again.
Is it possible one of the upgrades this file got renamed but never switched back by accident?
-
I have the same issue....
I am no programmer, so most of what is in the log file might as well be in Martian!! ;)
-
I found couatl.bak
I never touched this file.
I renamed it to couatl.exe and my GSX started working fine again[/quote]
Our installer not only will never put that file that, but it will never use it to backup it so no, you can be sure it wasn't an update or the installer. Either you renamed it and forgot about it, or some other interfering software, like an antivirus did.
However, that's not really the point.
The point is it shouldn't have made any difference, because no .exe is supposed to start from there and that's not how the EXE.XML in the sim is configured to start it from, because the .EXE that is being started by the EXE.XML is in \Addon Manager\Couatl64\Couatl64_MSFS.EXE.
Also, while you don't say anything about this file other than its name (knowing the length would be useful), fact it's named just "couatl" and not Couatl64_MSFS.EXE which is the one and only version that could possibly work with MSFS (Couatl.exe is the 32-bit FSX version and it's also not started from there), seems to indicate you must have renamed the couatl.LOG or the couatl.ERR files, and that would explain why it had a .BAK extension: you probably opened it with a text editor, which made a .BAK copy when you saved it back, which is quite common
So, if you really renamed it to .EXE what is essentially a text file (the backup copy of the log), you really haven't changed anything, since nowhere we use that folder to start the program, and the fact "GSX started to work" was just a coincidence.
-
I have the same issue....
I am no programmer, so most of what is in the log file might as well be in Martian!! ;)
OK.... I posted this in November.... well over a month ago, and I STILL haven't heard anything back... All I want is some help to get it working properly. I would like to use it.
-
Had this again today and I have just completed a full re-install of MSFS and all addons including GSX.
Loaded into Gate 6 at Manchester EGCC in Fenix A320 using this profile: https://flightsim.to/file/38303/gsx-profile-egcc-manchester-maccosim
It's not repeatedly reproducible, but I killed Couatl and then started via the shortcut "Start Couatl for GSX MSFS", pressed the GSX button in-game and the menu was working again.
I will fish for logs next time it happens
-
I had this again today at KORD. Haven't had the issue on the last three or four flights.
Loaded into FSDT's KORD at the gate. Pressed CTRL-SHIFT-F12 to bring up the GSX menu. Nothing happened. Checked the menu bar and noticed that the GSX menu was not lite up. Click on that. Menu appeared the disappeared quickly. Tried again - Same. tried again with CTRL-SHIFT-F12. Same.
Exited the simulator. I've attached the LOG file from. There was NO AI running so can't imagaine it was a sim objects issue and this is at FSDT's own KORD.
I hope this gets fixed - its very frustrating.
-
Exactly the same problem for me ever since SU14. Have run Live Update a number of times.
Richard
-
Exited the simulator. I've attached the LOG file from. There was NO AI running so can't imagaine it was a sim objects issue and this is at FSDT's own KORD.
Your log doesn't show any errors, and it doesn't show you ever tried opening the menu, but it shows you closed the sim and GSX closed normally after normally receiving your close command so, according to the log, everything is normal.
Are you SURE your GSX is installed in the Addon Manager folder and only LINKED to the Community folder, and you haven't done things like moving the Community folder after installing GSX or manually copying GSX instead of Relinking? Maybe a while ago? Check the two GSX packages in the GSX Community folder: they must be Symbolic links, not real folders, which means they should show a small arrow on their icon.
If you don't have the arrows, it means they are real folders, remove them and then "Relink" with the FSDT Installer.
-
I have the same issue....
I am no programmer, so most of what is in the log file might as well be in Martian!! ;)
OK.... I posted this in November.... well over a month ago, and I STILL haven't heard anything back... All I want is some help to get it working properly. I would like to use it.
This is the 3rd time I am trying to get some help on this!! :(
AGAIN... my log is attached.
-
Exited the simulator. I've attached the LOG file from. There was NO AI running so can't imagaine it was a sim objects issue and this is at FSDT's own KORD.
Your log doesn't show any errors, and it doesn't show you ever tried opening the menu, but it shows you closed the sim and GSX closed normally after normally receiving your close command so, according to the log, everything is normal.
Are you SURE your GSX is installed in the Addon Manager folder and only LINKED to the Community folder, and you haven't done things like moving the Community folder after installing GSX or manually copying GSX instead of Relinking? Maybe a while ago? Check the two GSX packages in the GSX Community folder: they must be Symbolic links, not real folders, which means they should show a small arrow on their icon.
If you don't have the arrows, it means they are real folders, remove them and then "Relink" with the FSDT Installer.
Hey mate - Addon Manager is installed and linked to the Community Folder. I haven't made any changes to my community folder or even opened MSFS_Addon Linker in weeks.
(https://i.imgur.com/cvHDUUd.jpg)
After the incident above I exited the SIM and went back in and it worked no problems.
Today, I just started the sim up, loaded into KMIA in the PMDG 737 and now getting the same flashing and disappearing menu. Makes no sense. Sometimes it works sometimes it doesn't.
EDIT - Whilst sitting in the sim at KMIA, I've just manually closed COUATL from the menu tray, waited 10 seconds and then manually started it using the desktop icon and am now getting the menu up. It took about 10 seconds for the menu to bring up the options but the GSX menu is appearing again.
Still confused.
-
I have the same issue....
I am no programmer, so most of what is in the log file might as well be in Martian!! ;)
OK.... I posted this in November.... well over a month ago, and I STILL haven't heard anything back... All I want is some help to get it working properly. I would like to use it.
This is the 3rd time I am trying to get some help on this!! :(
AGAIN... my log is attached.
Would you believe it is all of a sudden working again???
-
I have had the "flashing" issue off and on for months. It comes and goes but appears to be consistent now. Attached is what I think is the error file.
-
Unfortunately this issue seems to be getting worse! After the latest round of release, sometimes at the destination airport, I have to restart the app several times until it works! Every time it tries to put the objects in the parking spot but then they disappear...
-
Agreed.
Between this issue, and the other one I'm getting more and more frequently which is the GSX MAIN MENU LOADING spinning wheel... its getting a little annoying. I generally find that exiting COUTAL from the system tray and then re-running it from the desktop icon works...but its a pain in the arse.
-
Last night even that wasn't working for me! I had to restart it 3 times ...
-
add me to the list of having the gsx window quickly flash open then close. Any plane I choose and at any airport.
-
I have had the "flashing" issue off and on for months. It comes and goes but appears to be consistent now. Attached is what I think is the error file.
Enable logging in the Troubleshooting section of the GSX Settings page, because the panic log is not detailed enough to know what is your issue. If you can't start GSX in any way, see the manual at Page 34, which explains how to enable logging when GSX can't even start.
Then, post your Couatl.LOG file (not the .err file) instead.
To everybody else saying "I have the same issue", we can't neither confirm you *really* have the "same" issue, nor we can help you, UNLESS you Attach the Couatl.LOG to your message.
-
Still happening to me (again) after new PC, new OS, new Sim installation.
Only an issue when couatl starts through the exe.xml.
Switched back to FSUIPC autostart, no problemo.
-
Only an issue when couatl starts through the exe.xml.
Switched back to FSUIPC autostart, no problem.
Have you possibly changed the properties for the Couatl64_msfs.exe to always run "As Admin" (not how we install by default) ? This is surely causing not to autostart, because the sim won't autostart something that runs with admin permissions.
-
Only an issue when couatl starts through the exe.xml.
Switched back to FSUIPC autostart, no problem.
Have you possibly changed the properties for the Couatl64_msfs.exe to always run "As Admin" (not how we install by default) ? This is surely causing not to autostart, because the sim won't autostart something that runs with admin permissions.
No, I haven't changed anything in this regard. Also worth to mention, I don't think it's acutally really "failing" to start through the exe.xml, it DOES start, couatl is indeed running in the sys-tray... it's just not working properly in 5 out of 10 times (GSX window closes instantly when opening it, nothing will spawn/move, only manually restarting couatl solves it).
-
Only an issue when couatl starts through the exe.xml.
Switched back to FSUIPC autostart, no problem.
Have you possibly changed the properties for the Couatl64_msfs.exe to always run "As Admin" (not how we install by default) ? This is surely causing not to autostart, because the sim won't autostart something that runs with admin permissions.
No, I haven't changed anything in this regard. Also worth to mention, I don't think it's acutally really "failing" to start through the exe.xml, it DOES start, couatl is indeed running in the sys-tray... it's just not working properly in 5 out of 10 times (GSX window closes instantly when opening it, nothing will spawn/move, only manually restarting couatl solves it).
Same behavior for me. COUATL starts fine and runs in the system tray (not running as admin - never touched any GSX properties), its just that half the time the menu flashes and then disappears. Exiting COUATL from the system tray open and then running it from the desktop icon usually solves the problem. Interestingly though, if I don't EXIT COUATL from the system tray, but rather choose the RESTART option, it continues to not function.
-
Ok - lets try again. I start sim and select an airport and gate on the World Map and after that I push Fly button and wait as sim is loaded. Sometimes GSX Menu appeares but mostly not. If not I must go back to Welcome screen and then to World Map to select the same airport and gate and after that GSX works as it should be.
I have MSFS 2020 Steam version, Windows 11. Community & Official folders are moved to C:\MSFS folder. Couatl is not set run as admin.
Here is log
-
Here is log
+
Your log doesn't show any errors, it shows you enter the sim and exited. Or, the simulator just disconnected, which from GSX's point of view is exactly the same as you exited from the simulator.
If the sim is still running, but it disconnected, it might be caused by having reached the maximum Simobject limit, that's why you think GSX "randomly" works or not, because it's not as if you always exceed the limit but, if it happens, the whole Simconnect interface breaks apart and stops accepting commands.
-
Hi Umberto,
It appears that's what the log has shown a number of times - I'm just describing what behavior is being exhibited in the sim. I can keep attaching logs but based on what you've said they seem to show the same behaviour.
I don't believe its a sim object limit as some of the airports I'm seeing the issue occur at are small and without AI Traffic.
I hope the issue can be found. Its a little frustrating.
-
I'm just describing what behavior is being exhibited in the sim.
The issue is, the log should have recorded you opening the menu and eventually the menu closing down with a choice, a timeout or even not closing down. Instead, is not even registering, you tried to open the menu in the first place.
And that is precisely why I'm quite sure your issue is related to Simconnect communication because, in order for GSX to register you opened the Toolbar menu, it requires GSX being able to read some variables set by the menu code, and they are read using standard Simconnect calls, so I can't see any reason, other than a problem with Simconnect itself for not being able to communicate.
It's not as if GSX is crashing it's just prevented from communicating with the sim or, at least, the part related to reading the variable the menu surely sets.
I don't believe its a sim object limit as some of the airports I'm seeing the issue occur at are small and without AI Traffic.
That's just the most common case, and the airport you are in doesn't really matter, because ALL AI counts towards the limit, that includes the ones in the "AI reality bubble", which is about 30 nm around the airport so, you might still have lots of AI counting towards the max Simobject limit, as long there's a busy airport close enough.
But again, the max Simobject limit is not the only reason why the communication might have stopped, another possible cause is another add-on sending too many commands through Simconnect that MSFS can't keep up with all of them so, a first test might be disabling every addon that is using Simconnect and leave GSX only, to verify this theory.
-
For me this happens at multiple airports with AI traffic turned off, and only a restart of Couatl fixes it. I will try to attach a log when it happens again if it cannot be reproduced on your side
-
only a restart of Couatl fixes it. I will try to attach a log when it happens again if it cannot be reproduced on your side
It's important the log is take before a restart, since it might include important data about the problem.