Alright so we're still having issues with this multi routes thing. (For once even I am also seeing the issues with my own airline, lol)
For now I will have to revert back to the old system while I try to re-write the code to enable muti-route support.
Keep in mind you can still use a form of multi-routes even with the old system, as long as each route starts from a different airport. For example you cannot do:
LAX-HND-LAX
LAX-KIX-LAX
But you CAN do:
HND-LAX-KIX
KIX-LAX-HND
Same routes but in a different order. Get creative with it and you can probably make some things work.
Support for multiple routes being assigned to the same aircraft has now been implemented. It was actually possible before but was not "officially" supported, meaning in some cases routes would not fly in the intended order or would be skipped entirely.
The easiest way for me to explain this is to show an example. I have 1 aircraft, a 787-8 that I use on a LAX-SYD-DXB route, and back. Because routes with more than 2 stops cannot exceed 24 hours in length, I cannot create one route like follows: LAX-SYD-DXB-SYD-LAX.
But I CAN do the following:
LAX-SYD-DXB
DXB-SYD-LAX
As long as you pay careful attention to the arrival and departure times, you can set up routes like this. In my case, I depart LAX at 23:20 and arrive in DXB at 13:15. Then, the second route departs from DXB at 14:20 and arrives at LAX at 10:16. Of course all of this is over the course of several days. These are very long-haul routes.
Then, because I had even more time to kill (arriving back at LAX at 10:16 and not departing again until 23:20) I created ANOTHER route:
LAX-DFW-LAX
This route departs at 12:45 and arrives back in LAX at 19:22.
So I now have a nicely organized route system all assigned to a single aircraft.
There is one caveat - This will NOT work with routes that have already been created. Only routes that are created from this point onwards. This is because the system needs to know the initial departure time of the first leg of each route, and prior to today that information was not stored in the database.
For now I will have to revert back to the old system while I try to re-write the code to enable muti-route support.
Keep in mind you can still use a form of multi-routes even with the old system, as long as each route starts from a different airport. For example you cannot do:
LAX-HND-LAX
LAX-KIX-LAX
But you CAN do:
HND-LAX-KIX
KIX-LAX-HND
Same routes but in a different order. Get creative with it and you can probably make some things work.
Support for multiple routes being assigned to the same aircraft has now been implemented. It was actually possible before but was not "officially" supported, meaning in some cases routes would not fly in the intended order or would be skipped entirely.
The easiest way for me to explain this is to show an example. I have 1 aircraft, a 787-8 that I use on a LAX-SYD-DXB route, and back. Because routes with more than 2 stops cannot exceed 24 hours in length, I cannot create one route like follows: LAX-SYD-DXB-SYD-LAX.
But I CAN do the following:
LAX-SYD-DXB
DXB-SYD-LAX
As long as you pay careful attention to the arrival and departure times, you can set up routes like this. In my case, I depart LAX at 23:20 and arrive in DXB at 13:15. Then, the second route departs from DXB at 14:20 and arrives at LAX at 10:16. Of course all of this is over the course of several days. These are very long-haul routes.
Then, because I had even more time to kill (arriving back at LAX at 10:16 and not departing again until 23:20) I created ANOTHER route:
LAX-DFW-LAX
This route departs at 12:45 and arrives back in LAX at 19:22.
So I now have a nicely organized route system all assigned to a single aircraft.
There is one caveat - This will NOT work with routes that have already been created. Only routes that are created from this point onwards. This is because the system needs to know the initial departure time of the first leg of each route, and prior to today that information was not stored in the database.
I am the developer of Airline Enterprise