Uhm, the lf-bugs are fixed now, aren't they?
So the last week the routeserver was using the wrong script (which is corrected now), with this the following bugs are fixed:
- Multiple frequency had never ever better profits than a single roundtrip
- Projected revenues and calculated one were very different
- Manual priced routes were corrected in pricing by the system
These are the main issues and they are fixed (but yeah, you have to set your manual prices again - but they won't be touched any longer by the server).
All other issues related too "hey a route between x and y brings now profit, and between a and b it's too much" I won't fix. Why? It's simple: David is implementing a fully new load script, it's in beta as you know. With this in mind I won't invest much time to tweak the old script - this makes no sense if you throw away the old script in few weeks.
To come back to topic: I just a saw code that there disabled for a strike-feature. I just want to check if such a feature is a wish of the users and if I should add it to the "upcoming"-list or if I can remove the code 
Keep in mind: If I ask "whats about a feature xy?" doesn't mean "hey folks, integrating this soon" - I want to get a feedback if I should invest time in such a feature later or not. Just want to sort out things (and in the current case: I just scanning the code right now to clean it up and remove unused parts).
a couple of things:
1. From the US, one-way international route creation gives me back negative profits. Then if reset gives me under $40k. This through DFW to Asian and EU main cities. I auto priced and manually priced. Same result. A/c to be used A346.
2. The strike feature should not be a simple implementaion. One would have to manually have a scale to which level of salary based off of Regional average and size of company. And strikes should only happen if the wages are to low versus the profit level of the company and the regional airline average or something of the sort. If your like British Airways and have the some of the best paying salaries you should never get a strike. If you Airline is doing poorly vs the national avg., then you should be able to slide the bar down to a pay cut level. A feature like the load factor should give you a preview on the happiness of your employees.
3. Accidents should be be based of various things. Like the NBA lottery, more point your airline accumulates in a month on the following below, the higher the chance for a crash, it should be random and calculated on a couple of things.
---a.Real life statistics on the reliability of an a/c.
---b.The above stated wage level. Which would be used as a maintenance level indicator. But even the best maintenance airline has a small chance of crashing.
---c.fleet size, larger fleet higher chance.
---d.an a/c can crash in a airline only once a every 4 months.
---e.1 crash a month in the ae sim, unless certain airlines are deemed doomed and are not even close to par then a/c should be dropping out of the sky like flies.
---f.if airline is on strike and fly's it airplane, the a BIG chance of failure feature.
---g.the older the a/c the more chance. In brackets 0 - 4 years = 0.5% chance, 5 - 9 = 10% chance etc...
without it being thought through, please dont put the crash feature.
Sign In
Create Account
Back to top
