Location Manager 2 for MSFS 2024 is Here!

Discussion Hub Tools & Utilities
, ,
44

Hola! It’s been a while, and I hope you’re all having fun virtually flying.

I’ve been testing SU5 Beta and have been working on a few updates and fixes.

One issue that’s cropped up recently is OSM (Open Street Map) is throwing 403r errors on random map tiles. This isn’t specific to Location Manager 2; it’s an issue any toolbar or internal to MSFS addon using OSM is experiencing due to how the internal browser in the UI system works.
The Fix for now: just use another map layer, which is why LM2 has multiple map layers for redundancy in case of issues like this.

Some SU5 good news but bad news: SU5 now allows you to use toolbar addons in career mode! yay! But wait, there’s more! Teleport, unfortunately, at least based on my early testing with LM2 in Career mode, looks to still be deliberately nerfed. Cue sad face. I have no idea why they would do that, in a single player career mode, but so it goes. Don’t complain to me, not my call.
I will continue to do some more testing in case I missed something, but atm it looks like while you can now use LM2 in Career mode, the most wanted feature - quick teleport in lieu of the supplied skip to descent - is nerfed so you can’t use it for that. I would guess this will be the same for any teleport app, as it’s consistent with what they have done currently to nerf teleporting in Career mode.

Anway…onwards, upwards, sideways…

Here’s a short summary of the upcoming Location Manager 2 V1.0.5 release, which will be released once SU5 goes live sometime in April. Stay tuned!

Location Manager 2 V1.0.5 [Release date TBD once MSFS 2024 SU5 goes live]

V1.0.5 improves the teleport workflow in Location Manager 2, especially for quick air starts around custom points, airports, and runways.

The main goal of this update was to make the teleport modes behave more consistently and more predictably, while keeping the existing runway circuit entries stable.

What’s New

  • Added clearer shared behavior for air teleport modes: To, From, and Offset
  • Added support for Overhead placement through zero distance where supported
  • Added bearing-aware air teleports with clearer heading control
  • Added live bearing hint text in the teleport panel
  • Added preview rendering for supported target-point air teleports
  • Extended airport ICAO selection so airports can now be used as practical air teleport anchors, not just ground-only starts
  • Updated runway To, From, and Offset so they now use the selected runway threshold as the target point
  • Added warnings in the teleport panel that selected height and speed may exceed aircraft limits
  • Replaced the old Bing map source, added support for an alternate provider for personal API-key use, and added a persistent default map-layer setting. Getting started: Get started with MapTiler | Guides | MapTiler
  • Added a fix aimed at improving OSM map connection reliability

What This Means In Practice

You can now use LM2 more easily for fast scenario setup.

Examples:

  • Click a custom point on the map and spawn inbound, outbound, offset, or directly overhead
  • Click an airport and use it as a quick air-start anchor without needing to choose a runway first
  • Select a runway and use To, From, or Offset relative to the selected runway threshold

This makes it much easier to set up ad hoc practice starts, sightseeing starts, arrival rehearsals, and quick repositioning around airports or runway ends.

It also means the map layer side is more flexible:

  • users are no longer tied to the old Bing source
  • users can configure a preferred startup map layer
  • users who want to use the alternate provider can do so with their own API key for personal use via MapTiler: Get started with MapTiler | Guides | MapTiler

Important Behavior Notes

  • To now means spawn away from the target and face toward it
  • From now means spawn away from the target and face away from it
  • Offset now means spawn offset from the target while the chosen bearing controls aircraft heading independently
  • Overhead means zero-distance placement at the selected target point with heading still controlled by the selected bearing

What Was Left Unchanged

The classic runway circuit entries were intentionally left alone to reduce regression risk.

That means the following runway options keep their existing behavior:

  • Take Off
  • Final
  • Base L / Base R
  • Crosswind L / Crosswind R
  • Downwind L / Downwind R

Recommended After Updating

  • Test airport To, From, Offset, and Overhead
  • Test runway threshold To, From, Offset, and Overhead
  • If you rely on the runway circuit options, confirm they still behave as expected in your usual workflow
  • If you use OSM, keep in mind the connection fix depends on upstream server behavior and may need revisiting if those rules change later

Summary

V1.0.5 makes LM2 a stronger quick-start and scenario-setup tool while keeping the established runway circuit workflow intact.

Happy flying!