I just wonder how long till both worlds will just perish.
I spent time since day one of Stapelton building my airline there and this is the only gameworld I play on so no I would not like to see the world shutdown. I would like to see it fixed.
Same for me. Players with BIG airlines in Stapleton server do not want to see this lagging problem which disrupted our experience on playing Airlinesim. Honestly, I only play for one server in Airlinesim, "fortunately" the server I'm playing right now is largely affected. What the admin can do is to temporarily shut down the server and identify the problem, then re-open the server.
This comes with compensation as well. If this problem is not resolved within this week, I think I'm gonna just leave my account like that until the server is stable and good to play.
agree, I think the admin shall temporarily shut down the game world, then let us know when it is ready to play.
The problem now is that we can't control our airline, arrange cash flow due to stop of time, if the game world keep going like this, players are leaving the game world, it is not economic effective as well. Meanwhile, players like us that still in the game suffer alot and don't know when the nightmare ends.
Stop the game worlds for 24hours (If possible) and fix the problem.
I'm sure that we will all survive for 24hours without the game :) hard but possible. The wife will b happy (for once :)
Dan
Just let the AS team some time to work on it.
Aspern is already catching up, though slowly but better than nothing
agree, I think the admin shall temporarily shut down the game world, then let us know when it is ready to play.
The problem now is that we can't control our airline, arrange cash flow due to stop of time, if the game world keep going like this, players are leaving the game world, it is not economic effective as well. Meanwhile, players like us that still in the game suffer alot and don't know when the nightmare ends.
Well I haven't manage my airlines for days due to the slow response time. I do have faith with the team in solving the problem. But at this moment I believe that shutting it down would be a better choice.
I believe we should leave it to the AS team to decide what is best for something they know a lot more about than us.
[EN]
Official status for May 1st: I've been fiddling with the system for more or less the whole day but so far haven't found the "magic setting". The move of Quimby to new hardware did not bring the desired effect, at least not to the extend that I had hoped it would. Nevertheless, Aspern seems to steadily pick up some of its backlog, Stapleton looks like it's at least been stabilized. I just hope that once Aspern is back to normal, the load on the server decreases and Stapleton adds a notch or two. This is mere speculation though. The problem is that right now, I'm pretty much out of ideas on what else to do to improve the situation. Sorry guys, but I just don't see a "quick fix" at this point in time.
As a reminder: Both on Stapleton and on Aspern, payment has been deactivated for the time being. Please stick with us until we can find a way out of this mess.
[DE]
Offizieller Status am 1. Mai: Ich habe mehr oder weniger den ganzen Tag mit dem System herumgespielt, aber bisher die "magische Stellschraube" nicht gefunden. Der Umzug von Quimby auf neue Hardware hat leider nicht den gewünschten Effekt gebracht, zumindest nicht in dem Maße wie erhofft. Trotzdem scheint es zumindest so, dass Aspern langsam aber sicher seinen Rückstand abbaut, während sich Stapleton zumindest stabilisiert zu haben scheint. Meine Hoffnung ist, dass die Serverlast sich reduziert sobald Aspern seinen Rückstand beseitigt hat und damit auch Stapleton ein oder zwei Gänge zulegt. Das ist aber keine Spekulation. Das Problem ist momentan, dass mir mehr oder weniger die Ideen ausgegangen sind, was man noch zur Verbesserung der Situation tun könnte. Es tut mir leid sagen zu müssen, dass es gegenwärtig wohl keine schnelle Lösung für das Problem gibt.
Zur Erinnerung: Sowohl auf Stapleton als auch auf Aspern wurde die Bezahlung deaktiviert. Bitte bleibt dran, bis wir einen Weg auf diesem Schlamassel gefunden haben.
Oddly my game is showing 10:25HT but I have flights from 7:30HT that still haven’t departed. I’m worried this will somehow put me in a financial mess.
due to the backlog there will be no flights cancelled. Just treat it like a time shift by x-hrs. All actions like depatures, arrivals, Aircrafts orderd from the Market or delivered from Manufacture, Weekend Closures, stockmarket transfers etc are just hanging 10 hrs back. so all actions will be performed. It looks like in your case maybe the backlog was just building up. Nevertheless monitor your companies and the situation carefully and if in doubt send a support ticket and we will have a look at it. But there is no need to worry for now. Lets hope Aspern is catching up and frees some resources to reduce the backlog from Stapleton.
I just sent you a ticket...
What about transfer flights?? I couldn´t put it on schedule before the plane arrives, but the moment it arrives and the new airport is accepted, it is too late for the transfer.
I wonder if we all had a little "Gentlemens agreement" amongst ourselves, the users, to not touch Stapleton for 48 hours would help AS out?
Im sure the more we try to fiddle with our airlines during this time, the worse its getting...
Since all is delayed you can transfer the airplane like usual .... so you activate the Flightplan, wait at what airport you need to send the plane and send it to that airport. Or you send it to your hub and manually cancel the flights before ... normally you will not go bankcrupt if you do that even if you have a few passengers booked. Alternatively send again a support ticket to have a look at it and then wait for the decision.
To transfer a plane it will only accept a transfer flight from the "Last airport", which is the DEPARTURE airport and the plane is enroute, but due to the delay in time it is not actually at the destination, from where it should be transferred in time. Once it arrives there, it is falling in that gap between delay and actual local time. When you now try to book a transfer flight, the departure AIRPORT is right, but the departure TIME is local time +30. Too late for its next departure. I planned a change in schedule days ago which included the transfer flights.
A cancellation of fully booked wide body jet flights is more than I am willing to spend...
I don't get it at the moment .... Forget about the backlog for the moment. If you transfered the plane from its old Airport to the Airport you like to use it from and the Aircraft arrives at lets say 1200 at the new airport and your first flight from your new airport will depart at 1230 than the aircraft will arrive at 1200 even if 2 hrs after the aircraft departed a backlog of 8 hrs occured. All operations of all companies on that server are delayed by 8hrs. Of course you can submit a support mail and we have a look at it. If you did not activated the shedule then wait until the backlog is gone. Normally if you shedule a flight or do any action that is working beforeor during a backlog period means it will also work after the backlog is gone. . Usually we will look then at those issues once the backlog is cleared.
On the flight page it says:
Letzter Standort on the bottom above the transfer flight option.
Let´s say the aircraft is enroute from
11:00 local time FRA --> CDG 12:30 local time
Letzter Standort will be FRA and that´s the airport the transfer flight will be set up from!!
But you want to transfer it from CDG to let´s say MAD, you must wait till it arrived in CDG to set up the transfer flight, otherwise it will book a transfer from FRA to MAD. That´s clear, isn´t it?
Now with a backlog of let´s say 2:00 hours. The plane is still "inflight" till 14:30 local time. Correct? But you NEED it to depart latest at 13:30... which is not possible cause the backlog says "inflight", but the local time at CDG will tell you "landed" not until 14:30 local time. The setup of the transfer flight will give you an earliest departure time at 15:00 local time from CDG, because the actual LOCAL time is used, NOT the backlog time!!
Do you know what I mean? It´s ALL about the backlog!! TO be concrete... I took this right NOW:
The local time in LIN: 18:25; the transfer flight was just set 1 MINUTE ago.
EU 1129 Milan Linate 01.05. 10:35 LT Tenerife South 01.05. 13:31 LT inflight
XFER 
Milan Linate 01.05. 18:54 LT Amsterdam 01.05. 20:19 LT booked --
EU 1135 Amsterdam 01.05. 21:00 LT Tenerife South 02.05. 00:13 LT booked
It would be in time in AMS, but only from LIN. Once it gets to TFS, it is way too late.
Well .... I would nerver ever create a shedule where you have to transfer a flight at a certain time once a day or once a week.... but that's just me and more a personal advice...... what you do if you are on holiday or you have no internet connection to whatever reason at that time ?
But never the less .....
Let´s say the aircraft is enroute from
11:00 local time FRA --> CDG 12:30 local time
Letzter Standort will be FRA and that´s the airport the transfer flight will be set up from!!
But you want to transfer it from CDG to let´s say MAD, you must wait till it arrived in CDG to set up the transfer flight, otherwise it will book a transfer from FRA to MAD. That´s clear, isn´t it?
That is correct!
Now with a backlog of let´s say 2:00 hours. The plane is still "inflight" till 14:30 local time. Correct? But you NEED it to depart latest at 13:30... which is not possible cause the backlog says "inflight", but the local time at CDG will tell you "landed" not until 14:30 local time. The setup of the transfer flight will give you an earliest departure time at 15:00 local time from CDG, because the actual LOCAL time is used, NOT the backlog time!!
Now there you are getting confused ;)
Your Plane departed at 1100 in Fra and should arrive in CDG at 1230. If you have a backlog now of 2 hrs your plane will still arrive at 1230 .... If you are playing the game for example in Germany then your plane will depart at the same time as your local time at home, right ? Now with a backlog of 2hrs your plane will arrive at 1230 game time ... but at home for you it is now 1430. And now you a can transfer the plane to MAD and it will reach MAD then at the correct game time. Problem is you have to think like you are 6,8, or 10 hrs ahead of the actual game/Server time. It's confusing I know .....
No, once the plane will say "finished", it will use the actual local airport time +30 min, if you set up a transfer. NOT the backlog time!!!! It´s 12:30 by backlog, correct. The transfer will be set up at 15:00 once you put it in immediately after the plane´s status changed to "finished", if you set the transfer up BEFORE the plane has by backlog "finished" its last flight, you will have the last DEPARTURE airport as departure for the transfer which would not be correct, cause the plane is enroute. So you CAN´T transfer at the desired time. Did you see what I edited in my last post??
And just for the record... I had a major switch in aircraft types that´s why this and only this week I have planned transfer flights.
Metrodriver123 is right. Scheduling a transfer time will use actual time, rather than the current/backlog time:
Let’s say the flight is landing at 12pm at LHR and you need it at 2pm in LGW. Now the backlog is 3hours. By the time the flight lands in LHR, you book your xfer and then you look when its booked: xfer LHR 5:20pm -> 5:40pm LGW.
That is, you won’t be able to schedule xfer flights is you’ve got a tight schedule.
Just checked it with SK and you are right ... sorry never experienced that :blush: :unsure: You are right and during a backlog the transfer flight will then use the actual time .... well in that case write a support mail wenn you know how many flights are cancelled and what the total amount was so i think you will get compensated since it was not your fault in that case ....