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.
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:
Will try and fetch an older version of our packages.
If you are using the MSFS2020 Marketplace package, we have updated it last week and we have changed the the runway location coordinates to match the previous start positions, so that the problem is not anymore on our products in any case.
Reading through this topic again and just to avoid any misunderstanding:
What is the current version of your package where the fix was implemented?
And what is the version of the package that had this issue (before the fix)?
For USS America
The current version in MSFS2020 Markeplace is 1.1.7 (which is basically identical to 1.1.6). In both 1.1.6 and 1.1.7 the fix WAS IMPLEMENTED.
Latest version WITHOUT the fix was 1.1.5.
For USS Ford/Nimitz:
The current version in MSFS2020 Marketplace is 1.2.6.
In 1.2.6 the fix IS implemented.
The latest version WITHOUT the fix was 1.2.5
We don’t have an older version of your package, and since I can’t reproduce the issue I guess I can close this bug report ?
Unless you are still experiencing incorrect runway start positions that we can easily reproduce?
Link to older package was sent via a message to the Private Content recipient.
Bug is particularly evident on location “LHA6” (not far from Los Angeles).
I have also double checked it in MSFS2020 - package works as intended (the spawn location before and after “Ready to fly” is pressed is correct and identical).
As a reminder, in the latest package uploaded to the MSFS2020 vault the bug is NOT visible anymore as the invisible runways have been moved so that they are aligned with the spawn location.
Just a heads-up: for SU2, we’ve fixed an issue where the start position was not correctly taken into account when spawning (after clicking “Ready to Fly”) like the one you reported but in fact it was a larger issue than we expected.
You may want to review your project and revert any workarounds you implemented to bypass this.
I tested with your scenery, the spawn location when clicking “Ready to Fly” is still not 100% precise, but it’s the best we can achieve for now.
