I disagreed with most of what the responses to the above feedback right up to the point when ATC was mentioned.
The reason ATC threw a spanner into the argument was that I recalled a number of times with ATC getting broken in 4.35. There were plenty of times that AI flights would just stack on the EOR not taking off. I never knew why, but I also haven’t seen that behavior in 4.36 so thank you for that.
That being said I think the solution should be to keep working on ATC to accommodate trying to push the flight time up. I’m not a coder or even computer literate but perhaps a fix can be to have the code check on departing flights, and if departing flight < or = X minutes from your flight plan a dialog box comes up saying “There is a flight conflict, please adjust takeoff time.”
I hope you devs keep working on this, I’d support the feedback that this is a sub optimal solution to the ATC problem just as much as I’d acknowledge ATC needed fixing. I would also support a fix returning the 4.35 functionality with accommodations to the other items that were impacted. I’d also support a server option to turn the ability to move launch time to <20 minutes on/off with a warning it could impact ATC and let folks decide for themselves.
PS-I don’t frequent the site too often and I’m not up to date on all the stuff here, I can say this was the second thread I came across which mentioned a change in 4.36 which wasn’t adequately documented in the change log. Getting that feedback more than once in a release should be all the feedback required to improve the process on the dev side to correct that moving forward.