Tutorial: How to get Aircraft Center to work

[someguy]

Step 5 is where you will find it if I understand correctly, a subfolder obviously of flightgear.org

As a Mac user, I did not perform step 5, and no such path exists on my machine. However, I did eventually find the new Beaver, in the "standard" downloads folder, not used by anything else. There's a warning about changing it, and I am not confident I can predict what will happen when I consolidate it with my existing hangar folder. But I have a backup, so maybe tomorrow I'll attempt to thrash FG's resources into some sort of logical order, rather than scattered willy-nilly inside and outside the application.

Thanks to each of you who, with no insight into a Mac installation, offered enough clues to aim me vaguely in the right direction.

[wkitty42]

FWIW: zakalaw (aka james) is looking into these problems... as i have the entire FGAddon repo, i see a problem with all craft with variants... it seems that when one downloads and installs using the --launcher, something else is done to make the variants work... i listed all of the craft with this problem in a post to the dev list earlier yesterday (2016 Feb 25) and james is now looking into the problem with having a library of craft already installed...

[jaxsin]

good to know you are a mac user. This is still borked on windows. Not sure if there is any extra info here that would help the devs or not

[wkitty42]

@jaxsin: are you responding to me or swampthing's post above mine??

[jaxsin]

@wkitty it was meant towards someguy

Has anyone with and a not so default install location mange to get this to work?

[someguy]

I gathered all my aircraft, scenery, and other resources into a ~/flightgear folder. I eventually flogged fg into finding my planes and scenery, but Aircraft Center installs still go into hiding under their usual rock. Unfortunately, most of my settings got lost, and I have no idea where they are stored so I can fish them out of a backup. I can't remember the syntax of some of my --prop startup commands, e.g., how to get the NTPS HUD to display by default. The wiki wasted an hour of my time in futile searches (no big surprise there). Anyone know where the "Additional Options" are filed?

[jaxsin]

these http://wiki.flightgear.org/Command_line_options

[someguy]

Sorry, I didn't mean the somewhat-helpful wiki page, which I'd aleady found. I mean the actual storage location on my disk of those launcher settings. They must be somewhere, as they persist across launches.

[rominet]

I don't use the Qt launcher, but my bet would be: as indicated under Platform-Specific Notes in the Qt5 doc for QSettings. And feel free to improve the wiki if it wasted so much of your precious time. This is community work, you know.

Edits: fix typo and replace “Aircraft Center” with “Qt launcher” (despite the thread subject). And add smileys for good measure.

[Necolatis]

For all of you who got it to work, here is a another catalog you can add. It is from David Culp and contains all his planes: http://www.daveshangar.org/catalog.xml

[someguy]

So, nobody knows where those commands are stored, eh?

[rominet]

Did you look at the places given in the link I posted? Specifically, here?

[wkitty42]

on linux the --launcher currently places its settings in

~/.config/FlightGear/FlightGear.conf

on osx, i would guess that this would be

$HOME/Library/Preferences/FlightGearsomethingorother

the additional arguments box in the --launcher is represented in this file as one long line starting with "additional-args="... that long line is wrapped with double-quotes and each line in the box is terminated with a "\n" so you get something like this...

Code: Select all

[General]
additional-args="#--disable-ai-models\n#--disable-ai-traffic\n--disable-fgcom\n--disable-random-buildings\n--disable-random-objects\n--disable-random-vegetation\n#--disable-terrasync\n"
another-setting-here=blah
something-else-here=blerg


[someguy]

For the benefit of anyone searching in the future, in Mac OS X the additional commands are stored at the end of this file (nearly the only part readable in TextEdit):

[userhome]/Library/Preferences/org.flightgear.FlightGear.plist

Be careful, as they appear to be duplicated.

To spawn with the NTPS HUD enabled, add these commands:

Code: Select all

--enable-hud
--prop:/sim/hud/visibility=false
--prop:/sim/hud/visibility[1]=true
--prop:/sim/hud/path[1]=Huds/NTPS.xml

There may be a better way, but this works.

[jaxsin]

would the --config directive work? fgcamera uses this to load the fgcamera_cfg.xml file

fgcamera example
--config=D:/flightgear_dev/data/Nasal/fgcamera/fgcamera_cfg.xml