[Flightgear-devel] Re: New A-4/jet panel instruments
* Jon S Berndt -- Thursday 20 June 2002 18:14: Any chance someone could post some screen shots of the panel? http://www.unet.univie.ac.at/~a8603365/fgfs4.jpeg m. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: Landing hints (was re: [Flightgear-devel] New A-4/jet panel instruments)
There are two aspects to being on the glide slope. First, are you on _any_ path that ends up at the beginning of the runway? Second, are you on the _intended_ glide slope? For the first, I was taught to look at the intended landing spot and, being aware of the windscreen, see whether that spot is stationary relative to the windscreen. If so, you are on track toward that spot. Try to see and feel this before worrying about _which_ glide slope you're on. It seems to work quite well. (Or perhaps you've already got this part OK; I wasn't sure from you're description.) For the second aspect, as David (I think) said, I was taught to recognise the on-screen geometry of the runway, mainly the angle of its edges. That works well in getting used to your home airfield, and after gaining experience there, you will be comfortable enough to adjust for unknown runways by picking up more than one cue at a time. (I remember thinking runway looking good ... looking good ... oh, airspeed! quick! ... that's better ... that's better ... oh, where's the runway gone?. Maybe not literally, but that's what it felt like. I stopped flying after getting a PPL, and never really reached the comfortable stage. So please don't trust my tips and advice too much.) - Julian from:Andy Ross [EMAIL PROTECTED] David Megginson wrote: Andy Ross wrote: Judging glide slope is still difficult, and will remain so until we get some kind of approach slope lighting (VASI/PAPI/FLOLS, whatever) implementation working. Speaking as someone who has just learned this stuff, I'll assert that estimating a glide path and extended centerline is not that tricky in good VFR conditions when the runway is level (sloping runways cause all kinds of misery). Heh, I hear what you're saying, but can't quite *do* it. This is one of those techniques that I understand in my head, but just can't get right in practice. In the cessna, I can sort of get by because the throttle is much more responsive. But in the jet, the engine spools more slowly and there's just too much going on. By the time I force myself to decide whether I'm too low, I've either gotten way too slow and am about to die, or have overcorrected on the throttle and am balooning way above the glide slope. Practice, practice, practice. The velocity vector in the HUD has been a crutch, I think. Gimme a week or so, and maybe a set of AoA indexers, and I'll probably be OK. :) Andy ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] New A-4/jet panel instruments
Tony Peden wrote:
I think you mentioned that it was /accelerations/pilot-g's ?
I'd like to see some direction info added to the name as lateral accel
at the pilot seat is quite often of interest as well as normal.
So maybe:
/accelerations/pilot-normal-g and
/accelerations/pilot-lateral-g
Sounds good. Or maybe pilot-{x|y|z}-g instead? Might as well get the
longitudinal axis while we're at it. I guess this belongs in
FGInterface::bind(). Or is that deprecated these days? David? :)
Andy
--
Andrew J. RossNextBus Information Systems
Senior Software Engineer Emeryville, CA
[EMAIL PROTECTED] http://www.nextbus.com
Men go crazy in conflagrations. They only get better one by one.
- Sting (misquoted)
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] question about fg joystick support -- whereis it?/grep question
Norman Vine wrote: Check your editor's help file for 'multi-file grep' or 'multi-file search' IMHO this is an indispensible editor feature for developing 'large' projects and most 'good' code editors have this feature builtin so you don't have to resort to using commandline tools directly. Blam. Culture crash. Most of us unix geeks would contend until the day we die that doing a recursive search via a GUI interface is slower and more error prone than running find and grep. The idea not having to resort to command line tools is foreign -- they're better, not worse. To us, a GUI app exists to do what command line tools cannot (like editing visual stuff, or browsing big data sets), not to replace functionality that works great already. I do this particular operation so much that I have a little 2-liner cgrep script that looks for a string in all the C/C++ source files under a directory. I can type cgrep joy before you get past the Edit menu in any IDE. :) Smileys all around. I don't point this stuff out to start a flame war. It's just that I find that most GUI folks have a very hard time internalizing the fact that Unix folks might really prefer a command line for many tasks, and I like to cite evidence when the opportunity presents itself. (And after all that, I'm sure that someone will point out that emacs has a multi-file grep feature too. I'm just not aware of one.) Andy -- Andrew J. RossNextBus Information Systems Senior Software Engineer Emeryville, CA [EMAIL PROTECTED] http://www.nextbus.com Men go crazy in conflagrations. They only get better one by one. - Sting (misquoted) ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] US and Canadian Circuits
Alex Perry writes: C172 glide angle is about 1.4 miles per 1000 ft, which implies the canadian pattern gives you 300 ft to land with. However, that doesn't allow for the plane to make the initial 90 degree turn towards the airport and for the plane to align itself with the runway. You need some more height if the runway isn't twice as long as you need to land on. When you put that all together, you're best 1/2 mile away on downwind. I agree that closer is better, but you have left something out of the equation: if the engine failure is sudden (what we're assuming here, I think), *and* you react quickly, you have an extra 25-45kt of airspeed that you can trade for altitude before you get down to Vglide at 65 KIAS. That should be enough to hold circuit altitude through the 90deg turn and even a little on towards the runway. I've been able to glide back from downwind during engine-out exercises without much trouble, except once when I was a little too far and there was a strong opposing wind (I had to add a little power; in real life, I would have set it down on the golf course under the 22 approach). Note that our circuit altitude is 1,100 ft AGL, so I had a 10% bonus, but most times I did have to apply flaps on short final to get down, negating the bonus; I can also fly downwind at 100-110 KIAS when I'm not following a C150 or Katana, and that helps as well. In fact, I'm lucky when I can get even 1 mile from the runway on downwind. I've noticed that some other pilots have gotten into the habit of waiting until they're at circuit altitude to turn downwind: that works well enough for a 150 or 172 on a cool day, but on a hot, humid day, it puts you two miles or more out from the runway on downwind and everyone else is forced to follow you (muttering and cursing). Yes. Also, the Canadian pattern has you fly a longer final. For grins, try taking the engine to idle, as you make the downwind to base turn, and see how close you'd get to the airport. You barely get half way. The american pattern (for light aircraft) has a fairly short final. It would depend on the wind, of course -- remember that we're still at full circuit altitude and speed at the start of the turn to base. The other day, ATC gave me a sudden direct-to-threshold instruction during my base turn to get me down ahead of some other traffic, and I had to close the throttle and apply full flaps just to get the plane down to the threshold. With a strong headwind, though, I agree that I probably couldn't make it as easily. Also, in a C150, which doesn't glide as much, it would be a much bigger problem. Naw, we're used to visitors from up north, even down here. We'll hear the funny accent on the radio [*] and keep out of the way. 8-) The Canadian pilots are the ones who say thank you for every clearance (in the 1980s, SPY magazine said you could spot Canadians in New York because they say thank you to bank machines). * Actually, your callsign will be Canadian Alpha Bravo Charlie. A little longer, at least on first contact -- Canadian Charlie Gulf (or Foxtrot) Alpha Bravo Charlie. Apparently, American controllers have a tendency to add a November before Canadian callsigns, just out of habit. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: Landing hints (was re: [Flightgear-devel] New A-4/jet panel instruments)
[EMAIL PROTECTED] writes: For the second aspect, as David (I think) said, I was taught to recognise the on-screen geometry of the runway, mainly the angle of its edges. That works well in getting used to your home airfield, and after gaining experience there, you will be comfortable enough to adjust for unknown runways by picking up more than one cue at a time. (I remember thinking runway looking good ... looking good ... oh, airspeed! quick! ... that's better ... that's better ... oh, where's the runway gone?. Maybe not literally, but that's what it felt like. That sounds very, very familiar. Losing the Iron Grip Of Death on the yoke helped a lot, since I could feel what the pitch was doing even when I wasn't staring at the ASI. I stopped flying after getting a PPL, and never really reached the comfortable stage. So please don't trust my tips and advice too much.) Since you still have your PPL, you might consider taking a checkride (and updating your medical, if necessary) then trying again. I have been uncomfortable and nervous through much of my training, but I found that three things helped a lot: 1. Encouragement from the other FGFS developers and users. 2. Hours of practice on FlightGear with a proper USB yoke and rudder pedals (the JSBSim C172 handling is so close now that it's eerie: if I'm 5 kt too fast on approach in the real C172, I tend to be 5 kt too fast on approach in fgfs under the same conditions). One evening I did over 40 approaches in rapid succession using the forecast conditions from the TAF, then nailed my first solo the next morning. 3. Reading, rereading, and rerereading http://www.monmouth.com/~jsd/how/htm/ All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] question about fg joystick support -- whereis it?/grep question
Andy Ross writes: Blam. Culture crash. Most of us unix geeks would contend until the day we die that doing a recursive search via a GUI interface is slower and more error prone than running find and grep. Nah. I like running find, grep, and etags from inside Emacs, then stepping through the results. (And after all that, I'm sure that someone will point out that emacs has a multi-file grep feature too. I'm just not aware of one.) M-x grep M-x grep-find Or, if you've already run etags, M-x tags-search All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] US and Canadian Circuits
I agree that closer is better, but you have left something out of the equation: if the engine failure is sudden (what we're assuming here, I think), *and* you react quickly, you have an extra 25-45kt of airspeed that you can trade for altitude before you get down to Vglide at 65 KIAS. That should be enough to hold circuit altitude through the 90deg turn and even a little on towards the runway. My docs recommend doing 80 kias on downwind, giving you only 15 knots of margin to trade into height. Tests have shown that pilots spend about six seconds sitting in stunned amazement, after engine failure, before doing through their ABCs when it happens for-real and no warning. Naw, we're used to visitors from up north, even down here. We'll hear the funny accent on the radio [*] and keep out of the way. 8-) The Canadian pilots are the ones who say thank you for every clearance (in the 1980s, SPY magazine said you could spot Canadians in New York because they say thank you to bank machines). Have you seen the film Canadian Bacon ? ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Re: question about fg joystick support -- where is it?/grep question
Woohoo ... flame war! * Andy Ross -- Thursday 20 June 2002 19:27: I do this particular operation so much that I have a little 2-liner cgrep script that looks for a string in all the C/C++ source files under a directory. Hey, cgrep is already defined like this: #!/bin/bash trap echo -en '\\033[m' 0 p=$1 shift grep $p $*|sed s,$p,^[[31;1m^[[m,ig ... over here. (A little bit hackish, but useful sometimes.) I couldn't agree more with what you said about all the wonderful, =flexible=(!) command line tools. Every one of them is worth learning its man page by heart. ;-) m. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] question about fg joystick support -- where is it?/grep question
Andy Ross writes: Norman Vine wrote: Check your editor's help file for 'multi-file grep' or 'multi-file search' IMHO this is an indispensible editor feature for developing 'large' projects and most 'good' code editors have this feature builtin so you don't have to resort to using commandline tools directly. Blam. Culture crash. Most of us unix geeks would contend until the day we die that doing a recursive search via a GUI interface is slower and more error prone than running find and grep. The idea not having to resort to command line tools is foreign -- they're better, not worse. To us, a GUI app exists to do what command line tools cannot (like editing visual stuff, or browsing big data sets), not to replace functionality that works great already. YIKES who ever mentioned a GUI App ?? Have you ever heard of a key assignment to run a shell script in emacs or vi ??? Or editors that can capture and massage a 'standard output' stream FWIW In my 'EMACS' all I need to do is Meta-Ctrl F-7 and it runs a recursive grep for the regexp that I enter in the conveniently 'prompted command line' Then all matched lines are returned in a 'buffer' that also includes the filename and line #. Oh did I mention that all I need to do is click on any line to open up that file at the occurence of my regex in a new buffer :-) starting-a-task-is-faster-then-forking-a-shell'ly your's Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] question about fg joystick support -- where is it?/grep question
David Megginson writes: Andy Ross writes: Blam. Culture crash. Most of us unix geeks would contend until the day we die that doing a recursive search via a GUI interface is slower and more error prone than running find and grep. Nah. I like running find, grep, and etags from inside Emacs, then stepping through the results. (And after all that, I'm sure that someone will point out that emacs has a multi-file grep feature too. I'm just not aware of one.) M-x grep M-x grep-find Or, if you've already run etags, M-x tags-search Drat's ... Now you have gone and 'spoiled' all the 'good work habit's' of all those nimple fingered unix geeks Andy was refering to :-) Cheers Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Re: question about fg joystick support -- where is it?/grep question
On Thu, 20 Jun 2002 19:46:30 +0200 Melchior FRANZ [EMAIL PROTECTED] wrote: Woohoo ... flame war! Grep, schmep. It can't come close to actually printing out a copy of the source code and looking through it manually. I mean, if you want accuracy, what can beat a pair of human eyes and some bright white inkjet paper? I've even got grep aliased to print all .cpp files in draft mode (for speed)... ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Norman and others: what code editors do ya'll recommend
I really have to learn to type eventually 8-( --- Norman, I'm glad that you brought that up (it was my next question): What code editors do people recommend using? I can sort-of use vi, the one time I started emacs, I couldn't exit the darn thing. I'm evaluating a lite version of bb edit, but I don't mind command line type apps (used to use slick edit for dos on another os 8-)). I'd like to have something that I could set up to do my compiles, go from errors straight to an editing session at the point of error. Find in file like grep or the ability to call an external command like grep would be great too. It would either have to be open source, or macos x compatible to work for me. A powerful c-like macro editor would be a plus... 8-) I've heard of something called joe, but think that it requires a library that I can't get on macos x. Any other suggestions? TIA, Ima Check your editor's help file for 'multi-file grep' or 'multi-file search' IMHO this is an indispensible editor feature for developing 'large' projects and most 'good' code editors have this feature builtin so you don't have to resort to using commandline tools directly. Cheers Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Re: Norman and others: what code editors do ya'll recommend
* ima sudonim -- Thursday 20 June 2002 20:19: the one time I started emacs, I couldn't exit the darn thing. $ killall -9 emacs; alias emacs=vim m. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Re: New A-4/jet panel instruments
* Jon S Berndt -- Thursday 20 June 2002 18:14: Any chance someone could post some screen shots of the panel? http://www.unet.univie.ac.at/~a8603365/fgfs4.jpeg I get that, too. What I'm missing in recent releases is display of the gear in the outside view and keyboard control of throttle and flaps. This appeared to be introduced the the recent A-4 updates in YASim. Can anyone confirm ? Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Re: New A-4/jet panel instruments
Martin Spott wrote: I get that, too. What I'm missing in recent releases is display of the gear in the outside view and keyboard control of throttle and flaps. This appeared to be introduced the the recent A-4 updates in YASim. Can anyone confirm ? Works for me. Are you sure you have a current fgfsbase? There's no detectable difference (to the FDM) between keyboard, joystick and mouse control. All of those methods set the same properties in /controls, so I'd be stumped as to the reason only one of them would fail. I can verify that the gear animations work, too; check the values in /surface-positions and make sure that they're changing appropriately. Andy -- Andrew J. RossNextBus Information Systems Senior Software Engineer Emeryville, CA [EMAIL PROTECTED] http://www.nextbus.com Men go crazy in conflagrations. They only get better one by one. - Sting (misquoted) ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Re: New A-4/jet panel instruments
Martin Spott wrote: I get that, too. What I'm missing in recent releases is display of the gear in the outside view and keyboard control of throttle and flaps. This appeared to be introduced the the recent A-4 updates in YASim. Can anyone confirm ? Works for me. Are you sure you have a current fgfsbase? There's no detectable difference (to the FDM) between keyboard, joystick and mouse control. All of those methods set the same properties in /controls, so I'd be stumped as to the reason only one of them would fail. I can verify that the gear animations work, too; I don't even see the gear - the plane is hovering :-) I'm updating all the sources of plib, metakit, SimGear and FlightGear from CVS at least on a daily basis and I'm rsync'ing the base package from 'scenery.flightgear.org::Base'. I just did a new checkout and a new build so I suppose I'm up to date. I'd provide the contents of my ~/.fgfsrc, but I don't believe this has anything to do with it: --aircraft=a4-yasim --airport-id=KOAK --start-date-lat=2002:04:11:11:11:11 --enable-fuel-freeze --wind=270@10:15 --disable-splash-screen --disable-intro-music --control=mouse --enable-auto-coordination --disable-hud --enable-panel --enable-anti-alias-hud BTW, 747-yasim and c310 work great, so I believe it has something to do with the A-4 (which looks really great !), Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Re: New A-4/jet panel instruments
Martin Spott [EMAIL PROTECTED] said: I get that, too. What I'm missing in recent releases is display of the gear in the outside view and keyboard control of throttle and flaps. This appeared to be introduced the the recent A-4 updates in YASim. Can anyone confirm ? Martin, This sounds odd. Do you other keys work? AFAIK it works, but I just late last night applied all the code patches and did not test extensively. Will do this evening. What I have noticed in the past is that if you have an xml glitch in your keyboard.xml all the keys before the glitch will work, all the keys after the glitch will not. Generally this is the only case that I've observed where only some of the keys not work. But could be something else I suppose. Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: Landing hints (was re: [Flightgear-devel] New A-4/jet panel instruments)
[EMAIL PROTECTED] wrote: There are two aspects to being on the glide slope. First, are you on _any_ path that ends up at the beginning of the runway? Second, are you on the _intended_ glide slope? For the first, I was taught to look at the intended landing spot and, being aware of the windscreen, see whether that spot is stationary relative to the windscreen. If so, you are on track toward that spot. Try to see and feel this before worrying about _which_ glide slope you're on. It seems to work quite well. That's the same technique that sailors are using to figure out if they are on collision course. That that works can be proofen with basic geometry (intercept theorems, if the dictionary is correct...) CU, Christian -- The idea is to die young as late as possible.-- Ashley Montague ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Norman and others: what code editors do ya'll recommend
* [EMAIL PROTECTED] (ima sudonim) [2002.06.20 13:20]: Norman, I'm glad that you brought that up (it was my next question): What code editors do people recommend using? I can sort-of use vi, the one time I started emacs, I couldn't exit the darn thing. My experience with emacs started out exactly like that. :-) I later tried learning emacs but got tired of having to hit Ctrl+something to do anything. My personal preference is VIM. I use it for mail (mutt+vim) and programming (mostly in perl). FlightGear is the only large C/C++ project I'm involved with, so I've never felt like moving to a powerful IDE such as emacs. My poor man's IDE consists of a bunch of rxvt terminals running vim and gdb. :-) Having a large monitor helps. If you want to try vim, there are some great scripts and tips here: http://vim.sourceforge.net/ I still haven't tried this, but you can check out this script for using vim with gdb: http://vim.sourceforge.net/scripts/script.php?script_id=84 Thanks -- Cameron Moore / Officer, I know I was going faster than 55MPH, \ \ but I wasn't going to be on the road an hour. / ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] BW Online June 18, 2002 Giving Pilots a New Eye in the Sky
On Thursday, 20, 2002, at 09:55AM, Norman Vine [EMAIL PROTECTED] wrote: FYI http://www.businessweek.com/technology/content/jun2002/tc20020618_2463.htm?r ef=cnet ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel Rockwell-Collins in Cedar Rapids. That's where *I* work. ;) Of COURSE they can do that. They're engineers! ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Norman and others: what code editors do ya'll recommend
On Thursday, June 20, 2002, at 01:19 PM, ima sudonim wrote: I'd like to have something that I could set up to do my compiles, go from errors straight to an editing session at the point of error. Find in file like grep or the ability to call an external command like grep would be great too. It would either have to be open source, or macos x compatible to work for me. A powerful c-like macro editor would be a plus... 8-) I've heard of something called joe, but think that it requires a library that I can't get on macos x. Any other suggestions? I would really recommend Project Builder, which I would expect that you already have installed. There is an effort ongoing to try to get FlightGear to build natively under Project Builder, bit I have been having some problems with my hand-build projects (more talented people than I are working on getting the autoconfig to generate the project files). You could try using Project Builder's legacy interface and see if it fits the bill. http://developer.apple.com/techpubs/macosx/Darwin/PortingUNIX/compiling/Building_Le_ect_Builder. html I haven't given it a try, but I may be doing so. Some questions I have concerning the legacy interface is that I cannot generate Frameworks or .app wrappers, unless the underlying makefile does so. Jonathan Polley ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] question about fg joystick support -- whereis it?/grep question
On Thu, 2002-06-20 at 09:06, Norman Vine wrote: ima sudonim writes: Incidentally, how does one find within files using grep? If i'm in /src and want to search all components of /src (including recursively directories) I tried: find . | grep -i joy but that finds just files with joy in their names in the directory tree Is there another tool I should be using? Check your editor's help file for 'multi-file grep' or 'multi-file search' IMHO this is an indispensible editor feature for developing 'large' projects and most 'good' code editors have this feature builtin so you don't have to resort to using commandline tools directly. Do you like living dangerously? ;-) ;-) Cheers Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel -- Tony Peden [EMAIL PROTECTED] We all know Linux is great ... it does infinite loops in 5 seconds. -- attributed to Linus Torvalds ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] New A-4/jet panel instruments
On Thu, 2002-06-20 at 09:04, [EMAIL PROTECTED] wrote: from:Tony Peden [EMAIL PROTECTED] I'd like to see some direction info added to the name as lateral accel at the pilot seat is quite often of interest as well as normal. So maybe: /accelerations/pilot-normal-g and /accelerations/pilot-lateral-g And not forgetting the third one, of course: /accelerations/pilot-axial-g It's not nearly as interesting and isn't that different from the cg value since pitch and yaw don't affect it as much. (or longitudinal or forward or x/y/z ... perhaps the names ought to indicate the sign as well as the axis, e.g. right/up/forward) - Julian ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel -- Tony Peden [EMAIL PROTECTED] We all know Linux is great ... it does infinite loops in 5 seconds. -- attributed to Linus Torvalds ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] New A-4/jet panel instruments
On Thu, 2002-06-20 at 10:14, Andy Ross wrote:
Tony Peden wrote:
I think you mentioned that it was /accelerations/pilot-g's ?
I'd like to see some direction info added to the name as lateral accel
at the pilot seat is quite often of interest as well as normal.
So maybe:
/accelerations/pilot-normal-g and
/accelerations/pilot-lateral-g
Sounds good. Or maybe pilot-{x|y|z}-g instead? Might as well get the
longitudinal axis while we're at it.
I'd prefer the words, but either way will work for me.
I guess this belongs in
FGInterface::bind(). Or is that deprecated these days? David? :)
Andy
--
Andrew J. RossNextBus Information Systems
Senior Software Engineer Emeryville, CA
[EMAIL PROTECTED] http://www.nextbus.com
Men go crazy in conflagrations. They only get better one by one.
- Sting (misquoted)
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
--
Tony Peden
[EMAIL PROTECTED]
We all know Linux is great ... it does infinite loops in 5 seconds.
-- attributed to Linus Torvalds
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] US and Canadian Circuits
Alex Perry writes: My docs recommend doing 80 kias on downwind, giving you only 15 knots of margin to trade into height. Tests have shown that pilots spend about six seconds sitting in stunned amazement, after engine failure, before doing through their ABCs when it happens for-real and no warning. That makes sense for the tighter downwind and base. For our airport, my instructor advised pulling back to 2100 RPM/90kt when I'm sharing the circuit with 150's or Katanas; when I have it to myself, I tend to go a little faster. Have you seen the film Canadian Bacon ? No, but I've heard about it. Strange Brew is the classic Canadian-identity movie. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: Landing hints (was re: [Flightgear-devel] New A-4/jet panel instruments)
Christian Mayer writes: For the first, I was taught to look at the intended landing spot and, being aware of the windscreen, see whether that spot is stationary relative to the windscreen. If so, you are on track toward that spot. Try to see and feel this before worrying about _which_ glide slope you're on. It seems to work quite well. That's the same technique that sailors are using to figure out if they are on collision course. And WWII fighter pilots, for that matter. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] MSVC Build Problem for props.cxx
I just updated to the latest CVS for SimGear and tried to build. While Mac OS X builds like a champ, MSVC is complaining (again). If I backup two versions of the file, I can get it to build (but I get link errors with FlightGear). The compilation errors I get are as follows (looks like another STL problem?). props.cxx c:\simgear\simgear\misc\props.cxx(1997) : error C2653: 'vector >' : is not a class or namespace name c:\simgear\simgear\misc\props.cxx(1997) : error C2065: 'iterator' : undeclared identifier c:\simgear\simgear\misc\props.cxx(1997) : error C2146: syntax error : missing ';' before identifier 'it' c:\simgear\simgear\misc\props.cxx(1997) : error C2065: 'it' : undeclared identifier c:\simgear\simgear\misc\props.cxx(1998) : error C2065: 'find' : undeclared identifier c:\simgear\simgear\misc\props.cxx(1999) : error C2446: '!=' : no conversion from 'class SGPropertyChangeListener ** ' to 'int' This conversion requires a reinterpret_cast, a C-style cast or function-style cast c:\simgear\simgear\misc\props.cxx(1999) : error C2040: '!=' : 'int' differs in levels of indirection from 'class SGPropertyChangeListener ** ' c:\simgear\simgear\misc\props.cxx(2299) : error C2653: 'vector >' : is not a class or namespace name c:\simgear\simgear\misc\props.cxx(2299) : error C2146: syntax error : missing ';' before identifier 'it' c:\simgear\simgear\misc\props.cxx(2300) : error C2440: '=' : cannot convert from 'class SGPropertyNode ** ' to 'int' This conversion requires a reinterpret_cast, a C-style cast or function-style cast c:\simgear\simgear\misc\props.cxx(2300) : error C2446: '!=' : no conversion from 'class SGPropertyNode ** ' to 'int' This conversion requires a reinterpret_cast, a C-style cast or function-style cast c:\simgear\simgear\misc\props.cxx(2300) : error C2040: '!=' : 'int' differs in levels of indirection from 'class SGPropertyNode ** ' c:\simgear\simgear\misc\props.cxx(2301) : error C2100: illegal indirection c:\simgear\simgear\misc\props.cxx(2301) : error C2227: left of '->removeChangeListener' must point to class/struct/union c:\simgear\simgear\misc\props.cxx(2333) : error C2653: 'vector >' : is not a class or namespace name c:\simgear\simgear\misc\props.cxx(2333) : error C2146: syntax error : missing ';' before identifier 'it' c:\simgear\simgear\misc\props.cxx(2335) : error C2446: '!=' : no conversion from 'class SGPropertyNode ** ' to 'int' This conversion requires a reinterpret_cast, a C-style cast or function-style cast c:\simgear\simgear\misc\props.cxx(2335) : error C2040: '!=' : 'int' differs in levels of indirection from 'class SGPropertyNode ** ' Jonathan Polley
Re: [Flightgear-devel] MSVC Build Problem for props.cxx
I haven't tried building this, but this sort of error looks like you just have to put a using namespace std; into the props.cxx Cheers, Christian At 07:50 PM 20/06/2002 -0500, you wrote: I just updated to the latest CVS for SimGear and tried to build. While Mac OS X builds like a champ, MSVC is complaining (again). If I backup two versions of the file, I can get it to build (but I get link errors with FlightGear). The compilation errors I get are as follows (looks like another STL problem?). props.cxx c:\simgear\simgear\misc\props.cxx(1997) : error C2653: 'vector ' : is not a class or namespace name c:\simgear\simgear\misc\props.cxx(1997) : error C2065: 'iterator' : undeclared identifier c:\simgear\simgear\misc\props.cxx(1997) : error C2146: syntax error : missing ';' before identifier 'it' c:\simgear\simgear\misc\props.cxx(1997) : error C2065: 'it' : undeclared identifier c:\simgear\simgear\misc\props.cxx(1998) : error C2065: 'find' : undeclared identifier c:\simgear\simgear\misc\props.cxx(1999) : error C2446: '!=' : no conversion from 'class SGPropertyChangeListener ** ' to 'int' This conversion requires a reinterpret_cast, a C-style cast or function-style cast c:\simgear\simgear\misc\props.cxx(1999) : error C2040: '!=' : 'int' differs in levels of indirection from 'class SGPropertyChangeListener ** ' c:\simgear\simgear\misc\props.cxx(2299) : error C2653: 'vector ' : is not a class or namespace name c:\simgear\simgear\misc\props.cxx(2299) : error C2146: syntax error : missing ';' before identifier 'it' c:\simgear\simgear\misc\props.cxx(2300) : error C2440: '=' : cannot convert from 'class SGPropertyNode ** ' to 'int' This conversion requires a reinterpret_cast, a C-style cast or function-style cast c:\simgear\simgear\misc\props.cxx(2300) : error C2446: '!=' : no conversion from 'class SGPropertyNode ** ' to 'int' This conversion requires a reinterpret_cast, a C-style cast or function-style cast c:\simgear\simgear\misc\props.cxx(2300) : error C2040: '!=' : 'int' differs in levels of indirection from 'class SGPropertyNode ** ' c:\simgear\simgear\misc\props.cxx(2301) : error C2100: illegal indirection c:\simgear\simgear\misc\props.cxx(2301) : error C2227: left of '-removeChangeListener' must point to class/struct/union c:\simgear\simgear\misc\props.cxx(2333) : error C2653: 'vector ' : is not a class or namespace name c:\simgear\simgear\misc\props.cxx(2333) : error C2146: syntax error : missing ';' before identifier 'it' c:\simgear\simgear\misc\props.cxx(2335) : error C2446: '!=' : no conversion from 'class SGPropertyNode ** ' to 'int' This conversion requires a reinterpret_cast, a C-style cast or function-style cast c:\simgear\simgear\misc\props.cxx(2335) : error C2040: '!=' : 'int' differs in levels of indirection from 'class SGPropertyNode ** ' Jonathan Polley /blockquote/x-html ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Re: question about fg joystick support -- whereis it?/grep question
Grep, schmep. It can't come close to actually printing out a copy of the source code and looking through it manually. I mean, if you want accuracy, what can beat a pair of human eyes and some bright white inkjet paper? I've even got grep aliased to print all .cpp files in draft mode (for speed)... I grew up with the green-white lined printer paper, but the system printer was an NLQ and capable of graphics if you bypassed the driver. Use of a 6 point font conveniently allowed each printout sheet to have 264 lines of source code ... more if you didn't use all 80 columns. I could hang something like 1 lines of code on my cubicle wall. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] MSVC Build Problem for props.cxx
I didn't see anything like that in the new files, but I may not know what, exactly, I should be looking for. The only new using clause was in props.cxx: using std::find; Jonathan Polley On Thursday, June 20, 2002, at 08:02 PM, Christian Stock wrote: I haven't tried building this, but this sort of error looks like you just have to put a using namespace std; into the props.cxx Cheers, Christian At 07:50 PM 20/06/2002 -0500, you wrote: I just updated to the latest CVS for SimGear and tried to build. While Mac OS X builds like a champ, MSVC is complaining (again). If I backup two versions of the file, I can get it to build (but I get link errors with FlightGear). The compilation errors I get are as follows (looks like another STL problem?). props.cxx c:\simgear\simgear\misc\props.cxx(1997) : error C2653: 'vector ' : is not a class or namespace name c:\simgear\simgear\misc\props.cxx(1997) : error C2065: 'iterator' : undeclared identifier c:\simgear\simgear\misc\props.cxx(1997) : error C2146: syntax error : missing ';' before identifier 'it' c:\simgear\simgear\misc\props.cxx(1997) : error C2065: 'it' : undeclared identifier c:\simgear\simgear\misc\props.cxx(1998) : error C2065: 'find' : undeclared identifier c:\simgear\simgear\misc\props.cxx(1999) : error C2446: '!=' : no conversion from 'class SGPropertyChangeListener ** ' to 'int' This conversion requires a reinterpret_cast, a C-style cast or function-style cast c:\simgear\simgear\misc\props.cxx(1999) : error C2040: '!=' : 'int' differs in levels of indirection from 'class SGPropertyChangeListener ** ' c:\simgear\simgear\misc\props.cxx(2299) : error C2653: 'vector ' : is not a class or namespace name c:\simgear\simgear\misc\props.cxx(2299) : error C2146: syntax error : missing ';' before identifier 'it' c:\simgear\simgear\misc\props.cxx(2300) : error C2440: '=' : cannot convert from 'class SGPropertyNode ** ' to 'int' This conversion requires a reinterpret_cast, a C-style cast or function-style cast c:\simgear\simgear\misc\props.cxx(2300) : error C2446: '!=' : no conversion from 'class SGPropertyNode ** ' to 'int' This conversion requires a reinterpret_cast, a C-style cast or function-style cast c:\simgear\simgear\misc\props.cxx(2300) : error C2040: '!=' : 'int' differs in levels of indirection from 'class SGPropertyNode ** ' c:\simgear\simgear\misc\props.cxx(2301) : error C2100: illegal indirection c:\simgear\simgear\misc\props.cxx(2301) : error C2227: left of '-removeChangeListener' must point to class/struct/union c:\simgear\simgear\misc\props.cxx(2333) : error C2653: 'vector ' : is not a class or namespace name c:\simgear\simgear\misc\props.cxx(2333) : error C2146: syntax error : missing ';' before identifier 'it' c:\simgear\simgear\misc\props.cxx(2335) : error C2446: '!=' : no conversion from 'class SGPropertyNode ** ' to 'int' This conversion requires a reinterpret_cast, a C-style cast or function-style cast c:\simgear\simgear\misc\props.cxx(2335) : error C2040: '!=' : 'int' differs in levels of indirection from 'class SGPropertyNode ** ' Jonathan Polley /blockquote/x-html ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Spiffy new panel gadget
David Megginson wrote: Andy Ross writes: This panel isn't quite right, though. The center attitude indicator isn't a flat card, but is in fact a rotating globe. This might be a good time to mention that we have an alternative method for creating panels. 3D models can now include other 3D models You ever have one of those days where you think of a cute idea, casually code it up to try it, and discover that it works better than you'd have ever expected? It's been a good day. Check out A-4 panel. It isn't quite done, clearly: + It's so close to the near clip plane that the precision errors cause nasty jittering; this happens to the rest of the cockpit geometry too. Honestly, I think this is probably unavoidable. We should really look at solutions for drawing the cockpit into a separate depth range from the terrain. On the other hand, it's kinda nifty to be able to zoom in to the cockpit in the outside view and see thins thing on the panel. + The cockpit geometry is kind of whacked. :) It wasn't really intended for viewing at 1m, so it doesn't quite fit. I had to shrink the ball down to about 4 inches in order to make it look right in combination with the virtual cockpit's default plane, which is itself kind of whacked (I know, I know, I really need to fix that). Again, I think we should consider allowing for separating a cockpit scene graph from the aircraft model and terrain. + We need an enclosure for it, with roll indicators, cross hairs and a turn ball before it'll be truly useful. I'm hoping someone with more 3D skill than I is willing to try to make the box. :) + At 192 triangles and 6 128x128 textures, this is an expensive instrument. There were no significant effect on frame rate on my machine, but we can't be sprinkling gadgets like this around the panel without hurting someone. + It's exposed some strange behavior in the lighting code -- the specular highlights at night (I know, specular highlights at night?) are way to bright, and there is an odd popping behavior as the vertices enter shadow. I think this might be a bug in plib; I haven't investigated. + This one really annoys me: the AC3D file format apparently doesn't allow you to specify normals explicitly, it wants to calculate them itself. This works fine for the vertices inside the texture, but texture boundaries show up as sharp edges because the polygons in separate objects don't share their coincident vertices. Combined with the specular highlight issue, this can look very strange. Is there a better file format? I know SSG has a native one. This sounds great, but I couldn't find an ounce of documentation on it, even in the code that parses it. Andy -- Andrew J. RossNextBus Information Systems Senior Software Engineer Emeryville, CA [EMAIL PROTECTED] http://www.nextbus.com Men go crazy in conflagrations. They only get better one by one. - Sting (misquoted) ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] MSVC Build Problem for props.cxx
I have submitted a patch to David. Here is what is needed : SG_USING_STD(find); SG_USING_STD(vectorSGPropertyChangeListener *); SG_USING_STD(vectorSGPropertyNode *); around line 29 of props.cxx -Fred - Original Message - From: Jonathan Polley [EMAIL PROTECTED] I didn't see anything like that in the new files, but I may not know what, exactly, I should be looking for. The only new using clause was in props.cxx: using std::find; Jonathan Polley On Thursday, June 20, 2002, at 08:02 PM, Christian Stock wrote: ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
