Hi,

Simulator: MSFS24/Sim Update 6
Aircraft: A300-600F PW v.1.0.11 (D-AEAF livery)

Manual construction of alternate route results in messy flightplan
Phase: Cruise

When I want to add a STAR or waypoints before that star for the alternate in the primary flightplan, the first waypoint inserted will be put above the alternate, but it seems like there is one blank line in between when compared to other waypoints. When you scroll down, this waypoint's name will then be overlapped by other texts in the flightplan. A "CLR" to the blank line does not work, but going into the lateral revision of the first waypoint and setting the next waypoint once more as next waypoint at least removes the blank line, but overlapping text after scrolling remains.

Changing approach/STARs
Phase: Cruise
When in cruise, there are situations in which the change of an approach or STAR is blocked. I had this problem when the flightplan was imported via ACARS, for a manually constructed flightplan I can't remember if that happened. This happens for airports which have multiple approaches per category, for example an ILS-Z, ILS-Y etc. and or multiple runways. So far, I can't really pin it down, but it happened for example at BGGH and EGLL.

Let's assume we have a STAR and approach configured during flight preparation, let's call it ILSZ30.
If I go into the STAR page of either the destination airport or the STAR entry waypoint, the STARs, transitions and approaches are not "collapsed" into their respective category, instead all STARs are listed on the left and all approaches are listed on the right, basically what you would see while the approach is uninitialized. Selecting another approach (let's say ILSY30) does however not change anything, it looks like nothing happens. If I however select a VOR30 approach, this approach will be selected and I can reconfigure the STAR, now I can also select other ILS approaches. After inserting this into the flightplan, the new approach is sequenced after the approach which was configured in flight preparation. This happens in primary and secondary flightplan.

IRS Alignment problem with walkaround mode
Phase: Flight preparation

Sequence of events: IRS1/2/3 on, upload flightplan via ACARS, INIT PAGE initialize IRS, EFB open cargo door and set weights to start refueling, go into walkaround mode, start GSX boarding - let it finish, exit walkaround mode after couple of minutes, IRS alignment should be completed by now, but instead the INIT PAGE displays "ALIGN IRS" again.

Holding WASM crash
Phase: Flight preparation
Sequence of events: Go to secondary flightplan, set DEPARTURE/DESTINATION, select takeoff runway, insert engine out PDB for holding (either as PBD or as stored custom waypoint). Go to lateral revision, add holding. Time for holding is by default 1.5 minutes, if I input "1/" for a one minute holding, I get a WASM crash.

Some other observations:

Airports on ND seem limited
On the ND, no airports further away than ~90nm are displayed, this might be true to the real aircraft, I don't know. I just saw that VORs or NDBs can be displayed further away.

DESC PAGE conversion speed
On DESC PAGE it should be possible to enter [MACH]/[KTS] but gives a format error, it only allows one of the inputs. Preselecting a speed on FCU during descent in level change works however.

Bye

24 minutes ago, justarustyspoon said:

Hi,

Simulator: MSFS24/Sim Update 6
Aircraft: A300-600F PW v.1.0.11 (D-AEAF livery)

Manual construction of alternate route results in messy flightplan
Phase: Cruise

When I want to add a STAR or waypoints before that star for the alternate in the primary flightplan, the first waypoint inserted will be put above the alternate, but it seems like there is one blank line in between when compared to other waypoints. When you scroll down, this waypoint's name will then be overlapped by other texts in the flightplan. A "CLR" to the blank line does not work, but going into the lateral revision of the first waypoint and setting the next waypoint once more as next waypoint at least removes the blank line, but overlapping text after scrolling remains.

Changing approach/STARs
Phase: Cruise
When in cruise, there are situations in which the change of an approach or STAR is blocked. I had this problem when the flightplan was imported via ACARS, for a manually constructed flightplan I can't remember if that happened. This happens for airports which have multiple approaches per category, for example an ILS-Z, ILS-Y etc. and or multiple runways. So far, I can't really pin it down, but it happened for example at BGGH and EGLL.

Let's assume we have a STAR and approach configured during flight preparation, let's call it ILSZ30.
If I go into the STAR page of either the destination airport or the STAR entry waypoint, the STARs, transitions and approaches are not "collapsed" into their respective category, instead all STARs are listed on the left and all approaches are listed on the right, basically what you would see while the approach is uninitialized. Selecting another approach (let's say ILSY30) does however not change anything, it looks like nothing happens. If I however select a VOR30 approach, this approach will be selected and I can reconfigure the STAR, now I can also select other ILS approaches. After inserting this into the flightplan, the new approach is sequenced after the approach which was configured in flight preparation. This happens in primary and secondary flightplan.

IRS Alignment problem with walkaround mode
Phase: Flight preparation

Sequence of events: IRS1/2/3 on, upload flightplan via ACARS, INIT PAGE initialize IRS, EFB open cargo door and set weights to start refueling, go into walkaround mode, start GSX boarding - let it finish, exit walkaround mode after couple of minutes, IRS alignment should be completed by now, but instead the INIT PAGE displays "ALIGN IRS" again.

Holding WASM crash
Phase: Flight preparation
Sequence of events: Go to secondary flightplan, set DEPARTURE/DESTINATION, select takeoff runway, insert engine out PDB for holding (either as PBD or as stored custom waypoint). Go to lateral revision, add holding. Time for holding is by default 1.5 minutes, if I input "1/" for a one minute holding, I get a WASM crash.

Some other observations:

Airports on ND seem limited
On the ND, no airports further away than ~90nm are displayed, this might be true to the real aircraft, I don't know. I just saw that VORs or NDBs can be displayed further away.

DESC PAGE conversion speed
On DESC PAGE it should be possible to enter [MACH]/[KTS] but gives a format error, it only allows one of the inputs. Preselecting a speed on FCU during descent in level change works however.

Bye

Hi,

Thanks for the detailed feedback. There’s a lot of information to go through here, so I’ll do some investigating on my end and report back once I have a better understanding.

Thanks again!