Ok, less of a bug and more of a feature incompatibility, but there are problems with the new "Create Each Day as Different Route" feature for 7 day scheduling and the new(ish) features controlling how many routes are listed per page in the scheduling screen (20) and the maximum number of unscheduled routes allowed at "busy" airports. These issues make the 7 day scheduling feature just about unusable.
Example: Swapping 767 -> 787 at PEK in GW2
Since we still can't swap schedules between different types, this is still a time consuming manual process. Creating a route as 7 different routes SHOULD alleviate some of the pain, but it does not. Here is why.
767 has 8 weekly flights, so for 7 frames that is 56 flights. Only 20 fit per screen in the new scheduling pop up, meaning one must go through each plane and schedule the first 3 flights, then go back and schedule the next 3 flights, then go back a third time and schedule the last 2 flights. There are two tweaks that could fix this. First, allow the user to turn off the feature that prevents more than 20 flights from loading in the scheduling screen. All of us would take a slightly longer page load time to take usability from nil to fully usable. Second, the system could be programmed to logically group flights together so selecting the first 8 (in this case) would assign the proper flights to each aircraft. This option, I would think, would be infinitely more difficult to program than just allowing the user to decline the default option of arranging unassigned flights into groups of 20 and accept the option of allowing every unassigned flight for the selected aircraft type to load in the scheduling screen. Or, you could simply give the user the option to allow, say, 20, 50, 100, or unlimited routes per page at the scheduling screen.
Once we get past that issue, the problem of limiting unassigned routes at slot constrained airports still exists. Routes that I have flown for 50 game years can not all be rescheduled without triggering that "too many unassigned routes at this airport" warning. This means, that in addition to the issues above, now we have to only create the first 5 sets of flights (so as not to trigger that obnoxious red warning screen), assign them to a plane as described above (since we can only have 20 per page...), go back create the other 3 flights, go back schedule those to the plane. Fix for this, if a route has flown, turn off the limit to unassigned routes. There is really no reason for that limit on unassigned routes to exist unless new slots are being purchased anyway, so simply tell the system to ignore the unassigned routes at any given airport unless x number of new slots at said airport have been purchased in the last 4 game weeks (the time all new slots must be used during to avoid them expiring.)
Thanks for your attention to this, Sami.