Hi Dave, I pretty much understand what you sent...except for the last line of the launch script. Should that be (for my script) the path to my FlightGear file? thx, rlm
On Fri, 2005-12-30 at 15:23 -0600, Dave Culp wrote: > On Friday 30 December 2005 03:03 pm, Dick Murphy wrote: > > Question: in fedora/linux install of FlightGear, would I see a menu to > > choose a particular Aircraft similar to the menu I can pull down to > > choose Airport? If so, how would I make it visible? If not, what are the > > work-arounds? > > I've never gotten fgrun to work with linux. I run from launch scripts, which > I find convenient. I just created a bin directory in my home space, > i.e /home/dave/bin, and I keep my scripts there. Here's an example: > > #!/bin/bash > > cmdline=" > --fg-root=/home/dave/FlightGear > --aircraft=737 > --airport-id=KSFO > --geometry=1024x768 > --prop:/engines/engine[0]/running=true > --prop:/engines/engine[1]/running=true > --prop:/radios/marker-beacon/audio-btn[0]=false > --prop:/radios/nav/frequencies/selected-mhz[0]=111.7 > --prop:/radios/nav/radials/selected-deg[0]=283.0 > --prop:/radios/nav[1]/frequencies/selected-mhz[0]=115.8 > --prop:/radios/dme/switch-position=1 > --visibility-miles=14.0 > " > > /home/dave/FlightGear/source/src/Main/fgfs $cmdline > exit 0 > > > I named this script "737", so to launch a 737 I just type 737 at the command > line. You of course need to set the script as "executable" and make sure > your bin directory is in your path. I prefer to launch FlightGear from > within a console, I use Konsole, the KDE console app. By running out of a > console you get output which helps with fixing problems that may come up. > > To fly the 737 in multiplayer mode I made a copy of this script, called it > 737mp, and added three lines: > > --multiplay=out,10,o-schroeder.de,5000 > --multiplay=in,10,192.168.0.5,5000 > --callsign=DCulp > > Of course you have to make sure the new script is set to be "executable". > > This method is especially useful if you decide to do any development, or for > some reason have more than one version of FlightGear installed. For > instance, my other 737 script is called 737new and looks like the above > script except it runs a different version of FlightGear, which you can do by > changing two lines: > > --fg-root=/home/dave/FlightGear-NewJSBSim > /home/dave/FlightGear-NewJSBSim/source/src/Main/fgfs $cmdline > > Remember that the command line overrides any settings in preferences.xml or > in > the aircraft's *-set.xml file, so you have "ultimate control" without having > to edit the other files. > > Dave > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > Flightgear-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/flightgear-users ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Flightgear-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-users
