I recently downloaded the entire Windows version of FlightGear. Most everything works great and I have really been enjoying it... yet some of the downloaded airplanes don't seem to run at all. For intance, the A-10 Bronco will start to load, say that it is loading the airframe, then the scenery, etc. then it drops back to the FlightGear Wizard page instead of going into the sim. On the DOS page is printed this:opening file: C:/Program Files/FlightGear/data/Navaids/carrier_nav.datC:/Program Files/FlightGear/data/Navaids/TACAN_freq.datReading xml electrical system model from C:/Program Files/FlightGear/data/Aircraft/Generic/generic-electrical.xmlInitialising callsign using 'Aircraft/f16/Models/f16.xml'opening file: C:/Program Files/FlightGear/data/Navaids/carrier_nav.datC:/Program Files/FlightGear/data/Navaids/TACAN_freq.datYOU HAVE AN INCOMPATIBLE CFG FILE FOR THIS AIRCRAFT. RESULTS WILL BE UNPREDICTABLE !!Current version needed is: 1.65 You have version:FlightGear abortingDoes this make sense to any of you and can you point me to what setting I need to change to get it to work? I am sure the aircraft works fine for others otherwise it wouldn't be up on the site, but for the life of me I can't get it to load and the errors don't seem to make a lot of sense.(Also, has anyone else notes that you can't get the P-51 to do an outside loop? No matter what speed and power settings you use going in, it just won't do it. Funny... cause the real ones do it just fine....Lastly has anyone modelled a canard aircraft yet? I sure would like to try a Quickie, LongEZ or a Dragonfly!

OK, I seem to have figured some things out. The v1.65 they are referring to seems to be the JSBSim version. The OV-10 Bronco, the 737, the F104, the X-15 and others are all v2.0 models. However, it would appear that if you are running Windows, the FDMs are already all compiled into the code and you can't specify one version of the JSBSim or another. So, is there something I am doing wrong? Or is it just not possible to fly any of those planes under the Windows version of FGFS right now?

You don't provide sufficient information (see http://www.seedwiki.com/wiki/flight_gear/h...you?wpid=247004 in particular we need to know your version of FG!), however it seems you simply have a version <=0.9.9 while you are trying to run aircraft that require FlightGear >=0.9.10(pre), which has the latest JSBsim 2.0 engine integrated.Likewise, a similar problem can occur if you are trying to run old aircraft which haven't yet ported to the 2.0 format in a current version of FG.

Actually, I think I did give pretty accurate information, namely that I just downloaded and started using the Windows version of FGFS. Thus, it is the 0.9.9 version as that is all there seems to be available for download.Is it even possible to integrate the 0.9.10(pre) code into the Windows version of the code? If so, can you point me to a location with the step-by-step instructions for how to do this. Even though Windows isn't as good an operating system as Linux and others, there are bunches of us poor blighters out here that only really know it. Any help you can give us in keeping up with the new developments of FlightGear is going to go a long way towards increasing its userbase...

>Actually, I think I did give pretty accurate information,sorry, without meaning to sound rude: but ultimately it really doesn't matter what we may think about the information you provided or not, the most important thing is the information itself. Which simply wasn't particularly complete. There's no point in trying to argue about this now: if the information had been complete and accurate, there would not have been that much room for doubt in the first place.While you seem to try to back up your "information" with (false) assumptions that you have made, we prefer not to have to guess because this renders our help usually pretty ineffective.>namely that I just downloaded and started using the Windows>version of FGFS. Thus, it is the 0.9.9 version as that is all>there seems to be available for download.This is such an assumption/misconception: there are definitely other versions available for download, too-older ones, as well as more recent ones (for example the pre-release I mentioned)-it simply depends on where you look for said files. But in the end, you didn't even provide us with the information WHERE you actually looked for the corresponding files or which ones you downloaded (address/filename!), so theoretically there's a whole variety of places that may even offer versions that we are not aware of. Thus, it is generally a pretty good idea to be accurate and thorough in your descriptions, so that we do not have to make any guesses or assumptions that may turn out to be wrong and result in unnecessarily complicating the process of trying to provide support to people like you.>Is it even possible to integrate the 0.9.10(pre) code into the>Windows version of the code? I am not sure what you are asking here, or what you may be trying to ask (feel free to elaborate!).However, in general I would simply recommend to get the latest pre-release or even the 0.9.10 release itself if running JSBSim 2.0 is your absolute priority (whenever pre-releases are made available, it is usually only a matter of days until the actual release is published).>If so, can you point me to a>location with the step-by-step instructions for how to do>this.If you are indeed asking how to integrate a more recent FDM version (JSBSim 2.0) with FlightGear versions <=0.9.9, then I cannot provide the specifics directly, but would recommend to subscribe to the JSBSim mailing list: http://jsbsim.sourceforge.netHowever, if that should in fact be what you are trying to do, be prepared to get the same recommendation I made already( that is, simply get the latest 0.9.10 based version).>Even though Windows isn't as good an operating system>as Linux and others, there are bunches of us poor blighters>out here that only really know it. Any help you can give us>in keeping up with the new developments of FlightGear is going>to go a long way towards increasing its userbase...Thanks for trying to motivate me, but there is hardly any reason to do so, I will try to provide the help I can, regardless of whether you are a windows user or not. However, I have come to appreciate it when users who are asking for support provide the corresponding information without arguing about the specifics when being asked.good luck

OK, well we seem to have gotten off on completely the wrong foot here... I wasn't trying to be snotty. I appreciate any help that you can offer. You asked for:Hardware Specs: * Pentium IV 2.0GHz * 512MB Ram * integrated soundcard (Dell Soundblaster compatible) * nVidia GeForce 5500 AGP 256MB driver 8.1.9.8Software Specs: * Windows XP SP2 * Symantec AntivirusInput Hardware: * KEYBOARD: US english (language/country encoding) * MOUSE MS Optical * JOYSTICK None * YOKE None * PEDALS NoneFlightGear: * Windows pre-compiled 0.9.9 * downloaded from www.flightgear.org/downloads/ * Windows executables * installed FlightGear in c:Program FilesFlightGear * starting using FlightGear wizard provided in executable * stock wizard startup parameters * console messages: opening file: C:/Program Files/FlightGear/data/Navaids/carrier_nav.datC:/Program Files/FlightGear/data/Navaids/TACAN_freq.datReading xml electrical system model from C:/Program Files/FlightGear/data/Aircraft/Generic/generic-electrical.xmlInitialising callsign using 'Aircraft/f16/Models/f16.xml'opening file: C:/Program Files/FlightGear/data/Navaids/carrier_nav.datC:/Program Files/FlightGear/data/Navaids/TACAN_freq.dat * This machine has previously been used to run FlightGear successfully, v 0.9.9 with the aircraft provided in the Windows executable FGFS downloadIt has become clear to me that the precompiled Windows version available from FlightGear.org on the download page is version 0.9.9 and that it uses the older JSBSim 1.65 instead of the newer 2.0 version. As a result, some of the models available on the FlightGear.org/downloads/aircraft site will not work with the version of the Windows compiled code (0.9.9)that is available.So the question becomes, how can I implement a version of the 0.9.10 (pre-3) code on my Windows machine that will work with all the JBSSim 2.0 aircraft? I tried following the instructions for compiling a version found at: http://www.flightgear.org/Docs/getstart/ge...tml#x16-110000B however, after successfully configuring, making and installing the openal-0.0.8 in carroll@purple ~/source/openal-0.0.8, I get an error when trying to ./configure the simgear-0.3.10 saying: carroll@purple ~/source/simgear-0.3.10$ ./configurechecking for a BSD-compatible install... /usr/bin/install -cchecking whether build environment is sane... yeschecking for gawk... gawkchecking whether make sets $(MAKE)... yesCXX =CC =checking whether make sets $(MAKE)... (cached) yeschecking for gcc... gccchecking for C compiler default output file name... a.exechecking whether the C compiler works... yeschecking whether we are cross compiling... nochecking for suffix of executables... .exechecking for suffix of object files... ochecking whether we are using the GNU C compiler... yeschecking whether gcc accepts -g... yeschecking for gcc option to accept ANSI C... none neededchecking for style of include used by make... GNUchecking dependency style of gcc... gcc3checking how to run the C preprocessor... gcc -Echecking for g++... g++checking whether we are using the GNU C++ compiler... yeschecking whether g++ accepts -g... yeschecking dependency style of g++... gcc3checking for ranlib... ranlibchecking for a BSD-compatible install... /usr/bin/install -cchecking whether ln -s works... yeschecking build system type... i686-pc-cygwinchecking host system type... i686-pc-cygwinincludedir changed to ${prefix}/include/simgear libdir is ${exec_prefix}/liBuilding without Norman's jpeg image server supportno EXTRA_DIRS for i686-pc-cygwinchecking for extra include and lib directories...no fancy X11 checkchecking for egrep... grep -Echecking for ANSI C header files... yeschecking for sys/types.h... yeschecking for sys/stat.h... yeschecking for stdlib.h... yeschecking for string.h... yeschecking for memory.h... yeschecking for strings.h... yeschecking for inttypes.h... yeschecking for stdint.h... yeschecking for unistd.h... yeschecking pthread.h usability... yeschecking pthread.h presence... yeschecking for pthread.h... yeschecking for library containing pthread_exit... none requiredchecking for library containing inet_addr... none requiredchecking for library containing socket... none requiredchecking for library containing cos... none requiredWin32 specific hacks...Will link apps with -lglu32 -lopengl32 -luser32 -lgdi32 -lwinmmchecking for library containing glutGetModifiers... nochecking for library containing alGenBuffers... nochecking for library containing alutInit... noYou *must* have the openal library installed on your system to buildSimGear!Please see README.OpenAL for more details.configure aborted.Unfortunately, I can't find any README.OpenAL file anywhere on the machine and don't know why the SimGear won't install. *sigh* I am actually a fairly technical person, just not normally a Linux user. Getting all these packages installed correctly to compile a version of FlightGear is not exactly simple. I'd appreciate any help you can offer. Maybe the best advice is just to give up and wait until there is a download for a Windows Executable version of 0.9.10. Thanks.

>I'd appreciate any help you can offer. Maybe the>best advice is just to give up and wait until there is a>download for a Windows Executable version of 0.9.10. Thanks.Just for the record: were you aware of the possibility to use a BINARY (compiled) pre-release? That is, IF running running JSBSim 2.0 aircraft was a priority to you, why didn't you simply use the latest 0.9.10 PRE-release (ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/fgsetup-0.9.10-pre3.exe)?Apart from that, you can get the latest 0.9.10 Win32 binary (created yesterday) by downloading:ftp://ftp.ihg.uni-duisburg.de/FlightGear/...etup-0.9.10.exePS: I didn't get back to your other questions, because I am not sure whether they are still relevant, however if they ARE (i.e. compiling SimGear under linux) simply drop us a line. On the other hand, it would probably be a better idea to start a new thread then, because the scope of the problem would have changed (Win32 binary vs. Linux SimGear compilation)-you should be able to address the OpenAL issue by simply getting, compiling & installing OpenAL.

>(Also, has anyone else notes that you can't get the P-51 to do>an outside loop? No matter what speed and power settings you>use going in, it just won't do it. Funny... cause the real>ones do it just fine....>>Lastly has anyone modelled a canard aircraft yet? I sure>would like to try a Quickie, LongEZ or a Dragonfly!Apart from that it is usually a good idea to start multiple threads for different topics, I cannot provide any comments about your last two questions.But someone who might not be able to support you with installation related issues may very well be interested in aircraft modeling, and vice versa.So, if you want to make sure that your questions are actually read, try to provide each question with a separate thread (at least as long as these are not related).Likewise, it is important to note that this forum is currently not being officially supported by the FlightGear team, only very few of the developers actually check back with these forums in order to provide support, and if they do so then only very sporadically.Thus, if you are interested in other people's FlightGear related projects or efforts, it is usually a much better idea to use the FlightGear mailing lists in order to get in touch with other FlightGear users and developers:http://www.flightgear.org/mail.htmlThis is also where most of the new aircraft projects are likely to be discussed.

Thnaks!I didn't know that there was a windows binary available for 0.9.10! That is just what I needed! It wasn't listed on the www.flightgear.org download page. I'll give that a try.