[Flightgear-devel] FG version CVS: Bug in --config command line parameter handling and preferences.xml
Hi all, I have found a bug in the parsing of the --config command line parameter. Starting Flightgear, I noticed that the menu bar is using the default(blue) menu bar rather than the alternative black one. Which indicated that my preferences.xml isn't being loaded, rendering options was reset to the default. Also probably related is when exiting from fgfs, the error Error creating directory: home/gpatterson/.fgfs. .fgfs is my home direxctor already exists with appropriate permissions. It looks like the leading slash is being dropped. Version: CVS command: fgfs --aircraft=b1900d I will send a strace if required. Regards George ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FG version CVS: Bug in --config command line parameter handling and preferences.xml
On Sun, 2005-12-18 at 14:51 +0100, Frederic Bouvier wrote: George Patterson wrote : Hi all, I have found a bug in the parsing of the --config command line parameter. Starting Flightgear, I noticed that the menu bar is using the default(blue) menu bar rather than the alternative black one. Which indicated that my preferences.xml isn't being loaded, rendering options was reset to the default. Also probably related is when exiting from fgfs, the error Error creating directory: home/gpatterson/.fgfs. .fgfs is my home direxctor already exists with appropriate permissions. It looks like the leading slash is being dropped. Version: CVS command: fgfs --aircraft=b1900d I will send a strace if required. Does this patch improve things ? http://frbouvi.free.fr/flightsim/sg_path.patch -Fred Fred, I have applied the patch and rebuilt Simgear and Flightgear.. # patch sg_path.cxx sg_path.patch patching file sg_path.cxx Hunk #1 succeeded at 213 with fuzz 1. However, I am now getting this error instead (double slashes) Error creating directory: //home/gpatterson/.fgfs Why would Simgear be trying to create a directoy that already exists? George Patterson ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FG version CVS: Bug in --config command line parameter handling and preferences.xml
On Sun, 2005-12-18 at 15:26 +0100, Frederic Bouvier wrote: George Patterson wrote : On Sun, 2005-12-18 at 14:51 +0100, Frederic Bouvier wrote: George Patterson wrote : Does this patch improve things ? http://frbouvi.free.fr/flightsim/sg_path.patch -Fred Fred, I have applied the patch and rebuilt Simgear and Flightgear.. # patch sg_path.cxx sg_path.patch patching file sg_path.cxx Hunk #1 succeeded at 213 with fuzz 1. However, I am now getting this error instead (double slashes) Error creating directory: //home/gpatterson/.fgfs Why would Simgear be trying to create a directoy that already exists? Not sure you have the latest CVS. Your sg_path.cxx file should be revision 1.17. Is it the case ? Reload the patch as I made updates to remove the // at the beginning, and retrieve last version of the file from CVS so the patch will apply cleanly. -Fred Umm. no.. I had version 1.16 of that file. Compiling simgear/flightgear now. Regards George ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FG version CVS: Bug in --config command line parameter handling and preferences.xml
On Sun, 2005-12-18 at 15:26 +0100, Frederic Bouvier wrote: George Patterson wrote : On Sun, 2005-12-18 at 14:51 +0100, Frederic Bouvier wrote: George Patterson wrote : Hi all, I have found a bug in the parsing of the --config command line parameter. Starting Flightgear, I noticed that the menu bar is using the default(blue) menu bar rather than the alternative black one. Which indicated that my preferences.xml isn't being loaded, rendering options was reset to the default. Also probably related is when exiting from fgfs, the error Error creating directory: home/gpatterson/.fgfs. .fgfs is my home direxctor already exists with appropriate permissions. It looks like the leading slash is being dropped. Version: CVS command: fgfs --aircraft=b1900d I will send a strace if required. Does this patch improve things ? http://frbouvi.free.fr/flightsim/sg_path.patch -Fred Fred, I have applied the patch and rebuilt Simgear and Flightgear.. # patch sg_path.cxx sg_path.patch patching file sg_path.cxx Hunk #1 succeeded at 213 with fuzz 1. However, I am now getting this error instead (double slashes) Error creating directory: //home/gpatterson/.fgfs Why would Simgear be trying to create a directoy that already exists? Not sure you have the latest CVS. Your sg_path.cxx file should be revision 1.17. Is it the case ? Reload the patch as I made updates to remove the // at the beginning, and retrieve last version of the file from CVS so the patch will apply cleanly. -Fred Fred, Problem solved.. I was somehow stuck on sg_path.cxx revision 1.16. Deleted it, ran cvs update, applied patch. Patch works.. Now I just have to fix my preferences.xml file :-) George ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] website problem
Curt, the link is on the front page... I just checked and go the same 404 error. Broken link is http://flightgear.org/Gallery/ on http://flightgear.org/ I'm sure it is something simple. George Patterson On Sat, 2005-11-19 at 05:59 -0600, Curtis L. Olson wrote: Hi Ioan, Try reloading the page and select the link again, or if that doesn't work, tell me which page the broken link is on and I will check it out. Regards, Curt. Ioan Suciu wrote: The screenshot gallery does not work. There is a broken link, i think. IS Not Found The requested URL /Gallery/ was not found on this server. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] OT: Tower Simulator
On Wed, 2005-11-16 at 15:56 +, Martin Spott wrote: I just ran across this document http://www.adacel.com/prodserv/downloads/MAXSIM.pdf and thought: Isn't it great that FlightGear is so flexible to provide the visuals for such an application without modification ? Cheers, Martin. Hmmm.. The time could be right to restart the OpenATC project. :-) George -- George Patterson [EMAIL PROTECTED] ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: terrain texture question
On Wed, 2005-11-16 at 19:50 -0500, Ampere K. Hardraade wrote:
On November 16, 2005 05:37 pm, Melchior FRANZ wrote:
* Josh Babcock -- Wednesday 16 November 2005 23:25:
I considered using a Nasal script, but I don't know how the
script would know when the winter textures are being used.
if (getprop(/sim/startup/season) == winter) { ?? }
m.
I believe you would need more checkings. We don't have snow all the time in
winter.
Speaking of snow: is there anything about snow accumlation in METAR data?
I'm
just curious.
Ampere
We don't get snow at the local airport. Sleet maybe :-)
George Patterson
Adelaide, Australia
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Possible bug in yasim (not sure though?)
On Fri, 2005-11-11 at 22:43 -0500, Josh Babcock wrote: Curtis L. Olson wrote: George Patterson wrote: Thanks Andy. I just completed a nice flight from KSFO to KLAX with 3D clouds turned on. Mistakenly misread 25L as being 24L. George Ooops, stop by the FAA office, do not pass Go, do not collet $200 ... Curt. Or, into the office next door to the FAA, wonder where everyone is, wander back out, blame it on the weather :) Okay... I deserved that. :-P However I tried again this evening (though directed by ATC to use a different runway (07L) ) and got it right :-) George ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] OT: A380 arrived in EDHI (Hamburg-Finkenwerder)
On Sat, 2005-11-12 at 19:31 +, Jon Stockill wrote: Curtis L. Olson wrote: How about a spyware popup ... Oh I see you just typed the word Paris, here are some great hotel + airfare combinations you might be interested in, and would you like me to search ebay for berets? No, not spyware - clippy :-) Jon Hehe Hi, It looks like you are trying to pilot a plane. Would you like to... or Restart all systems a few seconds later.. Okay... restarting all systems.. George ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: OT: FYI, mac os x developers,
On Sun, 2005-11-13 at 03:51 +0200, Vassilii Khachaturov wrote: Just a suggestion: Maybe it is a good idea to put some of the important rules on the http://www.flightgear.org/mail.html webpage so people can read them, before they subscribe to the mailinglists. Good idea, in case someone really is annoyed with top-posts/encodes etc. Such folks are welcome to check-out the www module from the flightgear CVS, change the appropriate HTML, validate it, and send the patch over to Curt. Curt also likes the web pages' modified full text sent over as well, along with the patch, due to the way the website is now managed. This is the first time that someone gave me some insight about how to fg.org web page is managed, not that I asked explicitly on this list. Thanks Vassilii :-) George Patterson ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Possible bug in yasim (not sure though?)
Hi All, I have compiled and installed pre3 and noticed that I was not able to load the b1900d (my preferred plane), as FlightGear would load until the terrian appears and the splash screen starts to dissolve. At this point, flightgear is in a loop with some high pitched beeps. (That would normall stop). Loaded the beech99.. Same result... I asked Masser to check there... The Harrier loads correctly. I tried the harrier and was greeted with the harrier sitting on the runway. I tried running flightgear within strace and but that didn't reveal anything particularly interesting or out of the ordinary. Apart from a lot of lines like the following. (Spaces removed for readability.) read(5, 0x7f8ee290, 32) = -1 EAGAIN (Resource temporarily unavailable) All the above external models would load when choosing another fdm such as ufo or magic carpet. Any advice of what I could do next as I have ran out of debugging ideas? System: AMD64 3200+ 1 GB Memory GeForce 6600GT w/ 128MB George Patterson ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear Review (was: Which aircraft to include in v0.9.9?)
On Fri, 2005-11-11 at 16:13 +0100, Thomas Förster wrote: A slightly outdated version of FlightGear is installed for Suse via Yast and via Apt for Debian. For the newest release you have to compile the source code yourself [1]. For Mandrake 10.2, Fedora Core 3 and the newest version 5.10 of Ubuntu packets exist for the current release 0.9.8 of FlightGear. The packets may be found here [2]. Last sentence of this paragraph should be The packages may be found here [2]. -- George Patterson ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] 0.9.9 repost
On Fri, 2005-11-11 at 20:17 -0600, Dave Culp wrote: Due to underwhelming response to my previous post concerning a test run of 0.9.9-pre2, I'll repost now. Here is the console output while running the F-16: Dent: .Dent: ..Dent: EHAMopening file: /home/dave/FlightGear-0.9.9-pre2/data/Navaids/carrier_nav.dat /home/dave/FlightGear-0.9.9-pre2/data/Navaids/TACAN_freq.dat WARNING: ssgLoadAC: Failed to open '/home/dave/FlightGear-0.9.9-pre2/data/Aircraft/c172r/Models/c172-dpm.ac' for reading Reading xml electrical system model from /home/dave/FlightGear-0.9.9-pre2/data/Aircraft/Generic/generic-electrical.xml Initialising callsign using 'Aircraft/f16/Models/f16.xml' I don't know what the Dent stuff is. The carrier and TACAN stuff is obviously The Dents are someone's debug code and should probably be removed. carrier stuff. Every aircraft I've run tries to open a c172 model. Is this because the c172 model is the default and gets loaded even if it isn't needed, or is this the AI-Traffic manager trying to load GA traffic even when it's disabled by default? /home/dave/FlightGear-0.9.9-pre2/data/Aircraft/c172r/Models/c172-dpm.ac Does this file exist? And the callsign thing, is this a multiplayer or ATC message? It's a Multiplayer message -- George Patterson ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Possible bug in yasim (not sure though?)
On Fri, 2005-11-11 at 10:04 -0800, Andy Ross wrote: George Patterson wrote: I have compiled and installed pre3 and noticed that I was not able to load the b1900d Yeah, that was me. The patch yesterday for turn off the engines when out of fuel broke the solver for turbine aircraft. Fixed. That'll teach me to add features right before release. Apologies. Andy Thanks Andy. I just completed a nice flight from KSFO to KLAX with 3D clouds turned on. Mistakenly misread 25L as being 24L. George ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Which aircraft to include in v0.9.9?
On Thu, 2005-11-10 at 10:34 +, Thorben wrote: On Wednesday 09 November 2005 19:31, Curtis L. Olson wrote: The current list is: data/Aircraft/737 \ data/Aircraft/A-10 \ data/Aircraft/bo105 \ data/Aircraft/c172 \ data/Aircraft/c172p \ data/Aircraft/c310 \ data/Aircraft/c310u3a \ data/Aircraft/Citation \ data/Aircraft/f16 \ data/Aircraft/j3cub \ data/Aircraft/Hunter \ data/Aircraft/p51d \ data/Aircraft/pa28-161 \ data/Aircraft/ufo \ data/Aircraft/wrightFlyer1903 \ Just glancing through the list very quickly, potential candidates for inclusion might be the b1900d, Citation Bravo, Concorde, dhc2, F-8E, Hurricane, Marchetti, MiG-15, seahawk, Spitfire, tu154 ... (?) b1900d is my favourite plane, as it flies very well, has decent sound and a really good cockpit. And even the propeller blade pitch is animated i would ditch either the wright flyer, c310, ufo, c172 or Hunter in favor of b1900d. but i don't expect you to agree with me in all respects. thorben I second adding the b1900d for the above reasons. Drop the ufo as fun as it is for testing purposes it has no cockpit, and can't be verified as to the realism of the flight model. Just my opinion. The Wright Flyer could also be dropped as it's not really flyable (IMO). George Patterson ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: B1900D fuel/engines
On Tue, 2005-11-08 at 17:16 -0800, syd wrote: Andy, (or whoever is maintaining the b1900d), I hate to do this to you, but I think I have spotted another bug to do with fuel and engines. When you run out of fuel the engines continue to run, despite /engine/engine/out-of-fuel[0]='true' and /consumables/fuel/total-fuel-gals|lbs|norm[0]='0.00' But the both engines are still running. I hope this is clearer.. George Patterson Hi George . I am maintaining the b1900d , and yes I mentioned the same problem a while back, I run out of fuel and continue to fly on if I understand correctly, the turboprop engine code is fairly new and still a work in progress , so Im sure it will be straightened out soon.I have thought of trying to fix it myself , but I think the engine code is Andy's work and he knows FAR more than I do about such things . Thanks for the note , sometimes I get so far into the modelling aspect I miss bugs :) Cheers Syd, I didn't intend that to be a criticism of any sort.. I much appreciate the effort of all involved with the modelling of any of the planes and models. Otherwise, it looks and feels great :-) While I haven't seen a b1900d, it seem around the mark, tend to enter a spin when air speed drops too low but that's extreme flight dynamics. George Patterson ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: uneven brakes mystery
On Wed, 2005-11-09 at 21:54 +0100, Joacim Persson wrote: On Wed, 9 Nov 2005, Melchior FRANZ wrote: Is this the development version (cvs/head)? Yes, but it has been the same for shipped versions too. How can I tell which version of fgfs I'm running? fgfs --version didn't work on the version I have installed in /usr/local/... anyway. Think it's the last official stable release. In that installation I've replaced the calls to interpolate with setprop in the js config file, when I first noticed the problem after buying a new js. But it's an a few hours old cvs version I'm working on now. You have more than one version of FlightGear installed? To find out which copy is being loaded when you type fgfs, open up a terminal and type which fgfs and you should get something like /usr/local/bin/fgfs. Perhaps a command line parameter could be added to display the version of the binary and the version of the fg_root data. George ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] B1900d: Fuel consumption when engine has stopped.
On Sun, 2005-11-06 at 09:12 -0800, Andy Ross wrote: George Patterson wrote: /engines/engine/fuel-flow-gph[0] is shown as -0.232562 (fluctuates rapidly) /engines/engine/running[0] is shown as false. Good catch. The really primitive stop support in the turbine engine model didn't set the fuel flow value. This is fixed, such as it is. Real start/stop support is on my list, and will probably be done with some Nasal such that it can be hacked on a per-engine basis. Andy Andy, (or whoever is maintaining the b1900d), I hate to do this to you, but I think I have spotted another bug to do with fuel and engines. When you run out of fuel the engines continue to run, despite /engine/engine/out-of-fuel[0]='true' and /consumables/fuel/total-fuel-gals|lbs|norm[0]='0.00' But the both engines are still running. I hope this is clearer.. George Patterson ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Scenery DB (Was: San Jose)
On Tue, 2005-11-08 at 09:19 +0200, Vassilii Khachaturov wrote: I would like to see all new scenery object contributions to end up in the scenery database. However, the last time I wanted to sync the base package and the DB there were more than one objects in the same space because of automatic object generation. btw it looks pretty cute sometimes --- e.g., a skyscraper swallowing a radio tower and thus it looks like a skyscraper with a smaller antenna tower on its top; such things happen in real life as well :) A better example is a skyscraper covering a lighting beacon but the rotating light (white-green) shines through the wall of the building. This collision of objects is located within the perimeter of KSFO. Obviously the building doesn't belong there. And No, it is not a airport building :-) George Patterson ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Please upgrade to version: 0.9.8
On Tue, 2005-11-08 at 10:43 +0100, Georg Vollnhals wrote: Georg Vollnhals schrieb: Curtis L. Olson schrieb: It sounds like you aren't current with your flightgear source or executable? Could you still be running an older build of flightgear (or not fully up to date with your source code?) Curt. Did you upgrade your data from the cvs? Vassilii Just as a feedback: it seems that the file management system (CVS/compiler) got confused as a I had the system clock set to 2006 for some time and are now back in 2005. Some older files might be considered to be the newest one due to the date of 2006 :-) Ahhh! The perils of time travel. :-) You could also have touch-ed the files in question so that they are dated with something closer to today's date. Though this could have taken longer than rm -rf src and cvs update. George Patterson ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Please upgrade to version: 0.9.8
On Tue, 2005-11-08 at 12:42 +0100, Georg Vollnhals wrote: Curtis L. Olson schrieb: man touch ? Curt. Yes. My 13 years old son is actually a co-user on my PC. He does not ask, he does not think a lot - just trial and error method. Very good if you have all your important data burned on CD/DVD and have a good firewall, virus-scanner and no possibility to make a dial-up connection from your PC! But only until christmas, then I'll upgrade my PC and I'll build him his own with the parts I don't use anymore and those he gets as presents :-) :-) Joy of fatherhood! Regards Georg Georg, Even the parents should have the occasional Christmas present :-) George Patterson ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Please upgrade to version: 0.9.8
On Tue, 2005-11-08 at 13:43 +0100, Georg Vollnhals wrote: Georg, Even the parents should have the occasional Christmas present :-) George Patterson Thanx, just put your mail into my wife's mail account ;-) Georg I must have missed something?? George patterson ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] CVS make error (Cygwin)
On Mon, 2005-11-07 at 15:02 +, Kevin Jones wrote: Hi, CVS FG source at 2:30pm (UK time) Monday 7th November fails to make on Cygwin with the following error: make[2]: Entering directory blah/source/src/MultiPlayer make[2]: *** No rule to make target `tiny_xdr.cpp', needed by `tiny_xdr.o'. Stop. Can anyone help? Kevin. Kevin, You need to do a make clean and re-./configure before building... The file tiny_xdr.cpp has been renamed tiny_xdr.cxx. George Patterson ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] B1900d: Fuel consumption when engine hasstopped.
On Sun, 2005-11-06 at 20:00 +0800, Innis Cunningham wrote: George Patterson writes Oops, that was a typo. I meant the engines continues to consume fuel even with engines stopped. Thats ok I thought it might be something simple but it did add a bit of humor to my day. Sorry about the confusion. Currently amending the getting started and installation guide. Thats great there is a lot of outdated stuff in there and I dont have the skill or knowledge or enthusasm to do anything about it. LOL... Hence I have been working with Martin Splott to get the getstart manual into some sort of shape. Say does anyone know how you escape an @ symbol in LaTex. The rest of it is straight forward, if tedious. But I'm happy to be making a difference. George ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] B1900d: Fuel consumption when engine has stopped.
I have download the latest CVS data and compiled binaries for FlightGear and noticed that the fuel consumption for the b1900d continues even with the engines killed (cutoff). /engines/engine/fuel-flow-gph[0] is shown as -0.232562 (fluctuates rapidly) /engines/engine/running[0] is shown as false. The C172 doesn't behave properly. (It does not consume fuel unless the engine is running) George Patterson ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] B1900d: Fuel consumption when engine has stopped.
On Sun, 2005-11-06 at 14:37 +0800, Innis Cunningham wrote: Hi George George Patterson writes The C172 doesn't behave properly. (It does not consume fuel unless the engine is running) Hmm that would seem normal to me maybe I missed some thing. Oops, that was a typo. I meant the engines continues to consume fuel even with engines stopped. Sorry about the confusion. Currently amending the getting started and installation guide. George ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Cockpit Models
On Sun, 2005-11-06 at 17:46 +1000, Shelton D'Cruz wrote: Hi Where can I find the actual cockpit models? I looked under FlightGear/data/Aircraft/XXX/Models but can only find the external plane model not the internal cockpit. Regards Shelton. Shelton, I believe that you are looking for FlightGear/data/Aircraft/XXX/Panels for the cockpit panels. I think the cockpit framework is part of the external model. George ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Buildings ?????
On Sat, 2005-11-05 at 05:02 +0100, Arnt Karlsen wrote: On Fri, 04 Nov 2005 14:03:10 -0800, Andy wrote in message [EMAIL PROTECTED]: Mike Kopack wrote: It's not so much an issue of San Fran being BAD, it's just that KSFO is pretty far from downtown. We're talking about small slow-flying UAV's in my project (I'm using the Piper as a surrogate), so having to take off that far away means my demo is like 45 minutes long. As a left-field suggestion: how about defining the runways of the old NAS Alameda, which is just south of downtown Oakland and immediately across the bay from San Francisco. The base was closed in the mid 90's, I believe, and is now being converted into industrial loft space. But the runways are still there clear as day: http://maps.google.com/maps?ll=37.786114,-122.318387spn=0.027226,0.028824t=khl=en The folks who like to play with the carrier aircraft probably wouldn't mind having this active, either. ..if it's modelled correctly historically, setting the date back a decade or so should make it active. Hmm, interesting idea.. Can you get the METAR data from a decade or so back in time? George ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Compiling Flight Gear
On Fri, 2005-11-04 at 23:19 -0500, Steve Knoblock wrote:
I am trying to compile FG for the first time on Suse Linux 10.0
following the instructions at
http://www.flightgear.org/Docs/InstallGuide/getstartch2.html
I downloaded and unpacked SimGear 0.3.8
plib-1.8.4
I ran the install for the ZLIB package, but could not find the Metakit
package, so skipped it. It was not in the src-libs folder of SimGear.
I then ran without success. I am posting this from Evolution, so I do
have an X windowing system running. I have a Radeon 9600XT. I could not
get BSD to start X using this card, I gave up and installed Suse. Works
fine. It comes with an OpenGL game GL-117, which gave a warning the
first time I tried to run it that it needed the correct library to do 3d
with my card, so I installed the necessary ATI drivers and it works.
linux:/usr/local/source/plib-1.8.4 # ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
includedir changed to ${prefix}/include/plib libdir is
${exec_prefix}/lib
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for g++... no
checking for c++... no
checking for gpp... no
checking for aCC... no
checking for CC... no
checking for cxx... no
checking for cc++... no
checking for cl... no
checking for FCC... no
checking for KCC... no
checking for RCC... no
checking for xlC_r... no
checking for xlC... no
checking whether we are using the GNU C++ compiler... no
checking whether g++ accepts -g... no
checking dependency style of g++... none
checking how to run the C++ preprocessor... /lib/cpp
checking for a BSD-compatible install... /usr/bin/install -c
checking for ranlib... ranlib
checking build system type... i686-suse-linux
checking host system type... i686-suse-linux
checking for X... no
checking for pthread_create in -lpthread... no
checking for glNewList in -lGL... no
checking for glNewList in -lMesaGL... no
configure: error: could not find working GL library
linux:/usr/local/source/plib-1.8.4 #
Steve, you seem to have the following missing.
- C++ compiler
- X delopment libraries and header files are missing
- OpenGL libraries and header file
Have you compiled something else other than FlightGear?
For Suse, I'm not sure what packages you need to install, sorry..
George
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Instrument Making
On Thu, 2005-11-03 at 14:19 +1100, [EMAIL PROTECTED] wrote: HI Anyone know who looks after this site: http://www.seedwiki.com/wiki/flight_gear/volunteer_opportunities.cfm?wpid=213106 It says if anyone can help out - does anyone know if this is still required? Regards, Shelton. Shelton, Documentation is always welcome. The preferred format for documentation is LaTex from which html and pdf versions are generated. Yes, the FAQ can always be improved. (For example, the hyperlink to Wolfram's Hangar in section 2.7 is no longer valid.) If you wish to I'm usually online with irc most nights. I'm in Adelaide, Australia. George ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Santa's r[ae]i?ndeer
On Thu, 2005-10-27 at 14:19 +0100, Vivian Meazza wrote: Erik Hofman Vassilii Khachaturov wrote: Why are the bells commented out in raindeer-sound.xml? They do sound cute. I think it's a leftover from a previous test. It's corrected now. What happened to the poor reindeers' antlers? V. Correct me if I am wrong but isn't there supposed to be eight reindeers? What became of the other four? George Patterson ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Bug in ATC code.
Hi All, I have noticed two annoying bugs in the ATC dialog boxes. When you press ' for the first ATC dialog labelled ATC menu is displayed. (btw, Can we change that title as it's not an accurate description, perhaps ATC communication) Anyway, if you change frequencies for another ATC tower, extra lines showing :- 1. Contact tower for VFR arrival (full stop) 2. Contact tower for VFR arrival (full stop) 3. Contact tower for VFR arrival (full stop) etc, depending on how often you have switched frequencies. The other one which might be related is if you reset FlightGear (File-Reset), the state for the ATC is not reset back to the Contact tower ... dialog. Instead it will continue when you partially finished from before.. Contact tower- Report Downwind - Runway vacated. George Patterson ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Bug in ATC code.
On Thu, 2005-10-20 at 13:49 +0100, David Luff wrote: On 20/10/2005 at 21:40 George Patterson wrote: Hi All, I have noticed two annoying bugs in the ATC dialog boxes. When you press ' for the first ATC dialog labelled ATC menu is [Snipped] Thanks George. I'll attend to those in the next few weeks. The extra lines problem I was aware of, but the state persistance through reset is new to me. Yeah, Persistance or Persistence even was the word i was looking for. :-) David, Let me know when you have it committed and I'll check again. :-) George Patterson ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] fgfs on AMD64 status? Mobo suggestions/warnings?
On Wed, 2005-10-19 at 01:04 +, [EMAIL PROTECTED] wrote: Hi, I've been out of the fgfs development loop for an annoyingly long time. At first, I had to adjust to a big drop in free time after (thankfully) finally getting employed. Then I had a video card failure that forced me back to an old card I had lying around which had no 3D acceleration. And then, at the end of July, problems with my motherboard started, and worsened through the month until it became basically unusable by September. I'm secure enough now that I'm shopping to build a new machine. I'm looking at AMD64 motherboards and one of the newer nvidia cards. And what I'm wondering is whether any fgfs developers can speak to building and running fgfs, on linux, on an AMD64 box, and/or with the nv 6600's/6800's etc. I've seen some threads that people are running it on AMD64 OK; but I'm wondering if there are any suggestions, recommendations, or warnings that are worth hearing before I start shelling out the big $ (e.g. mobos you're happy with or had nothing but trouble with). I wanna get back to this stuff. Cheers, -c I am running a AMD64 based system Specifications: Gigabyte GA-K8NS Utlra Sock 939 nForce 3 Dual Bios Corsair DDR Ram 1 gig (matched pair) SATA Hard drive NV 6600GT AGP 128MB (You might want to consider PCI-E these days though.) That's the guts of it... Montherboard has dual network interfaces on board. (More about that one later) You didn't say what OS you are considering but It works a treat With Ubuntu Hoary (5.04) and Windows2000 (not interested in XP at this stage) Problems: After installing windows, the Gigabit network interface driver wasn't happy with it. plugged the network cable into the other socket and downloaded the up to date driver. Problem solved. On Linux, I had a sound problem with Warty (4.10) with the sound not intialising. apt-get update apt-get upgrade fixed that one. Also install the offical nvidia driver (7667 or higher) as the the version that is packaged for Hoary doesn't work with the AGP version of the NV 6600GT. I'd give the above combination the thumbs up. It is stable and I'm getting about 66fps at 800x600 when sitting on runway 28R at KSFO. The frame rate doesn't change when enlarging to full screen. One thing I didn't notice that --enabled-specular-highlights does kill the frame rate so i disabled that but the new 3D clouds doesn't present a problem. Overall, I'm happy with the purchase :-) George ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: A question regarding accurate taxiways
On Mon, 2005-10-17 at 21:57 -0400, Ampere K. Hardraade wrote: On October 17, 2005 02:23 pm, Durk Talsma wrote: - airport animations Just wondering what type of animations you were thinking of. We have support for moving aircraft now, but no ground vehicles yet, although this could be done using animation scripts. Bridges' movement, illumination, and so on; and yes, being able to use animation scripts and Nasal scripts in an airport would be great, and we should take these into account in our discussion as well. The problem is that at this point the requirement for FlightGear and x-plane start to deviate and I don't think we can expect an x-plane datamanager expect to switch to use a more sophisticated database format, just to support that *other* flight sim that happens to be using his database too. It's a difficult situation... In my opinion, if X-Plane wants to stay on a sinking boat, it doesn't mean we should follow either. ;-) I really think a new format is a must. If people insist, we can have an importer/exporter to exchange compatible data between Robin's database and our own database. It would benefit both FlightGear and X-plane if we synchronise data for beacons and other single point objects. However, the effort required for implmenting this may not be worth it. I notice some of airports in the FlightGear scenery over Scotland has lighting beacons in the middle of the runway. George Patterson ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Instant replay broken?
On Sun, 2005-10-16 at 17:11 +0100, David Luff wrote: Is it just me, or is it completely impossible to escape from instant replay once engaged in the current CVS? Cheers - Dave Yes, It's just you :-P You can stop the replay by select the View menu, select instant replay. On the Instant Replay dialog check the Disable replay. and click Ok. I hope that helps. George ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] [PATCH] README.multiplayer update
On Wed, 2005-10-12 at 20:22 +0200, Vassilii Khachaturov wrote: Sure. Here comes a new version, with an explicit further reading. Index: ../data/Docs/README.multiplayer === RCS file: /var/cvs/FlightGear-0.9/data/Docs/README.multiplayer,v retrieving revision 1.1 diff -u -p -r1.1 README.multiplayer --- ../data/Docs/README.multiplayer 21 Aug 2004 08:57:29 - 1.1 +++ ../data/Docs/README.multiplayer 12 Oct 2005 18:19:50 - @@ -54,19 +54,72 @@ is the sort of implementation that we ar visual simulator. -For use with a server (when one is created): - +For use with a server: +-- +Oliver Schroeder has created a server for multiplayer flightgear use. +The server acts as a packet forwarding mechanism. When it +receives a packet, it sends it to all other active players. +Future versions might be more scalable, only forwarding information +on the planes in the receiving player's vicinity. Gawd, I don't belive that I am commenting on a patch. I'm fairly certain that the selective positioin forwarding based on the players' position is already in the logic of the FG server. This was fixed in 0.0.6 of FG server. Apart from that the rest looks good. George Patterson ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] [PATCH] README.multiplayer update
On Thu, 2005-10-13 at 23:30 +0200, Arnt Karlsen wrote: On Thu, 13 Oct 2005 22:36:43 +0200 (IST), Vassilii wrote in message [EMAIL PROTECTED]: + +Options needed to enable multiplayer game with a server: Player1: ---multiplay=out,10,serveraddress,6000 --multiplay=in,10,myaddress,5500 I'm confused. The CVS had my patch accepted, I updated from the CVS, and I see no occurence of the number 6000 in README.multiplayer now. ..this works ok with X in lan's? (X uses port 6000 too.) Apparently not. ..aouch. Ok, the first X session on any box will use port 6000, the next 6001 etc, similarly 5900, 5901 upwards for vnc etc. ..how about putting the server on 5500 like we have done, and commandeer 5501 upwards for all clients? (Assuming they're vacant? Excluding non-FG app ports, I suspect METAR fetches has an established procedure, with ports and all.) Better would be server on 5000, with the telnet admin port on 5001. I'm not sure of the benefit of each client having it's own port. (Perhaps i have misread something) George Patterson ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: RFC: FlightGear 0.9.9
On Mon, 2005-10-03 at 14:02 +0200, Melchior FRANZ wrote: And here is what I have to say. :-) (A) will a new official plib release be required? I'm not really qualified to answer this one. (B) which bugs need to be fixed (and by whom :-)? I ran into another groundcache endless loop yesterday. This is IMHO a showstopper that needs a fix. I'll look into that next time I see it (and let Mathias fix it ;-). A fix for the cut-off 3d clouds would be nice. They collide with overcast cloud layers. Probably not easy to fix. No show-stopper. The cockpit view of other planes need to be fixed. For those that aren't aware of it. If you view another players/pilot's plane, you only see the cockpit panels and perhasp part of the tail or insignia. This is because the property list isn't send over the network. I think I have explained it right. Also can we add a ping function to flightgear which requests the server to send a packet back to the user's client. This will make is easier to debug people's MP setup. The MP server will not send the player's packets back to itself, fair enough decision except if there is only one player connected. (C) which features need to be completed? replacing the non-GPL-compatible sun/moon stuff Using an alternative GUI theme by default would IMHO be a good idea. Doesn't have to be mine, of course. The sharper and smaller pixmap fonts look better, the dark color is night-flight-friendlier, and a new look would cause an immense AAAHHH effect. :-) The nicer lighting would be good for those that want to compare Microsoft Flight Simulator 2004 with FGFS. gives a fairer comparison. The new shadows should possibly be activated by default. Or does not enough 3D hardware/software support it, so that this would cause too many problems? Activate 3D clouds by default, too? (D) which a/c should be included? I don't even know which a/c were in the last release. But the b1900d has such a nice cockpit, that it should get added if it isn't already. Yes, the b1900d is very nice and suitable for inclusion. The Citation has a few issued with the nose wheel shimmying across the runway during take off. (my opinion :-) ) (E) for when could/should the release be planned (i.e. how much time is left to fix bugs etc.)? I'll stay out of this one as well, seeing I haven't been subscribed to the -devel list for the last release. George Patterson ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: RFC: FlightGear 0.9.9
On Mon, 2005-10-03 at 19:57 +0200, Melchior FRANZ wrote: * Melchior FRANZ -- Monday 03 October 2005 19:47: * Durk Talsma -- Monday 03 October 2005 18:08: (B) which bugs need to be fixed (and by whom :-)? - Setting a wrong path for --fg-scenery results in an abort I'll look into this. It behaves exactly as it is supposed to: If no paths are given, the default is used. If paths are given, fgfs uses all that do actually contain scenery. (It doesn't complain about paths that don't!) But if a user specifies one or more paths but *none* contains valid scenery, it aborts with this error message: Fatal error: No valid scenery path defined! What do you think fgfs should do with no scenery? I consider this bug fixed. :-) Works for me might be closer. If flightgear can't find valid scenery in the area specified, what else can we do about it? Perhaps, popping up a dialog box but the message is okay. George ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: RFC: FlightGear 0.9.9
On Tue, 2005-10-04 at 11:11 +0200, Oliver Schroeder wrote: Am Tuesday 04 October 2005 09:26 schrieb George Patterson: The cockpit view of other planes need to be fixed. For those that aren't aware of it. If you view another players/pilot's plane, you only see the cockpit panels and perhasp part of the tail or insignia. This is because the property list isn't send over the network. I think I have explained it right. I was not aware that it is possible to switch to another clients cockpit. However, if this really depends on properties which get not transmitted over the network yet, we should disable this in the upcoming release. Sending properties over the net is more complicated than sending some values. I will address this in a seperate thread in the next days. It's not possible. Excuse my explanation. I meant that only the other planes cockpit panels are viewable from your cockpit and not the whole plane. Also can we add a ping function to flightgear which requests the server to send a packet back to the user's client. This will make is easier to debug people's MP setup. The MP server will not send the player's packets back to itself, fair enough decision except if there is only one player connected. I'm not sure what we gain if you (fgfs respectively) can ping the server. If you only want to debug the transmitted data you can simply connect 2 clients directly, without a server in the middle. Note that you can only connect 2 clients directly, not more. If you only want to know if the server recognises your (or any other) connection, you can simply telnet to the server and see the list of it's clients. The telnet port is commonly CONNECT-PORT +1. Yes, but just checking if the client is connect demonstrates that the client is sending the udp packets out okay. It does not show if the packets are able to get back in through someones firewall/NAT gateway. We have seen this happen on #flightgear irc channel a few times with a player saying that they can see other players but not be seen themselves. Maybe I'm barking up the wrong tree. George ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Adding Reverse thrust to the b1900d
The B1900d seemes to have thrust reversers fitted, but the best example of the cockpit si http://www.pookiedom.com/b1900d/inspiration.htm If I'm totally wrong and this is a bad example of a cockpit mockup, please let me know. :-) I'd be happy to implement this but not sure what it requires. I'm thinking of borrowing the code from the Citation II as it is a similar sized plane. A couple of questions on this topic. 1. The Citation has a keystroke bound to the reverse thrust (backspace I think code: 127). If I want to bind it to the throttle instead, can I make the idle position to cut in at about 10% of the range of the stick with the reverser starting to kick in below that point. The idea of having a button to push which activates reverse thrust is a a little scary. 2. Nasal. I write a nasal script to implement the logic between idle and reverse thrust being applied, how is that run from within Flightgear. George Patterson ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Does FlightGear model eclipse?
On Sun, 2005-10-02 at 19:49 -0400, Ampere K. Hardraade wrote: There will be an eclipse tomorrow, and I was just wonder whether FlightGear has this modelled. http://news.bbc.co.uk/2/hi/science/nature/4299074.stm Ampere It should do as FlightGear models the path of both the sun and the moon across the sky. But as for the darkening of the sky and the like, I'm not sure. George You mean an eclipse of the Sun. I prefer seeing the eclipse of the moon ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] irc.flightgear.org down: alternative server
Hi all, irc.flightgear.org is currently down (the machine is there but the irc service isn't) so I have set up a channel #flightgear on freenode.net to use untill the offical server comes back up. George Patterson ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: type conversion problem for amd64
On Fri, 2005-09-23 at 21:27 -0700, Alex Perry wrote: From: Erik Hofman George Patterson wrote: Tonight I cvs checkout the simgear sources tonight from cvs to recompile FlightGear. I was getting the following error. (Also got the same error in swap_test.* but worked around that problem by remove the file and references to it. Could you test the latest version in CVS, there was some restructuring of this code and I think this is solved now. Erik, it works fine for me under Debian/Sarge AMD64. George, what toolchain are you using ? $ gcc --version gcc (GCC) 3.4.4 20050314 (prerelease) (Debian 3.4.3-13) $ uname -a Linux host 2.6.13 #1 Sun Aug 28 19:57:26 PDT 2005 x86_64 GNU/Linux $ gcc --version gcc (GCC) 3.3.5 (Debian 1:3.3.5-8ubuntu2) $ uname -a Linux beast64 2.6.10-5-amd64-generic #1 Tue Apr 5 12:21:57 UTC 2005 x86_64 GNU/Linux However, I seem to have had a problem with syncing CVS but fixed it with some guidance from Oliver Schroeder (thanks). George ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Flightgear Documentation update: prefligh.tex
Hi all,
I have made some changes to the preflight: Installation section of the
Getting started guide.
While I am still learning latex, I did check my changes with lacheck
which didn't complain. Could someone (probably Erik or Martin) check the
patch file over and commit it into CVS?
CHANGES MADE
- Changed download link for Mac OS X binaries
- Amended Debian install instructions to be applicable for Ubuntu via
apt-get install.
- Formatting errors which lacheck reported.
Thanks
George Patterson
--- prefligh.tex2005-09-24 19:41:10.82636 +0930
+++ prefligh.gp.tex 2005-09-24 21:35:33.893210816 +0930
@@ -80,7 +80,7 @@
the simulator.
In case of doubt about the correct directory structure, see the summary at the
-end of chapter \ref{building}.
+end of chapter \~ref{building}.
%%%
\section{Installing the binary distribution on a Macintosh
system}\index{binaries!Macintosh}
@@ -90,7 +90,7 @@
Walisser)\index{Walisser, Darrell}. Download the file
\verb/FlightGear_Installer_0.X.X.sit/ from the corresponding subdirectory under
\medskip
-\web{http://icdweb.cc.purdue.edu/~walisser/fg/}.
+\web{http://macflightgear.sourceforge.net/}.
\medskip
\noindent
@@ -112,9 +112,10 @@
Note that there is no \texttt{runfgfs} script for Mac OS X yet.
%%%
-\section{Installing the binary distribution on a Debian Linux
system}\index{binaries!Debian}
+\section{Installing the binary distribution on a Debian based Linux
system}\index{binaries!Debian}
%%%
+
Download the file \verb/flightgear_0.7.6-6_i386.deb/ (being provided courtesy
Ove
Kaaven)\index{Kaaven, Ove} from any of the \Index{Debian} mirror sites listed
at
\medskip
@@ -129,9 +130,11 @@
\verb/dpkg --install flightgear_0.7.6-6_i386.deb/.
\medskip
+If you have a Debian, Ubuntu or other Debian package based linux distribution,
you might perfer using apt-get to install Flightgear \texttt{apt-get install
flightgear}.
+
\noindent
After installation, you will find the directory \texttt{/usr/local/Flightgear}
-containing the script \texttt{runfgfs} to start the program.
+containing the script \texttt{runfgfs} to start the program. If runfgfs has
not been included that you may run flightgear by running the binary
\texttt{runfgfs} directly.
%%%
@@ -161,7 +164,7 @@
\noindent
Moreover, Curt provides the complete set of US Scenery on \Index{CD-ROM} for
those who
-really would like to fly over all of the USA. For more detail, check the
remarks on the
+really would like to fly over all of the USA\. For more detail, check the
remarks on the
downloads page above.
An alternative data set was produced by William Riley\index{Riley, William}
and is available from
@@ -198,14 +201,14 @@
\medskip
\noindent
- with the directories w122n37 and w123n37, resp. containing numerous *.gz
+ with the directories w122n37 and w123n37, resp.\ containing numerous *.gz
files. Installation of the Grand Canyon scenery adds to this the directories
\medskip
\noindent
\texttt{/usr/local/FlightGear/Scenery/w120n30/w112n30}\\
\texttt{/usr/local/FlightGear/Scenery/w120n30/w112n31}\\
- \texttt{...}\\
+ \texttt{\.\.\.}\\
\texttt{/usr/local/FlightGear/Scenery/w120n30/w120n39}.
\medskip
@@ -216,7 +219,7 @@
%%%
Most of the packages named above include the complete \FlightGear{}
documentation
-including a .pdf version of this \textit{Installation and Getting Started}
Guide intended
+including a \.pdf version of this \textit{Installation and Getting Started}
Guide intended
for pretty printing using Adobe's Acrobat Reader being available from
\medskip
@@ -224,7 +227,7 @@
\medskip
\noindent
- Moreover, if properly installed, the .html version can be accessed via
+ Moreover, if properly installed, the \.html version can be accessed via
\FlightGear{}'s \texttt{help} menu entry.
Besides, the source code contains a directory \texttt{docs-mini} containing
numerous
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] type conversion problem for amd64
On Fri, 2005-09-23 at 10:16 +0200, Erik Hofman wrote: George Patterson wrote: Hi All, Tonight I cvs checkout the simgear sources tonight from cvs to recompile FlightGear. I was getting the following error. (Also got the same error in swap_test.* but worked around that problem by remove the file and references to it. Could you test the latest version in CVS, there was some restructuring of this code and I think this is solved now. Erik, I hate to to say it but No cigar, same problem, same errors :-/ I'm not quiet sure what changed. George Patterson ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Documentation Changes for the FlightGear installation and Getting Started guide
After an email to the flightgear-users list saying that a link to the Mac OS X binaries was broken, I went through the FlightGear Installation and Getting started guide. The following are the obvious errors due to changes in servers and feature crep of FligthGear. If need be, I'm happy to take on the maintenance of this document. I will need to learn latex first though. George Patterson Getting Started Guide Chapter 2 should probably be move to the appendix as it is not absolutely required. Binary downloads are an easier way to the computer novice to get started. They can always compile and install flightgear from source later. Section 3.1 Installing the binary distribution on a Macintosh system Contains the link ftp://www.flightgear.org/pub/flightgear/Win32/ This should be changed to http://www.flightgear.org/Downloads/binary.shtml#windows and choose one of the mirrors. A sentence should be added advising the user to upgrade to the latest version of their driver. Similar for Section 3.2 Installing the binary distribution on a Macintosh system Section 3.3 Installing the binary distribution on a Debian based Linux system Debian and other .deb (such as Ubuntu) package based distributions come with Flightgear in their respective repositories, hence install is as simple as apt-get install Flightgear. But the manual method of first downloading the binary, then installing it is a good idea also. The links need fixing. 4.1 Launching the simulator under Unix/Linux The command show to start flightgear is runfgfs ... when it should be fgfs. Question: Does the shell script runfgfs exist under any distro packages any longer? (I don't recall it and I have been using flightgear since 0.9.5.) Figure 3 need updating. It shows KSFO but without any airport terminal, tower or lights. Section 4.4.3 Aircraft The guide suggests that for possible aircraft see /Flightgear/Aircraft, when it's easier generaly to type fgfs --show-aircraft. 4.4.4 Flight Model Second Paragraph mentions --aero=abcd when it should probably be --aircraft= 4.4.5 Initial Position and Orientation The parameter --airport-id= should be --airport= 4.4.9 Network Options The two parameters, --enable-network-olk and --disable-network-olk can probably be removed and instrucion on using the new MP server code structure. It's easy enough to compile the server and run it locally for large number of machines with no network connection to the outside world. 4.5 Joystick support This section could do with being reworked as it is probably the case that your joystick will work out of the box :-) 4.6 A glance over our hangar Table 1 need altering as the aircraft has changed considerably. 5.1 Starting the engine The last paragraph says In addition, have a look if the parking brakes are on (red field lit). If so, press the B button to release them. That keystroke could be a little ambiguous. Perhaps shift-B would be clearer. 5.2 Keyboard Control In table 8, the keystroke ? should be added for displaying aircraft specific keystorckes eg (m/shift-M for mixture in the b1900d) 5.3 Menu Entries Menu Structure has changed substantially since the getting started document was written. Theses were the glaring bugs and annoyances that I spotted. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
