Re: [Flightgear-devel] model accumulation
Melchior FRANZ wrote: Is everyone aware that we *never* free model branches? They are only accumulated until fgfs is exited. If you teleport from KSFO to LOWW/Europe, then you still have the KSFO terminal in memory. Doesn't sound like a good idea to me. Currently we don't have that many individual objects, but as people are contributing to the fgdb, this may become a problem (textures!). And it certainly will be a problem once I got Nasal support for scenery objects into cvs. The original design of the scenery pager would delete these objects. What are you seeing that leads you to believe they aren't getting deleted? It's very plausible that something got broke along the way. This is something that you wouldn't necessarily notice right off unless you were paying close attention to the memory foot print (which I haven't been doing.) Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Re: model accumulation
* Curtis L. Olson -- Sunday 26 February 2006 07:13: Melchior FRANZ wrote: Is everyone aware that we *never* free model branches? The original design of the scenery pager would delete these objects. What are you seeing that leads you to believe they aren't getting deleted? It's very plausible that something got broke along the way. Could have been introduced recently with ssgSharedPtr. Around the time when we got random objects it was desirable not to have thousand separate tree objects etc. in memory. So the SGModelLib::load_model() function was introduced. It holds all models in a mapstring path, ssgSharedPtrssgEntity. The objects are removed from the scenegraph when the tile is freed, but because we still hold the refcounted model branches in this map, they are *not* freed. And this is not just a theory: I was actually about to add Nasal support to static objects. This wasn't meant to be used for trees or other frequent models, but for landmarks with special needs. (Example: Eiffel Tower lighting, Roberto's Space Needle, etc.) And, of course, the Nasal contexts would have to get destroyed once the model is removed from memory, so that they wouldn't accumulate. But my Nasal destructors were never called. Only when I modified my fgfs copy to only cache OBJECT_SHARED and random objects, but not OBJECT_STATIC, would it free the models. m. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Aircraft startup failure, confirmed by others (Concorde / Boeing314A)
Both pigeon and I are experiencing that the Concorde doesn't start. We both run Linux. Attempting to start with the Concorde gives a slightly messed-up splash screen (black blotches near the bottom), followed by an abort. Backtrace included below: } [Thread debugging using libthread_db enabled] } [New Thread 46912539295008 (LWP 24597)] } [New Thread 1082730848 (LWP 24600)] } FlightGear aborting } } } *** glibc detected *** free(): invalid pointer: 0x0111c208 *** } Program received signal SIGABRT, Aborted. } [Switching to Thread 46912539295008 (LWP 24597)] } 0x2c566e20 in raise () from /lib/libc.so.6 } (gdb) bt } #0 0x2c566e20 in raise () from /lib/libc.so.6 } #1 0x2c5682d0 in abort () from /lib/libc.so.6 } #2 0x2c59cc4e in __fsetlocking () from /lib/libc.so.6 } #3 0x2c5a29ab in malloc_usable_size () from /lib/libc.so.6 } #4 0x2c5a2c8e in free () from /lib/libc.so.6 } #5 0x2c2c5daa in std::basic_stringchar, std::char_traitschar, std::allocatorchar ::~basic_string () from /usr/lib/libstdc++.so.6 } #6 0x007ad5e7 in ~bucket (this=0x48949c0) at props.cxx:2157 } #7 0x007ad646 in ~hash_table (this=0x111c910) at props.cxx:2212 } #8 0x007ae693 in ~SGPropertyNode (this=0x111c270) at props.cxx:752 } #9 0x007ad582 in ~entry (this=0x48ee650) at SGSharedPtr.hxx:93 } #10 0x007ad5e7 in ~bucket (this=0x48949c0) at props.cxx:2157 } #11 0x007ad646 in ~hash_table (this=0x111c910) at props.cxx:2212 } #12 0x007ae693 in ~SGPropertyNode (this=0x111c270) at props.cxx:752 } #13 0x00427cd8 in ~FGGlobals (this=0x111bf90) at globals.cxx:103 } #14 0x0040c660 in fgExitCleanup () at bootstrap.cxx:223 } #15 0x2c5695bd in exit () from /lib/libc.so.6 } #16 0x0041f173 in fgInitFDM () at fg_init.cxx:1373 } #17 0x004207cc in fgInitSubsystems () at fg_init.cxx:1601 } #18 0x0040f5d1 in fgIdleFunction () at main.cxx:885 } #19 0x2af32dc4 in glutMainLoop () from /usr/lib/libglut.so.3 } #20 0x0040ccef in fgMainInit (argc=5, argv=value optimized out) } at main.cxx:1023 } #21 0x0040c753 in main (argc=5, argv=0x7fd7d458) } at bootstrap.cxx:198 I'm also seeing the Boeing 314A fail to start in the same fashion. Cheers, -c -- Chris Metzler [EMAIL PROTECTED] (remove snip-me. to email) As a child I understood how to give; I have forgotten this grace since I have become civilized. - Chief Luther Standing Bear signature.asc Description: PGP signature
Re: [Flightgear-devel] Is there a property that gest the distance between an object and the point of view?
Melchior suggested me to move them to the center. Well I can't, they have to scale separately around different centerpoints. Yes you can. You scale them and then translate them to the points that you want them. That's how all billboard animations have to be done. Take a look at the link he posted, that is how it works. http://members.aon.at/mfranz/donauturm.tar.gz Josh As I see in donauturm.tar.gz, billboarding objects have to be positioned at the center of the 3d model first, because there is no way to tell the billboard animation to make the object spin around an arbitrary center. I first thought you meant I have to scale it and translate it inside Blender. I was wrong. I have to do this within the animation .xml file. Right? Anyway I've found Blender is capable of positioning the pivot point wherever I want; although the problem remains, this pivot point is not saved in the .ac file. When I reopen the previously modified .ac file the pivot point is not remembered, all objects inside the .ac file have the pivot point in origin of the 3d space. Is that the cause for having that translation and scaling to be done with the scale/translate .xml animation? IMO this practice is a little odd, and gives the modeller unnecessary workload. It's a pity :-( Anyway, I'll try to work things out using that technique. Thanks people, Roberto --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] A-10 3D cockpit progress
Hi Chris, I don't disagree with anything you're saying. I don't (and never have) run 3-d cockpits, I believe my hardware setup is too primative to support them. This is not the fault of FG, it is a probelm I am saving up to remedy. You are right; I can't run 3-d cockpits. I run 098a binary and G099 data/0910 scenery but have tried a number of aircraft that have been developed for the 099 binary that won't work or have unpredictable behaviour when using the 098a binary. From: Chris Metzler [EMAIL PROTECTED] On Sun, 26 Feb 2006 18:47:26 +1300 dene maxwell wrote: Hi Chris, agreed, 3-D is not a 099 peculiarity... but I can't run 3-D cockpits under my implementation of 098a, I've put this down to hardware restrictions and it hasn't been important as there are plenty of options in the way of equally enjoyable aircraft. Some of the new aircraft are designed to run under FGFS 099 and have to have special makes to run under 098a. Again I reiterate this not because they have 3-d cockpits but for other reasons related to the changes from 098a to 099 (JBSim 2.0 and the changes to the FDM for example) Sorry, I'm feeling really slow (probably because it's late where I am, and I should go to sleep). There was a change in JSBSim configuration file format in going to JSBSim 2.0; that has caused a lot of aircraft that haven't yet been updated to not run under FG 0.9.9, and still others that *have* been updated to not run under earlier versions (although one can always hang on to an old version, I guess). But as you note above, that's separate from the ability to run 3D cockpits. You're saying you can't run 3d cockpits under 0.9.8a? Were you able to under other versions? How does the version come in, as opposed to I can't run 3d cockpits, period? Put another way, you suggested that adding the 3D cockpit wouldn't be popular with 0.9.8a users: It is, perhaps, unfortunate that I chose this message to respond to with my opinion, 3-D cockpits are not related to my (or any other users) inability to fly certain aircraft under 098a to the best of my knowledge. A separate A-10-3Dcockpit would make the existing A-10 redundant - who would want to fly it without your cockpit? :) Maybe those langishing on 098a? From what I've seen of Alexis cockpit, I would love to fly it with his cockpit, as I enjoy the A10 FDM. But any new a/c, unless they have a 098a implementation, are useless to us. This is assuming that the FDM will be updated as well. This may be an incorrect assumption. As far as I'm aware, upgrading to a 3-d cockpit alone will not stop 098a users, who can currently run 3-d cockpits, from flying this fantastic a/c and a 3-d cockpit as shown in the screen shots can only enhance this experience. . . .and I'm wondering why the FG version matters when it comes to adding the 3D cockpit. Plenty of people used 3D cockpits with 0.9.8a. The reason I'm looking at this is because you described FG as not maintaining backward compatibility; for the most part, I don't think that's fair to FG. I agree that the JSBSim config file change is an example of failing to maintain backward compatibility; but I'd claim that it's not breaking backward compatibility in the way you describe. Using the rest of the software industry as a guide, the breaking of backward compatibility there is *not* in 0.9.8a not being able to digest new aircraft; rather, it's in 0.9.9 not being able to use old aircraft files as is. and this is the basis of my concerns for any aircraft upgradeif an aircraft is available under to fly an earlier version of FG then a version that continues it to be able to be flown under that earlier vesion should continue to be available. Ie as a separate aircraft (or build of) That's the norm: new versions of software able to read files for old versions of software; but not vice-versa, since that would make adding functionality very difficult. For example, you can't use MS Word 2003 .doc files in Word 97; but older .doc files will work in newer versions of Word OK. And I don't think it's fair to call the adding of more functionality, which in turn overtaxes older hardware, as breaking backward compatibility. After all, that'll always be a problem with sophisticated software -- try running Windows XP on a 486DX machine. My backward compatibility comments where mainly aimed at MP. Unfortunately word processor analogies doesn't really apply as there aren't too mainly truely MP applications in the commercial world (ie each user interacting with others) Possibly the closest analogy is that of a DB app. If you run a newer version of the front end than me on the same DB then I could reasonably expect to encounter problems. At best using the old version of a front end would cause data inconsistencies. BUT If I chose to stay with the old version front end then I could still expect the functionality I had enjoyed to still be available. This is not the case
Re: [Flightgear-devel] A-10 3D cockpit progress
dene maxwell wrote: From: Lee Elliott [EMAIL PROTECTED] A separate A-10-3Dcockpit would make the existing A-10 redundant - who would want to fly it without your cockpit? :) Maybe those langishing on 098a? From what I've seen of Alexis cockpit, I would love to fly it with his cockpit, as I enjoy the A10 FDM. But any new a/c, unless they have a 098a implementation, are useless to us. Typically I'm a person that seeks for harmony so I resisted to post such words for quite some time, but now the moment has come where I realize that I definitely feel pissed by such comments like the one quoted above. How do you _dare_ to imply that every aircraft without a v098 implementation is useless tu _us_ ? You can't expect people to cease develompment of new features just because one or two users still prefer to run an outdated version of the software. This is real bullshit, not only that, it would leave Flightear development falling behind until it reaches insignificance. Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] A-10 3D cockpit progress
dene maxwell wrote: I would hate to see a aircraft that works under 098a and perhaps earlier that is enjoyed by many users overwritten and possibliy become unavailable. Nobody holds you back from keeping a copy of the old aircraft implementation, you just don't get all the new featuers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] A-10 3D cockpit progress
Lee Elliott a écrit : On Saturday 25 February 2006 17:56, alexis bory wrote: I'll do that ASAP, maybe sunday night or monday. I can't see any need for a separate folder - add your stuff to the A-10, your name and comments to the existing files, especially the author tag in the A-10-set.xml file and send it to one of the cvs maintainers. I have furbished a .tgz of A-10 with the actual 3D cockpit, it doesn't permit yet to disable the added 3D stuff, but why not ;) (Dene, please, will you try it ?) I just wonder who/where to send it ? Alexis --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
RE: [Flightgear-devel] Aircraft startup failure, confirmed by others (Concorde / Boeing314A)
smime.p7m Description: S/MIME encrypted message
Re: [Flightgear-devel] A-10 3D cockpit progress
On Sunday 26 February 2006 12:09, alexis bory wrote: Lee Elliott a écrit : On Saturday 25 February 2006 17:56, alexis bory wrote: I'll do that ASAP, maybe sunday night or monday. I can't see any need for a separate folder - add your stuff to the A-10, your name and comments to the existing files, especially the author tag in the A-10-set.xml file and send it to one of the cvs maintainers. I have furbished a .tgz of A-10 with the actual 3D cockpit, it doesn't permit yet to disable the added 3D stuff, but why not ;) (Dene, please, will you try it ?) I just wonder who/where to send it ? Alexis Could you send me a copy - I'd like to have a play with it:) I think there has been some misunderstanding with regard to the differences between version 0.9.8(a) and 0.9.9 YASim aircraft. The main issue isn't one of adding new features but of fixing a significant bug and this is why some YASim aircraft have become incompatible between the two releases. The nature of the bug - that of the wing incidence being reversed - means that affected aircraft i.e. those with non-zero incidence are fundamentally incorrect under 0.9.8(a) and so maintaining compatibility with 0.9.8(a) and earlier doesn't really make much sense. As it happened, I did add a couple of new 'features' to the current version of the A-10 but they aren't 0.9.9 specific and could be added to the 0.9.8(a) version but because that version is effectively broken there's not a lot of point in spending the time to do it, especially when I've still got other aircraft to fix - I'm currently working on the Canberra - another aircraft affected by the same bug. LeeE --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
RE: [Flightgear-devel] A-10 3D cockpit progress
Chris Metzler wrote: Sorry, I'm feeling really slow (probably because it's late where I am, and I should go to sleep). There was a change in JSBSim configuration file format in going to JSBSim 2.0; that has caused a lot of aircraft that haven't yet been updated to not run under FG 0.9.9, and still others that *have* been updated to not run under earlier versions (although one can always hang on to an old version, I guess). But as you note The reason I'm looking at this is because you described FG as not maintaining backward compatibility; for the most part, I don't think that's fair to FG. I agree that the JSBSim config file change is an example of failing to maintain backward compatibility; but I'd claim that it's not breaking backward compatibility in the way you describe. Well ... this is interesting. Somehow I missed this conversation until now. For the past year and more I have gone to great lengths to publicize the impending changes to JSBSim in this mailing list, the JSBSim mailing list, and the JSBSim newsletter. I've publicized the backward incompatibility, and the reasons for going to the new format. I've publicized that we have created a converter for going from the old format to the new. We did not fail to maintain backward compatibility so much as we did not *limit* ourselves by the past. This is not the first time there has been a major configuration file format change. Likely, it *will* be the last. Originally, eight years ago, the JSBSim configuration files were not rooted in XML, but were simply in a text format. We moved to XML somewhere about 2000. Some newer technologies (to me, anyhow) emerged, an industry standard began to emerge (that JSBSim helped to inspire), and some new and broad JSBSim capabilities were being added - all which dictated that there would need to be changes in the way the config files were arranged. This has all been communicated both here and in the JSBSim mailing list. Maintaining backward compatibility would have negated what we were hoping to accomplish - one of which was better formed XML config files and offloading JSBSim from much of the file parsing work by using the eXpat-based easyXML for our XML parser. Remember, were are not yet at v1.0. I wanted to make sure that we got it right for v1.0. There are many new capabilities that we really wanted to have. We spent a long time developing it and testing it. Some last minute adjustments presented some glitches with the config file in FlightGear, but those will soon be a thing of the past, and we'll be dealing with a more stable, more capable, JSBSim. Hang in there. Jon --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] 3d model animation: how to read the syntax alias=../../../../params/light?
Hi, Thanks to a few people giving me good hints I finally got those dist-scale/billboard/translate animations to work (reading the donauturn.xml example was very usefull). It was a try and guess exercise (because of the lack of docs) but it worked. Now I have three billboard lights which scale according to an interpolation table. That's the point now, there's some syntax in the dist-scale section I do not fully understand. The line dep alias=../../../../params/light/ seems to be related to the lines: params light1/light /params I interpret this as setting a variable called light and reading that value with alias=../../../../params/light Well, I'd like to know more about that particular path-like string (the ../../../../ before params/light) in order to use it in a correct manner in the future. How do I have to read that? It looks like a property tree path to traverse? If it is, what kind of property tree is that? What's the root? I don't find it in FG property browser. Second point is I used the following syntax (from donauturm example) in order to get the translation of the poly light: offset-m67.5/offset-m axis z0.20/z x-0.62/x y-0.17/y /axis Is that fully interchangable with: offsets x-offset-m22.0/x-offset-m y-offset-m-15.0/y-offset-m z-offset-m-62.0/z-offset-m /offsets Are there any difference in the way that's used in the animation code? cheers, Roberto p.s. I changed the object and param names according to my 3d model but the syntax is still the same as the donauturm example. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] A-10 3D cockpit progress
dene maxwell wrote: If I chose to stay with the old version front end then I could still expect the functionality I had enjoyed to still be available. This is not the case with 098a MP. 098a MP no longer exists and having supported a household upgrade to cable 'net on the basis of being able to enjoy the MP experience, you might be able to understand my disappointment when I found out what had been, no longer was. FlightGear is free software. Unlike mentioned word processors or operating system, there's just no outside reason to not upgrade to a newer version. If you _chose_ to stay with the old version, you'll have to live with not getting new features. But it's entirely up to you. I see no reason why everyone else should abandon new features, just because you chose to. You don't lose anything either. You can keep old versions of the data and if you want, even check them out from the CVS tree. http://ximbiot.com/cvs/manual/ Nine --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] fgrun problems
Hi guys not sure if anyone here can help , but since my last cvs update last week i am unable to see any aircraft or airports in FGRUN. The other options work fine , but there is nothing in the aircraft chooser window or airports. I update fgrun from cvs too and rebuild. What could have changed ? Justin Smithies --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] ATC
Not sure of whos in charge of the ATC but would love to be able to contact tower to take off etc. P.S Worked out how ATC works flew from dundee to dyce and tower gave me runway to land and said to follow cessna in etc. :) Justin Smithies --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Tutorial System patch (version 5)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Buchanan, Stuart schrieb: Hi All, Another post from me - must mean another iteration of the tutorial patch I've just tried the current version in CVS -- it's great! But one problem is that I don't have Festival - and thus have to read all messages... Reading and looking at the instruments as well as out of the cockpit and on the keyboard to hit the right keys is quite challenging... :) CU, Christian BTW and different topic: starting from Friedrichshaven with the www.custom-scenery.org scenery FGFS has on Windows a memory consumption of far more than 700 MB. Is that the same for Linux? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (MingW32) iD8DBQFEAdeZlhWtxOxWNFcRAoA7AKCYo4Av3fooVYTY7x1ztKd69RV0DQCfQScG h3L3DoSC07CZy9emh8bqEdI= =xbO2 -END PGP SIGNATURE- --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Adjustable pitch stops for YASim CS propellers (was Re: [Flightgear-devel] YASim question: propeller idle RPM)
On 22/02/06, Andy Ross [EMAIL PROTECTED] wrote: But the variable speed code will always seek to the specified RPM, and the current model gives it enough wiggle room to push the torque as far down as it wants, essentially. You could try setting a different/tunable floor to the pitch value (see the clamping in Propeller::modPitch()), but getting that value right is going to take a lot of experimentation. Since I don't have the time or expertise to do the right thing, I've added a work-around. The values in mod pitch are (loose) representations of the physical stops in a constant speed propeller. For many of the models, the fine-pitch stop allows too small a pitch, thus allowing the propeller to spin too fast at low power settings. I've just checked in some patches to allow aircraft designers to change these values at runtime, using the attributes fine-stop and coarse-stop to fine-tune the propeller. Currently, these default to the previously hard-coded values of 0.25 and 4.00, so current flight models won't be affected. When I set fine-stop to 1.0, for example, the Comanche (pa24-250) idles at a much more realistic RPM, and approach RPM also looks more credible -- I haven't checked in that change until Dave Perry reviews it, though (I'll send him the patch in a private e-mail). The user-visible (i.e. aircraft designer-visible) changes are documented in $FG_ROOT/Docs/README.yasim. Anyone maintaining a YASim flight model with (a) constant-speed propeller(s) should consider playing with these values a bit. All the best, David -- http://www.megginson.com/ --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Tutorial System patch (version 5)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Buchanan, Stuart schrieb: Yes, having festival really makes a difference. I compiled it successfully on Cygwin, but I don't know if it is possible to compile for straight windows. Perhaps some kind person will be able to compile a MS binary and make it available... AFAIK are at least some Windows versions comming with a native text to speech engine. But I don't know how to access its API. CU, Christian -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (MingW32) iD8DBQFEAd8hlhWtxOxWNFcRApldAJsGZGw57gnYhWCa+0UqyrKiVoLwyQCfS/YQ F+1MigAeUadGA4nznxtlc3s= =kj+6 -END PGP SIGNATURE- --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
RE: [Flightgear-devel] A-10 3D cockpit progress
Chris wrote: To what little I understand, I agree completely that changes were good. But from the FlightGear perspective, one could have imagined different ways of dealing with old-style config files. For example, one could have imagined a parser which detected the config file style, and acted differently on that basis -- anywhere from screaming about the old file's format and warning that it'll probably stop working with the next version, to encouraging the user to look into getting an updated config, to pointing the user to the conversion software so they can try it themselves, to having the user stand by while config file style conversion was attempted right then in an automated fashion -- all things I've seen other applications do when faced with this situation. We just broke the old files, and while that should nudge developers who hadn't yet reacted to the warnings about the config file changes, it also was probably rough on a few users, who found that planes they enjoyed suddenly didn't work anymore. Good suggestions. There are places I've tried to catch obvious problems, but it doesn't always work. One of those places is the configuration file version number. What is supposed to happen is that when an old configuration file is read, the new code is supposed to inform the user what is wrong. Sometimes it doesn't work as well as it could. Anyhow, I'll keep this in mind and maybe I can add some of these suggestions. But, I have noticed that sometimes when error messages are sent to the console, the user doesn't look for those, anyhow. SimGear also hides the messages that JSBSim normally puts out to prevent the user from being inundated with messages. At a time like this, users may want to turn on some of those messages, or some of them should bypass the SimGear message handling mechanism. (?) Jon --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] A-10 3D cockpit progress
Jon S. Berndt wrote: Anyhow, I'll keep this in mind and maybe I can add some of these suggestions. But, I have noticed that sometimes when error messages are sent to the console, the user doesn't look for those, anyhow. SimGear also hides the messages that JSBSim normally puts out to prevent the user from being inundated with messages. At a time like this, users may want to turn on some of those messages, or some of them should bypass the SimGear message handling mechanism. (?) FlightGear should always display messages when it is labeled alert. Maybe there is a log-level mismatch between FlightGear and JSBSim? Erik -- http://www.ehtw.info (Dutch)Future of Enschede Airport Twente http://www.ehofman.com/fgfs FlightGear Flight Simulator http://www.cafepress.com/fgfs_flightsim FlightGear Art --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Re: Adjustable pitch stops for YASim CS propellers (was Re: [Flightgear-devel] YASim question: propeller idle RPM)
David Megginson wrote: On 22/02/06, Andy Ross [EMAIL PROTECTED] wrote: But the variable speed code will always seek to the specified RPM, and the current model gives it enough wiggle room to push the torque as far down as it wants, essentially. You could try setting a different/tunable floor to the pitch value (see the clamping in Propeller::modPitch()), but getting that value right is going to take a lot of experimentation. Since I don't have the time or expertise to do the right thing, I've added a work-around. The values in mod pitch are (loose) representations of the physical stops in a constant speed propeller. For many of the models, the fine-pitch stop allows too small a pitch, thus allowing the propeller to spin too fast at low power settings. I've just checked in some patches to allow aircraft designers to change these values at runtime, using the attributes fine-stop and coarse-stop to fine-tune the propeller. Currently, these default to the previously hard-coded values of 0.25 and 4.00, so current flight models won't be affected. When I set fine-stop to 1.0, for example, the Comanche (pa24-250) idles at a much more realistic RPM, and approach RPM also looks more credible -- I haven't checked in that change until Dave Perry reviews it, though (I'll send him the patch in a private e-mail). The user-visible (i.e. aircraft designer-visible) changes are documented in $FG_ROOT/Docs/README.yasim. Anyone maintaining a YASim flight model with (a) constant-speed propeller(s) should consider playing with these values a bit. All the best, David -- http://www.megginson.com/ --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=kkid0944bid$1720dat1642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel Anybody else getting this? Making all in YASim make[3]: Entering directory `/usr/local/src/FlightGear/source/src/FDM/YASim' if ccache g++ -DHAVE_CONFIG_H -I. -I. -I../../../src/Include -I../../.. -I../../../src -I/usr/local/include -I/usr/X11R6/include -Wall -O2 -funroll-loops -march=athlon -g -I/usr/local -D_REENTRANT -MT YASim.o -MD -MP -MF .deps/YASim.Tpo -c -o YASim.o YASim.cxx; \ then mv -f .deps/YASim.Tpo .deps/YASim.Po; else rm -f .deps/YASim.Tpo; exit 1; fi YASim.cxx:1: error: expected unqualified-id before '' token /usr/lib/gcc/i486-linux-gnu/4.0.3/../../../../include/c++/4.0.3/i486-linux-gnu/bits/c++config.h:68: error: '__gnu_debug_def' is not a namespace-name /usr/lib/gcc/i486-linux-gnu/4.0.3/../../../../include/c++/4.0.3/i486-linux-gnu/bits/c++config.h:68: error: expected namespace-name before ';' token BodyEnvironment.hpp:75: warning: 'class yasim::BodyEnvironment' has virtual functions but non-virtual destructor Engine.hpp:16: warning: 'class yasim::Engine' has virtual functions but non-virtual destructor PistonEngine.hpp:8: warning: 'class yasim::PistonEngine' has virtual functions but non-virtual destructor make[3]: *** [YASim.o] Error 1 make[3]: Leaving directory `/usr/local/src/FlightGear/source/src/FDM/YASim' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/local/src/FlightGear/source/src/FDM' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/FlightGear/source/src' make: *** [all-recursive] Error 1 Josh --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Re: Adjustable pitch stops for YASim CS propellers (was Re: [Flightgear-devel] YASim question: propeller idle RPM)
Josh Babcock wrote: Anybody else getting this? YASim.cxx:1: error: expected unqualified-id before '' token There was a conflict when updating the CVS code. Try removing that file and run cvs update again. Erik --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Re: Adjustable pitch stops for YASim CS propellers (was Re: [Flightgear-devel] YASim question: propeller idle RPM)
Josh Babcock wrote: David Megginson wrote: On 22/02/06, Andy Ross [EMAIL PROTECTED] wrote: But the variable speed code will always seek to the specified RPM, and the current model gives it enough wiggle room to push the torque as far down as it wants, essentially. You could try setting a different/tunable floor to the pitch value (see the clamping in Propeller::modPitch()), but getting that value right is going to take a lot of experimentation. Since I don't have the time or expertise to do the right thing, I've added a work-around. The values in mod pitch are (loose) representations of the physical stops in a constant speed propeller. For many of the models, the fine-pitch stop allows too small a pitch, thus allowing the propeller to spin too fast at low power settings. I've just checked in some patches to allow aircraft designers to change these values at runtime, using the attributes fine-stop and coarse-stop to fine-tune the propeller. Currently, these default to the previously hard-coded values of 0.25 and 4.00, so current flight models won't be affected. When I set fine-stop to 1.0, for example, the Comanche (pa24-250) idles at a much more realistic RPM, and approach RPM also looks more credible -- I haven't checked in that change until Dave Perry reviews it, though (I'll send him the patch in a private e-mail). The user-visible (i.e. aircraft designer-visible) changes are documented in $FG_ROOT/Docs/README.yasim. Anyone maintaining a YASim flight model with (a) constant-speed propeller(s) should consider playing with these values a bit. All the best, David -- http://www.megginson.com/ --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=kkid0944bid$1720dat1642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel Anybody else getting this? Making all in YASim make[3]: Entering directory `/usr/local/src/FlightGear/source/src/FDM/YASim' if ccache g++ -DHAVE_CONFIG_H -I. -I. -I../../../src/Include -I../../.. -I../../../src -I/usr/local/include -I/usr/X11R6/include -Wall -O2 -funroll-loops -march=athlon -g -I/usr/local -D_REENTRANT -MT YASim.o -MD -MP -MF .deps/YASim.Tpo -c -o YASim.o YASim.cxx; \ then mv -f .deps/YASim.Tpo .deps/YASim.Po; else rm -f .deps/YASim.Tpo; exit 1; fi YASim.cxx:1: error: expected unqualified-id before '' token /usr/lib/gcc/i486-linux-gnu/4.0.3/../../../../include/c++/4.0.3/i486-linux-gnu/bits/c++config.h:68: error: '__gnu_debug_def' is not a namespace-name /usr/lib/gcc/i486-linux-gnu/4.0.3/../../../../include/c++/4.0.3/i486-linux-gnu/bits/c++config.h:68: error: expected namespace-name before ';' token BodyEnvironment.hpp:75: warning: 'class yasim::BodyEnvironment' has virtual functions but non-virtual destructor Engine.hpp:16: warning: 'class yasim::Engine' has virtual functions but non-virtual destructor PistonEngine.hpp:8: warning: 'class yasim::PistonEngine' has virtual functions but non-virtual destructor make[3]: *** [YASim.o] Error 1 make[3]: Leaving directory `/usr/local/src/FlightGear/source/src/FDM/YASim' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/local/src/FlightGear/source/src/FDM' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/FlightGear/source/src' make: *** [all-recursive] Error 1 Josh --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel Nope, local problem. I think a patch I applied got my version out of sync in a way that caused CVS to merge improperly. Works now. Josh --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
RE: [Flightgear-devel] A-10 3D cockpit progress
Erik wrote:
FlightGear should always display messages when it is labeled alert.
Maybe there is a log-level mismatch between FlightGear and JSBSim?
Here's the controlling code in JSBSim.cxx:
switch (logbuf::get_log_priority()) {
case SG_BULK:
FGJSBBase::debug_lvl = 0x1f;
break;
case SG_DEBUG:
FGJSBBase::debug_lvl = 0x0f;
case SG_INFO:
FGJSBBase::debug_lvl = 0x01;
break;
case SG_WARN:
case SG_ALERT:
FGJSBBase::debug_lvl = 0x00;
break;
}
If the JSBSim variable, debug_lvl, is set to zero, nothing comes out of
JSBSim. That turns off JSBSim output. Setting debug_lvl to 1 echoes the
inputs that JSBSim gets. Anything above that adds more stuff - probably more
than FlightGear needs. An overhaul is probably in order on the JSBSim side,
but at the moment at least the WARN|ALERT level of SimGear should set
debug_lvl to 0x01.
Jon
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] A-10 3D cockpit progress
On Sunday 26 February 2006 06:13, dene maxwell wrote: Hi Chris, I don't disagree with anything you're saying. I don't (and never have) run 3-d cockpits, I believe my hardware setup is too primative to support them. This is not the fault of FG, it is a probelm I am saving up to remedy. You are right; I can't run 3-d cockpits. I run 098a binary and G099 data/0910 scenery but have tried a number of aircraft that have been developed for the 099 binary that won't work or have unpredictable behaviour when using the 098a binary. You should be able to use the CVS version (and hence 3D cockpit) provide that you don't change your FDM config file. Ampere --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Plib make install problem?
Has anyone seen this when trying to run make install on plib? Making install in sg make[2]: Entering directory `/cygdrive/d/jon/src/plib/src/sg' make[2]: *** No rule to make target `install'. Stop. make[2]: Leaving directory `/cygdrive/d/jon/src/plib/src/sg' make[1]: *** [install-recursive] Error 1 --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] A-10 3D cockpit progress
Hi Alexis, How big is the file? as I have a size limit on the Hotmail account. If less than 1Mbyte please send to; [EMAIL PROTECTED] , if bigger please send to [EMAIL PROTECTED] I look forward to trying it out. Regards Dene From: alexis bory [EMAIL PROTECTED] Reply-To: flightgear-devel@lists.sourceforge.net To: flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] A-10 3D cockpit progress Date: Sun, 26 Feb 2006 13:09:47 +0100 Lee Elliott a écrit : On Saturday 25 February 2006 17:56, alexis bory wrote: I'll do that ASAP, maybe sunday night or monday. I can't see any need for a separate folder - add your stuff to the A-10, your name and comments to the existing files, especially the author tag in the A-10-set.xml file and send it to one of the cvs maintainers. I have furbished a .tgz of A-10 with the actual 3D cockpit, it doesn't permit yet to disable the added 3D stuff, but why not ;) (Dene, please, will you try it ?) I just wonder who/where to send it ? Alexis --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel _ Looking for love? Check out XtraMSN Personals http://xtramsn.match.com/match/mt.cfm?pg=channeltcid=200731 --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Re: Flightgear-devel digest, Vol 1 #544 - 9 msgs
On Sunday 26 February 2006 06:10, [EMAIL PROTECTED] wrote: A separate A-10-3Dcockpit would make the existing A-10 redundant - who would want to fly it without your cockpit? :) Maybe those langishing on 098a? From what I've seen of Alexis cockpit, I would love to fly it with his cockpit, as I enjoy the A10 FDM. But any new a/c, unless they have a 098a implementation, are useless to us. Hi Im not sure what you mean by 098a implementation ? I much prefer 3d cockpit to 2d I modelled the Citations ,B1900d and DHC2 with 3d cockpits . Would adding 2d panels to them help , for older hardware ? Personally Ive tried to generate JSBsim files for my aircraft but FG crashes before they load... thats the only major change I can think of.. Syd --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] silly questions !
Hi all , time to clear up some assumption of mine ! They may seem obvios to most of you so hopefully you can help. Does yasims 'approach aoa ' mean angle of decsent path or pitch of the aircraft? Ive always assumed it the angle of approach path. Thanks , Syd --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] silly questions !
syd sandy wrote: Does yasims 'approach aoa ' mean angle of decsent path or pitch of the aircraft? Ive always assumed it the angle of approach path. Neither. The acronym AoA is used in place of angle of attack, which is a technical term referring to the angle with which the airflow meets the airframe. In this case, because the solver uses level flight to solve for approach*, the AoA will be equal to the nose-high pitch angle. * Adding support for a glide-slope parameter would, for example, allow gliders to work. They don't right now. Andy --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] svg2ac
Well we have an SVG parser that reads the input svg file and extract the polygons for the keywords buildings, runways taxiways. The vertices are then stored and duplicated to create the roof. The side polygons are computed by duplicating again 2 consecutive nodes that form an edge. The altitude is fetched from a running session of FlightGear via telnet for the location of the center of each building. All the coordinates are then converted to meters using the 4 Lat/Long lines present in the SVG file and then the Lat/Long coordinates of the origin is obtained, this is needed in the .stg file. That's pretty much it. I recently tried a new airport (Toronto, CYYZ) given by Ampere, it looked pretty good besides the two problems presented in the previous email.
Re: [Flightgear-devel] Aircraft startup failure, confirmed by others (Concorde / Boeing314A)
On Sun, 26 Feb 2006 08:04:53 -0600 Jon S. Berndt wrote: 1) Which version of FlightGear are you running with, and which version of the Concorde? Version of both FG source and data -- CVS, current as to six hours ago. Ditto for SG. plib I haven't updated in a week. 2) Please turn console logging on and look for error messages in the information that is sent to the console at startup. With --log-level=debug, when the failure occurs, I only get (with some context): } FGTileMgr::update() } State == Start || Inited } } } JSBSim Flight Dynamics Model v0.9.10.111805 } [cfg file spec v2.0] } } JSBSim startup beginning ... } } FlightGear aborting } } } *** glibc detected *** free(): invalid pointer: 0x01102208 *** } Aborted Not too helpful, I know. If I rerun with JSBSIM_DEBUG=2, I get a ton of stuff that's pasted in below. Cheers, -c FGTileMgr::update() State == Start || Inited Instantiated: FGFDMExec FGModel Base Class Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGAtmosphere FGModel Base Class Instantiated: FGFCS FGModel Base Class Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGMatrix33 Instantiated: FGPropulsion FGModel Base Class Instantiated: FGMatrix33 Instantiated: FGMatrix33 Instantiated: FGMatrix33 Instantiated: FGMatrix33 Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGMassBalance FGModel Base Class Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGAerodynamics FGModel Base Class Instantiated: FGInertial FGModel Base Class Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGGroundReactions FGModel Base Class Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGAircraft FGModel Base Class Instantiated: FGColumnVector3 Instantiated: FGMatrix33 Instantiated: FGMatrix33 Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGMatrix33 Instantiated: FGMatrix33 Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGPropagate FGModel Base Class Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGColumnVector3 Instantiated: FGMatrix33 Instantiated: FGMatrix33 Instantiated: FGAuxiliary FGModel Base Class Instantiated: FGInput Instantiated: FGMatrix33 Instantiated: FGMatrix33 Instantiated: FGState Instantiated: FGMatrix33 Destroyed:FGMatrix33 Instantiated: FGMatrix33 Destroyed:FGMatrix33 Instantiated: FGInitialCondition FlightGear aborting *** glibc detected *** free(): invalid pointer: 0x01102208 *** Aborted -- Chris Metzler [EMAIL PROTECTED] (remove snip-me. to email) As a child I understood how to give; I have forgotten this grace since I have become civilized. - Chief Luther Standing Bear signature.asc Description: PGP signature
RE: [Flightgear-devel] Aircraft startup failure, confirmed by others (Concorde / Boeing314A)
Version of both FG source and data -- CVS, current as to six hours ago. Ditto for SG. plib I haven't updated in a week. OK, I updated by plib/simgear/flightgear/base installation as of this morning. The Concorde and Boeing 314 are both made of the old config file format. The newest code changes I have implemented in JSBSim to detect the old format and issue a message is not in FlightGear CVS, yet. I'll try and take care of both of those problesm soon. Jon --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] SimGear compile error
AFter a fresh plib/simgear/flightgear build, I got a successful plib and simgear build, but got tripped up in FlightGear due to a problem with SimGear as follows: === start === g++ -g -O2 -D_REENTRANT -L/usr/local/lib -o test-text.exe test-text.o if g++ -DHAVE_CONFIG_H -I. -I. -I../src/Include -I/usr/local/include -g -O2 -D_REENTRANT -MT test-up.o -MD -MP -MF .deps/test-up.Tpo -c -o test-up.o test-up.cxx; \ then mv -f .deps/test-up.Tpo .deps/test-up.Po; else rm -f .deps/test-up.Tpo; exit 1; fi In file included from /usr/local/include/simgear/math/SGMath.hxx:27, from /usr/local/include/simgear/math/point3d.hxx:55, from /usr/local/include/simgear/math/sg_geodesy.hxx:4, from test-up.cxx:10: /usr/local/include/simgear/math/SGMisc.hxx:28: error: expected unqualified-id before const /usr/local/include/simgear/math/SGMisc.hxx:28: error: expected `)' before const /usr/local/include/simgear/math/SGMisc.hxx:28: error: expected `)' before const In file included from /usr/local/include/simgear/math/SGMath.hxx:27, from /usr/local/include/simgear/math/point3d.hxx:55, from /usr/local/include/simgear/math/sg_geodesy.hxx:4, from test-up.cxx:10: /usr/local/include/simgear/math/SGMisc.hxx:30:50: macro min passed 3 arguments, but takes just 2 /usr/local/include/simgear/math/SGMisc.hxx:31: error: invalid member function declaration === end === Anyone else see this? Jon --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
RE: [Flightgear-devel] SimGear HEADER error in FLIGHTGEAR compile
AFter a fresh plib/simgear/flightgear build, I got a successful plib and simgear build, but got tripped up in FlightGear due to a problem with SimGear as follows: Stupid me. I worded the problem incorrectly. Obviously, the problem is with a compile of the FlightGear test program, with the definition or use of min. === start === g++ -g -O2 -D_REENTRANT -L/usr/local/lib -o test-text.exe test-text.o if g++ -DHAVE_CONFIG_H -I. -I. -I../src/Include -I/usr/local/include -g -O2 -D_REENTRANT -MT test-up.o -MD -MP -MF .deps/test-up.Tpo -c -o test-up.o test-up.cxx; \ then mv -f .deps/test-up.Tpo .deps/test-up.Po; else rm -f .deps/test-up.Tpo; exit 1; fi In file included from /usr/local/include/simgear/math/SGMath.hxx:27, from /usr/local/include/simgear/math/point3d.hxx:55, from /usr/local/include/simgear/math/sg_geodesy.hxx:4, from test-up.cxx:10: /usr/local/include/simgear/math/SGMisc.hxx:28: error: expected unqualified-id before const /usr/local/include/simgear/math/SGMisc.hxx:28: error: expected `)' before const /usr/local/include/simgear/math/SGMisc.hxx:28: error: expected `)' before const In file included from /usr/local/include/simgear/math/SGMath.hxx:27, from /usr/local/include/simgear/math/point3d.hxx:55, from /usr/local/include/simgear/math/sg_geodesy.hxx:4, from test-up.cxx:10: /usr/local/include/simgear/math/SGMisc.hxx:30:50: macro min passed 3 arguments, but takes just 2 /usr/local/include/simgear/math/SGMisc.hxx:31: error: invalid member function declaration === end === Anyone else see this? Jon --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] yasim aoa ...
Neither. The acronym AoA is used in place of angle of attack, which is a technical term referring to the angle with which the airflow meets the airframe. In this case, because the solver uses level flight to solve for approach*, the AoA will be equal to the nose-high pitch angle. * Adding support for a glide-slope parameter would, for example, allow gliders to work. They don't right now. Andy Thank you , that makes sense now !. Cheers, Syd BTW , Im still fighting with Festival, getting closer to hearing ATC voices every day :) --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
RE: [Flightgear-devel] Re: Flightgear-devel digest, Vol 1 #544 - 9 msgs
syd sandy writes Personally Ive tried to generate JSBsim files for my aircraft but FG crashes before they load... thats the only major change I can think of.. I to had this problem with a FDM that Dave Culp sent me for the new 737. Here is what occured. I needed to add a spoiler property to the FDM.Dave's suggestion was to copy and paste the speedbrake property changing were necessary.Running FG after the mod caused no change.I then decided to delete/comment out the speedbrake function.FG ran but offcourse no speedbrakes.The interesting thing occured when I then reinserted/uncommented the speedbrake property the sim then crashed every time at initailising subsystems in FGRUN.Reinserting Dave's original FDM restored FG operation. I have from my start of using FG used wordpad under windows 98se to do all my XML files without problem.Could there be something in the new XML format that my worpad does not handle leading to corruption of the FDM file?. Syd Cheers Innis --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
RE: [Flightgear-devel] Re: Flightgear-devel digest, Vol 1 #544 - 9 msgs
Hi Syd, I am running 098a because my hardware doesn't seem support 099. It even struggles with 098a/Atlas and 0.9.10 hardware. Although I really enjoy seeing and appreciate the effort that goes into 3-d cockpits and the realism they add, i unfortunately don't seem to be able to run them on the existing hardware. My comments seemed to have been taken to mean that I think all progress should stop until I (my hardware) manages to catch up. This of course is absurd! Both the contention and that I would think like that. You are right, and that is all I meant, if new and improved models of planes are developed please consider those that are running prior versions. Please do not over write the older versions and, if possible, 2-d panels might help a wider audience enjoy your efforts. I have a picture on my wall of your Citation and have downloaded and tried to fly it but for reasons unknown to me it suffers the same characteristics as the b737; pitching and yawing that gets progressively worse until I can't control it and it falls out of the sky. I have put this down to either the hardware or my lack of skill. Thank you for your efforts indeveloping such beautiful aircraft and if possible a 2-d panel version might help me enjoy them. Kind Regards =Dene From: syd sandy [EMAIL PROTECTED] Reply-To: flightgear-devel@lists.sourceforge.net To: flightgear-devel@lists.sourceforge.net Subject: [Flightgear-devel] Re: Flightgear-devel digest, Vol 1 #544 - 9 msgs Date: Sun, 26 Feb 2006 10:48:24 -0800 On Sunday 26 February 2006 06:10, [EMAIL PROTECTED] wrote: A separate A-10-3Dcockpit would make the existing A-10 redundant - who would want to fly it without your cockpit? :) Maybe those langishing on 098a? From what I've seen of Alexis cockpit, I would love to fly it with his cockpit, as I enjoy the A10 FDM. But any new a/c, unless they have a 098a implementation, are useless to us. Hi Im not sure what you mean by 098a implementation ? I much prefer 3d cockpit to 2d I modelled the Citations ,B1900d and DHC2 with 3d cockpits . Would adding 2d panels to them help , for older hardware ? Personally Ive tried to generate JSBsim files for my aircraft but FG crashes before they load... thats the only major change I can think of.. Syd --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel _ Discover fun and games at @ http://xtramsn.co.nz/kids --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] A-10 3D cockpit progress
Martin, I regret any offence I may have caused you. Given that this not the first time I have caused you personal offence. After careful consideration I feel it is prudent that I hang up the keyboard on the developer lists, at least until such time as I can afford hardware that will allow me to provide valid comments in the context of new developments. Regards Dene From: Martin Spott [EMAIL PROTECTED] Reply-To: flightgear-devel@lists.sourceforge.net To: flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] A-10 3D cockpit progress Date: Sun, 26 Feb 2006 11:42:50 + (UTC) dene maxwell wrote: From: Lee Elliott [EMAIL PROTECTED] A separate A-10-3Dcockpit would make the existing A-10 redundant - who would want to fly it without your cockpit? :) Maybe those langishing on 098a? From what I've seen of Alexis cockpit, I would love to fly it with his cockpit, as I enjoy the A10 FDM. But any new a/c, unless they have a 098a implementation, are useless to us. Typically I'm a person that seeks for harmony so I resisted to post such words for quite some time, but now the moment has come where I realize that I definitely feel pissed by such comments like the one quoted above. How do you _dare_ to imply that every aircraft without a v098 implementation is useless tu _us_ ? You can't expect people to cease develompment of new features just because one or two users still prefer to run an outdated version of the software. This is real bullshit, not only that, it would leave Flightear development falling behind until it reaches insignificance. Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel _ Need more speed? Get Xtra Broadband @ http://jetstream.xtra.co.nz/chm/0,,202853-1000,00.html --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
RE: [Flightgear-devel] Re: Flightgear-devel digest, Vol 1 #544 - 9 msgs
I to had this problem with a FDM that Dave Culp sent me for the new 737. Here is what occured. ... I have from my start of using FG used wordpad under windows 98se to do all my XML files without problem.Could there be something in the new XML format that my worpad does not handle leading to corruption of the FDM file?. Cheers Innis It is possible that you trashed your XML file - for instance, your element tags don't match or something. It is good policy to validate your XML files after making an edit or using them the first time - and this is a good policy not just for JSBSim files, but for any XML file. A schema has been created for JSBSim aircraft config files that specifies what is legal. You can use a tool such as oXygen or Stylus Studio to validate the document. There are other tools as well. Another thing you can do is to open the aircraft config file in a browser. That *should* display the XML file using the style sheet specified in the processing instruction at the top of JSBSim aircraft config files. There is a style sheet (JSBSim.xsl) at the JSBSim web site. If the xml file loads properly, chances are it is well-formed, at least. You should peruse the data presented to make sure it is what you expect to see. Jon --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Error in SGMisc class? I don't see it ...
On Monday 27 February 2006 04:44, Jon S. Berndt wrote:
Stupid me. I worded the problem incorrectly. Obviously, the
problem is with
a compile of the FlightGear test program, with the definition or use of
min.
Here's the offensive code in /usr/local/include/simgear/math/SGMisc.hxx
=== start ===
#ifndef SGMisc_H
#define SGMisc_H
#include cmath
templatetypename T
class SGMisc {
public:
static T pi() { return T(3.1415926535897932384626433832795029L); }
static T min(const T a, const T b)
=== end ===
The last line, above, is the culprit. As before, the errors are:
SGMisc.hxx:28: error: expected unqualified-id before const
SGMisc.hxx:28: error: expected `)' before const
SGMisc.hxx:28: error: expected `)' before const
The rest of the errors (lots of them), likewise involve min.
Jon
P.S. What is the test-up application, anyhow? Can we avoid compiling that?
Or, is it needed?
Yes it is needed and used.
It is a handy and typesafe way to program a min or max function.
You know exactly what type the input arguments are and which the output
arguments are.
What you can do when you want a float max is
SFMiscfloat::max(b, a)
You don't get ambiguities and you dont get whatever min/max is defined in the
global namespace you dont know about which types are used when it is really
defined.
What brakes, but that brakes anyway if you do includes in the wrong order, is
that a prevously defined min/max macro will disturb the
declaration/implementation of the SGMisc min/max as it would disturb that for
every other min/max declaration/implementation like the std::min/std::max
functions for example too.
I bet that you defined such a macro and past that include SGMath.h
Greetings
Mathias
--
Mathias Fröhlich, email: [EMAIL PROTECTED]
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
