Version: 1.0.84.0
Frequency: Consistently
Severity: Low
Marketplace package name: Indiafoxtecho USS America, USS Ford and other startic aircarft carriers
Context: MSFS2020 static carriers imported in Community folder
Similar MSFS 2020 issue: it seems to happen VERY RARELY (maybe 1%) on MSFS2020, but we could not reproduce the issue consistently.
Bug description:
Our MSFS carriers are made with an invisible small “airport” (hidden below the ship), roughly positioned on the ship coordinates (and slighly offset towards the bow).
Runways starting positions are placed in exact “realistic” spawn position for aircraft on the deck, which are often off the ship axis and placed outside the airport runway.
In MSFS everything works fine: starting the flight on the runway will spawn the aircraft at the exact position we intended, and flight starts from there.
In MSFS2024, however:
In the “UI-World” environment, the aircraft is spawned at the correct position.
As the flight actually starts (in the actual simulation world) the plane is moved to another position (apparently the runway).
Repro steps:
Install either the USS America or USS Ford package and observe the change of position from the “spawn” position (in the “world” environment) and the position in which the flight actually starts.
Attachments:
Example: F-35 starting for USS Tripoli near San Diego.
Spawn position on the map is correct:
After selecting “start flight” on the map UI the aircraft spawns in the correct position:
Then after selecting Start Flight, the plane is “moved” to another location (apparently the start of the runway) irrespective of the start position set in the scenery:
Note:
-
in the scenery the runway start is actually out of the runway boundaries.
-
this problem is probably limited to “special” airports, so very uncommon. Still, the behavior is different from MSFS2020.
-
player can still take-off by moving on the correct position, but it is an annoyance.