Board index FlightGear Support

doesn't start in launcher

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.

doesn't start in launcher

Postby the_rainmaker » Sun May 20, 2018 9:05 am

when i launch this simulator it starts in plane (cessna) not in launcher where i can (probably) download planes etc.
how to fix it ?
the_rainmaker
 
Posts: 4
Joined: Sun May 20, 2018 8:55 am

Re: doesn't start in launcher

Postby Parnikkapore » Sun May 20, 2018 11:05 am

May we know your operating system? Is it Windows, Mac, Ubuntu, Arch...?

How did you start the program?
There are free alternatives to every program you encounter. You just have to find them.
Parnikkapore
 
Posts: 818
Joined: Thu Oct 29, 2015 10:16 am
Callsign: HS-FGS
Version: next [PPA]
OS: Mint 18

Re: doesn't start in launcher

Postby Necolatis » Sun May 20, 2018 2:40 pm

Linux:

start it using: fgfs --launcher

Windows:

to modify the shortcut, right-click the shortcut and select properties
Add 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


Hangar: https://sites.google.com/site/fghangar/
User avatar
Necolatis
 
Posts: 1945
Joined: Mon Oct 29, 2012 12:40 am
Location: EKOD
Callsign: Leto
IRC name: Neco
Version: 2019.1.2
OS: Windows 10

Re: doesn't start in launcher

Postby the_rainmaker » Mon May 21, 2018 8:08 am

a --launcher at the end was already there
anybody help ?
the_rainmaker
 
Posts: 4
Joined: Sun May 20, 2018 8:55 am

Re: doesn't start in launcher

Postby wkitty42 » Mon May 21, 2018 3:43 pm

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."
User avatar
wkitty42
 
Posts: 5647
Joined: Fri Feb 20, 2015 3:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 14.04.5

Re: doesn't start in launcher

Postby the_rainmaker » Mon May 21, 2018 7:35 pm

my OS is windows (7 and 35 bit)
FlightGear version is 2018.1.1

and (about) 100 lines

general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:451:Created multi-app mutex, we are in writeable mode
general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\main.cxx:466:CrashRpt enabled
general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\main.cxx:493:FlightGear: Version 2018.1.1
general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\main.cxx:494:FlightGear: Build Type Release
general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\main.cxx:495:Built with Microsoft Visual C++ version 1900
general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\main.cxx:497:Jenkins number/ID 231:231
general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2896:platform default fg_root = Path "../data"
general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:532:Reading global defaults
general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:542:Finished Reading global defaults
input:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\globals.cxx:804:Reading user settings from Path "C:/Users/m/AppData/Roaming/flightgear.org/autosave_2018_1.xml"
general:5:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\main.cxx:551:
!Launcher requested, but FlightGear was compiled without Qt support!

general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:1223:init package root at:Path "C:/Users/m/Documents/FlightGear/Aircraft"
input:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2202:No user specified aircraft, using default
general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:267:Loading aircraft -set file from:Path "C:/Program Files/FlightGear 2018.1.1/data/Aircraft/c172p/c172p-set.xml"
aircraft:4:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:373:Aircraft does not specify a minimum FG version: please add one at /sim/minimum-fg-version
general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\locale.cxx:83:Detected user locale:pl-PL
general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\locale.cxx:237:Reading localized strings for 'en' from Path "C:/Program Files/FlightGear 2018.1.1/data/Translations/default/sys.xml"
general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\locale.cxx:237:Reading localized strings for 'en' from Path "C:/Program Files/FlightGear 2018.1.1/data/Translations/default/atc.xml"
general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\locale.cxx:237:Reading localized strings for 'en' from Path "C:/Program Files/FlightGear 2018.1.1/data/Translations/default/tips.xml"
general:5:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\locale.cxx:203:System locale not found or no internationalization settings specified in defaults.xml. Using default (en).
general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2505: option:launcher =
general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2530:Using default download dir: Path "C:/Users/m/Documents/FlightGear"
general:4:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\globals.cxx:394:read-allowed path not found:Path "C:/Users/m/Documents/FlightGear/AI"
general:4:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\globals.cxx:394:read-allowed path not found:Path "C:/Users/m/Documents/FlightGear/Liveries"
general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2555:Using TerraSync dir: Path "C:/Users/m/Documents/FlightGear/TerraSync"
general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\main.cxx:586:EmbeddedResourceManager: selected locale 'pl-PL'
astro:3:C:\Jenkins\workspace\Windows-release\simgear\simgear\scene\sky\cloud.cxx:343:initializing cloud layers
general:4:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\main.cxx:605:Enabling ATI/AMD viewport hack
general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:735:Configuration State
general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:736:======= ==============
general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:738:aircraft-dir = "C:/Program Files/FlightGear 2018.1.1/data/Aircraft/c172p"
general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:739:fghome-dir = "Path "C:/Users/m/AppData/Roaming/flightgear.org""
general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:740:download-dir = "C:/Users/m/Documents/FlightGear"
general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:741:terrasync-dir = "C:/Users/m/Documents/FlightGear/TerraSync"
general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:743:aircraft-search-paths =

general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:744:scenery-search-paths =
C:/Users/m/Documents/FlightGear/TerraSync
C:/Program Files/FlightGear 2018.1.1/data/Scenery
io:4:C:\Jenkins\workspace\Windows-release\simgear\simgear\scene\model\ModelRegistry.cxx:204:Image loading failed:Warning: reading "C:/Program Files/FlightGear 2018.1.1/data/Aircraft/c172p" not supported.
general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\GUI\gui.cxx:122:Intel
general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\GUI\gui.cxx:125:Intel(R) HD Graphics
general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\GUI\gui.cxx:128:4.0.0 - Build 10.18.10.3958
general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\GUI\gui.cxx:138:4.00 - Build 10.18.10.3958
view:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\splash.cxx:678:Splash screen progress loading-aircraft-list
view:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\splash.cxx:678:Splash screen progress loading-nav-dat
navaid:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\NavDataCache.cxx:261:NavCache at:Path "C:/Users/m/AppData/Roaming/flightgear.org/navdata_2018_1.cache"
navaid:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\NavDataCache.cxx:264:NavCache read-only flags is:0
navaid:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\NavDataCache.cxx:1347:NavCache: no main cache rebuild required
view:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\splash.cxx:678:Splash screen progress init-scenery
general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:701:General Initialization
general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:702:======= ==============
general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:711:FG_ROOT = "Path "C:/Program Files/FlightGear 2018.1.1/data""

general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\positioninit.cxx:331:Attempting to set starting position for PHNL:04L
event:3:C:\Jenkins\workspace\Windows-release\simgear\simgear\timing\sg_time.cxx:84:Reading timezone info from: Path "C:/Program Files/FlightGear 2018.1.1/data/Timezone/zone.tab"
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\scenery.cxx:353:Selected scenery is tilecache
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\terrain_stg.cxx:244:FGStgTerrain::init - init tilemgr
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:156:Initializing Tile Manager subsystem.
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilecache.cxx:64:Initializing the tile cache.
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilecache.cxx:67: max cache size = 100
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilecache.cxx:69: current cache size = 0
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilecache.cxx:73: done with init()
view:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\splash.cxx:678:Splash screen progress finalize-position
view:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\splash.cxx:678:Splash screen progress creating-subsystems
general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:753:Creating Subsystems
general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:754:========== ==========
input:3:C:\Jenkins\workspace\Windows-release\simgear\simgear\scene\material\matlib.cxx:74:Reading materials from C:/Program Files/FlightGear 2018.1.1/data/Materials/regions/materials.xml
systems:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Systems\system_mgr.cxx:41:Reading systems from Path "C:/Program Files/FlightGear 2018.1.1/data/Aircraft/c172p/Systems/systems.xml"
cockpit:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Instrumentation\HUD\HUD.cxx:116:Initializing HUD Instrument
sound:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Sound\fg_fx.cxx:122:Reading sound sound from Path "C:/Program Files/FlightGear 2018.1.1/data/Aircraft/c172p/c172-sound.xml"
general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\main.cxx:327:Creating subsystems took:50828
view:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\splash.cxx:678:Splash screen progress binding-subsystems
general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\main.cxx:335:Binding subsystems took:300
view:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\splash.cxx:678:Splash screen progress init-subsystems
general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\locale.cxx:237:Reading localized strings for 'en' from Path "C:/Program Files/FlightGear 2018.1.1/data/Translations/default/menu.xml"
input:4:C:\Jenkins\workspace\Windows-release\flightgear\src\GUI\new_gui.cxx:373:dialog Path "C:/Program Files/FlightGear 2018.1.1/data/Aircraft/c172p/gui/dialogs/c172p-menu.xml" has no name; skipping.
general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\GUI\FGPUIMenuBar.cxx:56:Initializing old dialog commands:
environment:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Environment\realwx_ctrl.cxx:325:Reusing metar properties at /environment[0]/metar[0] for
environment:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Environment\realwx_ctrl.cxx:335:Adding metar properties at /environment[0]/metar[1] for
environment:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Environment\realwx_ctrl.cxx:335:Adding metar properties at /environment[0]/metar[2] for
environment:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Environment\realwx_ctrl.cxx:335:Adding metar properties at /environment[0]/metar[3] for
environment:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Environment\realwx_ctrl.cxx:335:Adding metar properties at /environment[0]/metar[4] for
environment:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Environment\realwx_ctrl.cxx:335:Adding metar properties at /environment[0]/metar[5] for
environment:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Environment\realwx_ctrl.cxx:335:Adding metar properties at /environment[0]/metar[6] for
environment:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Environment\realwx_ctrl.cxx:335:Adding metar properties at /environment[0]/metar[10] for
environment:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Environment\realwx_ctrl.cxx:335:Adding metar properties at /environment[0]/metar[11] for
environment:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Environment\realwx_ctrl.cxx:390:NoaaMetarRealWxController::update(): nearest airport with METAR has changed. Old: '', new: 'PHNL'
environment:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Environment\realwx_ctrl.cxx:481:NoaaMetarRealWxController::update(): spawning load request for station-id 'PHNL'
astro:3:C:\Jenkins\workspace\Windows-release\simgear\simgear\ephemeris\stardata.cxx:58: Loading stars from Path "C:/Program Files/FlightGear 2018.1.1/data/Astro/stars"
astro:3:C:\Jenkins\workspace\Windows-release\simgear\simgear\ephemeris\stardata.cxx:114: Loaded 3141 stars
autopilot:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "C:/Program Files/FlightGear 2018.1.1/data/Environment/metarinterpolator.xml"
autopilot:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding property-rule subsystem Environment METAR Interpolation Rule
autopilot:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "C:/Program Files/FlightGear 2018.1.1/data/Environment/interpolator.xml"
autopilot:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding property-rule subsystem Environment Interpolation Rule
autopilot:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "C:/Program Files/FlightGear 2018.1.1/data/Environment/local-weather-rules.xml"
autopilot:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding property-rule subsystem Local Weather Rules
autopilot:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "C:/Program Files/FlightGear 2018.1.1/data/Aircraft/Generic/g-forces.xml"
autopilot:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding property-rule subsystem g force effects
autopilot:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "C:/Program Files/FlightGear 2018.1.1/data/Aircraft/c172p/Systems/instruments.xml"
autopilot:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding property-rule subsystem FiltersOnly
autopilot:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "C:/Program Files/FlightGear 2018.1.1/data/Aircraft/c172p/Systems/ground-effects.xml"
autopilot:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding property-rule subsystem unnamed_autopilot_101
autopilot:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "C:/Program Files/FlightGear 2018.1.1/data/Aircraft/c172p/Systems/als-lights.xml"
autopilot:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding property-rule subsystem unnamed_autopilot_102
autopilot:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "C:/Program Files/FlightGear 2018.1.1/data/Aircraft/c172p/Systems/engine.xml"
autopilot:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding property-rule subsystem unnamed_autopilot_103
autopilot:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "C:/Program Files/FlightGear 2018.1.1/data/Aircraft/c172p/Systems/damage.xml"
autopilot:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding property-rule subsystem unnamed_autopilot_104
autopilot:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "C:/Program Files/FlightGear 2018.1.1/data/Aircraft/c172p/Systems/pax.xml"
autopilot:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding property-rule subsystem unnamed_autopilot_105
autopilot:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "C:/Program Files/FlightGear 2018.1.1/data/Aircraft/c172p/Systems/views.xml"
autopilot:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding property-rule subsystem unnamed_autopilot_106
autopilot:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "C:/Program Files/FlightGear 2018.1.1/data/Aircraft/c172p/Systems/sounds.xml"
autopilot:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding property-rule subsystem unnamed_autopilot_107
autopilot:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "C:/Program Files/FlightGear 2018.1.1/data/Aircraft/c172p/Systems/electrical.xml"
autopilot:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding property-rule subsystem unnamed_autopilot_108
systems:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:63:FlightRecorder: Recorder configuration #0
the_rainmaker
 
Posts: 4
Joined: Sun May 20, 2018 8:55 am

Re: doesn't start in launcher

Postby wlbragg » Mon May 21, 2018 8:22 pm

Where did you download FlightGear from?

Right click on the FlightGear.exe then select properties, does the "target" field look like this
"C:\Program Files\FlightGear 2018.1.1\bin\fgfs.exe" --launcher
including quotes?


Doesn't matter your log shows
Launcher requested, but FlightGear was compiled without Qt support!


So where did you download it from?
Kansas(2-27-15)/Ohio/Midwest scenery development.
KEQA (2-27-15), 3AU, KRCP Airport Layout
User avatar
wlbragg
 
Posts: 4889
Joined: Sat Aug 25, 2012 11:31 pm
Location: Kansas (Tornado Alley), USA
Callsign: WC2020
Version: next
OS: Win10/Debain/nVGT640

Re: doesn't start in launcher

Postby wkitty42 » Tue May 22, 2018 2:40 am

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."
User avatar
wkitty42
 
Posts: 5647
Joined: Fri Feb 20, 2015 3:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 14.04.5

Re: doesn't start in launcher

Postby the_rainmaker » Tue May 22, 2018 8:02 am

okay i will wait ...
the_rainmaker
 
Posts: 4
Joined: Sun May 20, 2018 8:55 am

Re: doesn't start in launcher

Postby wkitty42 » Tue May 22, 2018 10:50 pm

the release candidate is out now... it looks like there's only one .exe but i don't know if it is 32bit or 64bit...

https://sourceforge.net/projects/flightgear/files/release-candidate/
"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."
User avatar
wkitty42
 
Posts: 5647
Joined: Fri Feb 20, 2015 3:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 14.04.5


Return to Support

Who is online

Users browsing this forum: No registered users and 7 guests