Hi,
the Maddogs FMC shows NOT IN DATABASE when I enter some well known ICAO airport codes like EDDM, EDDL, EHAM and others. It however knows other airports (I tried LOWI and KJFK). Are there any known problems with the current AIRAC data, or can someone reproduce the problem?
Thanks
AIRAC 2506
Fly the Maddog X
MSFS 2024
Hi,
We can’t reproduce it or have any reports on this issue. How have you updated the Maddog? Via the Hub?
Cheers
Richard
Hi Richard,
exactly, I have loaded the navdata via the Hub. Both, for the Fly the Maddog X and the Fly te Maddog X EFB. There are no errors displayed on the Hubs UI.
Cheers
Falk
Correction: EDDM works - my bad. Others like EDDL, EHAM, EBBR, EKCH don’t. For clarity EDDM also worked whe I have opened this topic, I just didn’t remembered correctly.
What Hub version do you use?
Cheers
Richard
I’m using version 1.2.15.
Cheers
Falk
Hi Falk,
Thanks for the info … Ok, the Hub is up to date. The main issue is more on the Maddog side.
Since SU2 in MSFS2024, ASOBO has implemented a new logic.
There are now two important things:
The Hub still supports #2 with your version, but #1 can only be solved by the addon developer, because they must move the location into the correct place/working folder.
We have made a re-check with the Maddog devs, and they haven’t made this change till now - expecting after FSExpo.
We can’t do anything here; we must wait for the fix from Maddog first. It’s a pity, I know, but this change in SU2 was also new for us.
Cheers
Richard
Hi Richard,
Thank you for the insights. For me, it’s good news that this isn’t some weird issue with my system, but rather an identified problem. Leonardo’s Maddog has been around for many years and remains an outstanding simulation. I’m optimistic that there will be a fix.
Is it possible to narrow down the effects of this issue, or could it affect different airports, navaids, or fixes on different systems?
Cheers
Falk
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.