FSDreamTeam forum
Products Support => GSX Support MSFS => Topic started by: StephanG2312 on October 03, 2022, 05:43:49 pm
-
Hi,
since approx. 2 weeks, from one day to another, I experience that the GSX menu after starting a flight keeps on loading, no matter what aircraft, at which airport and also if I haven't changed anything within the sceneries. Before I haven't had this issue. The only way solving this problem is restarting the couatl and then wait for approx. another minute, then the menu entries are appearing. From there, everything works fine. As this is very annoying I would be happy for any kind of assistance. I used already the offline installer, so I am already on Oct 3rd version, but still the same.
Thanks & Brgds
Stephan
-
It's entirely normal that, after you did an FSDT update or you installed/removed a scenery, that airport cache will require to be rebuilt, it can take a minute or so, and until it's completed, you can't use GSX.
It's not normal it's happening every time, unless you purposely change the scenery configuration before each flight, for example using the Addon Linker to enable/disable only certain airports before each flight. By doing that, you are forcing the airport cache to be rebuilt at every start, so you'll always have to wait.
-
It's entirely normal that, after you did an FSDT update or you installed/removed a scenery, that airport cache will require to be rebuilt, it can take a minute or so, and until it's completed, you can't use GSX.
It's not normal it's happening every time, unless you purposely change the scenery configuration before each flight, for example using the Addon Linker to enable/disable only certain airports before each flight. By doing that, you are forcing the airport cache to be rebuilt at every start, so you'll always have to wait.
Dear Umberto,
well understood and noted, but as said, it happens every time. If I hold the cursor over the couatl icon, I read "Airport cache loaded succesfully" but the loading wheel in GSX is continueing spinning (until I restart couatl as described).
Brgds
Stephan
-
If I hold the cursor over the couatl icon, I read "Airport cache loaded succesfully" but the loading wheel in GSX is continueing spinning (until I restart couatl as described).
The cache regeneration process runs in a separate thread, so it's not always sure "just" because the tooltip said so, the cache is really ready.
As I've said, it should normally happen only after you run the FSDT Updater, or if you change the scenery configuration ( add/remove/enable/disable a scenery ), subsequent restarts will use the existing cache.
-
Dear Umberto,
and as I've said, it happens every time. E.g. I just completed some minutes ago a flight in which GSX worked fine (after restarting the couatl). I returned to main menu, created another flight at a different airport and after starting the flight, guess what? Yes, the loading wheel is spinning. If I do nothing, it continues spinning forever. Between both flights, I didn't even leave MSFS. I hope you trust me now that it is correct what I am describing and that I understand well that the cache needs to be rebuilt IF any changes within the sceneries are made as I understand what GSX normally does. But obviously there is something not normal with my installation.
-
So what next steps do you suggest, Umberto? Might a complete reinstall help? I'm sure you understand that the current behaviour of GSX is not acceptable on a permanent basis.
-
I hope you trust me now that it is correct what I am describing and that I understand well that the cache needs to be rebuilt IF any changes within the sceneries are made as I understand what GSX normally does. But obviously there is something not normal with my installation.
It's entirely normal Couatl would restart when returning from the main menu, because this has been found to be the most reliable way to be sure every object created with the previous session would be removed for the next one.
What is not normal, is the cache is being regenerated at each start because, from GSX point of view, it should only happen if the previous cache regeneration failed for some reason, but if it did, it would show in your log, but it doesn't.
So, the only possible explanation is that, for some reason, something in the simulator community folder is changing AS IF you enabled/disabled/added/removed a scenery, triggering a cache rebuild.
Nobody ever reported this problem happening this way ( regeneration each time with no errors ) so, it clearly must be something very unique to your installation that plays with files/folders, since GSX checks a folder last modification date to know if changes have happened, perhaps something like an antivirus that doesn't do anything other than changing that data, just to flag it has checked that folder.
However, I don't think it's really worth investigating further, because when we'll release the SU10 Navdata upgrade, which will allow to use GSX on any airports, including the encrypted ones from the Marketplace, the other major benefit is that it won't even use an airport cache anymore, because it will take airport data from Simconnect without having to open the airport file.
-
I have no idea what could change my community folder every time. Never heard of that. I meanwhile deactivated GSX and reinstalled, but no result.
I found out that GSX creates every time I start a flight a panic log. Shall I post the content here (if yes, completely or just the error part?)?
-
I found out that GSX creates every time I start a flight a panic log. Shall I post the content here (if yes, completely or just the error part?)?
You posted a log, meaning you had logging enabled, and your log didn't show any error. Do you mean if you disable logging, instead of the complete log, you get the automatic panic log instead ?
If that log only contains issues related to Simconnect exceptions, don't worry, they are just Simconnect bugs that won't affect the airport cache issue in any way. If you see other errors, then please re-enable the full diagnostic log, because the panic log is usually not detailed enough.
-
Neither I had logging enabled yet nor did I post a log anywhere. ???
I will enable logging for the next flight.
Here's the extract from the panic log, which is always created when starting a new flight:
couatl v4.8 (build 5027)
panic log started on Fri Oct 7 18:30:31 2022
problem raised by engine or unspecified addon
{}
Simulator version (from MAIN.DLL) is 11.0.282174.999
isPBRAvailable returned False
isRTTAvailable returned False
GetSimObjectsFolder() returned E:\Program Files (x86)\Addon Manager/MSFS/fsdreamteam-gsx-pro/SimObjects
GetAdditionalSimObjectsFolder() returned E:\Program Files (x86)\Addon Manager/MSFS/fsdreamteam-gsx-world-of-jetways/SimObjects
GetAdditionalSimObjectsFolderV5() returned
gateDistanceThreshold = 20
Error: exception UNRECOGNIZED_ID in call SetDataOnSimObject param #2 '-214248176'
{}
Error: exception UNRECOGNIZED_ID in call SetDataOnSimObject param #2 '-214246832'
{}
GSX SimStart
GSX SimStop
-
Attached you find the log of last flight.
-
Attached you find the log of last flight.
Your log shows some issues indicating several problems in your Community folder: some packages can't be accessed for some reason, and you have two copies of Aerosoft EBBR, both inaccessible.
Note sure if this could cause that problem with the menu, but if you have access or other permission issues with the Community folder, it might.
-
I deleted the relevant folders from the log inside the community folder as all were empty (your Basel scenery I had to relink). Now no more entries in the new log but it's still the same behaviour of the menu. Let's see if the next bigger update you mentioned will solve the issue.
-
Unfortunately the latest update has not improved my situation. I have to restart Couatl everytime before I can access GSX menu. What is new now (and for sure not an improvement) that couatl seems to crash during flight. When I open GSX again after arrival at destination airport I see again the spinning wheel, but couatl is gone in the windows app tray down right. After starting couatl again, the menu appears. Would really like to know what is wrong with my installation as I get a little frustrated meanwhile! :-[
Log is after starting again couatl at destination airport.
-
After starting couatl again, the menu appears. Would really like to know what is wrong with my installation as I get a little frustrated meanwhile!
That's not a problem with your installation, there seems to be a problem when using the SU10 Navdata API that results in a crash while flying through over various airports.
Until we'll understand more, just restart Couatl before or soon after landing, it has been designed to be used that way.
-
But if SU10 Navdata API doesn't change my situation (that I have to restart couatl at origin airport before I can access the menu), why should I use it? With all necessary respect, but what should I think about a developer who tells me I have to interrupt my flight everytime to restart something to make a software work? Sorry, this is not acceptable. I guess it's better that I pause using GSX until it is no more beta!
-
But if SU10 Navdata API doesn't change my situation (that I have to restart couatl at origin airport before I can access the menu), why should I use it?
Please clarify: are you having this problem regardless of the SU10 Navdata being used or not ?
With all necessary respect, but what should I think about a developer who tells me I have to interrupt my flight everytime to restart something to make a software work?
Why you think you have to interrupt your flight ? You can restart at any time, without the slightest effect on the flight.
We made the Couatl engine be started and restarted because we assumed most user would *want* to quit it intentionally after takeoff, to save even the tiniest bit of performance, since it's clearly not required in flight, and they would restart it before or shortly after landing.
Sorry, this is not acceptable. I guess it's better that I pause using GSX until it is no more beta!
I'm not sure what you are trying to say here: nobody said it will remain like this. I clearly said Until we'll understand more, does it sound a "definitive" solution to you ?
Using the Navdata API IS clearly advertised as a Beta, which is why by default is disabled. But if you are getting the same problem regardless if you use it or not, than perhaps YOUR problem is DIFFERENT, and it's not really related to the Navdata API.
But it wasn't really clear from your message. Please confirm you are getting *exactly* the same problem, that is the Couatl engine disappearing during the flight, even with the Navdata DISABLED.
-
Please clarify: are you having this problem regardless of the SU10 Navdata being used or not ?
Yes, exactly.
Why you think you have to interrupt your flight ? You can restart at any time, without the slightest effect on the flight.
Ok, interrupting not in the meaning that I have to pause MSFS, but I have to keep it in mind every flight. If I forget, it takes me again time to start Couatl and wait for the menu to appear after arrival at the gate which compromises my flightsim experience. If you deem that as neglectebale, your opinion.
I'm not sure what you are trying to say here: nobody said it will remain like this. I clearly said Until we'll understand more, does it sound a "definitive" solution to you ? Using the Navdata API IS clearly advertised as a Beta, which is why by default is disabled. But if you are getting the same problem regardless if you use it or not, than perhaps YOUR problem is DIFFERENT, and it's not really related to the Navdata API.
Didn't say that. Couatl does not disappear during flight if SU10 API is disabled. But once again, this is not my prior problem but the problem with the menu at start of flight.
-
If I forget, it takes me again time to start Couatl and wait for the menu to appear after arrival at the gate which compromises my flightsim experience. If you deem that as neglectebale, your opinion.
You only have to "wait" a few seconds to restart it, especially if you use the Navdata API so yes, it is neglectable in my opinion. In fact, it was the way we assumed most users would use GSX anyway.
Didn't say that. Couatl does not disappear during flight if SU10 API is disabled. But once again, this is not my prior problem but the problem with the menu at start of flight.
We are finally getting there. So no, you don't have the same issue depending if Navdata is enabled or not, which at least is consistent and something to work on. However, it is always fixed by restarting Couatl ?
P.S.
Please try to quote in a sane way, the way I edited your post, and don't use colors.
-
You only have to "wait" a few seconds to restart it, especially if you use the Navdata API so yes, it is neglectable in my opinion. In fact, it was the way we assumed most users would use GSX anyway.
And that's exactly the issue: Not in my case! I have to wait until I restarted Couatl at least once after I started it again shortly before or after landing to get the menu to work. Same behaviour as after starting the flight.
We are finally getting there. So no, you don't have the same issue depending if Navdata is enabled or not, which at least is consistent and something to work on. However, it is always fixed by restarting Couatl ?
Yes. Sometimes it needs 2 restarts, but mostly it works after the first one, but never initially.
So the big question is very simple: What hampers the menu to appear after the start of the software?
-
And that's exactly the issue: Not in my case!
Please note my sentence: You only have to "wait" a few seconds to restart it, especially if you use the Navdata API. Do you mean in your case it always takes much longer, even if you DO use the Navdata ?
Because, NOT using the Navdata API will surely result in a slower start, because it will need to load the airport cache and check for any possible changes to decide if it requires being regenerated, and this might take longer, depending how many sceneries you have installed.
And, in this case, if you try to Restart *before* the airport cache has been loaded, it might let you think you need a 2nd restart, when in fact you only had to wait a bit longer. And no, since the airport cache is loaded in a separate thread, it's not always certain the cache is really ready just because the tooltip over the Couatl icon says so, the reasons are complex to explain and are related to how the tray bar notification are works, but it's the way it is.
However, when you DO use the Navdata API, the startup shouldn't take more than a few seconds, since no Community folder is read, no airport cache is used, it just starts and connects to the sim, waiting for Simconnect to reply with the data about the airport.
-
Yes, exactly, that's what I try to explain. It takes much longer after initial start when starting a flight as well as after starting it again when the flight comes to an end. No matter if Navdata is enabled or not.
-
It takes much longer after initial start when starting a flight as well as after starting it again when the flight comes to an end. No matter if Navdata is enabled or not.
"No matter" you mean it takes exactly the SAME (long), regardless if Navdata is enabled or not ? You should at least see some difference.
If yes, the only thing I can think of that can slow down the Navdata, is Simconnect too swamped by too many connections ( AI traffic injectors, for example, but not only those ), that it doesn't have enough time to talk with everybody, so it returns data with some delay.
And of course, the usual suggestion of being sure the whole Addon Manager folder is added to the antivirus Exclusion is always valid.
-
The menu never starts initially. I can wait for an hour (believe me, I tried it), nothing happens until I restart Couatl at least once.
-
The menu never starts initially. I can wait for an hour (believe me, I tried it), nothing happens until I restart Couatl at least once.
Do you mean:
- Couatl starts together with the sim, but it doesn't load the menu until you Restart it manually
OR
- Couatl doesn't start with the sim
-
Option 1 is the case. It starts with the sim but the menu doesn't load until restart.
-
Option 1 is the case. It starts with the sim but the menu doesn't load until restart.
Then I'm afraid to be out of explanations because, right now, you are the only one with this particular problem that, if I understood correctly again is:
Regardless of using Navdata or not, even if Couatl starts normally, you don't see the GSX menu until you restart it at least once AND, in addition to that, it doesn't take the normal few seconds to start, but an unspecified longer amount of time, every time, even when it works.
Is this last description of the problem accurate ? If yes, nobody has ever reported it exactly this way before.
-
Then I'm afraid to be out of explanations because, right now, you are the only one with this particular problem that, if I understood correctly again is:
Regardless of using Navdata or not, even if Couatl starts normally, you don't see the GSX menu until you restart it at least once AND, in addition to that, it doesn't take the normal few seconds to start, but an unspecified longer amount of time, every time, even when it works.
Is this last description of the problem accurate ? If yes, nobody has ever reported it exactly this way before.
Yes, unfortunately it describes the problem correctly.
-
I meanwhile found out that if I prevent that Couatl is started by MSFS but when I start it manually, the menu appears with the initial start, no restart of Couatl necessary. It might also make a difference if I start MSFS with admin rights or without. Have to make some more tries to confirm that.