This is something else I have noticed today. The term start date seems to get changed every time the gate gets used (or I assume, the only ones that are not changed to the last few days are the four that are stuck in use, and another in LHR that may not have been used for a while as I was switching flights from there around). I'm not sure if this will help with the bug, but I just thought I'd point this out.
I have included the information from my YYZ and LAX gate information below.
YYZ:
254 In use () Dedicated Jul 17 2017 Jun 16 2018
964 In use (PAYYZ3) Dedicated Sep 12 2017 Jul 13 2018
4 In use () Dedicated Jul 13 2017 Jul 15 2018
1058 Available Dedicated Sep 12 2017 Jul 18 2018
1187 In use (PAYYZ1) Dedicated Sep 12 2017 Jul 22 2018
1407 Available Dedicated Sep 12 2017 Jul 30 2018
LAX:
226 In use (PAHND2) Dedicated Sep 12 2017 Jun 15 2018
788 In use () Dedicated Jul 13 2017 Jun 30 2018
926 Available Dedicated Sep 12 2017 Jul 11 2018
1059 In use () Dedicated Jul 31 2017 Jul 18 2018
1185 In use (PALAX1) Dedicated Sep 11 2017 Jul 22 2018
One more thing that I have noticed tonight. I got this issue with ATL today. I only have two planes flying out of there right now, both are on the ground but one leaves tomorrow at noon, the other tomorrow at 6pm. It seems that the gate stays in use from the time the plane lands until it departs again. In my case, I got the error even though the plane that landed first is going to be idling at the airport for the next 18 or so hours .
Is there any way to have it be that the plane doesn't start "using" the gate until shortly before departure, whatever the turnaround time for that particular aircraft would be I would assume.
Yes that's as intended. When a plane lands it will stay at the gate until it takes off again. But isn't that how it works in real life as well?
Either way programming it to start using the gate only just prior to departure is too difficult I believe. Not sure how I would accomplish that. Too many checks and balances to keep everything synced up.
10-02-2017, 05:58 PM (This post was last modified: 10-02-2017, 05:58 PM by Unknown98.)
(09-12-2017, 03:20 PM)PolarMonkey Wrote: This is something else I have noticed today. The term start date seems to get changed every time the gate gets used (or I assume, the only ones that are not changed to the last few days are the four that are stuck in use, and another in LHR that may not have been used for a while as I was switching flights from there around). I'm not sure if this will help with the bug, but I just thought I'd point this out.
This has been fixed now (as of today), so the term start date should remain at what it currently is and will not update every time the gate is used. I do not believe this was related to the gate in-use bug however as it was a database error, not a programming error.
I'm curious though, has this gate bug re-appeared for anyone since the game reset?
10-03-2017, 11:33 AM (This post was last modified: 10-03-2017, 11:34 AM by khush37.)
I just realised why gates were being used even when it shouldn't after reading this thread. This problem is occurring for 1 of my gates at AMD. The gate code is 4301. It seems that it just AMD and not any others for me (at least for now).
I haven't noticed any issues with my gates so far. I noticed that some of the gates had the start date changed to the last few days, but I assume that is just because you had only just made the fix. I'll try to remember to check them out every so often to see if anything happens.
I just noticed that when I'm on the Gate Management page, the utilization for AMD is 0% but when I click on Manage..., Gate 4301 is in use, but it isn't by a plane. I would have expected the utilization to be shown as 50% if it says it's In use. Is that happening for everyone?
Idk if that makes sense, but look at the attachments and it will make more sense.
It's due to the way the system checks to see if a gate is in-use. The management page shows the correct utilization because it has gone through all your aircraft and checked that none of them are using any gates at that airport. But the individual gate itself has been toggled as 'in-use' for some reason even though no plane is actively assigned to it. Basically each plane has a "gate" status and each gate has an "aircraft" status. Those two are always supposed to match each other but somehow they are getting un-synced.
I may be able to patch this temporarily by creating a script that goes through all the gates in the game and cross-checks their status with actual statuses of the aircraft... might look into doing that until I can figure out what is causing this to happen.
