Re: [Flightgear-devel] radials
among other FAA documents which use the phrase inbound radial without the slightest hesitation. There are many other instances where you need to know one thing when taking the written test, and need to know something quite different for flying in the real world. Unless otherwise specified, you can assume what I say comes from the real-world point of view. Well - at least on the eastern side of the atlantic, where I do instrument flights in real world, the 090 radial is always EAST of the station, the 270 radial is WEST of the station. A controller advice proceed on radial 090 or intercept radial 090 always means you shall fly exactly east (magnetic) of the station and fly away from it. If you are requested to fly on radial 090 *inbound*, you are expected to be east of the station and fly *to* it on a track of 270. So the radial tells you where you are (or should be) and the word inbound gives the direction to fly. If omitted, fly in the direction of the radial and if present use the opposite direction. That is my experience from the written test, my flight training and my real-world flying. greetings outbound, Torsten - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] location-in-air ... magnetic bearings from the reference
That's a good point. I consider it a bug in what I've written. The canonical behavior is to use the magnetic deviation at the /reference/ point. Can somebody give me a hint how to obtain the deviation at the location of arbitrary navaids and airports? The magnetic variation is calculated in SimGear for the present position in calc_magvar() file coremag.cxx and I don't know of any mag-variation information in our database. You will never get any data for deviation, since that is specific for the aircraft. A dirty hack might be to relocate to the new position using the true bearing, reading the magnetic-variation property for the new position thereafter and relocate again using the new variation. Greetings, Torsten - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Simgear compilations
Hello, I am trying to compile, FlightGear-0.9.9 on my WinXP machine. I have succesfully installed plib-1.8.4 using Cygwin and also have my AL include and dll files intact. When I compile simgear-0.3.9, I get the following error. In file included from ../../simgear/sound/soundmgr_openal.hxx:50, from visual_enviro.cxx:33: /fg-0.9.9/include/AL/alc.h:39: error: expected constructor, destructor, or type conversion before '*' token /fg-0.9.9/include/AL/alc.h:39: error: expected `,' or `;' before '*' token /fg-0.9.9/include/AL/alc.h:51: error: variable `alcMakeContextCurrent' definition is marked dllimport. /fg-0.9.9/include/AL/alc.h:51: warning: `__cdecl__' attribute only applies to function types /fg-0.9.9/include/AL/alc.h:51: error: `ALCcontext' was not declared in this scope /fg-0.9.9/include/AL/alc.h:51: error: `alcHandle' was not declared in this scope /fg-0.9.9/include/AL/alc.h:63: error: variable or field `alcProcessContext' declared void /fg-0.9.9/include/AL/alc.h:63: error: variable `alcProcessContext' definition is marked dllimport. /fg-0.9.9/include/AL/alc.h:63: warning: `__cdecl__' attribute only applies to function types /fg-0.9.9/include/AL/alc.h:63: error: `ALCcontext' was not declared in this scope /fg-0.9.9/include/AL/alc.h:63: error: `context' was not declared in this scope /fg-0.9.9/include/AL/alc.h:70: error: variable or field `alcSuspendContext' declared void /fg-0.9.9/include/AL/alc.h:70: error: variable `alcSuspendContext' definition is marked dllimport. /fg-0.9.9/include/AL/alc.h:70: warning: `__cdecl__' attribute only applies to function types /fg-0.9.9/include/AL/alc.h:70: error: `ALCcontext' was not declared in this scope /fg-0.9.9/include/AL/alc.h:70: error: `alcHandle' was not declared in this scope /fg-0.9.9/include/AL/alc.h:76: error: variable or field `alcDestroyContext' declared void /fg-0.9.9/include/AL/alc.h:76: error: variable `alcDestroyContext' definition is marked dllimport. /fg-0.9.9/include/AL/alc.h:76: warning: `__cdecl__' attribute only applies to function types /fg-0.9.9/include/AL/alc.h:76: error: `ALCcontext' was not declared in this scope /fg-0.9.9/include/AL/alc.h:76: error: `context' was not declared in this scope /fg-0.9.9/include/AL/alc.h:79: error: variable `alcGetError' definition is marked dllimport. /fg-0.9.9/include/AL/alc.h:79: warning: `__cdecl__' attribute only applies to function types /fg-0.9.9/include/AL/alc.h:79: error: `ALCdevice' was not declared in this scope /fg-0.9.9/include/AL/alc.h:79: error: `dev' was not declared in this scope /fg-0.9.9/include/AL/alc.h:81: error: expected constructor, destructor, or type conversion before '*' token /fg-0.9.9/include/AL/alc.h:81: error: expected `,' or `;' before '*' token /fg-0.9.9/include/AL/alc.h:86: error: expected constructor, destructor, or type conversion before '*' token /fg-0.9.9/include/AL/alc.h:86: error: expected `,' or `;' before '*' token /fg-0.9.9/include/AL/alc.h:88: error: variable or field `alcCloseDevice' declared void /fg-0.9.9/include/AL/alc.h:88: error: variable `alcCloseDevice' definition is marked dllimport. /fg-0.9.9/include/AL/alc.h:88: warning: `__cdecl__' attribute only applies to function types /fg-0.9.9/include/AL/alc.h:88: error: `ALCdevice' was not declared in this scope /fg-0.9.9/include/AL/alc.h:88: error: `dev' was not declared in this scope /fg-0.9.9/include/AL/alc.h:90: error: variable `alcIsExtensionPresent' definition is marked dllimport. /fg-0.9.9/include/AL/alc.h:90: warning: `__cdecl__' attribute only applies to function types /fg-0.9.9/include/AL/alc.h:90: error: `ALCdevice' was not declared in this scope /fg-0.9.9/include/AL/alc.h:90: error: `device' was not declared in this scope /fg-0.9.9/include/AL/alc.h:90: error: expected primary-expression before '*' token /fg-0.9.9/include/AL/alc.h:90: error: `extName' was not declared in this scope /fg-0.9.9/include/AL/alc.h:90: error: initializer expression list treated as compound expression /fg-0.9.9/include/AL/alc.h:91: warning: `__cdecl__' attribute only applies to function types /fg-0.9.9/include/AL/alc.h:91: error: variable `alcGetProcAddress' definition is marked dllimport. /fg-0.9.9/include/AL/alc.h:91: error: `ALCdevice' was not declared in this scope /fg-0.9.9/include/AL/alc.h:91: error: `device' was not declared in this scope /fg-0.9.9/include/AL/alc.h:91: error: expected primary-expression before '*' token /fg-0.9.9/include/AL/alc.h:91: error: `funcName' was not declared in this scope /fg-0.9.9/include/AL/alc.h:91: error: initializer expression list treated as com pound expression /fg-0.9.9/include/AL/alc.h:92: error: variable `alcGetEnumValue' definition is marked dllimport. /fg-0.9.9/include/AL/alc.h:92: warning: `__cdecl__' attribute only applies to function types /fg-0.9.9/include/AL/alc.h:92: error: `ALCdevice' was not declared in this scope /fg-0.9.9/include/AL/alc.h:92: error: `device' was not declared in this scope /fg-0.9.9/include/AL/alc.h:92: error: expected
Re: [Flightgear-devel] location-in-air ... magnetic bearings from the reference
On Wed, 3 Jan 2007, John Denker wrote: *) I spelled out deg. I tried putting the ° symbol in the xml file, but it complained of a parse error. Using deg; didn't work, either. Any suggestions on how to encode symbols? Not directly an answer to you question but here's a tip that may be useful to you or others: I've recently switched to generating the xml config file (for the ch47d project) (ab)using the C preprocessor and a Makefile. So I put comments in the source file I feed to cpp instead, using regular c/c++ comments or #if -- #endif's. I find that very convenient. But most of my notes go, as plain prose, into a separate textfile. (The main reason for that setup, however, is to avoid doing a mistake I've done too many times before: adjusting common airfoil/rotorhead parameters for only one rotor with something completely unflyable as a result. Now I just #include the common parameters from one single file instead of changing two identical instances everytime. I didn't investigate the matter at depth, but I got the impression that there is no general include function in the xml standard. Many xml parser implementations add that functionality on top of xml though.)- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Animation and osg
Hi, I am preparing put the panel code into the scenegraph. For that I needed a generic scenery picking mechanism. That is now in place together with an 3D model animation type that can be used to execute some commands from our command manager on a mouse pick on specific 3D model objects. That animation type will not be supported with plib. So I omitted to check in an example usage for that. But the documentation in data/Docs/model-howto for that animation type is there. Have fun with interactive 3d objects. Greetings Mathias - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Animation and osg
--- Mathias Fröhlich wrote: Hi, I am preparing put the panel code into the scenegraph. For that I needed a generic scenery picking mechanism. That is now in place together with an 3D model animation type that can be used to execute some commands from our command manager on a mouse pick on specific 3D model objects. That's great news - no more difficult to create hot-spot panels for 3-D cockpits. Something that isn't clear from the model-howto.html is whether you can include Nasal fragments within the binding, or whether you need to use a listener on the property that is bound. -Stuart Send instant messages to your online friends http://uk.messenger.yahoo.com - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Animation and osg
Hi, IIRC you can use Nasal fragments using the nasal command. binding commandnasal/command script!-- your script here --/script /binding Cheers, Ralf - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] radials
On 01/04/2007 04:28 AM, Torsten Dreyer wrote: Well - at least on the eastern side of the atlantic, where I do instrument flights in real world, the 090 radial is always EAST of the station, the 270 radial is WEST of the station. A controller advice proceed on radial 090 or intercept radial 090 always means you shall fly exactly east (magnetic) of the station and fly away from it. If you are requested to fly on radial 090 *inbound*, you are expected to be east of the station and fly *to* it on a track of 270. This is the sort of thing that gives pedantry a bad name. 1) I started this discussion by discussing a number of scenarios and emphasizing that in most of them, position was specified in terms of bearing /from/ the reference. So please let's not argue about specifying pointlike positions and locations. There is nothing to argue about. The --azimuth option to fgfs is unconventional, and AFAICT nobody disagrees about that. 2) The exception to the outbound radial rule applies not so much to positions as to course lines. Pedantically and etymologically, all radials should be rays i.e. half-lines. In contrast course lines are /lines/ (not half-lines). Operationally, lines are very significant. If you are west of the station, -- a controller could (in pedantic theory land) instruct you to intercept the 090 course line that passes overhead the XYZ VOR; -- or I suppose another circumlocution might be intercept the reciprocal of the XYZ 270 radial; ++ but it is rather more concise to call it the XYZ 090 radial, which is the terminology that US controllers use (and are required to use). You can think of it as a _generalization_ of the idea of radial if you like: a radial that is a line rather than a half-line. I say again that using half-lines /from/ the station is good practice and common practice for specifying locations. But the point remains that using full-lines is good practice and verrry common practice for specifying courses. (The full-line terminology differs from the half- line terminology only for inbound courses.) As additional support for this, if any were needed, consider the case where you are southwest of the station, and instructed to fly a 045 heading to intercept the 090 radial. Depending on the deails of the situation, you might intercept the relevant line on the near side or far side of the station. The controller doesn't care -- and you shouldn't care either -- which of these two cases comes to pass. From a human-factors point of view it would be bad practice, indeed it would be absurd to worry about the distinction between these two cases. For good reason the VOR CDI indicator was designed to conceal the distinction. These human factors have been understood since at least the 1940s, when the VOR system was designed. Bottom line: -- When specifying pointlike positions, radials are rays i.e. half-lines radiating /from/ the station. -- When specifying course lines, radials are full lines. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] A6M2
The artificial horizon in the A6M2 appears to have roll reversed. I'm not sure if the problem was introduced in one of the recent commits, or if it's been there since instruments were first added. Other than that little (somewhat confusing) niggle it's a really nice model! Jon - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] radials
On Thu, 2007-01-04 at 10:45 -0500, John Denker wrote: Bottom line: -- When specifying pointlike positions, radials are rays i.e. half-lines radiating /from/ the station. -- When specifying course lines, radials are full lines. OK, which is it? My initial *correction* was to 1) in this quote: First, some background information. Suppose we are up in the air, 10 nm west of KXYZ airfield (which is colocated with the XYZ vortac). 1) If we were inbound to the field, I would report our position as 10 nm west, inbound on the 090 radial. 2) If we were outbound from the field, I would report our position as 10 nm out on the 270 radial. You indicate in this quote that for both cases 1) and 2) you report our position as. So applying your own *bottom line* to the stated goal of reporting your position, 2) is the correct position independent of your course/heading. Position never depends on your course. The VOR/OBS/CDI don't know anything about your heading or course. 1) is at best ambiguous since by your own *bottom line*, you are reporting your position as on the 090 radial which contradicts the less specific position report 10 nm west. The inbound statement should communicate your approximate magnetic course, but since you have reported two totally contradictory positions, your course is unknown from this report. The controller should ask for clarification. Happy New Year and please close this flight plan, Dave -- Dave Perry [EMAIL PROTECTED] - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Aircraft maintainers sought
Hi all, due to a combination of reasons it's very unlikely that I'll be doing any more FG work in the foreseeable future. if any one wants to pick up and maintain any of the aircraft I've started please feel free to do so. Mind you, you'll have your work cut out - they're all broken to some degree atm. LeeE - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Aircraft maintainers sought
Hi Lee, leee wrote: due to a combination of reasons it's very unlikely that I'll be doing any more FG work in the foreseeable future. I hope these reasons are not hidden in the nature of the FlightGear project Anyway, I'd like to thank you for the effort you put in 'your' aircraft, I had much pleasure with several of these ! Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Improved c172p autopilot
Can you send me your version of the file? Thanks in advance. On 1/3/07, Roy Vegard Ovesen [EMAIL PROTECTED] wrote: On Wednesday 03 January 2007 10:27, woodyst wrote: It can be fixed in kap140.nas file, I think. I would study that file well and if I can, I will send another patch. I've overhauled kap140.nas quite extensively. I've changed to more sensible property data types like boolenas instead of text. I've also fixed the bug that Joacim Persson reported. I'll try to hand it over to someone with write access to CVS tonight. Because of this you should hold off studying the code until the new version is in CVS. -- Roy Vegard Ovesen - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Woodyst. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Aircraft maintainers sought
leee schrieb: Hi all, due to a combination of reasons it's very unlikely that I'll be doing any more FG work in the foreseeable future. LeeE Dear Lee Elliot, this new year really starts with bad news for the FlightGear community. I just searched through the aircraft folder to remember which a/c were your work and found you unbelievable busy throughout the time. I want to thank you for all these nice aircraft with a broad spectrum (from Comper CLA 7 Swift up to the big ones), especially for the SU37 project which I enjoyed a lot the last time. But my hope is, although you won't have any time for developers work, you will stay with us and enjoy the further development of FlightGear. Regards Georg EDDW - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Animation and osg
Hi, On Thursday 04 January 2007 16:06, Stuart Buchanan wrote: Something that isn't clear from the model-howto.html is whether you can include Nasal fragments within the binding, or whether you need to use a listener on the property that is bound. Well, I would like to be able to include nasal commands. But that is not yet tested. And may be there is a part missing from the implementation. As this is a split out patch from one of the bigger chunks I have on my disk and that bigger chunk concentrates on rendering errors in the panel I did not yet include that. I also must admit that I never did include nasal myself in c code. So may be Andy or Melchior are faster than me to do that part. Or could somebody with nasal background give me a hint what I need the 'module name' for? That is the open question that is in this current code. Greetings Mathias - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
