[Flightgear-devel] Spitfire model
I'm off to Italy tomorrow for a couple of weeks. I've put the spitfire files here: http://myweb.tiscali.co.uk/vmeazza/FlightGear/spitfire.tar.gz - they might work! There are 2 versions: spitfireIIa with legacy propeller/engine code, and spitfireIIa-mod1 propeller/engine code. Only spitfireIIa flies, spitfireIIa-mod1 only allows you to taxi, and that barely. The POH is here: http://home.clara.net/wolverine/BOB/misc/Spit_Hurri_Manuals.zip The model should operate as advertised! F/f slides the canopy H/h operates the radiator flap. Both have drag associated, and the radiator flap gives a little lift. As per the real thing. D/d CtrlD operates the door, which should be interlocked with the canopy, but isn't. Some problem in the -set file or property tree. Landing/takeoff are pretty realistic, except that the tail doesn't come up soon enough. Over use of the brakes will nose the model over, as should over use of the throttle, but doesn't. I might adjust the CofG a bit. Ailerons are sensitive - you'll need them! K/k toggles the gear warning klaxon. N/n and M/m control the prop pitch and mixture respectively. (leave these alone in normal flight) The sound is a mess right now - pity because the sound file contains recordings of a genuine Spitfire - Mk IX, but close enough. Some more work left to do in the cockpit (pilot needs a seat, and animating etc.), but it's pretty much finished now. Look forward to the prop/engine problem being solved soon. Arrivederci, Vivian Meazza ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Problems with ILS/LOC
> > Message: 2 > > I just tried to practice the ILS RWY 30 approach into KLBF (Lee Bird > Field at North Platte, Nebraska) since I plan to be there this week. > When I tune nav1 to 111.5, no response. So I gunzip nav.dat.gz, and > search on ILBF and sure enough the LLZ record is there with the right > frequency and runway, etc. Here is the record. > > > 4 41.134508 -100.694367 2775 11150 305.990 ILBF KLBF 30 LLZ > > Here is the glideslope record. > > > 6 41.121867 -100.668792 2768 11150 300305.235 --- KLBF 30 GS > > So why is FG not finding this ILS? > > I did note that there are other locations with ILBF as the code for > their localisers. Is the search algorithm getting confused? I am > running yesterday's CVS. I have no specific knowledge of your problem however I have been battling with the ILS code this last week and have found and fixed a problem. Also in your case the ILS only operate on RWY 30 there is no record for RWY 12 so you won't have this problem. The problem I was having was that on an approach bearing 092 to EGLC (London City Airport) using the ILS on 111.15 there are two localisers one at each end of the runway. The code in navlist.cxx (findByFreq) is picking up the nearest transmitter which is not facing the approach. (It's direction held in ...->multiuse() is 180 wrong). There are two consequences of this 1) CDI instrumentation is reversed. 2) because of the above an autopilot approach will turn the aircraft around and flay away from the airport. I'm not sure of the protocol in this matter is it good etiquette to post code fragments here? If it is I'll post a modified version which gets (appears to get) it right. We select the ILS/LOC transmitter that is nearest to the aircraft and if the plane is also within the +/- 30 degs of the required approach radial. -- Ed Sirett <[EMAIL PROTECTED]> ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Why doesn't FG find ILS data that is in nav.dat.gz?
Dave Perry wrote: I just tried to practice the ILS RWY 30 approach into KLBF (Lee Bird Field at North Platte, Nebraska) since I plan to be there this week. When I tune nav1 to 111.5, no response. So I gunzip nav.dat.gz, and search on ILBF and sure enough the LLZ record is there with the right frequency and runway, etc. Here is the record. Ok, good catch, thanks. There is a VOR with that same frequency over in Europe that was getting picked up. I think a reasonable solution is to ignore stations further away than some maximum distance, such as 300nm. I'll commit a fix to CVS that should take care of the problem. Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Why doesn't FG find ILS data that is in nav.dat.gz?
I just tried to practice the ILS RWY 30 approach into KLBF (Lee Bird Field at North Platte, Nebraska) since I plan to be there this week. When I tune nav1 to 111.5, no response. So I gunzip nav.dat.gz, and search on ILBF and sure enough the LLZ record is there with the right frequency and runway, etc. Here is the record. 4 41.134508 -100.694367 2775 11150 305.990 ILBF KLBF 30 LLZ Here is the glideslope record. 6 41.121867 -100.668792 2768 11150 300305.235 --- KLBF 30 GS So why is FG not finding this ILS? I did note that there are other locations with ILBF as the code for their localizers. Is the search algorithm getting confused? I am running yesterday's CVS. ... Dave ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] OT: Windows Wallpaper
I suppose it's a little off topic, but it seems like something you guys would know about (since it seems like I saw it here to begin with, anyway) Would any of you know where I can find the image somewhat matching this description: A swimsuit model with big gazongas, with general information relating to several parameters of the arc of a curve (properly fitted to one of the nearly semi-circular aforementioned gazongas). I seem to remember it as being titled something like "Engineering Wallpaper", but I can't really find it on the internet anymore (I might not be typing in the right keywords, though). Anyone know anything? Yeah, I know it's a little out there, but so am I, JD -- A scientist claims in court that the reason he ran a red light is that, due to his speed, the color was blueshifted till it appeared green. Needless to say, the charges of running the red light were dropped and he lost his license for speeding excessively. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
