Re: [Flightgear-devel] power/gear warning
From the PA-44-180 Seminole Pilot's Operating Handbook: A micro switch incorporated in the throttle quadrant activates the gear warning horn under the following conditions: (a) The gear is not locked down and the manifold pressure has fallen below 14 inches on either one or both engines (b) The gear selector switch is in the UP position when the airplane is on the ground (c) The gear selector switch is in the UP position and wing flaps are extended to the second or third notch position Regards, Torsten Curtis L. Olson wrote: On some more complex aircraft, if you pull back the power without having the landing gear down, you get an audible warning signal. I don't know if I've ever had the chance to hear this tone in real life. Does any one have (or can anyone create) a suitable sound to be included in the base package? Thanks, Curt. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Dashes in filenames
Quoting Martin Spott : Martin Spott wrote: I didn't hunt for debug output this morning but I'll do that tonight. My friend told me something like FlightGear is broken, it stops after selecting the A-10 - so I assume 'fgrun' works correctly, I was unable to reproduce after I reverted the filename change. I wasn't able to reprocude this effect with the A-10fl neither. Might there be an issue with this single A-10cl-set.xml file in the installer package which got lost (the issue) during renaming ? I'm aware that this souds a bit strange, but I would not tell this story if it actually didn't happen I'll reinstall FlightGear on the PeeCee some day this week to determine if the problem persists, IIRC, there has been permission issues in the unix base package. Maybe they affected fgsetup too. -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Dashes in filenames
Am Montag 14 Mrz 2005 22:41 schrieb Martin Spott: Martin Spott wrote: I didn't hunt for debug output this morning but I'll do that tonight. My friend told me something like FlightGear is broken, it stops after selecting the A-10 - so I assume 'fgrun' works correctly, I was unable to reproduce after I reverted the filename change. I wasn't able to reprocude this effect with the A-10fl neither. Might there be an issue with this single A-10cl-set.xml file in the installer package which got lost (the issue) during renaming ? I'm aware that this souds a bit strange, but I would not tell this story if it actually didn't happen Problem with file permissions? Just a guess... Thomas ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Help with B-29
Jon Berndt wrote: Yeah, I actually took a look at that. I have a handle on how to do the XML, I just don't have the expertise to make the actual sound files. The DC3 engine sounds are nice, but they don't quite have that throaty sound that you get from an 18 cyl radial. I found a few recordings, but they are low quality. I suppose I should write to the CAF in Midland and see if they have any recordings of Fifi. That would probably be the best starting point. Josh You could also try Aeromatic at the JSBSim web site: http://www.jsbsim.org/aeromatic.html For giving you a very quick start on a JSBSim flight model. Jon Yes, I actually have. In fact that's where I got the only working flight model that I have. Unfortunately, I couldn't seem to get the engines to work right. I abandoned the idea of using JSBSim mostly though because I can't find any polar data on the superfort wing. I do have cross sections, but it' a lot of work for me to get a fluid dynamics program running to generate the data from the cross sections. I'm also missing some of the geometry info, like twist and hstab incidence. It just seems like the data that I do have is much more suited to YASim. Josh ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] [BUG]? plib: culling
Ever since FlightGear used shadows for some of the aircraft there is an annoying bug, in plib(?) that makes the shadow not appear again after it had once been culled away. I've worked around this in the bo105 files, but I'd like to get rid of the workaround. I decided to put the description here, because it contains a few screenshots and code parts: http://members.aon.at/mfranz/flightgear/plib.html Does someone have an idea how to fix it? m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: [BUG]? plib: culling
* Melchior FRANZ -- Tuesday 15 March 2005 16:04: Ever since FlightGear used shadows for some of the aircraft there is an annoying bug, in plib(?) that makes the shadow not appear again after it had once been culled away. I've worked around this in the bo105 files, but I'd like to get rid of the workaround. I decided to put the description here, because it contains a few screenshots and code parts: http://members.aon.at/mfranz/flightgear/plib.html Does someone have an idea how to fix it? And it should better be an fgfs developer, because I'm unable to send this message to the plib list, because of an erratic spamcop listing. The mailserver isn't listed any more, but shitty sourceforge doesn't update their blocklist. :-( m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Airspeed (indicated vs. calibrated) question.
Anyone have any thoughts or ideas? 1. FlightGear has a property called /velocities/airspeed-kt; does anyone know if this was originally intended to be VCAS, VIAS, VTAS, or what? 2. The pitot system uses /velocities/airspeed-kt as it's input (and seems to assume this value is VIAS.) 3. We tie /velocities/airspeed-kt to v_calibrated_kts in the FDM structure, but the pitot/airspeed systems interprets this value as indicated airspeed. 4. I want to pass in velocity from an external FDM. I can feed in vcas or vias. The FDM structure only has a slot for VCAS, but this is tied to /velocities/airspeed-kt, which seems to be interpreted as VIAS by the rest of the sim. 5. Do we have any code on the FG side that computes VCAS given VIAS or visa versa? 6. If we split out /velocites/airspeed-kt into /velocities/airspeed-vcas-kt and /velocities/airspeed-vias-kt are we going to break a lot of stuff? Right now I have to do something ... either pass in VIAS from the external fdm and have the subsystems work correctly (but it hurts to do this because everything in the FDM structures are calling the value calibrated speed.) Or I try to fix this up and probably make a bigger mess of everything. ??? 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 Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Airspeed (indicated vs. calibrated) question.
Curtis L. Olson wrote: 1. FlightGear has a property called /velocities/airspeed-kt; does anyone know if this was originally intended to be VCAS, VIAS, VTAS, or what? 2. The pitot system uses /velocities/airspeed-kt as it's input (and seems to assume this value is VIAS.) This value looks like IAS to me. It's set from YASim via the FGInterface::_set_V_calibrated_kts() function. Note that the difference between IAS and CAS are due solely to gauge/pitot system issues. As far as the FDMs are concerned, they mean exactly the same thing. There is also an equivalent airspeed value that comes out, which is CAS without the mach corrections. I have no idea if this ever makes it to the property system, but FGInterface has a slot for it. A true TAS value* comes out via _set_V_rel_wind(), but I'm not sure where this ends up in properties. * Er... sorta. This is total airspeed velocity magnitude, whereas the pitot would really only measure velocity along its axis... If your suggestion is that we chuck all of this stuff and just pick some standard output props for the FDMs to fill out, then I agree. :) Andy ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Airspeed (indicated vs. calibrated) question.
Would this be a valid way to explain away the problem: The conversion between VCAS and VIAS is aircraft specific and is often shown in a table in the POH (and depends on things like flap position.) So FG can't come up with a nice tidy formula to convert between the two values. Thus FlightGear leaves everything as VCAS internally and doesn't allow for a separate VIAS at this point in time? Curt. Curtis L. Olson wrote: Anyone have any thoughts or ideas? 1. FlightGear has a property called /velocities/airspeed-kt; does anyone know if this was originally intended to be VCAS, VIAS, VTAS, or what? 2. The pitot system uses /velocities/airspeed-kt as it's input (and seems to assume this value is VIAS.) 3. We tie /velocities/airspeed-kt to v_calibrated_kts in the FDM structure, but the pitot/airspeed systems interprets this value as indicated airspeed. 4. I want to pass in velocity from an external FDM. I can feed in vcas or vias. The FDM structure only has a slot for VCAS, but this is tied to /velocities/airspeed-kt, which seems to be interpreted as VIAS by the rest of the sim. 5. Do we have any code on the FG side that computes VCAS given VIAS or visa versa? 6. If we split out /velocites/airspeed-kt into /velocities/airspeed-vcas-kt and /velocities/airspeed-vias-kt are we going to break a lot of stuff? Right now I have to do something ... either pass in VIAS from the external fdm and have the subsystems work correctly (but it hurts to do this because everything in the FDM structures are calling the value calibrated speed.) Or I try to fix this up and probably make a bigger mess of everything. ??? 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 Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Airspeed (indicated vs. calibrated) question.
Curtis L. Olson wrote: The conversion between VCAS and VIAS is aircraft specific and is often shown in a table in the POH (and depends on things like flap position.) So FG can't come up with a nice tidy formula to convert between the two values. Thus FlightGear leaves everything as VCAS internally and doesn't allow for a separate VIAS at this point in time? Sounds good to me, although I'd still argue for renaming all the properties and removing the FGInterface code (just make the FDMs set them properties themselves). Andy ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] FlightGear BitTorrents
Hey everyone, FlightGear (source and base), and SimGear source are now available for download via BitTorrent, thanks to http://www.open-bits.org See: http://www.open-bits.org/browse.php?cat=3 http://www.open-bits.org/details.php?id=902 (SimGear Source) http://www.open-bits.org/details.php?id=901 (fgfs-base) http://www.open-bits.org/details.php?id=900 (FlightGear source) For those who don't know what BitTorrent is, see http://www.bittorrent.com/introduction.html And you can download the client from http://www.bittorrent.com Currently we need seeders. So even though I'm very sure most if not all of you already have the above releases, you can still seed for those who don't :) Curtis, Maybe you might want to link to the torrents on the download page? I have no idea what kind of load you have on your servers but this may sure help to reduce it. Thanks, and enjoy! (And happy seeding) -- Arthur/ ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Help with B-29
Jon Berndt wrote:
Yeah, I actually took a look at that. I have a handle on how to do the XML, I
just don't have the expertise to make the actual sound files. The DC3 engine
sounds are nice, but they don't quite have that throaty sound that you get from
an 18 cyl radial. I found a few recordings, but they are low quality. I suppose
I should write to the CAF in Midland and see if they have any recordings of
Fifi. That would probably be the best starting point.
Josh
You could also try Aeromatic at the JSBSim web site:
http://www.jsbsim.org/aeromatic.html
For giving you a very quick start on a JSBSim flight model.
Jon
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Jon,
I took another crack at this with aeromatic, but I'm getting the following
segfault from fgfs. It seems that it is looking at the engine file and then
discarding it and looking for an alternative file that doesn't exist. Also,
http://home.comcast.net/~jrbabcock/superfort/b29.xml exists.
Josh
[big snip]
open(/usr/local/share/FlightGear/data/Aircraft/b29/Engines/R-3350.xml,
O_RDONLY) = 9
fstat64(9, {st_mode=S_IFREG|0644, st_size=443, ...}) = 0
mmap2(NULL, 131072, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xa7b9b000
read(9, ?xml version=\1.0\?\n!--\n Fil..., 131072) = 443
read(9, , 131072) = 0
open(/usr/local/share/FlightGear/data/Aircraft/b29/Engine/R-3350.xml,
O_RDONLY) = -1 ENOENT (No such file or directory)
read(9, , 131072) = 0
close(9)= 0
munmap(0xa7b9b000, 131072) = 0
open(/usr/local/share/FlightGear/data/Aircraft/b29/Engines/R-3350.xml,
O_RDONLY) = 9
fstat64(9, {st_mode=S_IFREG|0644, st_size=443, ...}) = 0
mmap2(NULL, 131072, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xa7b9b000
read(9, ?xml version=\1.0\?\n!--\n Fil..., 131072) = 443
read(9, , 131072) = 0
open(/usr/local/share/FlightGear/data/Aircraft/b29/Engine/R-3350.xml,
O_RDONLY) = -1 ENOENT (No such file or directory)
read(9, , 131072) = 0
close(9)= 0
munmap(0xa7b9b000, 131072) = 0
open(/usr/local/share/FlightGear/data/Aircraft/b29/Engines/R-3350.xml,
O_RDONLY) = 9
fstat64(9, {st_mode=S_IFREG|0644, st_size=443, ...}) = 0
mmap2(NULL, 131072, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xa7b9b000
read(9, ?xml version=\1.0\?\n!--\n Fil..., 131072) = 443
read(9, , 131072) = 0
open(/usr/local/share/FlightGear/data/Aircraft/b29/Engine/R-3350.xml,
O_RDONLY) = -1 ENOENT (No such file or directory)
read(9, , 131072) = 0
close(9)= 0
munmap(0xa7b9b000, 131072) = 0
open(/usr/local/share/FlightGear/data/Aircraft/b29/Engines/R-3350.xml,
O_RDONLY) = 9
fstat64(9, {st_mode=S_IFREG|0644, st_size=443, ...}) = 0
mmap2(NULL, 131072, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xa7b9b000
read(9, ?xml version=\1.0\?\n!--\n Fil..., 131072) = 443
read(9, , 131072) = 0
open(/usr/local/share/FlightGear/data/Aircraft/b29/Engine/R-3350.xml,
O_RDONLY) = -1 ENOENT (No such file or directory)
read(9, , 131072) = 0
close(9)= 0
munmap(0xa7b9b000, 131072) = 0
read(8, , 131072) = 0
read(8, , 131072) = 0
close(8)= 0
munmap(0xa7c0d000, 131072) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
FYI:
tower:b29$ cat /usr/local/share/FlightGear/data/Aircraft/b29/Engines/R-3350.xml
?xml version=1.0?
!--
File: R-3350.xml
Author: Aero-Matic v 0.7
Inputs:
name: R-3350
type: piston
power: 2200 hp
augmented? no
injected? no
--
FG_PISTON NAME=R-3350
MINMP 6.0
MAXMP 30.0
DISPLACEMENT 3520.00
MAXHP2200.00
CYCLES 2.0
IDLERPM 700.0
MAXTHROTTLE1.0
MINTHROTTLE0.2
/FG_PISTON
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Airspeed (indicated vs. calibrated) question.
From: Curtis L. Olson snip 6. If we split out /velocites/airspeed-kt into /velocities/airspeed-vcas-kt and /velocities/airspeed-vias-kt are we going to break a lot of stuff? This has been there so long I'd almost suggest depricating it and removing airspeed-kt sometime in the distant future. A massive edit in the base package and c source would take care of FlightGear, but I'd guess it might break some things for external interface users. Can we have the vcas and vias properties and continue to write the vcas value to airspeed-kt? An after thought...maybe we should NOT write airspeed-vias-kt unless it is actually being modeled. Then change all the current references from airspeed-kt to airspeed-vcas-kt so people (modelers, autopilot designers) know what they are actually using. If at some point the FDM models IAS for a particular aircraft, then the gauges and autopilot configurations can be changed accordingly. Best, Jim ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] FlightGear BitTorrents
Good idea! Now what would be really neat is if we could get some seeders started with the entire world scenery distribution. Things that size (i.e. HUGE!) is where bit torrent can really shine. I would volunteer, but I don't have the entire set ... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Arthur Wiebe Sent: Tuesday, March 15, 2005 2:24 PM To: FlightGear developers discussions; FlightGear user discussions Subject: [Flightgear-devel] FlightGear BitTorrents Hey everyone, FlightGear (source and base), and SimGear source are now available for download via BitTorrent, thanks to http://www.open-bits.org See: http://www.open-bits.org/browse.php?cat=3 http://www.open-bits.org/details.php?id=902 (SimGear Source) http://www.open-bits.org/details.php?id=901 (fgfs-base) http://www.open-bits.org/details.php?id=900 (FlightGear source) For those who don't know what BitTorrent is, see http://www.bittorrent.com/introduction.html And you can download the client from http://www.bittorrent.com Currently we need seeders. So even though I'm very sure most if not all of you already have the above releases, you can still seed for those who don't :) Curtis, Maybe you might want to link to the torrents on the download page? I have no idea what kind of load you have on your servers but this may sure help to reduce it. Thanks, and enjoy! (And happy seeding) -- Arthur/ ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear BitTorrents
Yes, getting the entire scenery available via bittorrent would be great. (As long as there are seeders) But it's huge, and would take some work. On Tue, 15 Mar 2005 17:19:23 -0800, Vandewalle, David E [EMAIL PROTECTED] wrote: Good idea! Now what would be really neat is if we could get some seeders started with the entire world scenery distribution. Things that size (i.e. HUGE!) is where bit torrent can really shine. I would volunteer, but I don't have the entire set ... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Arthur Wiebe Sent: Tuesday, March 15, 2005 2:24 PM To: FlightGear developers discussions; FlightGear user discussions Subject: [Flightgear-devel] FlightGear BitTorrents Hey everyone, FlightGear (source and base), and SimGear source are now available for download via BitTorrent, thanks to http://www.open-bits.org See: http://www.open-bits.org/browse.php?cat=3 http://www.open-bits.org/details.php?id=902 (SimGear Source) http://www.open-bits.org/details.php?id=901 (fgfs-base) http://www.open-bits.org/details.php?id=900 (FlightGear source) For those who don't know what BitTorrent is, see http://www.bittorrent.com/introduction.html And you can download the client from http://www.bittorrent.com Currently we need seeders. So even though I'm very sure most if not all of you already have the above releases, you can still seed for those who don't :) Curtis, Maybe you might want to link to the torrents on the download page? I have no idea what kind of load you have on your servers but this may sure help to reduce it. Thanks, and enjoy! (And happy seeding) -- Arthur/ ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d -- Arthur/ - http://artooro.blogspot.com (Weblog) - http://sourceforge.net/users/artooro/ ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Help with B-29
open(/usr/local/share/FlightGear/data/Aircraft/b29/Engine/R-3350.xml, The directory should be plural, Engines. Maybe that will fix it. Also, this prop config will give you better thrust. Aero-Matic's prop generator needs some work. xml version=1.0? !-- Generated by Aero-Matic v 0.7, with new CT and CP tables from Aero-Matic v 0.8 Inputs: horsepower: 2200.0 pitch:variable Outputs: linear-blade-inches: 248.59203527064 -- FG_PROPELLER NAME=prop IXX 53.2729 DIAMETER 199.2 NUMBLADES 4 GEARRATIO 2.3 MINPITCH 12 MAXPITCH 40 MINRPM904 MAXRPM 1130 C_THRUST 2 2 12 40 0.0 0.0519 0.0519 2.4 0.0519 0.0519 C_POWER 17 2 12 40 0.0 0.0604 0.1204 0.1 0.0604 0.1204 0.2 0.0575 0.1204 0.3 0.0547 0.1204 0.4 0.0481 0.1204 0.5 0.0396 0.1191 0.6 0.0321 0.1177 0.7 0.0189 0.1151 0.8 0.0075 0.1097 1.0 -0.0226 0.0896 1.2 -0.0660 0.0602 1.4 -0.1226 0.0301 1.6 -0.1811-0.0026 1.8 -0.2415-0.0734 2.0 -0.3019-0.1469 2.2 -0.3623-0.2203 2.4 -0.4227-0.2937 /FG_PROPELLER Dave ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Help with B-29
Dave Culp wrote:
open(/usr/local/share/FlightGear/data/Aircraft/b29/Engine/R-3350.xml,
The directory should be plural, Engines. Maybe that will fix it.
Also, this prop config will give you better thrust. Aero-Matic's prop
generator needs some work.
[snip]
Dave,
Thanks for the prop file. I'll try it out, though I may have written that file
from scratch myself, which is probably no better :)
As for the directory, it is Engines, but that doesn't matter, I tried it both
ways and it pretty much does the same thing. I just took a closer look at this.
I had misread the strace before. Here's what I found that it's doing:
brk
brk
open b29.xml
fstat
mmap2 address
some junk
for i = 1 .. 4
Attempt to open the file in Engines
memap2
read from it
close it
munmap
Attempt to open the file in Engine
memap2
read from it
close it
munmap
munmap address
segfault
So it looks like it's choking when it tries to free some memory that it was
using when it started parsing the FDM file, and the engine file has nothing to
do with it.
Thoughts?
Josh
Here's a bigger strace starting before the first mmap2 call:
brk(0) = 0xcb44000
brk(0xcb7) = 0xcb7
open(/usr/local/share/FlightGear/data/Aircraft/b29/b29.xml, O_RDONLY) = 8
fstat64(8, {st_mode=S_IFREG|0644, st_size=12009, ...}) = 0
mmap2(NULL, 131072, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xa7c3e000THIS ONE**
read(8, FDM_CONFIG NAME=\b29\ VERSION=\..., 131072) = 12009
rt_sigaction(SIGINT, {SIG_IGN}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGQUIT, {SIG_IGN}, {SIG_DFL}, 8) = 0
rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
clone(child_stack=0, flags=CLONE_PARENT_SETTID|SIGCHLD,
parent_tidptr=0xbfffed40) = 4875
waitpid(4875, [{WIFEXITED(s) WEXITSTATUS(s) == 0}], 0) = 4875
rt_sigaction(SIGINT, {SIG_DFL}, NULL, 8) = 0
rt_sigaction(SIGQUIT, {SIG_DFL}, NULL, 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
fstat64(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 2), ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xa7c3d000
write(1, \n, 1) = 1
write(1, \n, 1) = 1
write(1, \33[1mThis aircraft model is a \33[3..., 58) = 58
write(1, \n, 1) = 1
write(1, \33[0mThis aircraft model probably..., 59) = 59
write(1, \n, 1) = 1
write(1, \33[34m\33[1mUse this model for deve..., 66) = 66
write(1, \n, 1) = 1
open(/usr/local/share/FlightGear/data/Aircraft/b29/Engines/R-3350.xml,
O_RDONLY) = -1 ENOENT (No such file or directory)
open(/usr/local/share/FlightGear/data/Aircraft/b29/Engine/R-3350.xml,
O_RDONLY) = 9
fstat64(9, {st_mode=S_IFREG|0644, st_size=434, ...}) = 0
mmap2(NULL, 131072, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xa7bcc000
read(9, ?xml version=\1.0\?\n!--\n Fil..., 131072) = 434
read(9, , 131072) = 0
read(9, , 131072) = 0
close(9)= 0
munmap(0xa7bcc000, 131072) = 0
open(/usr/local/share/FlightGear/data/Aircraft/b29/Engines/R-3350.xml,
O_RDONLY) = -1 ENOENT (No such file or directory)
open(/usr/local/share/FlightGear/data/Aircraft/b29/Engine/R-3350.xml,
O_RDONLY) = 9
fstat64(9, {st_mode=S_IFREG|0644, st_size=434, ...}) = 0
mmap2(NULL, 131072, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xa7bcc000
read(9, ?xml version=\1.0\?\n!--\n Fil..., 131072) = 434
read(9, , 131072) = 0
read(9, , 131072) = 0
close(9)= 0
munmap(0xa7bcc000, 131072) = 0
open(/usr/local/share/FlightGear/data/Aircraft/b29/Engines/R-3350.xml,
O_RDONLY) = -1 ENOENT (No such file or directory)
open(/usr/local/share/FlightGear/data/Aircraft/b29/Engine/R-3350.xml,
O_RDONLY) = 9
fstat64(9, {st_mode=S_IFREG|0644, st_size=434, ...}) = 0
mmap2(NULL, 131072, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xa7bcc000
read(9, ?xml version=\1.0\?\n!--\n Fil..., 131072) = 434
read(9, , 131072) = 0
read(9, , 131072) = 0
close(9)= 0
munmap(0xa7bcc000, 131072) = 0
open(/usr/local/share/FlightGear/data/Aircraft/b29/Engines/R-3350.xml,
O_RDONLY) = -1 ENOENT (No such file or directory)
open(/usr/local/share/FlightGear/data/Aircraft/b29/Engine/R-3350.xml,
O_RDONLY) = 9
fstat64(9, {st_mode=S_IFREG|0644, st_size=434, ...}) = 0
mmap2(NULL, 131072, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xa7bcc000
read(9, ?xml version=\1.0\?\n!--\n Fil..., 131072) = 434
read(9, , 131072) = 0
read(9, , 131072) = 0
close(9)= 0
munmap(0xa7bcc000, 131072) = 0
Re: [Flightgear-devel] Airspeed (indicated vs. calibrated) question.
On Dienstag 15 März 2005 22:10, Andy Ross wrote: Curtis L. Olson wrote: The conversion between VCAS and VIAS is aircraft specific and is often shown in a table in the POH (and depends on things like flap position.) So FG can't come up with a nice tidy formula to convert between the two values. Thus FlightGear leaves everything as VCAS internally and doesn't allow for a separate VIAS at this point in time? Sounds good to me, although I'd still argue for renaming all the properties and removing the FGInterface code (just make the FDMs set them properties themselves). This is a good thing. I think that an FGInterface class should get a base property node which should be the root for this aricraft. Currently this is just the root property node for /. What we need to write then is a document which property nodes are required and which should, if present, be named with a specific name. Also having a consistent naming scheme for units might be a good idea. Where I like the approach we have now is for the position (lat/lon/alt). Since most FDM's do not compute in geodetic coordinates we can keep an interface where the FDM sets the the position in geocentric, geodetic or cartesian coordinates. Greetings Mathias -- Mathias Fröhlich, email: [EMAIL PROTECTED] ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
