RE: [Flightgear-devel] Hovercraft
Just an idle thought, but has anyone thought about simulating hovercraft/Ground-Effect vehicles within the FG framework yet? That could be done. I've thought about it. But, no time. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] VRP and Camera View
It occurred to me (during communications with Mathias) this morning that one downside with the VRP is the seeming rotation about the nose of the aircraft in the view. If either: 1) The offset from CG to VRP, or 2) The CG position itself (being effectively the actual physical rotational center) is supplied, then perhaps a LOOK_AT parameter for the camera view (external) can be adjusted so that the aircraft appears to pivot naturally. Is this already being done? If not, would this suggestion be implementable and helpful? Am I off-base? Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] VRP and Camera View
Yes. I mean no you aren't, but yes it is already being done. ;-) For anyone interested in this subject take a look at the -set.xml files for the pa28-161 or the p51d. Both add target-offset parameters to the views. These are offsets from the VRP (e.g. Nose) to where the camera should be pointing when it is operating in a tracking or LOOK_AT mode. What can we (JSBSim) provide to make this work for us; or, is there anything we need to do? Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Build process fails under Cygwin
Jon Berndt writes: Have the build process files changed at all for plib and simgear? I've been using the same process in building plib/simgear/flightgear for years, but this morning I get this when trying to build plib and simgear: --start-- $ automake Can't locate object method path via package Request at /usr/autotool/devel/share/autoconf/Autom4te/C4che.pm line 69, GEN1 line 198. configure.in: no proper invocation of AM_INIT_AUTOMAKE was found. configure.in: You should verify that configure.in invokes AM_INIT_AUTOMAKE, configure.in: that aclocal.m4 is present in the top-level directory, configure.in: and that aclocal.m4 was recently regenerated (using aclocal). automake: no `Makefile.am' found or specified -- end -- Now, this could also be due (and is more likely to be due) to changes in my **CygWin** environment, and the tools I use there. In any case, as far as plib and simgear go, I seem to be dead in the water. Remove autom4te.cache, retry, and all should be fine. Cheers - Dave Well, that made things *different*, at least: --- start --- --- automake -a --- Can't locate Autom4te/C4che.pm in @INC (@INC contains: /usr/autotool/devel/share /autoconf /usr/lib/perl5/5.8.2/cygwin-thread-multi-64int /usr/lib/perl5/5.8.2 /u sr/lib/perl5/site_perl/5.8.2/cygwin-thread-multi-64int /usr/lib/perl5/site_perl/ 5.8.2 /usr/lib/perl5/site_perl .) at /usr/autotool/devel/bin/autom4te line 39. BEGIN failed--compilation aborted at /usr/autotool/devel/bin/autom4te line 39. configure.in: no proper invocation of AM_INIT_AUTOMAKE was found. configure.in: You should verify that configure.in invokes AM_INIT_AUTOMAKE, configure.in: that aclocal.m4 is present in the top-level directory, configure.in: and that aclocal.m4 was recently regenerated (using aclocal). automake: no `Makefile.am' found or specified --- autoconf --- Can't locate Autom4te/C4che.pm in @INC (@INC contains: /usr/autotool/devel/share /autoconf /usr/lib/perl5/5.8.2/cygwin-thread-multi-64int /usr/lib/perl5/5.8.2 /u sr/lib/perl5/site_perl/5.8.2/cygwin-thread-multi-64int /usr/lib/perl5/site_perl/ 5.8.2 /usr/lib/perl5/site_perl .) at /usr/autotool/devel/bin/autom4te line 39. BEGIN failed--compilation aborted at /usr/autotool/devel/bin/autom4te line 39. --- end --- I don't think I've changed anything, other than updating the flightgear and related sources ... JOn ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Build process fails under Cygwin
So the question is -- What did you do to your Cygwin environment ? Norman I'd like to know. I just now reinstalled some of the things like automake, etc.. I'm going to try again. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Build process fails under Cygwin
So the question is -- What did you do to your Cygwin environment ? Norman I'd like to know. I just now reinstalled some of the things like automake, etc.. I'm going to try again. Jon Still no joy. I guess it must be something I did, but I don't know what it could be. I still get this: $ automake -a Can't locate Autom4te/C4che.pm in @INC (@INC contains: /usr/autotool/devel/share/autoconf /usr/lib/perl5/5.8.2/cygwin-thread-multi-64int /usr/lib/perl5/5.8.2 /usr/lib/perl5/site_perl/5.8.2/cygwin-thread-multi-64int /usr/lib/perl5/site_perl/5.8.2 /usr/lib/perl5/site_perl .) at /usr/autotool/devel/bin/autom4te line 39. BEGIN failed--compilation aborted at /usr/autotool/devel/bin/autom4te line 39. configure.in: no proper invocation of AM_INIT_AUTOMAKE was found. configure.in: You should verify that configure.in invokes AM_INIT_AUTOMAKE, configure.in: that aclocal.m4 is present in the top-level directory, configure.in: and that aclocal.m4 was recently regenerated (using aclocal). automake: no `Makefile.am' found or specified Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Build process fails under Cygwin
Now, this could also be due (and is more likely to be due) to changes in my **CygWin** environment, and the tools I use there. In any case, as far as plib and simgear go, I seem to be dead in the water. Remove autom4te.cache, retry, and all should be fine. Cheers - Dave I uninstalled and reinstalled autoconf and automake and now all seems well. I think I had my versions out of sync. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] VRP and Camera View
If I understand the VRP correctly, for almost all the airplanes the VRP location will be 0 0 0 IFF (not a typo) the nose of the aircraft is coincident with (0,0,0) in structural coordinates, yes, your statement is true. Otherwise, wherever the nose tip is located in the structural frame - that's the VRP. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Building FlightGear / getting some errors
When building FlightGear (and my setup in CygWin is now building plib and SimGear just fine), when I get to the YASim directory, I get these errors: g++ -D_REENTRANT -L/usr/local/lib -o yasim.exe yasim-test.o Airplane.o Atmosphere.o ControlMap.o FGFDM.o Gear.o Glue.o Integrator.o Jet.o Math.o Model.o PistonEngine.o PropEngine.o Propeller.o RigidBody.o Rotor.o Rotorblade.o Rotorpart.o SimpleJet.o Surface.o Thruster.o Wing.o Turbulence.o -lsgxml -lsgprops -lsgmisc -lsgdebug -lsgstructure Atmosphere.o(.eh_frame+0x11):Atmosphere.cpp: undefined reference to `___gxx_personality_v0' ControlMap.o(.text+0x1db):ControlMap.cpp: undefined reference to `__Unwind_Resume' ControlMap.o(.text+0x34e):ControlMap.cpp: undefined reference to `__Unwind_Resume' ControlMap.o(.eh_frame+0x12):ControlMap.cpp: undefined reference to `___gxx_personality_v0' Gear.o(.eh_frame+0x11):Gear.cpp: undefined reference to `___gxx_personality_v0' ... etc. 1) Did I do something stupid to my build setup again? :-) 2) For an FDM developer, how can some of the FDMs be left out of the build if a developer is only concentrating on development of one FDM? Is this easily possible? Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] tables and images and borders ... oh my
For the life of me, I can't get my sliced images to appear in a table without padding and borders, etc. Does anyone know if images have to be sized any particular way to get this to work, i.e. an even number of pixels or something? Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Web, tables, and image layout
OK. Fixed. Jon www.jsbsim.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Motion Base Simulator ?
You've seen those hydraulically actuated little simulator rides? Forget that, here's a bigger one: http://tinyurl.com/2oxzd Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Web, tables, and image layout
Check this out: http://validator.w3.org/check?uri=http%3A%2F%2Fwww.jsbsim.org You will want to decide what your target doctype really is and correct this before calling the problem solved. Interesting. This is helpful. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] FlightGear performance
I just did a bit of a performance test with FlightGear on my PC running Windows 2000, 1.2GHz Athlon, 256 MB RAB, and 64MB GeForce 2MX400. I did a reboot first, made sure I had no extraneous processes running, and cranked up FlightGear under CygWin (My desktop is 32 bit, 1024x768). FlightGear took a bit over a minute to come up, during which time there were NO messages at all from the command line. I think this is a bad thing. There ought to be occasional informative messages indicating the program is still running. After showing the splash screen, it was another 20 seconds or so until I was able to fly the C172. My initial frame rate was about 4-8 fps - very poor. As I was taking off the frame rate evened out at about 15 fps. I'm not sure why the performance has gotten so much worse than before. The first thing I'm going to check is my screen and openGL configuration. I've installed the latest video drivers from nVidia, so maybe something got overwritten. Is there anything in particular I want to keep track of? I vaguely remember a discussion about full-screen display, and I also think I should run in 16 bit color mode, but that's different than my screen depth ... I also noticed something that has been mentioned before here, that is that the C172 engine spins the prop at 2500-2700 rpm at full speed - obviously an FDM problem if it is one at all. I'll look into that, but any thoughts and comments on that are also solicited. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Menu: set airport from list - core
I selected the Location menu item that allows selection of an airport from a list. When I selected the menu item I got a segfault. I had just taken off in the c172, paused the sim, and made the menu selection. I did a make on flightgear this morning. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] [OT] Modeling and Control of a UAV
Interesting read (look carefully) :-) http://www.itk.ntnu.no/ansatte/Fossen_Thor/MSc/AndrewRoss.pdf Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] OpenAL update
I need help though from the Mac people and cygwin/mingwin people. What are the openal libraries called on these platforms. At the moment the I didn't see a CygWin platform listed for OpenAL on their web site (openal.org). I also didn't see mention of Cygwin here: http://developer.creative.com/landing.asp?cat=1sbcat=31top=38. I wonder if I simply download the source if I can compile it ... there's an experiment waiting for a developer. I'd do it, but the weather is turning nice (http://instacam.com/instacamimg/KEMAH/KEMAH_s.jpg - just up the street overlooking Galveston Bay, tonight's dinner destination), so I'm going outside with the family. This OpenAL thing has got me a little uneasy, being a CygWin user, but the benefits look real good. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] OpenAL update
I need help though from the Mac people and cygwin/mingwin people. What are the openal libraries called on these platforms. At the moment the configure script assumes we want to link with -lopenal, but I don't expect this to work right for every platform. I expect there may be a couple days of head aches here while we get these platform dependent differences ironed out. Please be patient! Has anyone seen reference to the use of OpenAL with CygWin anywhere? I downloaded it, and tried configuring the linux subdirectory to build under cygwin - no joy (yet, at least). The Windows directory is so far a bit of a mystery, but there is no mention of cygwin there, either. I did a google search but so far have not found the words cygwin and openal together in a meaningful web page. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] OpenAL
There is a link to a binary SDK available from Creative, though, so presumably cygwin users could use that? I believe cygwin can link programs against normal windows .lib files, right? Andy Unfortunately that's starting to get outside the range of expertise I have and also the time constraints I'm under ... :-( Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] OpenAL
Jon, you might also search for libopenal along with cygwin ... if cygwin packaged openal, I bet that is what they'd call it. Curt. That search appeared to be more productive initially, but nothing helpful has cropped up, yet. Jon, CygWin user - Help, Help! I'm being repressed! ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] OpenAL
I tried essentially what you suggested yesterday. I'll try again later today, but following your explicit example. If needed I may re-checkout the distro. I'll let you know what I get. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Real-Time Atmospheric Scattering
FYI: http://www.gamedev.net/columns/hardcore/atmscattering/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Jsbsim trim
..ok, time for another of my stupid questions: Mathias, does your new model code include tire creep? And tire sidewall flex? There are a lot of tire effects that might be modeled. The question faced in deciding what to model is: given the purpose of this FDM, what should be included to achieve the desired effect? There are some great technical papers hosted in the NASA Langley (and perhaps NASA Dryden) technical report servers. Several years ago when I was doing some initial RD for the JSBSim gear model I had some discussions with Bob Daugherty of NASA Langley about gear modeling (where they do a lot of very serious gear modeling and analysis), and he also referred me to some papers. The range of characteristics that might be modeled include tire slip, tire wind-up, spin up, and complex strut interactions, to name only a few of the more difficult ones. These problems are difficult even for detailed engineering sims, and in the case of trying to model any generic vehicle, these problems are compounded. There are some things I'd like for us to model, but JSBSim also hopes to remain comprehensive and comprehensible at the same time, so modeling some of the more subtle effects probably is not worth the effort. In any case, Mathias and I in particular are working on some sweeping changes for JSBSim that ought to make the gear modeling much more stable. After that, there are many other improvements to make - one of which is looking at the gear model to discern where improvements can (and _should_) be made. In the meantime, we are discussing some changes that might be made and doing some limited research into the matter, including reviewing the approaches used by other simulators such as racing sims. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] OpenAL
Jon, I have *no* idea if it actually produces any sound as I don't have a sound board on my development system but after getting the OPENAL CVS files cvs -d:pserver:[EMAIL PROTECTED]:/usr/local/cvs-repository login (use password guest) cvs -d:pserver:[EMAIL PROTECTED]:/usr/local/cvs-repository co openal then % cd $OPENAL % cd linux % ./autogen.sh I got this after running autogen.sh: configure.in:147: warning: AC_TRY_RUN called without default to allow cross compiling configure.in:147: warning: AC_TRY_RUN called without default to allow cross compiling configure.in:256: warning: AC_TRY_RUN called without default to allow cross compiling ... and then make totally cratered. % make % make test Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] OpenAL
You need to re run configure before make I left this step out in my original msg :-( % ./configure % make % make test Norman I got a successful build. I tried running some of the also-successfully-built test programs: --start-- $ ./testpitch2 got Windows native audio chans 2 bps 16 bal 4 sps 44100 abs 176400 cbs 0 setfmt okay note E beats 9 no sound --end-- Nothing produced any sound. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] 3d audio and doppler shift
(Requires latest CVS code of course.) Sorry Jon, no screen shots for this one. :-) Ha! How about a frequency/time plot? ;-) Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] OpenAL
Norman wrote: Have you tried my partial build of the openal / win directory http://www.vso.cape.com/~nhv/files/fgfs/openal.tgz probably best to install this into /usr/local i.e. cd /usr/local tar -xzvf $PATH_TO/openal.tgz -- test -- $ ./testdevice got Windows native audio -- test -- $ ./testmp3 boom.mp3 got Windows native audio chans 2 bps 16 bal 4 sps 44100 abs 176400 cbs 0 setfmt okay Could not GetProc alutLoadMP3_LOKI -- test -- $ ./testvorbis got Windows native audio chans 2 bps 16 bal 4 sps 44100 abs 176400 cbs 0 setfmt okay Could not GetProc alutLoadVorbis_LOKI -- test -- Many of the rest of them seemed to simply hang, but no sound was ever produced. I wonder, though, if your stuff was being used here, because I already have libopenal32.a in /usr/local/lib. I recompiled all the tests. Are we CygWin users going to be stuck with the previous codebase because openal doesn't work under CygWin? Or, do we have a choice with audio APIs? I'm hesitant to do a CVS update on the FlightGear tree at the moment because I'm not sure what the state of this OpenAL stuff is ... has it been formally introduced into FlightGear CVS, and does it replace the current audio system? Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] [OT] CygWierdness
Does anyone know why this might be happening: $ ls -al *.exe ls: invalid option -- Try `ls --help' for more information. I've already checked alias - I don't have anything for ls. ls --version gives: $ ls --version ls (fileutils) 4.1 Written by Richard Stallman and David MacKenzie. Copyright (C) 2001 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] [OT] CygWierdness
Curt wrote: The only thing that comes to mind is to check if you have a .exe filename that starts with a -. This will confuse ls's command line parser. There are a few ways around that, such as ls -al ./*.exe Heh. You're good. I had a file named -o parseDatcom.exe. Removing that fixed it. Thanks. [I wonder how that file got there ...] Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] (no subject)
There's someone that could help me or to find an aircraft which is more or less same at MB339PAN (it's the aircraft used by Frecce Tricolori, the Italian acrobatic team). I've tried to adjust the config file myself but every change I made meets some targets and estrange some others. An example are the flaps: the take off speed was too high so I've added more lift to them. As a result the aircraft has more lift but even the drag, that I've not changed, was increased. Why? Thanks, Luca PS: The config file is for JSBSim. So, if there's a way to calculate the data using some programs, I'll try even this way. There will be a way, but it's not quite ready, yet. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Beech 99
If you're connecting a prop to a turbine, that won't work. The present turbine model can't be used as a turboprop. As a result, the best way to model a turboprop is to use a turbine with a direct thruster, and adjust the thrust table to simulate a propeller (see the OV-10). The issue is that we do energy different between the turbine and piston engine, right? Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Beech 99
Dave C. wrote: Right. The relevant code from FGPropulsion is: PowerAvailable = Engines[i]-Calculate(Thrusters[i]-GetPowerRequired()); Thrusters[i]-Calculate(PowerAvailable); vForces += Thrusters[i]-GetBodyForces(); // sum body frame forces vMoments += Thrusters[i]-GetMoments(); // sum body frame moments Presently, the turbine model ignores PowerRequired and returns pounds-force. The Piston and Electric models use PowerRequired and return horsepower. I think this is fixable - are you working on it? If not, I might take a quick try at it. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Heading error calculation [brain exercise]
Does anyone know of a simple algorithm to calculate the difference between the desired heading and the actual heading, where the angle is given in degrees from 0 to 260? The stipulations are that the result must be = 180. For example, you can go from 60 to 340 degrees (counter-clockwise), 110 to 280 (clockwise), 290 to 40 (clockwise), etc. The desired result in the first case is -80, in the second case, 170, and for the last case, 110. And so on ... The ideal algorithm will have the fewest trivial operations. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Heading error calculation [brain exercise]
Does anyone know of a simple algorithm to calculate the difference between the desired heading and the actual heading, where the angle is given in degrees from 0 to 260? The stipulations are that the result must be = 180. For example, you can go from 60 to 340 degrees (counter-clockwise), 110 to 280 (clockwise), 290 to 40 (clockwise), etc. The desired result in the first case is -80, in the second case, 170, and for the last case, 110. And so on ... The ideal algorithm will have the fewest trivial operations. desired heading - actual heading - difference ( in the range -360 to +360) if difference -180 then add 360 if difference 180 then substract 360 Jorge Van Hemelryck Thanks, Jorge, for the answer I was looking for, as well is for ignoring my re-definition that a complete circle goes from 0 to 260 (See above ... Ooops!). Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] FlightGear news letter
I've volunteered to help John Wojnaroski with editing a FlightGear newsletter, This is great news. Firstly, a title. Jon's newsletter is called 'Back of the Envelope', which I think is particularly clever - JSBSim is anything but a back-of-the-envelope calculation, and there are echoes of flight envelope, too. I'm severely lacking inspiration of this calibre, so here's my offer: a bottle of one of the fine beers from my local brewery [1], lovingly packed and shipped to your location, for the best suggestion for the title of a FlightGear newsletter. Competition closes 3 weeks from today, judges' decision is final, all entries become the property of, er, (forget that one), yadda yadda. FlightBeer. A just reward. :-) Fame, glory and Wickwar beer! What are you waiting for? Secondly, we're missing suggestions for content. Suggest away, but what I'd really like is for you to suggest and volunteer to write, as well. I think that the first one should contain some sort of introduction to FlightGear. There are certainly a lot of articles already written on that topic, but it just seems appropriate. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] FlightGear news letter
snip FlightBeer. A just reward. :-) Hmm. http://news.bbc.co.uk/1/hi/uk/3286049.stm refers, I think :¬) Nonetheless, your entry is in the hat; multiple tries are allowed! Actually, that wasn't an entry for the newsletter title, but a little joke about the reward! Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Cygwin and OpenAL
Was the OpenAL/Cygwin issue ever cleared up? I can't update my FlightGear codebase. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Cygwin and OpenAL
I have created a new OpenAL tarball that breaks ALut into a separate DLL http://www.vso.cape.com/~nhv/files/fgfs/openal_cyg.tgz $ tar -tzf openal_cyg.tgz bin/ bin/ALut.dll bin/openal32.dll include/ include/AL/ include/AL/al.h include/AL/alc.h include/AL/alctypes.h include/AL/altypes.h include/AL/alu.h include/AL/alut.bak include/AL/alut.h include/AL/aluttypes.h include/AL/alutypes.h lib/ lib/libALut.a lib/libopenal32.a win/Makefile HTH Norman I don't know who takes care of these matters, but I wonder what is the viability of getting these as an option to be auto-installed via the CygWin installer? Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] [OT, article] Memphis Belle pilot passes away
I hope this doesn't offend anyone's sensitivities, but from a purely historical perspective this article is interesting: http://www.foxnews.com/printer_friendly_story/0,3566,120053,00.html Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] [OT, article] Memphis Belle pilot passes away
Only because it's from fox news. Don't bother wasting time on a reply, just eat shit Tex. Jeez, shouldn't there be a minimum age for posting to this list? Yes, I'm puzzled. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] YASim prop changes
Hi Jim The other day you were saying about Jon do a JSBSIM fdm well there is one over at JSBSIM but I have done a separate one that will drop into FG if you are interested.If not no problems. I was doing one ... still have it in-work. Kept running into things I wanted to fix and add in the code and getting distracted. I was using DATCOM to help with aero tables. Now we are close to having aero tables generated with DATCOM+ directly (thanks to Bill Galbraith). Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] YASim prop changes
Yes I know I downloaded it and used it. Didn't know about the monitoring file you were outputing from it, ended up with a 400meg file, good thing I had it on the big drive(LOL). Oops! :-) I really ought to turn these off by default. In fact, the OUTPUT section is destined to be removed from aircraft files and put in a different environment/simulation config file in the future I think. Some things about the FDM.The engine and prop tie up seems strange. If I increase the diameter of the prop the idle rpm drops and with a 10'5'' prop for some reason the prop pitch never got past about 12deg with the throttle wide open.Is the prop a direct drive off the crankshaft or is there a gearing property somewhere I have not found. We did implement gearing, but I am not sure what the status if that is, or if the changes made it into the P-51D FDM. In any case, it is untested and rough beta. Also the best I have been able to get out of the P51 is about 275mph at about 5000' and the best climb rate with out loseing speed is about 1500'/min. What properties would be worth playing with in the aero FDM to improve these figures closer to what the actual A/C could achive. Sounds like drag is too high, or it could be that the prop problems are causing low performance from the engine model ... What I am most curious about is how easy it was to take off. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] RFD: JSBSim Cessna 172p stability patch
Coming back to the (default) JSBSim Cessna 172p after spending a couple of months flying the YASim pa28-161, I find the 172 extremely slippery, far too much for a trainer. While the Cherokee tends to feel more stable in flight than a 172 (i.e. it has more roll, pitch, and yaw damping), the 172 still shouldn't be nearly so light in roll, pitch, or especially yaw as it currently is. I've made a patched-up file that allows the 172p to handle much more realistically, but I'm not willing to upload it to CVS yet, because I'm not sure that I've done the right thing. To keep the 172 from wallowing, I increased the roll damping coefficient (Clp) from -0.484 to -1.2, the pitch damping coefficient (Cmq) from -12.4 to -15, and the yaw damping coefficient from -0.0937 to -0.2. The patched file ($FG_ROOT/Aircraft/c172p/c172p.xml) is available at http://www.megginson.com/Aviation/c172p.xml I don't want to commit this file to CVS yet for a couple of reasons: 1. Increasing the damping may simply mask a different problem, such as a unit mismatch or mistaken value for another coefficient (the biggest problem comes around yaw/roll coupling) -- someone who understands aerodynamics better needs to look at the actual moments generated by each coefficient at runtime to see if they are out of whack. 2. I have over 200 hours in a Piper since I last sat in a Cessna 172, so I don't know how accurate my memory is of its handling -- I remember that it felt a bit less stable than a Cherokee, but as a trainer, it still had a *lot* of damping compared to a high-performance aircraft. My revised file seems to fly much better to me, but I'd like to hear opinions from other people with real experience in 172's, as well as the aerodynamic engineering types. I'd also be interested in feedback from non-pilots about the handling difference. Thanks, David. There are a couple of things I can think of to do, here. One is that I sure wish I had time to make a DATCOM model of the C-172 that could give me some aero data for comparison. But with my schedule now I can't make any promises, but I will get to this someday! The second comment is that it ought to be possible to get some real numbers for you pretty quickly from comparable aircraft. I think I can do that tonight or tomorrow. Third, there are some equations that ought to shed some light on things. Fourth, it will be interesting to see if pilot perceptions suggest altering all/most coefficients in the same direction for all aircraft in order to give the perception of proper flight characteristics. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] RFD: JSBSim Cessna 172p stability patch
For comparison: I've made a patched-up file that allows the 172p to handle much more realistically, but I'm not willing to upload it to CVS yet, because I'm not sure that I've done the right thing. To keep the 172 from wallowing, I increased the roll damping coefficient (Clp) from -0.484 to -1.2, the pitch damping coefficient (Cmq) from -12.4 to -15, and the yaw damping coefficient from -0.0937 to -0.2. The patched file ($FG_ROOT/Aircraft/c172p/c172p.xml) is available at The Navion has Clp = -0.410 Cmq = -9.960 Cnr = -0.125 The Cherokee has Clp = -0.429 Cmq = ?? Cnr = -0.0873 Equations from Nicolai (Royal Aeronautical Society) has: Clp = -0.350 My thinking is that given this, it appears to be unlikely that Clp should go from -0.484 (a seemingly reasonable number) to over twice that. Further, the other numbers seem OK, too. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] RFD: JSBSim Cessna 172p stability patch
The Navion has Clp = -0.410 Cmq = -9.960 Cnr = -0.125 ... Given these numbers I'd suspect that if there is a problem, perhaps we need to review our MoI's. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] RFD: JSBSim Cessna 172p stability patch
That is a tricky issue, because using spring-loaded controllers gives a significantly different feel than fully-loaded aircraft controls, and there is always a danger of altering the flight characteristics to compensate for the control differences. FWIW, I sent an email to Cessna customer support last night asking them about the availability of some aero and mass props data for their C-172 - or at least Ixx and Clp. I wonder if I will even hear back. To try to avoid that problem this time, I tried to concentrate on rates (how fast the plane could bank, pitch, and yaw), coupling (how much adverse yaw a particular bank causes and how much bank a particular yaw causes), and recovery (how the plane recovers from a yaw or pitch disturbance). I deliberately ignored control feel. The model I posted seems a lot closer to what I remember of the 172 and what I observe in my PA-28, but unfortunately, I do not currently have measurements to test it against. I have data for the PA-28 somewhere. I ought to validate the PA-28 JSBSim mode we have and see how they all compare. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] JSBSim C-172 Performance
2) The MoIs are too low. This is possible - I have not yet checked these out, but again I believe we will find these numbers to be pretty good. I have access to a commercial C172 model that has been FAA certified for a level 3 FTD. I wish I could share more of it, but I will say that the IXX, IYY, IZZ we use in FG are *exactly* the same numbers the commercial C172 uses. The empty weight values? I suppose they must have originated from the manufacturer. I looked at some of the other parameters and they are at least an order of magnitude different so they must be using different units or different conventions or something. For C172: Clp = -0.484 if p is in rad/sec = Clp = -0.0084 if p is in deg/sec This number is highly reliable by calculation and by comparison. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] JSBSim C-172 Performance
Relevant technical reports (I think the C-172 is included in this report): http://www.dfrc.nasa.gov/DTRS/1966/Bib/H-451.html Abstract: A review of existing criteria indicated that the criteria have not kept pace with aircraft development in the areas of dutch roll, adverse yaw, effective dihedral, and allowable trim changes with gear, flaps, and power. This study indicated that criteria should be specified for control-system friction and control-surface float. Furthermore, this program suggests a method of quantitatively evaluating the handling qualities of aircraft by the use of a pilot-workload factor. --- Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Re: making instrument scales with MetaPost
* Jon S Berndt, Fri May 21 16:44:16 CDT 2004: FWIW, Gimp has a script that creates text arcs that I have considered using if I ever get a chance to make some instruments. Gimp is always a good choice. However ... http://members.aon.at/mfranz/textarc.png (27kB) m. :-] Show-off. ;-) That's cool. You think it would work for this? http://www.dfrc.nasa.gov/gallery/photo/XB-70/HTML/ED97-44244-1.html Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Panels, Properties, and FDMs
You might want to take a look at the code yourself, I don't have the answers off the top of my head. But one suggestion: How about enhancing the interface by allowing the JSBSim-side to FGFS-side property mappings to be defined in the JSBSim configuration file? If we are talking about the same thing, I think this has a lot of appeal, and I've been thinking about something like this for about a week or two. I'll post some thoughts on it when I git some time. I'm about ready to make a major commit into CVS that will change all aircraft models and bump up the config file version number a notch. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] itoa? sprintf?
What is the best way (most supported, cross-platform) to turn an integer into an STL string type? Or, even an ASCII char[]? It seems that itoa() is not totally common. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Autoconf, autoheader, automake, etc.
I've looked in a few places, but can't find a definitive reference on automake, autoconf, etc. There don't seem to be any O'Reilly books on this, either! Anyone have any suggestions? Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Newsletter
What's the status on the FlightGear newsletter? Did a name ever get chosen? Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Speaking of King Airs ...
From AvWeek: Cause Circumstance: Another King Air Stalls on Short Final http://www.aviationnow.com/avnow/news/channel_bca_story.jsp?id=news/cc054.xml Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] f16 model broken?
Since the JSBSIM update some days ago the f16 model stopped working properly for me. The elevator appears to be oscillating randomly, it's seemingly in a different position for each frame update. ..the real thing does this too. Erik's F-16 has been around for a while, and working. So, it may be some change I made recently. There have been a few changes to the FCS. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] f16 model broken?
Erik's F-16 has been around for a while, and working. So, it may be some change I made recently. There have been a few changes to the FCS. Jon I might add that my changes were to fix things that really were broken. :-) Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] f16 model broken?
I might add that my changes were to fix things that really were broken. Which might be the reason the F-16 is left broken right now. Maybe it was relying on broken code too much in the past? That thought did occur to me. I did correct the way some filters were done. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] f16 model broken?
Ok. The first thing I will try is to see if I can get the PID controllers to work correctly again. If that fails we can always look further into it. Something wierd is also going on with alpha that may have had to do with changes to FGAuxiliary. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Property references
I need some references to papers, articles, discussions, etc. regarding properties. If anyone can suggest where I might find writings on this subject, please let me know ASAP. I'll be looking around, too, so I may find something shortly, but this is a timely and urgent need. Thanks a bunch. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] RE: [Jsbsim-devel] Property references
I need some references to papers, articles, discussions, etc. regarding properties. If anyone can suggest where I might find writings on this subject, please let me know ASAP. I'll be looking around, too, so I may find something shortly, but this is a timely and urgent need. Thanks a bunch. Jon Found the perfect reference for my needs: props.html Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] props.html
Can anyone tell me if/where the props.html file is that describes the property system? I can't seem to find it in the source tree or on the web sites - but it IS in simgear CVS. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] props.html
Jon Berndt wrote Can anyone tell me if/where the props.html file is that describes the property system? I can't seem to find it in the source tree or on the web sites - but it IS in simgear CVS. It used to be around - I have a print-out of it! What bit do you want? I could scan it in. Vivian I actually need to refer to it as a reference, but I don't see that it actually exists as a live document on any web site. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] props.html
The property system is best described as an in-memory LDAP database which holds the state of global variables. The system has a tree like hierarchy (like a file system) and has a root node, sub nodes (like subdirectories) and end-nodes (variables). All variables are kept internally as raw values and can be converted to any other supported type (boolean, int, float double and string). Like a file system, every node can be accessed relative to the current node, or absolute to the root node. The property system also allows aliasing nodes to other nodes (like symbolic linking files or directories to other files or directories) and may be assigned read-only or read-write. If necessary it would be possible for parts of the program to hold it's own property tree, which is inaccessible from the global property tree, by keeping track of it's own root-node. This is pretty good - I may incorporate some of this in the paper. Property I/O code allows one to easily read the tree from, or write the tree to an XML file. After reading this, I suspect that we (JSBSim) could be using the property system inherent features more advantageously. This will all come when we incorporate a better XML parser, I expect. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] props.html
That just appears to be a list of properties. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Vivian Meazza Sent: Saturday, July 03, 2004 9:00 AM To: 'FlightGear developers discussions' Subject: RE: [Flightgear-devel] props.html Vivian Meazza wrote Sent: 03 July 2004 14:52 To: 'FlightGear developers discussions' Subject: RE: [Flightgear-devel] props.html Jon Berndt wrote Can anyone tell me if/where the props.html file is that describes the property system? I can't seem to find it in the source tree or on the web sites - but it IS in simgear CVS. It used to be around - I have a print-out of it! What bit do you want? I could scan it in. Is this what you were after? Source/docs-mini/README.properties V. ___ 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
RE: [Flightgear-devel] props.html
The property system is best described as an in-memory LDAP database which holds the state of global variables. The system has a tree like hierarchy (like a file system) and has a root node, sub nodes (like subdirectories) and end-nodes (variables). All variables are kept internally as raw values and can be converted to any other supported type (boolean, int, float double and string). Like a file system, every node can be accessed relative to the current node, or absolute to the root node. The property system also allows aliasing nodes to other nodes (like symbolic linking files or directories to other files or directories) and may be assigned read-only or read-write. If necessary it would be possible for parts of the program to hold it's own property tree, which is inaccessible from the global property tree, by keeping track of it's own root-node. Property I/O code allows one to easily read the tree from, or write the tree to an XML file. Would you say that the JSBSim property tree is grafted onto the FlightGear tree? Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] domain name
We have a sourceforge account for the project, and SF offers some kind of built in capability for accepting donations. I don't know how it works and have never used it, but it might be worth investigating sometime in the next 11 months. Yes. It's not that hard to set up. I've turned on the feature for JSBSim, hoping beyond hope that some kind souls would send a few pennies our way. As you know I've got a conference I'm supposed to present a paper at in several weeks. Unfortunately, the conference has not been deemed to be work-related enough to justify my company sending me there, so it will be on my dime. :-( Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Concorde
This ought to be easy (haven't I said that before?). If no one else gets to it, I'll give it a shot after the kids get to sleep - if _I_ am still awake... Which version of JSBSim do you have now? It makes a difference. Look in FGJSBBase.cpp at top to see. Jon -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Curtis L. Olson Sent: Tuesday, July 06, 2004 5:37 PM To: [EMAIL PROTECTED] Subject: [Flightgear-devel] Concorde I have commited a first stab at a Concorde model, first created by Melchior and the further enhanced by Thierry (a mailing list reader, but non-poster.) However, when I try to run it with the latest cvs version of FG, I get an endless string of: Unknown identifier: EOF in engine file: Olympus593Mrk610 Unknown identifier: EOF in engine file: Olympus593Mrk610 Unknown identifier: EOF in engine file: Olympus593Mrk610 Unknown identifier: EOF in engine file: Olympus593Mrk610 Unknown identifier: EOF in engine file: Olympus593Mrk610 Unknown identifier: EOF in engine file: Olympus593Mrk610 . . . Can anyone familiar with JSBSim aircraft construction and engines take a quick peek and see if there is an easy fix. I suspect it is some sort of version mismatch with the code, or maybe some sort of installation mistake on my part. Hopefully a quick fixer for someone who knows what they are doing. Thanks, 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 mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] L1011-500
I'm still very confused with the axis used, and the model is appearing behind the actual FDM A/C In the aircraft config file, locations are given in structural frame. Structural frame in an aircraft has the X axis pointing backwards, the Z axis up, and the Y axis out the right side. The origin can, technically, be anywhere. Usually, it is near the nose. The exact location does not really matter, because *internal* to the FDM, contact point distances from the CG are computed and used - again: _internal_ to the FDM only the difference between two points is used. values used are: AC_CGLOC 921.1 0.0 -18.0 AC_AERORP921.1 0.0 0.0 AC_EYEPTLOC 0.0 -30.0 75.0 AC_VRP 0.0 0.0 0.0 the 3d model has nose at (0,0,0) I understand it this way, please correct what's wrong: AC_CGLOC - this is the center of gravity, from which all other points are related to Sort of. The CG is the point about which the equations of motion are based - the CG is the point about which the forces and moments act, and about which the aircraft rotates. AC_AERORP - aerodynamic reference, should be near the CG, so it has a similar value Yes. AC_EYEPTLOC - this is where the view is placed when in cockpit view, related to(??) CG (??) This is just the point where the pilot's eyes are located. I do not think this is used in FlightGear, but it is used in JSBSim to also calculate the accelerations that the pilot feels. The pilot's sensors are located near his/her eyes, too. This is given in inches as other measurements are, and in the same coordinate system as CG, reference point, etc. AC_VRP - point related to the CG where the nose of the 3d model should be A 3d model with nose made at (0,0,0) in the editor should have a VRP of (0,0,0) and this should be enough to position the model properly This is the point that the 3D modeler and the aircraft flight model designer agree upon as a reference point. From the FDM point of view, really only the CG is of interest - i.e. the latitude/longitude/altitude that is reported by the FDM refers actually to the specific lat/lon/alt of the CG. After long discussions some months ago, we decided that in order to make things work out better, the FDM would report the position of some common point that the modeler could easily see. That point was agreed upon as the nose of the aircraft. So, the VRP is simply the (x,y,z) coordinate (in inches) of the nose of the aircraft in the same coordinate system being used for reporting the CG, aero reference point, landing gear locations, etc. The modeler would then make sure either that their 3D model had its origin at the nose, or that the offset from the origin of the 3D model to the nose (the agreed upon visual reference point) is given. I forget which file is used to report this 3D model offset, or skew. The end result of using the VRP is that the FDM always reports the position of the nose (considering the orientation and position of the aircraft), and if FlightGear places the 3D model so that the nose of the aircraft model is at the lat/lon/alt reported by the FDM, then everything works out. But, the camera (I believe) looks at the nose of the aircraft, too, so it appears as though the aircraft rotates about the nose, so there is probably some adjusting that needs to be done to the camera angle ... I forget, and that's not my area of expertise. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] status of aircraft carrier
It's important to remember that the FDM doesn't know a ship from Shinola. guffaw Very good. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] RE: Help 3D model about FlightGear.
Hi, John: This is a question for the FlightGear mailing list. I will forward this there. Jon -Original Message- From: [mailto:[EMAIL PROTECTED] Sent: Friday, July 16, 2004 9:50 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Help 3D model about FlightGear. Dear Sir: Hello. I am a new user of FlightGear, and there are some problems when I use it. I have downloaded and used the software FlightGear(0.9.4) for windows. The 3D model files in FlightGear are files with suffix ac. I want to draw a 3D model by myself, and I have downloaded the software AC3D from www.ac3d.org (I havent buy the license). The problem is that, the 3D model built by AC3D can not be used in FlightGear. There are the steps I have done next: 1.Draw my own 3D model with the software AC3D and name it as ufo.ac. 2.Replace the old file ufo.ac(in C:\FlightGear\data\Aircraft\ufo\Models) by that new ufo.ac which I drew before. 3.Execute FlightGear launcher. After that, when I select the UFO model in the interface Select an aircraft, the wrong would appear: the FlightGear would stop. There are some questions I want to ask: 1.Why cant I use the new 3D model? 2.If I buy the AC3D license, could the 3D model built by AC3D be used in FlightGear? 3.Are there some other ways to make 3D model with suffix ac? If there are, which software should I use? 4.Are the steps I have done alright? I beg you some advice. Thank you. Best wishes, john 2004.7.17 _ MSN Messenger: http://messenger.msn.com/cn ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Building the latest ...
I had forgotten that FlightGear has been moved over to OpenAL. I downloaded the new base package to see if there is an L1011 there (I didn't see one). But, now, my FlightGear executable doesn't work with the new base package, so I tried downloading plib, but plib cvs doesn't seem to be up at the moment. I also found that I have this: libopenal32.a in /usr/local/lib. I'm wondering if this is now standard issue in a CygWin install. Does anyone know? Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Building the latest ...
Never mind. I guess the CVS repository for plib has changed/ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Jon Berndt Sent: Sunday, July 18, 2004 9:23 PM To: Flightgear-Devel Subject: [Flightgear-devel] Building the latest ... I had forgotten that FlightGear has been moved over to OpenAL. I downloaded the new base package to see if there is an L1011 there (I didn't see one). But, now, my FlightGear executable doesn't work with the new base package, so I tried downloading plib, but plib cvs doesn't seem to be up at the moment. I also found that I have this: libopenal32.a in /usr/local/lib. I'm wondering if this is now standard issue in a CygWin install. Does anyone know? Jon ___ 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] Difficulty with building under Cygwin
I updated plib/simgear/flightgear/base from CVS. Built plib and simgear. Checked the dates on the libs - they're all current. The sources were updated from CVS. I tried building FlightGear and got this: ... checking for simgear/version.h... yes checking for simgear 0.3.6 or newer... 0.3.6 or greater... wrong version So, the FlightGear build failed. How do I get around this? Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Plotting
Hi While trying to correctly tweak the FDM and PID controllers for the L1011-500, i though it would be really nice to have some sort of standalone app running on a remote machine, plotting selected property(es) oscilloscope style (in my case, i'd like to make it run in my old P133). There is a facility in both JSBSim and FlightGear for piping data through a socket. I am not familiar with the method used by FlightGear. For JSBSim, you can specify a PORT, IP address, as well as select a set of terms to send (for instance, flight control component input/outputs from the control laws as specified using JSBSim FCS components). You can also specify a property to send. Here is the format: OUTPUT NAME=192.168.0.2 TYPE=SOCKET PORT=5156 RATE_IN_HZ 20 SIMULATION ON ATMOSPHERE OFF MASSPROPSOFF AEROSURFACES ON RATESON VELOCITIES ON FORCES ON MOMENTS ON POSITION ON COEFFICIENTS OFF GROUND_REACTIONS ON FCS ON PROPULSION ON /OUTPUT Actually, the data sent across a socket is now not configurable, as is writing data to a data file, at this time. It's not that hard to change. You can use the netcat (nc) application under unix/linux/cygwin to test out the socket. I saw that this is not a new idea, is there anything usable at the moment? If not, i wouldn't mind to work on it, just point me in the right direction :) a little OT: What other tools might be useful in debugging aircrafts? I use another tool I wrote called SimPlot. It's in JSBSIm CVS. It does require you to download the DISLIN plotting library, but it is the quickest dirtiest plotting tool I've seen and perfect for doing fast analysis. You can also set up a plotting directives file (XML format) and have SimPlot automatically create a set of plots from a data file created by a previous JSBSim run, and SimPlot will also create an HTML file that interfaces with the auto-generated plots. It makes for a very quick turnaround cycle in debugging, making changes, and seeing the results. This might be a good topic for an article in the upcoming Back of the Envelope JSBSim newsletter, which is now about half done. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Difficulty with building under Cygwin
What is the content of /usr/local/include/simgear/version.h ? ( or wherever you installed SimGear ? ) -Fred The version looks right, I think (but the $Id date is way off): // $Id: version.h.in,v 1.1.1.1 2002/09/07 02:58:19 curt Exp $ #ifndef _SIMGEAR_VERSION_H #define _SIMGEAR_VERSION_H #define SIMGEAR_VERSION 0.3.6-pre1 ... It seems as though, then, that my installation of FlightGear is not looking for the correct pre-release version of simgear, but I don't know why. I've updated it from CVS. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Difficulty with building under Cygwin
The version looks right, I think (but the $Id date is way off): // $Id: version.h.in,v 1.1.1.1 2002/09/07 02:58:19 curt Exp $ Don't llok at the $Id, it is the Id of version.h.in that is an old template but version.h is generated every time you run configure. Correct. I was just pointing it out. #ifndef _SIMGEAR_VERSION_H #define _SIMGEAR_VERSION_H #define SIMGEAR_VERSION 0.3.6-pre1 ... It seems as though, then, that my installation of FlightGear is not looking for the correct pre-release version of simgear, but I don't know why. I've updated it from CVS. Do you have another simgear version somewhere else ? -Fred Nope. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Being's new colors
This is pretty: http://www.boeing.com/news/releases/2004/photorelease/q3/pr_040719g.html Might be nice to see this on some of the FlightGear Boeing planes (the test ones ;^) Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Difficulty with building under Cygwin
This is a case where you really should go look at the end of the config.log
file to see *exactly* why the version check is failing.
Curt.
What should one look for in config.log? There appears to be several problems. The
following shows what the worst problem is, however (but I'm not sure how to fix it):
configure:9805: test -z
|| test ! -s conftest.err
configure:9808: $? = 0
configure:9811: test -s conftest.o
configure:9814: $? = 0
configure:9824: result: yes
configure:9828: checking simgear/version.h presence
configure:9838: g++ -E conftest.cc
configure:9844: $? = 0
configure:9864: result: yes
configure:9899: checking for simgear/version.h
configure:9906: result: yes
configure:9923: checking for simgear 0.3.6 or newer
configure:9969: g++ -o conftest.exe -D_REENTRANT -L/usr/local/lib conftest.cc 5
configure:9972: $? = 0
configure:9974: ./conftest.exe
configure:9977: $? = 255
configure: program exited with status 255
configure: failed program was:
| /* confdefs.h. */
|
| #define PACKAGE_NAME
| #define PACKAGE_TARNAME
| #define PACKAGE_VERSION
| #define PACKAGE_STRING
| #define PACKAGE_BUGREPORT
| #define PACKAGE FlightGear
| #define VERSION 0.9.5-pre1
| #ifdef __cplusplus
| extern C void std::exit (int) throw (); using std::exit;
| #endif
| #define FG_MPLAYER_AS 1
| #define ENABLE_THREADS 1
| #define STDC_HEADERS 1
| #define HAVE_SYS_TYPES_H 1
| #define HAVE_SYS_STAT_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STRING_H 1
| #define HAVE_MEMORY_H 1
| #define HAVE_STRINGS_H 1
| #define HAVE_INTTYPES_H 1
| #define HAVE_STDINT_H 1
| #define HAVE_UNISTD_H 1
| #define FGFS 1
| #define FG_USE_CLOUDS_3D 1
| #define HAVE_DAYLIGHT 1
| #define ENABLE_AUDIO_SUPPORT 1
| #define HAVE_LIBPTHREAD 1
| #define PU_USE_GLUT 1
| #define FG_GLUT_H GL/glut.h
| #define WIN32 1
| #define NOMINMAX 1
| #define ENABLE_PLIB_JOYSTICK 1
| /* end confdefs.h. */
|
| #include stdio.h
|
| #include simgear/version.h
|
| #define STRINGIFY(X) XSTRINGIFY(X)
| #define XSTRINGIFY(X) #X
|
| #define MIN_MAJOR 0
| #define MIN_MINOR 3
| #define MIN_MICRO 6
|
| int main() {
| int major, minor, micro;
|
| printf(%d.%d.%d or greater... , MIN_MAJOR, MIN_MINOR, MIN_MICRO);
|
| sscanf( STRINGIFY(SIMGEAR_VERSION), %d.%d.%d, major, minor, micro );
|
| if ( major MIN_MAJOR ) {
|return -1;
| } else if ( major == MIN_MAJOR minor MIN_MINOR ) {
|return -1;
| } else if ( major == MIN_MAJOR minor == MIN_MINOR micro MIN_MICRO ){
|return -1;
| }
|
| return 0;
| }
|
|
configure:9987: result: wrong version
configure:9989: error: Install latest simgear first...
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Difficulty with building under Cygwin
My SimGear build was not completing. I think it has something to do with the move to OpenAL. As I was building simgear I got this: ... checking for library containing alGenBuffers... -lopenal32 checking for library containing alutInit... no ... Later on, I get this: g++ -D_REENTRANT -L/usr/local/lib -o openal_test1.exe openal_test1.o ../../simgear/debug/libsgdebug.a -lopenal32 -lwinmm -ldsound -ldxguid -lole32 openal_test1.o(.text+0x366):openal_test1.cxx: undefined reference to `_alutInit' openal_test1.o(.text+0x5b1):openal_test1.cxx: undefined reference to `_alutLoadWAVFile' openal_test1.o(.text+0x6cc):openal_test1.cxx: undefined reference to `_alutUnloadWAV' ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Being's new colors
Hi Jon Jon Berndt writes This is pretty: http://www.boeing.com/news/releases/2004/photorelease/q3/pr_040719g.html Might be nice to see this on some of the FlightGear Boeing planes (the test ones ;^) You volunteering Jon all you need is gimp and 8 or so hours LOL. Jon Cheers Innis I'm not sure I could do that. I can't even spell Boeing right! ;-) Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Cygwin and OpenAL
I have created a new OpenAL tarball that breaks ALut into a separate DLL http://www.vso.cape.com/~nhv/files/fgfs/openal_cyg.tgz $ tar -tzf openal_cyg.tgz bin/ bin/ALut.dll bin/openal32.dll include/ include/AL/ include/AL/al.h include/AL/alc.h include/AL/alctypes.h include/AL/altypes.h include/AL/alu.h include/AL/alut.bak include/AL/alut.h include/AL/aluttypes.h include/AL/alutypes.h lib/ lib/libALut.a lib/libopenal32.a win/Makefile HTH Norman NOrman: I am about to download and install (?) these. Not sure where to put them, though. And, is there anything I need to do on the build side to get these files seen and used? Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] OpenAL / Cygwin
Note you will need a recent Cygwin DLL to use these this is untested http://www.vso.cape.com/~nhv/files/fgfs/openal.tgz Norman: Is this file still online? Cape.com seems to think the site is offline or the file doesn't exist. Transient ISP problems? Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Cygwin and OpenAL
I think this is what you are looking for : ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/openal_cyg.tgz -Fred OK, I got it from the link that Erik supplied (thanks Erik). Now I have these files. Can you tell me where I can put them? Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Cygwin and OpenAL
Beware, the name seems to imply they are for MinGW, not CygWin The link I provided is the tarfile from Norm that was on my harddisc -Fred I have MingW installed along with CygWin. This might be problematic, then? Is FlightGear under Cygwin normally NOT MingW built? JOn ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Latest OpenAL for new build?
Vivian Meazza writes: Right now we are relying on Norman Vine's OpenAL files. We must just hope that Norman can find the tme to update when and if required. The Makefile I used is in my tarball and the only changes I made in the code are in the header files also in the tarball Has that tarball been relocated? I tried downloading yours from teh link you posted a few months ago without success. Note: You should be able to drop my tarball into a source tree then cd into the windows directory and issue a make command Not sure what you mean, exactly. Drop your tarball into an OpenAL source tree? Make, then make install? Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Success
I'll stop whining, now. ;-) I was able to build simgear and flightgear with the OpenAL libs. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] test the L1011-500
sorry for the delay, but i've been quite busy, here is is link: http://tristar500.net/modelo3d/L1011-500.zip the 3d model is still needing fixes, nose will be remade, so i can apply the windshield texture separetely from the side texture to avoid the stretch effect. also slats are not animated there are other visible problems and discrepancies, i will be fixing them when i can. the aircraft is controllable, but not very realistic, i will be tuning it and the auto-pilot, using SimPlot when possible FYI i am using a 2/3 week old cvs, i suppose it should run fine on latest cvs, maybe there are some VRP issues (?) Oh, good. I was hoping someone would do an L1011. Where do all these files go? Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Spitfire
To create smoke, we will need two things: smoke emitter and smoke object. I really hope you can do this. Smoke and fire are important for the X-15, too. :-) Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Taildragger takeoff and landing
David M. wrote: I'm getting seriously out of my depth here, since I didn't even take high school physics, but as far as I understand the most important part of lift is the suction created by the partial vacuum *above* the wings -- that means that wings are pulling air down more than pushing it down, effectively, and the hstab will be in downwash even if it is level with or slightly above the wings. Only a very high hstab, like the one on a t-tail, will be clear of it. Now Jon, Tony, or Andy can step in and explain how I've totally misunderstood the aerodynamics. I've heard it described several ways (lift); I think you're pretty close. I don't know if I'd say partial vacuum, though, which might give an exaggerated impression. Thinking of Bernoulli's nozzle example from elementary physics, the flow over the top, curved surface of a wing sees faster airflow, and lower pressure. Integrating the pressure over the lower and upper surfaces of the wing results in a net upward force (assuming steady-state flight). Probably there is a bit of both pushing _and_ pulling going on. If the lower surface of the wing is at a positive alpha, it's not too difficult to think that there is some pushing going on. Well, it would be interesting to get Tony's impression, and of course a physicist will describe this in his own way, too. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: Downwash (was Re: [Flightgear-devel] Taildragger takeoff and landing)
Getting back on topic, I think everyone agrees that the horizontal stabilizer on a typical plane (excluding t-tails) should be seeing downwash Yes. _When_ there is positive lift being generated by the wing. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Taildragger takeoff and landing
Erik Hofman [EMAIL PROTECTED] wrote: Jon S Berndt wrote: That's because it's _mostly_ (or entirely) the sucking action above the wing that contributes the most to lift. No, that is the *result* of lift, not the *cause*. Erik No, you're mixing up cause and effect. One more thing: think of a baseball or better yet a lightweight ball. How do those things curve? Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Taildragger takeoff and landing
Tony wrote: I hope you guys realize that this is an ages old debate that still goes on in the relevant academic circles. I've heard about the debate on whether it is circulation or the pressure difference that causes lift. I've never heard it argued that mechanical deflection is the cause for lift in subsonic flight. In my mind (and I've read this, too), circulation causes the pressure difference which in turn causes lift. Think of a baseball thrown with a spin. In that case, the lift generated is purely by circulation. Same thing with a cambered airfoil. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] FlightGear base package request --versionparameter to fgfs
Hi ! As a user on the FG user list requested a patch from base package pre2-pre3 in order to reduce download size/time, I was looking for the required pre2 package, it doesn't seem to be available on ftp.flightgear.org anymore - so I decided to look what base package I am currently using in order to see whether I could simply tar my current base directory and use this as a patch basis, but there doesn't seem to be any version information included in the base directory either, nor does fgfs --version provide _any_ information at all, I think particularly the version information via command line should be added ASAP, possibly even directly available from within FlightGear. I think that's an excellent idea. I also think that fgfs --version should report the SimGear, JSBSim, YASim, etc. version numbers. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Data source battle?
I don't use real weather because most of my flying is to test the fdms I'm working on, Just so I am clear, when you say fdms are you referring to Flight Dynamics Model source code, or are you referring to something I'd call an Aircraft Flight Model (AFM) or Aircraft Flight Model Definition (AFMD). I don't mean to sound snobbish, but when I think of FDM I think of math (equations of motion). The aircraft definition files - whether it be a JSBSim aircraft definition file, a YASim one, or whatever - define the aircraft - which the FDM code interprets and brings to life. We've never really discussed terminology as far as I can remember, but maybe a clarification would be good - if only so that my filter rules don't categorize messages incorrectly. :-) Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] FlightGear v0.9.5
Did someone already do a CYgWin build? ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] CVS - problem
166 if(cap 1) { continue; }
1 still doesn't seem to work with JBS models.
What? I could not figure out from the posts what wasn't working with the JSBSim models
(is
that what you meant by JBS Models?)
Jon
I also have 1. Are you dowloading with the cvs client or with
the flightgear.org viewcvs application. In the latter case, beware
that your browser might eator similar html reserved
character when exporting to text.
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Re: yasim + bo105 + vrp + @#%$#@ == argh!
Curt quipped: If you want to use the same 3d model for multiple FDM configurations which choose different reference points, then that makes life a lot harder. I think that is what the JSBsim VRP is for. I had to laugh when reading these two sentences together. It sort of read ( to me ) like: The JSBSim VRP is for making life a lot harder. Ha! Some might argue that that is exactly what the VRP does. I wrote up an article on the VRP for the first JSBSim newsletter (on our site). [BTW, the second newsletter is 99% ready, I just need to tie up some loose ends, but conference preps have got me busier than usual.] Without the VRP, JSBSim would simply report the location of the CG to FlightGear. With the VRP specified in the JSBSim config file, instead of reporting the CG, JSBSim will report the lat/lon/alt (the position) of the VRP instead. By convention, we say that the nose of the aircraft is what we want the VRP to represent. This can be advantageous (I think) because everyone knows where the nose of the aircraft is. This should make 3D model placement in the scene easy. Note that I am always open to suggestions on a better way to do this. While I feel that it should not be so confusing to people (i.e. maybe there is a better way), the simple fact is that given the multiple FDMs that FlightGear supports, 3D models built by many different people, etc. maybe we would be silly to expect the simulation to do all the work - i.e. there is some thinking one has to do for all of this. In the end, all the FDM can do is to report lat/lon/alt. What this represents can be [re-]opened for discussion if need be. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Properties and speed of lookup
It's been a long time since I worked on the property system code, and other people have hacked on it since I've been there, but basically, Curt's right. Here's a quick overview: THANK YOU, David! I am just finishing up (this very minute) the loose ends on my presentation and this information is very helpful. Just in time. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Interesting movies of structural failures
http://www.airandspacemagazine.com/asm/web/site/QT/menu.html ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] JSBSim Helicopter ... ?
Maybe we'll get some more user feedback. The release of the ec130 may motivate more people to fly helicopters. In the end a property might be necessary. Now, if only we had someone to finish YASim's missing helicopter FDM parts, and fix the bugs. Hey, or what about a JSBSim helicopter? :-) This is something I have always intended on doing. THere is an FGRotor class that has not been filled out, yet. Apart from that, the dynamics of a helicopter I think would make it a lot more difficult to get a realistic model going. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
