Can't locate A320-family (as if the file is invisible)

[enriqueyow]

Hi,

I tried to use A320-family to start up my flight gear using sh file, flight gear could be launched but it gave me such error:

The requested aircraft (A320-family) could not be found in any of the search path.

It failed to locate the file. I have no issues on running with other aircrafts.

I wonder if I should isolate a specific aircraft type in the A320-family file?

Does anyone here knows how to fix that? Thank you in advanced.

Catalina
Flightgear 2018.3.5

[legoboyvdlp]

Hi,

You cannot use the A320-family (presuming you mean, the newer version) with 2018.3.5, unfortunately, as it is not compatible with version prior to 2019.2.0.

For 2018.3.5 you could download it from:

http://mirrors.ibiblio.org/flightgear/f ... family.zip

It is rather lower in quality, however, whenever 2020.2 is released (or else, you update to 2020.1), then the newer version will be compatiable

In terms of your specific issue, I believe it is because you did not remove -dev from the folder name, when downloading from GitHub, it is required to remove the appended branch (usually -master) from the folder name.

Hope this helps!

[enriqueyow]

Hi,

Thank you for the reply!

I downloaded the file you attached and it didn't work this time too There is no -dev from the folder name. Do you think it's really the flight gear version's problem? Maybe I should try the 2020.1 release.

Thank you for answering!

[legoboyvdlp]

The one I linked is for 2018.3.5, and doesn't have -dev in it. But, yeah to use the more modern A320-family you will need 2020.1 or later.


You actually should download aircraft through the launcher in any case -- much easier!

[enriqueyow]

Hi,

I will try what you have suggested!

Once again, thank you very much

[enriqueyow]

Apparently the aircraft works if I open it using the launcher. If I use the terminal .bat / .sh file to launch flight gear, it couldn't locate the folder.

I'm using the terminal way to launch flight gear because I'm connecting it to Simulink.

I guess I will have to drop the idea on using A320 for now

[Johan G]

If you need start parameter for Simulink, you can write it in the launcher under 'Settings' -> 'Additional Settings'.

[Gijs]

If I use the terminal .bat / .sh file to launch flight gear, it couldn't locate the folder.

Could you share the contents of your file? It sounds like you didn't point FlightGear (correctly) to the aircraft folder where you've installed the A320.

[enriqueyow]

The code of the sh file is as follow:

#! /bin/sh

cd /Applications/FlightGear.app/Contents/Resources

./../MacOS/fgfs --fg-root=./ --aircraft=A320-family --fdm=network,localhost,5501,5502,5503 --fog-fastest --disable-clouds --start-date-lat=2004:06:01:09:00:00 --disable-sound --in-air --enable-freeze --airport=KSFO --runway=10L --altitude=7224 --heading=113 --offset-distance=4.72 --offset-azimuth=0 --prop:/sim/rendering/shaders/quality-level=0


It works for other aircraft such as a340-600, a380, 747-8i etc using the same file. Maybe it's like what legoboyvdlp said, it's not compatible with version 2018.3.5.


Using:
macOS Catalina
flightgear 2018.3.5
Matlab r2019b

[Maerchenprinz]

Hi!

Not knowing anything about Mac, I think there is a totally independent solution of that anyway (and an easy one as well!):
As FG does not look at the folder names ("A320-family") but at the *-set.xml files inside, simply change

Code: Select all

--aircraft=A320-family

Into e.g.

Code: Select all

--aircraft=A320-100-CFM

Hope that helps!

Ciao,

Adrian

[Gijs]

In addition to what Adrian said, you probably also need to add the following command, unless you've added the aircraft to fgroot (not recommended). From the fact that it works for other aircraft, you've probably installed them in fgroot, so then you won't need this command and only using Adrian's trick will do

Code: Select all

--fg-aircraft=path/to/the/folder/where/your/aircraft/is/located

Have fun!

Gijs

[enriqueyow]

Thank you everyone for the reply!!!

It worked using the mentioned trick!. It was so frustrating before because I was using other aircraft for the visualization of my work on the A320.

Once again, thank you!!!