I'll probably add the #--multiplay=out,10,127.0.0.1,5000 --multiplay=in,10,127.0.0.1,5001 example to the default config, because I think the more aircraft developers know about it, the better their models are likely to be MP-wise.
Just for the record, related to --enable-real-weather-fetch: I still believe it is not useful anymore, but
according to llsouder, --disable-real-weather-fetch
is useful to have --metar work...
chris_blues wrote in Wed Mar 16, 2016 11:25 pm:On my 1920x1080 screen this looks much better. I can see some instruments without having to fiddle in the property-browser. Because every time you look around (aka move the view), when you click it snaps back to forward view and default-field-of-view. If it's set to sth else (most aircraft set this to some value) I only see the top-most instrument borders and a lot of scenery...
For a similar purpose, I use
this patch to allow easy saving and reloading custom persistent views with keyboard shortcuts. So, usually when starting with an aircraft, I save the default view with Windows-F1, then my preferred “general” view with Windows-F2 and a few other views that seem useful, then restart FG (the patch in its current state only saves views when FG is quit). Starting from this point, I can recall the aircraft default view with Ctrl-F1, my preferred “general” view with Ctrl-F2, and so on. This is very convenient, especially for views that take time to tune, as when you want to watch the cabin temperature in the c172p.
Note: all views are saved per-aircraft in
$FG_HOME/aircraft-data/<aircraft>-views.xml.
I see
. Especially if, like the extra500, it then says you threw x thousand dollars out of the window!
Concerning --prop:/sim/menubar/autovisibility/enabled=1: since you are unlikely to want to switch it on or off depending on the particular aircraft/flight/etc., one good way IMHO to declutter your FFGo Options Window is to put this setting in a file such as
$FG_HOME/YourName/my-preferences.xml that looks like this:
- Code: Select all
<?xml version="1.0" encoding="UTF-8"?>
<PropertyList>
<sim>
<menubar>
<autovisibility>
<enabled type="bool">true</enabled>
</autovisibility>
</menubar>
</sim>
</PropertyList>
and then load this file with the following fgfs option:
- Code: Select all
--config=/home/you/.fgfs/YourName/my-preferences.xml
This way, such settings can even by trivially shared with other launchers or used on the fgfs command line, by simply passing --config=/home/you/.fgfs/YourName/my-preferences.xml. For the record, the complete contents of this file in my case is:
- Code: Select all
<?xml version="1.0" encoding="UTF-8"?>
<PropertyList>
<sim>
<menubar>
<autovisibility>
<enabled type="bool">true</enabled>
</autovisibility>
</menubar>
</sim>
<!-- Inspired by <http://forum.flightgear.org/viewtopic.php?f=25&t=26145> -->
<gui>
<map>
<aircraft-heading-up type="string" userarchive="y">0</aircraft-heading-up>
<centre-on-aircraft type="bool" userarchive="y">true</centre-on-aircraft>
<draw-data type="bool" userarchive="y">false</draw-data>
<draw-fixes type="string" userarchive="y">1</draw-fixes>
<draw-flight-history type="bool" userarchive="y">false</draw-flight-history>
<draw-navaids type="string" userarchive="y">1</draw-navaids>
<draw-traffic type="string" userarchive="y">1</draw-traffic>
<magnetic-headings type="bool" userarchive="n">true</magnetic-headings>
<transparent type="string" userarchive="y">1</transparent>
<!-- <zoom type="int" userarchive="n">5</zoom> -->
</map>
</gui>
<input>
<keyboard>
<key n="265">
<name>F9</name>
<desc>Toggle pilot list</desc>
<binding>
<command>nasal</command>
<script>multiplayer.dialog.toggle()</script>
</binding>
<!-- Commented out for now
binding>
<command>dialog-show</command>
<dialog-name>chat-full</dialog-name>
</binding -->
</key>
</keyboard>
</input>
</PropertyList>
(I have put only one keyboard shortcut here, but I think it is a good way to override most keyboard shortcuts without having to patch
$FG_ROOT/keyboard.xml—which obviously causes hassles if you are using the
FGData Git repo, or when just upgrading FG).
About --httpd=8080 or --httpd=127.0.0.1:8080:
It seems you are right on this point. At least static testing with the 707 on the 02 runway at LEBL in FG 2016.2.0 doesn't show any noticeable difference in fps for me. That is good news.
All in all, I think I may add commented out options to the default config for:
- The --multiplay option allowing to test multiplayer stuff with one computer only and without going through the MP servers;
- the --httpd option to start Phi;
- Maybe an example of --disable-real-weather-fetch in conjunction with a --metar=... sample option, for those who want to repeatedly practice landings or whatever they want in particular weather conditions.
I don't want to add too many, otherwise it is likely to frighten newcomers if they think they have to read and understand all these things (plus, it's a kind of a pain to translate, as you know
, and such comments/options are likely to remain in users' configs for a very long time even after being deprecated on the FG side).
I don't claim the rest is useless, not at all, but IMO its place is not in the default config (and I don't claim you claimed it all had to go in the default config!). I'm thinking that, if you want to share these other options with other users, e.g., the one that may save your life when you have to pee or so
, then maybe a section such as “User selection of options” or “User favorites”, or “User tips”, at the end of
http://wiki.flightgear.org/Command_line_options would do well. Contrary to the official documentation of these options—which doesn't necessarily exist for properties, BTW—you would be free to explain your use cases in all their glorious context.
Concerning the dropdown list for --timeofday:
chris_blues wrote in Wed Mar 16, 2016 11:25 pm:No, haven't played much with this, but this big list of options, with only one of them uncommented is very annoying. On the other hand I'm much too lazy to always look up the possible values. A dropdown would take up a very small box, whereas these lines take up much more...
One possibility to use less space is to write it as:
- Code: Select all
--timeofday=noon # dawn,morning,noon,afternoon,evening,dusk,midnight
Granted, you have to do a bit more than just add or remove a comment char (#) in this case, but this saves a few lines.
But
I also have a space problem with your suggestion. On my 1920x1080 screen, the FFGo main window fills the whole screen in font size 12. There isn't much space to add anything without reducing something else or making things look ugly. And I don't like the idea of having to check several tabs or windows in order to choose or verify the essential parameters before starting FG. I have no problem with the Airport Finder or GPS Tool or whatever dialogs I added recently, because they have no influence whatsoever on the fgfs parameters, thus you don't have to check these Windows before starting FG.
One way to add the feature while respecting these constraints, if it's really deemed useful to be able to set the time of day via a GUI control, would be to have a separate window reachable from a menu that, by default, wouldn't influence the --timeofday option at all, but would override it when the user does "click click" in the window in question to select a particular time of day. This would certainly work, but I don't see much gain compared to just starting FG and changing the time via Environment -> Time settings...
jaxsin wrote in Thu Mar 17, 2016 1:45 am:The --trim option for JSBsim is for when the airplane is initially placed on the runway or ground I believe. I have a local airport that is sort of on a hill in FG and when the Cessna is loaded you get a trim error message in console. So it seems to have to do with placement on un-level surfaces? Not really sure, erik would be the one to ask.
Uhhhm, okay... Thanks for your comment.