Agreement Changes, ATC Map Labels, and Quality of Life Fixes

Agreement requirements eased for Operations Centres

We've adjusted the Operations Centre (OC) requirements for international slot agreements to make them more flexible and accessible.

Previously, some agreements required you to have an OC at the specific airport where the agreement was signed. Now, these agreements only require you to have a suitably-sized OC anywhere within the same country. This means a single Operations Centre in the United Kingdom, for example, can now support international slot agreements at both London Heathrow and Manchester without needing a separate building at each.

In addition, the minimum OC size required for some international slot agreements has been reduced. For example, some agreements that previously required a 'Large' OC now only require a 'Medium' one. These changes should make it easier and more cost-effective to expand your international route network.

Live Map gets ATC-style labels

The live flight map has been updated to include Air Traffic Control-style data blocks for each aircraft. This provides more information at a glance, showing the aircraft's callsign and tail number directly on the map for easier identification and tracking.

Passenger Weight Adjustment

The standard weight for passengers has been updated to 100kg. This change accounts for the average weight of a passenger plus their baggage, providing a more realistic figure for weight and balance calculations in your flight planning.

Other Improvements & Fixes

• Operations Centre Sales: You will now be prevented from selling an Operations Centre if you have active agreements at that airport or in that country that depend on it. This ensures you do not inadvertently violate the terms of your agreements.
• Automatic Aircraft Movement: When a pilot accepts a route-based job, their aircraft will now be automatically moved from its hangar or stand into the correct departure slot.
• Agreement & Building Naming: When purchasing new buildings or signing new agreements, the default naming system will now correctly increment names (e.g., "My Hangar 2") only when another asset with the same name exists at the same airport, allowing for clearer organisation across your network.
• Route Re-evaluation: The process for re-evaluating route enablement after a change in your slot agreements has been moved to a background job. This will improve performance and reduce loading times when making changes that affect a large number of routes.
• Airport Search: An issue that could cause errors when searching for airports under specific map conditions has been resolved.
• Demand Filtering: A bug affecting the "total demand" count filter has been fixed, leading to more accurate results when searching for demand.
• SimBrief Settings: The company settings page for SimBrief integration is now only visible to users with the appropriate permissions.
• Company Deletion: The process for deleting a company has been improved to correctly clean up all associated data, including airport reachability and capability usage records.