All general support: help on flying, installation, hardware, getting online etc. There are lots of users and developers to help you out.

Forum rules
In order to help you, we need to know a lot of information. Make sure to include answers to at least the following questions in your initial post.

- what OS (Windows Xp/Vista, Mac etc.) are you running?- what FlightGear version do you use?- what graphics card do you have?- does the problem occur with any aircraft, at any airport?- where did you download your aircraft/scenery from?- is there any output printed to the console (black window)?- copy&paste your commandline (tick the "Show commandline box on the last page of FGRun or the "Others" section on the Mac launcher).

If you experience FlightGear crashes, please report a bug using the issue tracker (can be also used for feature requests).To run FlightGear on old computers with bad OpenGL support, please take a look at this wiki article.

Note: If you did not get a reponse, even after 7 days, you may want to check out the FlightGear mailing lists to ask your question there.

to modify the shortcut, right-click the shortcut and select propertiesAdd this to the end of target field: --launcher(remember to put a space before it.For example target would look like this:"C:\Program Files\FlightGear 2018.1.1\bin\fgfs.exe" --launcher

"Airplane travel is nature's way of making you look like your passport photo."— Al Gore

somehow you posted this in the wrong area... i'll get a moderator to move it...

anyway, there's normally a pink box at the top in the support area... that box asks for certain information... in this case, we need to know

1. what OS are you running?2. which version of flightgear are you running?

i'm going to guess you are running windows since you responded to Necolatis' post as if you edited the shortcut on windows... so, click your start button and type "%APPDATA%" without the quotes and hit enter... a window should open where you can find a flightgear folder... inside that folder is a fgfs.log file... please post the top 100 lines or so in a reply here...

"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up.""Why not?" said Gurder."Dunno. It's frightened of heights, I guess."

the_rainmaker wrote in Mon May 21, 2018 7:35 pm:general:5:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\main.cxx:551:!Launcher requested, but FlightGear was compiled without Qt support!

this is why you cannot get to the launcher... there was a flaw in the build process that causes Qt to be missed for the 32bit build... the 64bit build was OK... i thought this was fixed and a new installer built but i'll ask on the dev list to make sure... we do have a thread on the list titled "new 2018.1.1 32bit release has no Qt??" so i know it was discussed... you might try downloading the 2018.1.1 32bit installer again but you might want to wait until we get an answer to my question on the list...

in the mean time, we're trying to get 2018.2.1 out the door... it has just been branched and the release candidates should be appearing in the next day or so...

"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up.""Why not?" said Gurder."Dunno. It's frightened of heights, I guess."

"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up.""Why not?" said Gurder."Dunno. It's frightened of heights, I guess."