ATC FLT NBR in ATC/CONNECTION/NOTIFICATION not filled or disappearing

[AdrienR]

Aircraft Version

Stable

Build info

{
    "built": "2024-11-26T16:07:50+00:00",
    "ref": "refs/heads/master",
    "sha": "cf3a5f10c4eadf3423e2ca40503960e93ae9d414",
    "actor": "Saschl",
    "event_name": "manual",
    "pretty_release_name": "master:cf3a5f10",
    "version": "a32nx-v0.13.0-dev.cf3a5f1"
}

Describe the bug

When i load a flightplan from SimBrief into the MCDU (ATSU -> AOC -> INIT DATA RAQ then Init page -> INIT REQUEST) then i go to ask a clearance into the ATSU -> ATC -> GROUND REQ. There, i can get two behavior :

• the ATC FLT NBR being dashed, filling the ATC CENTER results in ENTER ATC FLT NBR ;
• the ATC FLT NBR is filled, and i can enter the ATC CENTER, and it's working, BUT the ATC FLT NUMBER will reset to dashes few seconds after

I can retry using the MCDU reset "feature" (DATA -> A/C status, 2e database), the first case is happening the most of the time.

Expected behavior

The ATC FLT NBR is filled, and i can enter the ATC CENTER, and it's working.

Steps to reproduce

1. Load a flightplan from SimBrief into the MCDU
2. In the MCDU: ATSU -> AOC -> INIT DATA RAQ then Init page -> INIT REQUEST)
3. Then go to ask a clearance into the ATSU -> ATC -> GROUND REQ. There, i can get two behavior :
   4.1. the ATC FLT NBR being dashed, filling the ATC CENTER results in ENTER ATC FLT NBR ;
   4.2. the ATC FLT NBR is filled, and i can enter the ATC CENTER, and it's working, BUT the ATC FLT NUMBER will reset to dashes few seconds after

References (optional)

You can find a video showing the second case here: https://youtu.be/5zNX67QYzVM

Additional info (optional)

When i enter the ATC CENTER and hit NOTIFY in the right timeperiod, i'm able to use ACARS message (through hoppie software) even if the ATC FLT NUMBER is deleted.

I notice a random latency (from instant to nearly 1 minute) when sending/receiving messages. I want to investigate on the network side (my connexion doesn't seems reliable for now), is there a log file somewhere about the MCDU/ATSU/ACARS network requests ? If i can confirm this is network related, eventually adding a warning in the EFB would be a nice aid to debug this.

Using Windows 11, MSFS 2020 and FBW A320 (stable & devel), all up to date.

Discord Username (optional)

No response

[AdrienR]

Noticed that the steps to reproduce are simpler : just enter a random flt nbr into the init page, then go to ATC / CONNECTION / NOTIFICATION page. And retry if necessary.
Is there someone who knows where are the log files ?