FlightGear Qt launcher: Difference between revisions

Jump to navigation Jump to search
Move background up, change preferences heading level, add some clarifications
m (https://forum.flightgear.org/viewtopic.php?f=25&t=28877&start=90#p284607)
(Move background up, change preferences heading level, add some clarifications)
Line 54: Line 54:


As of May 2016, the Qt launcher is under active development. This includes the adding of new features, fixing bugs, and refining existing features.
As of May 2016, the Qt launcher is under active development. This includes the adding of new features, fixing bugs, and refining existing features.
== Background ==
In accordance with the [[FlightGear 4.xx Roadmap]], FlightGear's current graphical interface (based on the [[PUI]] library of [[PLIB]]) will be replaced by one based on Qt. [[FGRun]] will also be removed in future to be replaced by this launcher. In addition, a browser-based UI (called [[Phi]]) will continue to be developed in parallel.<ref>{{cite web
|url=https://forum.flightgear.org/viewtopic.php?f=18&t=25115#p229445
|title=Re: New Canvas GUI
|author=Torsten
|date=Jan 10th, 2015
}}</ref> This will result in the following user interface:
* Qt launcher
* Internal UI based on Qt, possibly with [[Canvas]] integration
* External browser-based UI (Phi)
However, it should be made clear that Qt will always remain an optional dependency.<ref name="GUIquestions">{{cite web
|url    = https://sourceforge.net/p/flightgear/mailman/message/34532040/
|title  = <nowiki>[Flightgear-devel] GUI questions (again)</nowiki>
|author = James Turner
|date  = Oct 11th, 2015
}}</ref>


== Usage ==
== Usage ==
Line 72: Line 90:


=== Multiplayer connections ===
=== Multiplayer connections ===
As the launcher is still under development, only some basic options are present; notably, no multiplayer option is shown. To connect to the multiplayer servers, either:
As the launcher is still under development, only some basic options are present. Notably, no multiplayer option is shown. To connect to the multiplayer servers, you can do either of the following:
* start FlightGear from the launcher and then choose '''Multiplayer''' -> '''Multiplayer Settings''' inside the simulator;
* Start FlightGear from the launcher and then choose {{menu item|Multiplayer|Multiplayer Settings}} inside the simulator.
* or open the '''Settings''' tab in the launcher and specify the following parameters:
* Open the '''Settings''' tab in the launcher and specify the following parameters:
<syntaxhighlight lang="shell">
<syntaxhighlight lang="shell">
--console --multiplay=out,10,mpserver01.flightgear.org, --multiplay=in,10,, --callsign=mycallsign
--multiplay=out,10,mpserver01.flightgear.org, --multiplay=in,10,, --callsign=mycallsign
</syntaxhighlight>
</syntaxhighlight>
replacing ''mpserver01.flightgear.org'' with the multiplayer server to be used and ''mycallsign'' with the desired callsign.
replacing ''mpserver01.flightgear.org'' with the multiplayer server to be used and ''mycallsign'' with the desired callsign. Note that a callsign can only be 7 characters long.


=== Enabling console display on Windows systems ===
=== Enabling console display on Windows systems ===
To enable console display on Windows systems, right-click on the FlightGear shortcut on the Desktop and click '''Properties'''. In the '''Target''' box, add <tt>--console</tt> at the end and click '''OK'''.
To enable console display on Windows, right-click on the FlightGear shortcut on the Desktop and click '''Properties'''. In the '''Target''' box under the '''Shortcut''' tab, add <tt>--console</tt> at the end and click '''OK'''.


=== Aircraft/TerraSync download directory ===
=== Aircraft/TerraSync download directory ===
Line 93: Line 111:
}}</ref>
}}</ref>


== Preferences ==
=== Preferences ===
In FlightGear 2016.2 and later, the preferences are stored in ''[[$FG_HOME]]/flightgear.org/FlightGear.ini''.<ref name="LauncherChanges" /> Older versions make use of the default location used by Qt:
In FlightGear 2016.2 and later, the preferences are stored in ''[[$FG_HOME]]/flightgear.org/FlightGear.ini''.<ref name="LauncherChanges" /> Older versions make use of the default location used by Qt:
* the Registry on Microsoft Windows;
* the Registry on Microsoft Windows;
Line 107: Line 125:
| added  = Nov 23rd, 2015
| added  = Nov 23rd, 2015
| script_version = 0.23
| script_version = 0.23
}}</ref>
== Background ==
In accordance with the [[FlightGear 4.xx Roadmap]], FlightGear's current graphical interface (based on the [[PUI]] library of [[PLIB]]) will be replaced by one based on Qt. [[FGRun]] will also be removed in future to be replaced by this launcher. In addition, a browser-based UI (called [[Phi]]) will continue to be developed in parallel.<ref>{{cite web
|url=https://forum.flightgear.org/viewtopic.php?f=18&t=25115#p229445
|title=Re: New Canvas GUI
|author=Torsten
|date=Jan 10th, 2015
}}</ref> This will result in the following user interface:
* Qt launcher
* Internal UI based on Qt, possibly with [[Canvas]] integration
* External browser-based UI (Phi)
However, it should be made clear that Qt will always remain an optional dependency.<ref name="GUIquestions">{{cite web
|url    = https://sourceforge.net/p/flightgear/mailman/message/34532040/
|title  = <nowiki>[Flightgear-devel] GUI questions (again)</nowiki>
|author = James Turner
|date  = Oct 11th, 2015
}}</ref>
}}</ref>


Navigation menu