[Flightgear-devel] INCOMPATIBLE CFG FILE
hi @ all! i have a problem with the Concorde aircraft (and other aircrafts i downloaded) from flightgear.org. when i start flightgear in terminal flightgear aborts after loading subsystems and ends with the message below: YOU HAVE AN INCOMPATIBLE CFG FILE FOR THIS AIRCRAFT. RESULTS WILL BE UNPREDICTABLE !! Current version needed is: 1.65 You have version: i found a work-arround because i had to edit the first line in the concorde.xml file to FDM_CONFIG NAME=Aerospatiale/BAC Concorde VERSION=1.65. after i do that a new error occured: opening file: /usr/share/games/FlightGear/Navaids/carrier_nav.dat /usr/share/games/FlightGear/Navaids/TACAN_freq.dat num gear units = 0 This is a very bad thing because with 0 gear units, the ground trimming routine (coming up later in the code) will core dump. Halting the sim now, and hoping a solution will present itself soon! i hope anybody can help me with this error when i start flightgear, thanks for doing that! ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Memory leak
Lee Elliott wrote On Saturday 17 June 2006 20:18, Vivian Meazza wrote: Lee On Saturday 17 June 2006 07:34, Melchior FRANZ wrote: * Lee Elliott -- Saturday 17 June 2006 05:02: Is anyone else seeing a memory leak in current cvs? I would be surprised if we had no leaks at all. But in a short test with $ fgfs --aircraft=ufo --airport=kufo ... i didn't see anything like you observed. The memory consumption was quite stable after a few minutes. (This was with ATC turned off.) m. Tried fgfs --aircraft=ufo --airport=kufo and had no problems. Went back to the a/c I was testing and just let it sit there while doing nothing but reduce the sound volume - no problem. I then closed the canopy (nasal), which resulted in a slight increase of fgfs vm utilisation but after waiting for a minute or two it was stable. I then revealed the 2D panel and that's when the vm utilisation for fgfs started to ramp up (I ssh'd in from another m/c and ran top to watch this). I switched back to the ufo and when I revealed the 2D panel (C-172 default) fgfs vm utilisation seemed to start ramping, although a lot more slowly than the a/c I was testing, so it looks as though it may be something to do with the 2D panel, which is a bit strange. As I said, the rate seems quite a bit lower with the ufo - I had to wait about a minute or so before it was apparent that fgfs's vm utilisation was ramping and it was only grabbing an extra mb every 30 seconds or so. Do you see this? I just left the KC135 running airborne - it chewed up VM and finally froze. 2D panel as well. I'm not clear if this is the same phenomenon that you are seeing, or if the 2D panel is significant. Vivian Sounds very much like it - I first noticed under the same conditions. I'll try cvs with Melchior's latest update, but a bit later - I'm of to a birthday now. I have now completed a bit more testing using the Seahawk using cvs-head of this am on Windows XP. With the 3D panel there is no memory leak. When I switch to the 2d panel on the fly, the memory leak starts. When I switch back to 3d, the leak stops. This can be repeated at will. Vivian ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] INCOMPATIBLE CFG FILE
You need to update your base package. The entire configuration file that you have for the Concorde, engines, etc. do not work anymore. The format for JSBSim aircraft has changed. The current FlightGear executable and source code expects the new format. Jon Jon S. Berndt Development Coordinator JSBSim Project www.JSBSim.org -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Sunday, June 18, 2006 7:52 AM To: flightgear-devel@lists.sourceforge.net Subject: [Flightgear-devel] INCOMPATIBLE CFG FILE hi @ all! i have a problem with the Concorde aircraft (and other aircrafts i downloaded) from flightgear.org. when i start flightgear in terminal flightgear aborts after loading subsystems and ends with the message below: YOU HAVE AN INCOMPATIBLE CFG FILE FOR THIS AIRCRAFT. RESULTS WILL BE UNPREDICTABLE !! Current version needed is: 1.65 You have version: i found a work-arround because i had to edit the first line in the concorde.xml file to FDM_CONFIG NAME=Aerospatiale/BAC Concorde VERSION=1.65. after i do that a new error occured: opening file: /usr/share/games/FlightGear/Navaids/carrier_nav.dat /usr/share/games/FlightGear/Navaids/TACAN_freq.dat num gear units = 0 This is a very bad thing because with 0 gear units, the ground trimming routine (coming up later in the code) will core dump. Halting the sim now, and hoping a solution will present itself soon! i hope anybody can help me with this error when i start flightgear, thanks for doing that! ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] pthreads: FlightGear runtime segfault under Cygwin
I've run into an error message seeming to fault pthreads for a flightgear segfault: (gdb) run Starting program: /usr/local/bin/fgfs.exe Program received signal SIGSEGV, Segmentation fault. 0x610ae938 in pthread_key_create () from /usr/bin/cygwin1.dll Is there a way to turn off pthreads? What do pthreads buy me under Cygwin? Jon ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Joystick and DEAD-BAND
Yep, you are right! I configured it with fgfj and it puts it behind, I don't know why. The config is working properly now. Someone should update fgfj... Thank you so much... On Saturday 17 June 2006 08:18 am, Gonzalo Aguilar Delgado wrote: Hi there! I'm trying to configure my joysticks to use it with FGFS. I'm having trouble with the dead-zone setting that seems to do nothing. My joy is not very new and has a big dead zone (-0.1,0.1) and I'm trying to set sead-band to 1.0 or even greater values. But it did not work. How can I solve this? Because it's terrible to see how controls move from time to time a lot! Thank you. I had the same problem when setting up my joystick taken from README.joystick.html that ended up working for me: You may recall from the section about raw axis value modifiers that dead-band is implemented outside the command manager. This means that if you want to apply a dead-band, the tag *must* precede the binding tag. ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Gonzalo Aguilar Delgado - Ingeniero en Informática [ Seguridad Medios de pago ] ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Joystick and DEAD-BAND
David, you are right. A good joystick is what I need... I now that Thrustmaster does bests but I have not much time to play with FGFS. And about the parameters you said. I have to test it because as you finals are now complicated because dead-band... Thank you so much for your help. On 17 Jun 2006, Gonzalo Aguilar Delgado wrote: My joy is not very new and has a big dead zone (-0.1,0.1) and I'm trying to set sead-band to 1.0 or even greater values. But it did not work. How can I solve this? Because it's terrible to see how controls move from time to time a lot! Lots of joysticks have a dead zone so large that it makes them unusable. I got my private license on an aircraft that had a stick, not a yoke, and I know how a responsive stick should feel. You can't control your aircraft on final with crosswind and turbulence with a big dead zone -- little stick movements don't do anything, and bigger movements can jerk the plane right into the ground. When I bought my last joystick, I tested several demo joysticks in a computer store by taking a laptop into the store running a modified version of fgjs. I recompiled fgjs to display the axis positions with an extra digit of precision. I attached each demo joystick and tested each axis of movement. Regardless of price, most joysticks had a huge dead zone in all three axes. Only one model (Thrustmaster Top Gun Fox 2 Pro USB) showed an acceptably smooth and continuous movement through the center. I'm very happy with it. There's an alternative to adjusting the dead band. You might try setting a very non-linear filter on the position in the joystick's .xml file. For example, you can try a combination of parameters such as: power type=double2.5/power offset type=double+0.0/offset factor type=double+1.0/factor tolerance type=double0.0/tolerance This will let you slap the stick around the center dead zone to make small corrections, while still allowing the controls to reach full travel. That much non-linearity is not realistic, however. ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Gonzalo Aguilar Delgado - Ingeniero en Informática [ Seguridad Medios de pago ] ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] tacan
What property can I increment to change the channel on the TACAN? I have a knob on a TACAN instrument that is supposed to either inc/dec the channel, or the x/y selector, depending on the position of another switch. I could do this by introducing another property and some nasal to translate between it and the three existing numeric properties, but this seems like a bit of a kludge. Josh ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
