Routes System is Live
#31
That seems to work fine. One problem I do have is that I scheduled my flights yesterday to operate today, which they did, however they have automatically been scheduled for tomorrow again rather than the route ending

It seems as soon as the route has ended it is reallyscheduled
Reply
#32
That's strange. no idea why that would happen... I'll have to watch my route that is about to end and see if the same thing happens.

(04-23-2017, 09:17 AM)Sora Wrote: I'm not a big fan of the fact, that my flights HAVE TO depart not later than one hour after the turn-around has been completed. Why's that? If I want my planes to sit on the ground for a bit longer, then let me do it for god's sake. Granted, I could extend the turnaround times for all my aircraft, but even then, it doesn't work all the time.

I think, there should be an extension to two or three hours - because I'm quite sure, that you had a good reason to add the original 1-hour-limit to the code, Unk. Tongue

This limitation has been lifted now.
I am the developer of Airline Enterprise
Reply
#33
It only done it on one of my routes. The others have since ended fine
Reply
#34
That's frickin weird lol. What's route? So I can try to reproduce the issue
I am the developer of Airline Enterprise
Reply
#35
MAN — GLA — MAN — JER — LGW — JER — MAN — SOU — MAN — LGW — MAN. DEP@: 09:30 BST
Reply
#36
(04-23-2017, 11:22 PM)Unknown98 Wrote: [...] This limitation has been lifted now.

Thank you very much.

For unknown reasons, it's still showing the "Departure time of leg Y is before the ready at time of leg X" warning though.

First, the complete route with the (local) times like I've originally scheduled them:

HND — IWK, Departs at 08:50 | IWK — OKA, Departs at 11:25 | OKA — FUK, Departs at 14:00 | FUK — OKA, Departs at 16:30 | OKA — FUK, Departs at 18:50 | FUK — HND, Departs at 21:20

And now, the route with what the game thinks I've been scheduling:

HND — IWK
04-24, 23:50 UTC Departure Time
--------- 01:25 Flight Time
04-25, 01:15 UTC Arrival Time
--------- 00:30 Turnaround Time
04-25, 01:45 UTC Ready At Time
01:55 Cumulative Flight+Turnaround Time
0 Seconds Extra Time
SUCCESS.

IWK — OKA
04-25, 02:25 UTC Departure Time
--------- 01:46 Flight Time
04-25, 04:11 UTC Arrival Time
--------- 00:30 Turnaround Time
04-25, 04:41 UTC Ready At Time
04:11 Cumulative Flight+Turnaround Time
2400 Seconds Extra Time
SUCCESS.

Departure time of leg 3 is before the ready at time of leg 2.
OKA — FUK
04-25, 04:20 UTC Departure Time (should actually be 05:00 UTC)
--------- 01:37 Flight Time
04-25, 05:58 UTC Arrival Time
--------- 00:30 Turnaround Time
04-25, 06:28 UTC Ready At Time
06:19 Cumulative Flight+Turnaround Time
1140 Seconds Extra Time
SUCCESS.

FUK — OKA
04-25, 07:11 UTC Departure Time (should actually be 7:30 UTC)
--------- 01:37 Flight Time
04-25, 08:48 UTC Arrival Time
--------- 00:30 Turnaround Time
04-25, 09:18 UTC Ready At Time
08:26 Cumulative Flight+Turnaround Time
3720 Seconds Extra Time
SUCCESS.

Departure time of leg 5 is before the ready at time of leg 4.
OKA — FUK
04-25, 08:48 UTC Departure Time (should actually be 09:50 UTC)
--------- 01:37 Flight Time
04-25, 10:25 UTC Arrival Time
--------- 00:30 Turnaround Time
04-25, 10:55 UTC Ready At Time
10:33 Cumulative Flight+Turnaround Time
1920 Seconds Extra Time
SUCCESS.

FUK — HND
04-25, 11:48 UTC Departure Time (should actually be 12:20 UTC)
--------- 01:38 Flight Time
04-25, 13:27 UTC Arrival Time
--------- 00:30 Turnaround Time
04-25, 13:57 UTC Ready At Time
12:42 Cumulative Flight+Turnaround Time
5100 Seconds Extra Time
SUCCESS.

Not quite sure, why it's only displaying the message for legs 3 and 5 respectively. Guess I was just lucky with leg 4, haha.
Reply
#37
Looks like it's not applying the custom departure times for certain legs when you leave extra time between the flights. You set 05:00 UTC departure for leg 3 but for some reason it's trying to use 04:20 UTC. Probably has something to do with not adding the "extra time". If you notice 04:20 is 40 minutes less than 05:00, and the extra time that is supposed to be applied is 2400 seconds, which is 40 minutes. So if it was working correctly it should do 04:20 + 2400 seconds = 05:00 UTC.

I'll have to look at it tomorrow and see why it's doing that.

OR maybe the game just smoked too much weed on 4/20 and we're still feeling the side effects.
I am the developer of Airline Enterprise
Reply
#38
Ah ha! I think I got it fixed.

Basically the game was not accounting for the cumulative "extra time" between flights. i.e if you leave 30 extra minutes between each leg, leg 2 will have 30 extra minutes, leg 3 will have 60 extra minutes, and so on. But it was just adding 30 minutes between each flight, it wasn't adding them up cumulatively.
I am the developer of Airline Enterprise
Reply
#39
Unk, don't get me wrong, but YOU. ARE. THE MAN! Tongue

Tried it out immediately and it works like a charm. And with this, I can finally fly my airline's real-life routes (with their respective departure times) now.
Reply
#40
(04-25-2017, 02:02 PM)Unknown98 Wrote: Ah ha! I think I got it fixed.

Basically the game was not accounting for the cumulative "extra time" between flights. i.e if you leave 30 extra minutes between each leg, leg 2 will have 30 extra minutes, leg 3 will have 60 extra minutes, and so on. But it was just adding 30 minutes between each flight, it wasn't adding them up cumulatively.

Im still don't quite sure I understand but fortunately I don't need to.  Tongue Congratulations on working it out and fixing it.  Smile
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)

About Airline Enterprise

Welcome to the official message boards of Airline Enterprise. Feel free to join the discussions, ask for help or just browse!

              Quick Links

              User Links