sviridovt

Update 23.12.27 New Features Updated Willingness to pay formula to slightly increase pax willingness to pay on ultra short haul routes, decreasing it significantly for medium haul and long haul routes. Note that this change will not impact Arcade ∅ which will stay with the current algorithm but will impact Arcade I when that gets started, this change will also effect World B IX following any route updates. Changed default price for routes to be slightly below median willingness to pay, such that assuming there are no competitors you should be able to capture majority (though not all) of the demand for a route given the default price. The Scheduler direction selector will now flip on flight creation to make it easier to create flights in the opposite direction Various Scheduler performance improvements Bug Fixes Fixed an issue where updating the route in the Scheduler would not force a route update. Fixed an issue where the Scheduler would allow creation of flights before the turnaround time. Fixed Airline selector drop down on route research and some other pages not showing user's airlines. Please note that these willingness to pay changes are designed to make the game harder and will be applied to the current World B IX, as such you might need to re-adjust your prices down. I apologize for not getting these changes out earlier, I expected to get them out before the world reset but miscalculated when the B VIII was going to end. Also note that while this update changes how much pax are willing to pay, it does not change the demand itself. Please let me know if there are any issues or suggestions, I will continue to mess around with the values in the coming days to further tweak them for best in game experience. Thanks!

I'm sorry what's the issue?

hmm, I wonder if it's still updating in the background but removed the box too early, these are the kinds of shenanigans I would expect if that were to happen.

World B IX will have all the same configuration as B, though I might play around with game balancing to reduce revenue and balance the game out during the swap. There is also a new world in the works to be an open arcade world where there are no political restrictions, planes can be bought at any time, and time will advance by a week at a time rather than a day. That world would also reset every IRL year and be 'endless' rather than fixed to a timeline. Currently working on all of the required changes for that and plan to get a preview world out hopefully within a week as a test run to run for the rest of the month.

Ok, I'll take a look later. It does appear that something hasn't gone right since you do have gates without any flights in your new terminal, so there should be capacity.

Update on the new dashboard I haven't had quite the time to work on it as I had hoped due to work commitments, but have made some progress. For one, I have made a decision to move away from the 3 pane approach and instead have 2 equal panes with the left pane being the informational pane, showing cards that will show up all the time including valuation graph, fuel prices, top/worst flights etc. with the long term plan to support user customization on which cards there are and where they appear. The left pane, or the notification pane will show notification cards, such as alerts about issues with your airline (plane leases expiring, aircraft running out of cycles etc.), aircraft deliveries, as well as competitive outlook when any of your competitors update prices, add/remove flights etc. This notification system will also replace the current in-game messaging mechanic thus deprecating that system. On mobile and smaller screens the two panes will appear as tabs instead, thus furthering support for mobile users which is a priority for me. The other use of the new dashboard is the introduction of React into the game as part of an effort to refresh the UI and add interactivity to the sim as well as increase performance. At present, the entire UI is processed server side, which results in some issues such as high latency on certain pages that require a lot of data, as well as limitations on the interactivity we can do (we do leverage APIs to enable interactivity in some places such as the seat map generator or lately in dynamic tables, but currently this is very much an exception rather than the rule). This is a quite dated approach and one I hope to replace. The long term plan here is to completely sever the front end and the back end, however with the amount of pages we have, with most requiring some amount of new APIs this is significant amount of work. Instead of stopping working on new features in favor of dedicating significant effort to purely front end work (or as I would call it, hell), in the interim I am redesigning pages as I go to embed react pages as components within existing site. Since the dashboard is the first such page, there is a lot of additional work to set everything up, especially since I want to be cautious about having all of this new work in a separate package such that whenever the full migration does happen, I can just import it into the new UI rather than needing to put in a lot of effort migrating everything over. I'm happy to say that much of this pre-requisite work is completed and I can now start working on the actual dashboard.

Your flights should move in automatically assuming there are enough gates in the new terminal to support them.

Released a small fix, there was a minor bug whereby if there are services classes with 0 seats, they would cause the routes API to error out and table to not load. This resulted in 11 requests failing over the course of the day. This is now confirmed to be fixed. Let me know if there are issues.

I am playing with an idea of an arcade world, so a new world might be coming. Whereby the world is unending (or at least runs for a predefined real world period), has all aircraft unlocked, no political restrictions and time advances by a week at a time. All of those features except the last are already supported (done through a world configuration). Was going to play with that idea this weekend but haven't had the time. Not sure if that will help with inactivity and I do plan to do something about that but since the idea of a new world was brought up 🙃

Hi folks! In addition to a small update to the ranking page a few weeks back to make the ranking table dynamic, the my flights page has also been updated. This should make those two pages, which have been some of the slowest pages as far as latency is concerned much faster. Further the APIs that were implemented for those changes will be used as part of the new dashboard. Further APIs were added for the new fuel model, though at present they're unused but progress is being made on that front.

Is this after waiting for the blue box to disappear? The recalculations are weird until the flight updates.

Which tutorial are you referring to? The blue notifications at the top of the screen?

That's probably why it is in weight as I was (am) quite a fan of flight sims so it was natural, but most sources use volume (liters, gallons etc.) when citing fuel capacity as well as fuel prices are typically volume based, hence to avoid errors it would make sense to use that.

I probably won't add a route map to the dashboard as I would prefer to keep the dashboard as a 'quick summary' of sorts rather than omnibus of all the information (you can go on your airline page or flights page to get that info), though I do think having options to decide what metric top 3 best/worst routes are shown (by default this is revenue currently) would be a useful feature. It should also not be particularly difficult thing to add, since the APIs I'm working on should already implement these filters (I've been working on adding/relying more on reusable APIs both to speed up development as well as to move away from server side rendering which is a major driver of latency)

No issues, I'll look into it some time this week, working on an issue with my development server at the moment.

It's actually stored in weight, so in Kg (not ideal, not sure why I implemented it this way as it was years back). There are conversions involved in saving fuel costs so definitely an error prone process. I have to go through and check for errors. Might refactor this to a more sensible unit as part of fuel update.

Yep, that is a bug that I intentionally have not fixed, I plan to fix it when there is an easy way to move schedules between aircraft.

Thanks for the suggestion! I have thought about such a system before though have not thought too deeply as this would be a long way down the line if implemented. That said, we would need to be careful in how we implement it to make sure that the system is fair and difficult to abuse.

Yeah, inactive airlines are a problem. Although I'm generally against having 'hard set' rules like an activity rule, I do plan on introducing something where if your airline is in the red for some predetermined amount of time the airline will be liquidated. But still need to work out the exact mechanism for that.

There is a plan for a new demand model (probably going to be my primary focus next year, as it's a major update) to introduce city/nation ratings of 0-20 that will impact things like tourism and work travelers (the new model will split travelers into 7 different groups, each with their own preferences). If you'd like to help out, we do need to start compiling this data which is already in the database but unused (and all data currently sits at a default value). The values I'm tracking are as follows: Avg Personal Wealth Income Inequality Immigration Laws (How open a given country is) Travel Appeal Luxury Travel Appeal Domestic Commercial Activity International Commerce These values are there for each nation and city, with the city rating being relative to the nation rating (so an average commerce rating in a city with high commerce will still have high commerce, the nation rating acts as a base level)

Yeah, the route scheduler is a page I wanted to redesign since inception as it wasn't meant to be permanent. It's a priority but also something that I really don't want to touch 😛

Yeah, this is something I need to look at. The way countries are determined is based on city assignment which is based on proximity. This is something that I want to rework at some point.

There is a different formula for each, but generally it is tied to the number/duration of flights, number of airports you operate in and number of aircraft and distinct aircraft type.

Thanks for pointing this out, it's a low priority issue at the moment but is on my radar. Thanks!

Yeah the original vision some time ago had something like that, will see about doing something like that long term but for now keeping it simple.