Hm, actually…it would have to be a bit more involved than that. I figure that if one has specified custom arrival times before, just not enabling the fixed arrival times by default would discard previous settings. So I guess, it should only be disabled if the computed arrival time happens to be the same as the currently set one…in which case, we wouldn’t actually need a custom setting in the first place?
And flaw in my thinking here?
Is it better now? 6.10.1 removes the timezone label, adds a minimum width and cuts down on padding, so the hours/minutes should always be visible, even on small screens.
Hi,
I’m playing on Bleriot server, as I have different aircraft scheduled on the same route, I usual use the scheduling section to modify the times when needed.
With the new update of timing I notice that when you try to modify a departure or arrival time through the scheduling windows, you must select an Aircraft otherwise all scheduling will be deleted!
As you can see in the below image, I have 7 different aircraft on the same route and now the only way is to operate through single aircraft flight plan.
Now it become a very long job when you need to vacate a slot!
Thanks for the heads-up, I’ll have a look.
Ah, nevermind. Just tried it myself and I think the issue is, that you have checked all the boxes of the “flight day selection”. In this context this means that for that day you want to set the aircraft selected above (possibly none). If you just want to change the times, you can just do so and the assigned aircraft will remain the same. No need to select the days.
Does that work or am I missing something?
Yes, really good now. Always visible even if I change the window size. Thank you!
Thank you very much for your prompt response.
I’ve tried and it works perfect without check the aircraft box.
I found another bug.
This is the flight screen after just clicking to edit flight
If I change the departure just by 1 minute, it recalculates the flight at an absurd speed and makes the flight out of performance
I have to actually unclick the “fix arrival time” in order for the new arrival time to be reflected. This is an unnecessary click and delay.
Please consider fixing this by making “fix arrival time” not preselected by default but deselected.
And for the bug you might want to look into why the calculation so ridiculously increases the speed if moving the departure time by just 1 minute.
The speed isn’t absurd…the flight distance is 145 km and the total flight time is 35 minutes. At 25 minutes of fixed flight duration (overhead for alignment, holding etc), you already arrive at a speed of 870 km/h as in your screenshot. Decrease the flight time by another minute and you get 967 km/h. It’s not exactly intuitive on such short distances. I struggled with this myself when I worked on the changes and built an Excel sheet to make sure I’m not failing at basic math. That’s how I confirmed your case as well 
While I have something planned to move a whole block into the next slot (meaning both departure and arrival time, although the current idea is a whole slot, not minute precision), just not setting the fixed arrival time likely isn’t an option when editing flights. I might remove the flag by default when the computed arrival time equals the currently set one. But I’ll return to the whole subject after the weekend and see what feels like the best approach.
Has the ‘Delete Unused Flight Numbers’ function been broken on the Flight Number Management page since the update? It seems even with the ‘Ignore empty flight assignments with fixed arrival times’ unclicked, the unused flight numbers don’t get deleted. Basically, if you schedule a flight number and remove it from the assigned aircraft, the function no longer deletes that flight number. The only way seems to be go to the flight number page, and delete them one by one
It should still work. But I’ll check it out as soon as I get around to it.
