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

[James T. <ja...@fl...>]

> On 4 Feb 2022, at 15:20, Jonathan R <leg...@gm...> wrote:
> 
> All these errors are entirely due to users not reading the installation instructions and not renaming the folder. I get these bug reports quite regularly as well. It's very frustrating that users don't seem to find or read the installation instructions. There's nothing I can do to fix this, other than to make use of the new feature in 2020.3 to specify the "expected aircraft directory". 
> 
> >  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'.
> 
> These specifically are from the old A320 from artix75 which I can't fix.
> 
> Josh, I don't think that's entirely correct -- yes, the error listed are from the artix A320, but the first errors are definitely from the A320-family -- they occur when the folder name is not renamed.

Hehe, these kind of issues are exactly why I originally designed the hangar system all those years ago, since it was clear many users screwed up the installation process :) 

The ‘expected aircraft dir’ feature will help us for the future, what I’m wondering is to maybe add a heuristic list in a file, to detect this problem. Since it looks as if detect about eight or ten cases, would catch a huge % of the problems in practice. Basically lettings us retro-actively specify the expected aircraft dir based on the -set.xml name, for those common ones. (And show some prompt to the user like ‘aircraft A320 is not installed correctly’)

I wonder why it’s so prevalent for the A330 and A320 : is it because the dir name inside the zip *needs* to be renamed? Or just that those aircraft are very popular, so the issue shows up more?

Kind regards,
James