Hi!I am implementing a project UAV, called Manta, in Flightgear and am having a bit of a problem...I created a Manta-set.xml from the aeromatic page, as a starting point, and saved it in the aircraft folder. The engine is also set-up. The 3D model is borrowed from an Optica aircraft.When I load FlightGear the aircraft is listed and displayed. When I try and launch the flight, FlightGear aborts, due to uncompatible cfg file for this aircraft.It says the version needed is 1.65, you have version "blank!"... and finally aero does not exist.I have both the compiled version and the binary version of FlightGear and both lead to the same problem.Can anyone offer some help? Thanks!Sam - Aero student in Sweden

To clarify, you have created a Manta folder within the FlightGeardataAircraft folder, and then the Manta-set.xml and the Manta.xml inside that folder?

I don't know what is the cause of the error, so I can only offer your a suggestion. Try finding out which file is causing the problem by conducting a process of elimination. For example, replace your flight dynamic file with one from another aircraft. If the error still exists, try replacing the engine dynamic file, etc.

>When I load FlightGear the aircraft is listed and displayed.>When I try and launch the flight, FlightGear aborts, due to>uncompatible cfg file for this aircraft.>It says the version needed is 1.65, you have version>"blank!"... and finally aero does not exist.Sam:You need to have the version number in your FDM (JSBSim) configuration file:Do you have the version number specified at the top of your configuration file, like this?If you do this and are still having problems, email me the configuration file so I can look at it.Another thing you can do (I'll assume you are running under Linux or Cygwin) is to turn on a logging feature to see just what the FDM thinks it is reading from the config file. Set the JSBSIM_DEBUG environment variable to "1":export JSBSIM_DEBUG=1-or-setenv JSBSIM_DEBUG 1depending on the shell you are using. Then, carefully watch the output from the JSBSim startup messages.Let me know if this helps.JonCoordinator,JSBSim Projectwww.JSBSim.org

yes exactly, FlightGeardataAircraftMantaManta.xml and Manta-set.xmland when I replace both files with the j3cub files for exemple, and rename the paramaters inside them, I get the same error msg.

the version number in my FDM (JSBSim) configuration file is: (from aeromatic)I have tried replacing it with 1.55 and 1.65 but it doesn't change anything.Come to think of it, I am not sure if I have JSBSim installed... In my usr/local/source folder I have a file named JSBSim-0.9.4.1.tgz.htm. That was one of the files I downloaded when compiling FlightGear.Is there anything needed to be installed in order for flightgear to read the Manta-set.xml and Manta.xml?Another strange thing is that if I take the j3cub files for exemple, aircraft that works fine, and place them in my Manta folder with renamed parameters, they also cause the same error... Finally I tried "export JSBSIM_DEBUG=1" which was executed ok but there was no extra information in the error msg.I will email you the configuration file.Thanks! Sam

I have been doing that a bit, but not with the engine file... I'll give it a go to see.

>the version number in my FDM (JSBSim) configuration file is:> (from aeromatic)Hmmm. It should be 1.65>I have tried replacing it with 1.55 and 1.65 but it doesn't>change anything.>>Come to think of it, I am not sure if I have JSBSim>installed... In my usr/local/source folder I have a file named>>JSBSim-0.9.4.1.tgz.htm. That was one of the files I downloaded>when compiling FlightGear.>Is there anything needed to be installed in order for>flightgear to read the Manta-set.xml and Manta.xml?You likely have not installed any NEW JSBSim files. The file you list above seems to be an html file (look at the extension). FlightGear comes with JSBSim, but your probably have an old version of BOTH. You need to look at some of the JSBSim aircraft in your FlightGear installation (the JSBSim aircraft will have a line like this at the top:You will need to see which version those aircraft have. Then take that version number and put it in your file.>Finally I tried "export JSBSIM_DEBUG=1" which was executed ok>but there was no extra information in the error msg.FlighGear may have overridden that method of getting information out.Jon

>You likely have not installed any NEW JSBSim files. The file you list >above seems to be an html file (look at the extension). FlightGear >comes with JSBSim, but your probably have an old version of BOTH. You >need to look at some of the JSBSim aircraft in your FlightGear >installation (the JSBSim aircraft will have a line like this at the >top:>>You will need to see which version those aircraft have. Then take that >version number and put it in your file.--> I have checked with the Cessna 310 and the c310.xml has the following heading:so I changed my file heading to that version but it still doesn't work, same problem.

Please post this question again on the FlightGear-devel mailing list. This forum is not really frequented by the FlightGear developers group much. You'll likely get a much better (and quicker) solution there.Did you download the code and build FlightGear yourself? It could be that the version you have is out of date with the base distribution (which includes the aircraft).Jon

I have found a solution to my initial problem, I downloaded the X-15 aircraft and am editing its files directly, and it works (version 1.65).I am now faced with a new problem concerning the propulsion, but I have posted the question on the FlightGear-devel mailing list.Sam