Route scheduling bug combined with aircraft ERROR
This is a pretty big one, a large number of routes not scheduling. I'm not sure how this started, but I just noticed that quite a few of my aircraft were on the ground at outstations, with the flights scheduled for those aircraft beginning at airports that they were not at (so for example a plane is at BZE, but the next scheduled flight for it is CUN-GCM). Several of these routes also had only every second leg scheduled, any only flights out of the airport the aircraft is based in (so only GCM-GUA, GCM-NAS, GCM-BGI etc instead of the return legs being scheduled as they should be). Other routes had all legs in the route scheduled, but the aircraft was not at the airport that the next scheduled leg began at, as described above. The following routes were affected:
[route ID] operated by [aircraft ID]
- f2c08d9e58dd10a3a599517257fabb6e operated by 10435
- 7d66b66286701dc0bf08cfe1dc21a723 operated by 10475
- ec9a60919df75e5c7712c86b068bf715 operated by 10436
- ac6353d070c618fb11a6d6df31ef14cf operated by 10431
- d764657d04f7ed7e600d261370727e72 operated by 6026
- e89b0d089d00c3d6a2130864a49d6322 operated by 8690
- b7ea4b5bdf804de6cde22c8b074cc579 operated by 4341
After cancelling scheduled flights, I quick-flew all these aircraft back to the airports they are based at. They all flew successfully, but every single one now displays ERROR as the flight number, and they do not appear on the active flighst page. Mousing over the blue airplane icons on the fleet page displays "enroute to ANU" and "enroute to GCM" etc, though.