We had a real-time gate usage system but it was disabled due to not being accurate enough. The game used a script that ran every 5 minutes and updated the status of each gate. If your aircraft left the gate at 1:01 the gate would not update until 1:05, so if you had another aircraft land at 1:04 - the gate wouldn't be available. The only way I see a system like that working is to store and keep track of the gate (and slot) usage times in a database, and every time you update a route or make changes to an aircraft's turn time it would have to re-calculate that and update the stored values. I will have to think about it and see if it is something that can be done. But I will say it won't happen before the reset, it would be post-reset or possibly post-release. That kind of goes back to something I mentioned before but got some backlash on - limiting routes to only depart on the 5 min mark. So when creating a route you would select 00:05, 00:10, 00:15 and so on instead of being able to say, "depart at 8:37". It would make managing gate and slot block times much easier.
So does someone mind explaining to me how a separated gates/slots system would work? Would you need both a gate and slots to operate flights? Just one or the other? Would you lease a slots in addition to leasing gates? Excuse my ignorance but I just don't really understand how it all works together.
So does someone mind explaining to me how a separated gates/slots system would work? Would you need both a gate and slots to operate flights? Just one or the other? Would you lease a slots in addition to leasing gates? Excuse my ignorance but I just don't really understand how it all works together.
I am the developer of Airline Enterprise
