2 replies to this topic

[flightvision]

You can push any load factor by just updating the route.

I think the better players know that, but they would not file a bug.

It is about the LF script which is complex. But it is strange that it ends up with different numbers depending on how it is called (Called automatically -> LF decreases; Called manually again -> LF up again).

[fish10]

Watch your ticket prices when you're doing this... what I see is that it frequently assigns a ticket price much higher than the original estimate the first time causing a low load factor... when you reprice the route it seems to bring the assigned price much closer to the estimated price... causing what you are calling a "pushed" LF...

I think the bug is that there needs to be a way to make the estimated ticket price stick and carry through to the actuall assigned price when using autoprice.

Something else that I thoght about that might solve this if its too complex to make the price stick... just make it so we can use autoprice but assign a price cap on it so it can't go above $x,xxx... this would prevent it from assigning a higher price than our limit (which we would probably derive from the autoprice estimate).

[Glennos]

Well, this has been a "problem" for a while. A few years ago you used to be able to keep updating the routes and it would forever increase the ticket price and therefore profits

I normally don't bother too much now though as I was so used to updating and resetting routes every 5 minutes weeks at a time that the times I have to do this now makes it a pleasure

Some routes it works on and some it does not. I guess we need to wait so that these things can be tested fully (by this I mean just more than 1 person testing) before going into the game.