Re: [Flightgear-devel] A320/A330 property errors / missing files

[Josh D. <jos...@gm...>]

Please note:
These are all in the outdated A320 and A330 crafts, not the new ones. The
maintainer of those old has been absent for a long time (6-7 yrs?)

Kind Regards,

--
Josh Davidson

On Fri, Feb 4, 2022, 09:43 James Turner <ja...@fl...> wrote:

> Hey folks,
>
> Chasing down lingering aircraft issues on stable, there’s a large number
> (tens per day) from the A320 and A330 variants. This is with 2020.3.11
> (usually), and the properties seem like ones which should exist:
>
>         FGPropertyValue::GetValue() The property
> /instrumentation/airspeed-indicator/indicated-speed-kt does not exist.
>
>         FGPropertyValue::GetValue() The property
> /instrumentation/pfd/logic/autoland/pitch-land does not exist.
>
>         FGPropertyValue::GetValue() The property fcs/elevator-fbw-output
> does not exist.
>
> .. and so on..
>
> The common feature is that these failures are preceded by a large number
> of missing files, including all the Nasal files:
>
> =========
>
> Error:error-type-not-found from error-aircraft-systems::FGInstrumentMgr:
> Missing instrumentation file
> Error:error-type-not-found from error-aircraft-systems::Autopilot XML not
> found:Aircraft/A320neo/Systems/FMGC/auto-throttle.xml
>         Aircraft/A320neo/Systems/FMGC/auto-throttle.xml
> Cannot find property-rule configuration file
> 'Aircraft/A320neo/Systems/FMGC/auto-throttle.xml'.
> Error:error-type-not-found from error-aircraft-systems::Autopilot XML not
> found:Aircraft/A320neo/Systems/FMGC/aileron-ctrl.xml
>         Aircraft/A320neo/Systems/FMGC/aileron-ctrl.xml
> Cannot find Nasal script 'Aircraft/A320neo/Nasal/mCDU/init_A.nas' for
> module 'mcdu’.
> Cannot find Nasal script 'Aircraft/A320neo/Nasal/procedures/fmsDB.nas' for
> module 'procedures'.
> =======
>
> (above is just a sample, basically it seems almost everything is missing)
>
> I guess that for some reason nearly all the aircraft data files are not
> found, but this only seems to happen for the A320  and its variants (A319,
> neo, etc, etc), and for the A330 and its variants (KC,  Voyager, etc). Is
> there anything special about the file layout that might cause this complete
> failure of all the ancillary files to load? It seems the -set.xml itself is
> present and loads correctly, but almost nothing else does?
>
> One thing to note is these are /not/ aircraft installed via the
> package/hangar system, I don’t know if there is some other common source
> for these aircraft? Maybe people are screwing up the directory name when
> manually adding the aircraft?
>
> Kind regards,
> James
>
>
>
>
>
>
>
>
> _______________________________________________
> Flightgear-devel mailing list
> Fli...@li...
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>