You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ATSU Flight number doesn't match the flight number in the FMGC section after importing the flight plan from simbrief or setting the flight number manually.
This issue is due to a bug in the 2024 SDK where the function to set the 'ATC FLIGHT NUMBER' simvar in not functioning as expected. The flight plan import will attempt to set the simvar (which fails in 2024) and the ATSU will retrieve the flight number via the simvar.
This renders the ATSU pages which uses the flight number inop due to an incorrect flight number.
A long term solution would be to skip the use of setting and getting the flight number through simvars.
Expected behavior
The flight number in the ATSU section should reflect the flight number set in the FMGC page.
Steps to reproduce
Navigate to a page in the ATSU that uses the flight number (eg. ATC COM Ground Request page) and observe the flight number
Go to the INIT page and import a flight plan or set a flight number manually
Return to the previous page in the ATSU and check the flight number. Flight number would still remain the same.
References (optional)
No response
Additional info (optional)
No response
Discord Username (optional)
Heclak
The text was updated successfully, but these errors were encountered:
Simulator Version
2024
Aircraft Version
Development
Build info
Describe the bug
Note: This is a 2024 only bug. The SDK issue has been reported and logged in the dev support forum. https://devsupport.flightsimulator.com/t/unable-to-set-atc-flight-number-atc-id-and-atc-airline/12486
ATSU Flight number doesn't match the flight number in the FMGC section after importing the flight plan from simbrief or setting the flight number manually.
This issue is due to a bug in the 2024 SDK where the function to set the 'ATC FLIGHT NUMBER' simvar in not functioning as expected. The flight plan import will attempt to set the simvar (which fails in 2024) and the ATSU will retrieve the flight number via the simvar.
This renders the ATSU pages which uses the flight number inop due to an incorrect flight number.
A long term solution would be to skip the use of setting and getting the flight number through simvars.
Expected behavior
The flight number in the ATSU section should reflect the flight number set in the FMGC page.
Steps to reproduce
References (optional)
No response
Additional info (optional)
No response
Discord Username (optional)
Heclak
The text was updated successfully, but these errors were encountered: