Re: [Flightgear-devel] Minor keyboard reassignment
On sam 10 novembre 2007, Melchior FRANZ wrote: * Melchior FRANZ -- Saturday 10 November 2007: L is used to engage in the aircraft carrier's catapult (see $FG_ROOT/Input/Keyboard/carrier-bindings.xml). So around 10 aircraft will overwrite the new lighting binding anyway. err ... the tailwheel lock binding. (I didn't even know that it was there. I have that on my js.) We have still several keys globally unassigned, but it's increasingly hard to find one that isn't used by at least one aircraft. In the long run we'll have to reorganize a bit. We waste a lot of keys for obscure features that a typical simulator user will never need and/or that are too easy to press by accident (a/A, t/T, r, ...). The carrier bindings could IMHO be in a small popup dialog (like the ATC dialog). They aren't for controlling the aircraft after all, but to give orders to the carrier crew. m. Anyhow, i am not sure it would be a good idea to use the reserved carrier KEYS. There is only a the little number of persons who use and like the carriers, which is not the majority of the FG community :(, so i can understand that many persons don't mind about carrier, and i worry it. The L is very useful , i mean a key on the keyboard (not a like ATC dialog). Please keep it. Regards -- Gérard http://pagesperso-orange.fr/GRTux/ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Minor keyboard reassignment
Gerard robin wrote Sent: 10 November 2007 09:29 To: FlightGear developers discussions Subject: Re: [Flightgear-devel] Minor keyboard reassignment On sam 10 novembre 2007, Melchior FRANZ wrote: * Melchior FRANZ -- Saturday 10 November 2007: L is used to engage in the aircraft carrier's catapult (see $FG_ROOT/Input/Keyboard/carrier-bindings.xml). So around 10 aircraft will overwrite the new lighting binding anyway. err ... the tailwheel lock binding. (I didn't even know that it was there. I have that on my js.) We have still several keys globally unassigned, but it's increasingly hard to find one that isn't used by at least one aircraft. In the long run we'll have to reorganize a bit. We waste a lot of keys for obscure features that a typical simulator user will never need and/or that are too easy to press by accident (a/A, t/T, r, ...). The carrier bindings could IMHO be in a small popup dialog (like the ATC dialog). They aren't for controlling the aircraft after all, but to give orders to the carrier crew. m. Anyhow, I am not sure it would be a good idea to use the reserved carrier KEYS. There is only a the little number of persons who use and like the carriers, which is not the majority of the FG community :(, so i can understand that many persons don't mind about carrier, and i worry it. The L is very useful , i mean a key on the keyboard (not a like ATC dialog). Please keep it. And I don't think a dialog would be a good way to fire the catapult. Regards Vivian - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Minor keyboard reassignment
* Vivian Meazza -- Saturday 10 November 2007: Gerard robin wrote There is only a the little number of persons who use and like the carriers, I'm not even sure about that. It's one of the frequently asked questions, and it seems as if everyone of the IRC regulars uses the carrier once in a while. I do pretty often. The L is very useful , i mean a key on the keyboard (not a like ATC dialog). And I don't think a dialog would be a good way to fire the catapult. Hmm ... ok. I'm just not sure if having two separate keys is a good thing. Maybe we should standardize on c ... toggle canopy C ... engage disengage (toggle) catapult \__c as in carrier Ctrl-c ... launch catapult / control the crew :-) l ... lights (though most are operated via 3D cockpit switches!) L ... tail wheel lock Ctrl-l ... liveries (l for liveries is a bit exaggerated, anyway) m. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Minor keyboard reassignment
Melchior FRANZ Sent: 10 November 2007 10:00 To: flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] Minor keyboard reassignment * Vivian Meazza -- Saturday 10 November 2007: Gerard robin wrote There is only a the little number of persons who use and like the carriers, I'm not even sure about that. It's one of the frequently asked questions, and it seems as if everyone of the IRC regulars uses the carrier once in a while. I do pretty often. The L is very useful , i mean a key on the keyboard (not a like ATC dialog). And I don't think a dialog would be a good way to fire the catapult. Hmm ... ok. I'm just not sure if having two separate keys is a good thing. Maybe we should standardize on c ... toggle canopy C ... engage disengage (toggle) catapult \__c as in carrier Ctrl-c ... launch catapult / control the crew :-) l ... lights (though most are operated via 3D cockpit switches!) L ... tail wheel lock Ctrl-l ... liveries (l for liveries is a bit exaggerated, anyway) Sounds reasonable to me. V. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] [RFC] c172x ... fix or kill?
The c172c by John CHECK is broken since a long time. It references a file that doesn't exist: Error reading default aircraft: Failed to open file at $FG_ROOT/Aircraft/c172x/../c172r/c172r-base.xml And even if one changes that to use ../c172r/c172r-set.xml it doesn't work: Could not open thruster file: prop_Clark_Y7570.xml Could not open file: $FG_ROOT/Aircraft/c172x/c172ap.xml Engine file c172x/Engines/prop_75in2f.xml is identical with the one in c172r/Engines/, but c172x/Engines/eng_io320.xml differs slightly, which is a bad sign. So, what are we going to do with the c172x? Anyone interested in fixing it? Otherwise I move it to the Attic/. m. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] New aircraft for CVS - Pitts S1C
Hi All, Over the last couple of weeks, I've been working on a Pitts S1C - the classic aerobatic biplane. It is available for download at http://www.nanjika.co.uk/flightgear/pittss1c.tar.gz. Screenshot at http://www.nanjika.co.uk/flightgear/pittss1c.jpg The model and FDM are fairly basic, but it is quite fun to fly, and a challenge to land. Comment and any modifications are very welcome. This is my first YASim aircraft, so I'm sure the FDM could benefit from some tuning. The included livery is for the well-known fictional beer company, but the .rgb files are very straightforward to edit for those who like to personalize their steeds, or just don't like the yellow colour Could someone commit it to CVS please? Thanks, -Stuart ___ Yahoo! Answers - Got a question? Someone out there knows the answer. Try it now. http://uk.answers.yahoo.com/ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Minor keyboard reassignment
Vivian Meazza a écrit : Melchior FRANZ Hmm ... ok. I'm just not sure if having two separate keys is a good thing. Maybe we should standardize on c ... toggle canopy C ... engage disengage (toggle) catapult \__c as in carrier Ctrl-c ... launch catapult / control the crew :-) l ... lights (though most are operated via 3D cockpit switches!) L ... tail wheel lock Ctrl-l ... liveries (l for liveries is a bit exaggerated, anyway) Sounds reasonable to me. V. I Agree too. Alexis - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] New aircraft for CVS - Pitts S1C
* Stuart Buchanan -- Saturday 10 November 2007: The included livery is for the well-known fictional beer company, Hmm ... I'm not sure if that's fictional enough. 20th Century Fox has already sued an Australian brewery for making Duff beer, although they aren't brewing beer themselves, obviously. They are quite greedy and sue-happy, I think. How's that different from using airline liveries? As long as we are depicting real aircraft that's IMHO like painting a picture or making a photo and giving it away, which is perfectly legal. And airlines don't lose anything from it. On the contrary. It's free advertisement. Personally, I don't have anything against the livery. But I don't want to be the one who commits it and is responsible for it being in CVS. I won't complain if someone else commits. :-) m. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Minor keyboard reassignment
* alexis bory -- Saturday 10 November 2007: Vivian Meazza a écrit : Sounds reasonable to me. I Agree too. Umm ... it's only that I had forgotten that Ctrl-c is toggle clickable panel hotspots. So the plan doesn't work out exactly like that. m. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Minor keyboard reassignment
On sam 10 novembre 2007, Melchior FRANZ wrote: * alexis bory -- Saturday 10 November 2007: Vivian Meazza a écrit : Sounds reasonable to me. I Agree too. Umm ... it's only that I had forgotten that Ctrl-c is toggle clickable panel hotspots. So the plan doesn't work out exactly like that. m. A stupid question: Why is it necessary to have a key for lights, isn't it a cockpit feature with hotspot, and switch ? Regards -- Gérard http://pagesperso-orange.fr/GRTux/ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Minor keyboard reassignment
On Saturday 10 November 2007, gerard robin wrote: A stupid question: Why is it necessary to have a key for lights, isn't it a cockpit feature with hotspot, and switch ? I'm guessing because pressing a key on the keyboard resembles the gesture of pressing a key inside a cockpit of a real aircraft. -- Roy Vegard Ovesen - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [RFC] c172x ... fix or kill?
The C172x is an experimental model for use with JSBSim by itself. It's the aircraft model I use to test all the new features. It should not be released. Jon -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Melchior FRANZ Sent: Saturday, November 10, 2007 5:29 AM To: flightgear-devel@lists.sourceforge.net Subject: [Flightgear-devel] [RFC] c172x ... fix or kill? The c172c by John CHECK is broken since a long time. It references a file that doesn't exist: Error reading default aircraft: Failed to open file at $FG_ROOT/Aircraft/c172x/../c172r/c172r-base.xml And even if one changes that to use ../c172r/c172r-set.xml it doesn't work: Could not open thruster file: prop_Clark_Y7570.xml Could not open file: $FG_ROOT/Aircraft/c172x/c172ap.xml Engine file c172x/Engines/prop_75in2f.xml is identical with the one in c172r/Engines/, but c172x/Engines/eng_io320.xml differs slightly, which is a bad sign. So, what are we going to do with the c172x? Anyone interested in fixing it? Otherwise I move it to the Attic/. m. --- -- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] New aircraft for CVS - Pitts S1C
Melchior wrote: * Stuart Buchanan -- Saturday 10 November 2007: The included livery is for the well-known fictional beer company, Hmm ... I'm not sure if that's fictional enough. 20th Century Fox has already sued an Australian brewery for making Duff beer, although they aren't brewing beer themselves, obviously. They are quite greedy and sue-happy, I think. How's that different from using airline liveries? As long as we are depicting real aircraft that's IMHO like painting a picture or making a photo and giving it away, which is perfectly legal. And airlines don't lose anything from it. On the contrary. It's free advertisement. Personally, I don't have anything against the livery. But I don't want to be the one who commits it and is responsible for it being in CVS. I won't complain if someone else commits. :-) OK. Better safe than sorry, I guess. I'll update the livery to something more fictional. Good job I made it so easy to re-paint then! -Stuart ___ Want ideas for reducing your carbon footprint? Visit Yahoo! For Good http://uk.promotions.yahoo.com/forgood/environment.html - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [RFC] c172x ... fix or kill?
* Jon S. Berndt -- Saturday 10 November 2007: The C172x is an experimental model for use with JSBSim by itself. It's the aircraft model I use to test all the new features. It should not be released. That only explains why it is in JSBSim's CVS. It does not explain why it should be in FGFS' CVS. It includes a non existent file and is broken. Again: does anyone intend to *FIX* it? Otherwise it should be removed. m. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Minor keyboard reassignment
On Sat, 10 Nov 2007, David Megginson wrote: So, in summary, I think a single switch to turn on all required interior and exterior lights for night flying can be a big win for FlightGear. That sounds reasonable. But maybe a menu entry or setup dialog would be better for this - after all it would usually only be used once per flight. Just my 0.05 SEK.. Cheers, Anders -- --- Anders Gidenstam mail: anders(at)gidenstam.org WWW: http://www.gidenstam.org/FlightGear/JSBSim-LTA/ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [RFC] c172x ... fix or kill?
* Jon S. Berndt -- Saturday 10 November 2007: The C172x is an experimental model for use with JSBSim by itself. It's the aircraft model I use to test all the new features. The funny thing is, after I removed the reference to the non-existent file ... --- c172x-set.xml 20 Sep 2003 03:57:13 - 1.1 +++ c172x-set.xml 10 Nov 2007 14:28:00 - @@ -10 +10 @@ Started October 23 2001 by John Check, f -PropertyList include=../c172r/c172r-base.xml +PropertyList ... JSBSim *segfaults*. Still want to keep it? :-} m. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] New aircraft for CVS - Pitts S1C
I wrote: From: Stuart Buchanan [EMAIL PROTECTED] To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Sent: Saturday, 10 November, 2007 1:56:40 PM Subject: Re: [Flightgear-devel] New aircraft for CVS - Pitts S1C Melchior wrote: * Stuart Buchanan -- Saturday 10 November 2007: The included livery is for the well-known fictional beer company, Hmm ... I'm not sure if that's fictional enough. 20th Century Fox has already sued an Australian brewery for making Duff beer, although they aren't brewing beer themselves, obviously. They are quite greedy and sue-happy, I think. How's that different from using airline liveries? As long as we are depicting real aircraft that's IMHO like painting a picture or making a photo and giving it away, which is perfectly legal. And airlines don't lose anything from it. On the contrary. It's free advertisement. Personally, I don't have anything against the livery. But I don't want to be the one who commits it and is responsible for it being in CVS. I won't complain if someone else commits. :-) OK. Better safe than sorry, I guess. I'll update the livery to something more fictional. New version with FlightGear livery (well, we might as wel advertise ourselves) available from: http://www.nanjika.co.uk/flightgear/pittss1c.tar.gz -Stuart ___ Yahoo! Answers - Got a question? Someone out there knows the answer. Try it now. http://uk.answers.yahoo.com/ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Minor keyboard reassignment
On Sat, 10 Nov 2007 10:59:58 +0100 Melchior FRANZ [EMAIL PROTECTED] wrote: l ... lights (though most are operated via 3D cockpit switches!) L ... tail wheel lock Ctrl-l ... liveries (l for liveries is a bit exaggerated, anyway) m. Im not sure what you mean by exaggerated , but its temporary anyway , until someone adds a sim/model/texture property , that is... If that gets implemented I'd like to add a livery dialogue to the help section , (without keypress to save keys ) , and I dont like the current popup dialog method ... we shouldn't need a separate folder just to enable livery changes thats MY 2 cents worth ;) Cheers -- SydSandy [EMAIL PROTECTED] - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: data keyboard.xml, 1.99, 1.100
On sam 10 novembre 2007, David Megginson wrote: Update of /var/cvs/FlightGear-0.9/data In directory baron:/tmp/cvs-serv32383 Modified Files: keyboard.xml Log Message: Reassign tail-wheel locking from 'l' to 'L' (previously unused), and use 'l' to toggle lighting. Index: keyboard.xml === RCS file: /var/cvs/FlightGear-0.9/data/keyboard.xml,v retrieving revision 1.99 retrieving revision 1.100 diff -C 2 -r1.99 -r1.100 *** keyboard.xml 1 Aug 2007 08:20:21 - 1.99 --- keyboard.xml 10 Nov 2007 01:30:04 - 1.100 *** *** 625,628 --- 625,637 /key + key n=76 + nameL/name + descToggle tail-wheel lock./desc + binding +commandproperty-toggle/command +property/controls/gear/tailwheel-lock/property + /binding + /key + key n=77 nameM/name *** *** 856,863 key n=108 namel/name ! descToggle tail-wheel lock./desc binding !commandproperty-toggle/command !property/controls/gear/tailwheel-lock/property /binding /key --- 865,872 key n=108 namel/name ! descTurn on aircraft panel lighting./desc binding !commandnasal/command !scriptcontrols.toggleLights()/script /binding /key I can notice the update has been done , before we could give any opinion on the topic. Does it mean , that there is not any other alternative, and the CHOICE is that way nothing else :) :) :) Regards -- Gérard http://pagesperso-orange.fr/GRTux/ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [RFC] c172x ... fix or kill?
* Jon S. Berndt -- Saturday 10 November 2007: The C172x is an experimental model for use with JSBSim by itself. It's the aircraft model I use to test all the new features. It should not be released. That only explains why it is in JSBSim's CVS. It does not explain why it should be in FGFS' CVS. It includes a non existent file and is broken. Again: does anyone intend to *FIX* it? Otherwise it should be removed. m. I think you missed my point. I was stating that I believe it should be removed from FlightGear CVS. It shouldn't have been there in the first place. Some features from the C172x migrate to the other C172 models, which is fine, but again the c172x is not for prime time. It doesn't really represent a real aircraft, as far as I am concerned. Jon - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [RFC] c172x ... fix or kill?
* Jon S. Berndt -- Saturday 10 November 2007: * Jon S. Berndt -- Saturday 10 November 2007: The C172x is an experimental model [...] It should not be released. I think you missed my point. I was stating that I believe it should be removed from FlightGear CVS. It shouldn't have been there in the first place. Oh, sorry. I didn't consider moving files from JSBSim/CVS to fgfs/CVS a release, and even less so on the fgfs mailing list (where we desperately wait for a release since ... a year? :-) Erik routinely merges JSBSim code into our CVS, and this was never seen as a release. So I thought you defended the c172x' presence in fgfs/CVS and only meant it shouldn't be released with fgfs. Some features from the C172x migrate to the other C172 models, which is fine, but again the c172x is not for prime time. It doesn't really represent a real aircraft, as far as I am concerned. OK. Yes, the c172x dir in our CVS looks like an empty shell, unmaintained since years, broken since years. The c172x-set.xml is almost empty, etc. I'm not quick with removing stuff. I even kept as350 for now, although Maik wanted to get rid of it. But I'll remove the c172x, then. Thanks for clearing this up. :-) m. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: data keyboard.xml, 1.99, 1.100
On 10/11/2007, gerard robin [EMAIL PROTECTED] wrote: I can notice the update has been done , before we could give any opinion on the topic. Does it mean , that there is not any other alternative, and the CHOICE is that way nothing else :) :) :) From my original message: quote I just moved tailwheel-lock from lowercase 'l' to uppercase 'L', and reassigned lowercase 'l' to toggle lighting (for easy night starts without searching for switches). I assigned lighting to the lowercase 'l' because I think it would be much more commonly used than tailwheel lock, but if there are general objections (from DC-3 users?) I can swap the two around so that tailwheel lock goes back to 'l'. Let me know what you think. /quote I or anyone else with access can change it again once there's a consensus -- remember that CVS is the experimentation branch, not the release branch. All the best, David - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: data keyboard.xml, 1.99, 1.100
On sam 10 novembre 2007, David Megginson wrote: On 10/11/2007, gerard robin [EMAIL PROTECTED] wrote: I can notice the update has been done , before we could give any opinion on the topic. Does it mean , that there is not any other alternative, and the CHOICE is that way nothing else :) :) :) From my original message: quote I just moved tailwheel-lock from lowercase 'l' to uppercase 'L', and reassigned lowercase 'l' to toggle lighting (for easy night starts without searching for switches). I assigned lighting to the lowercase 'l' because I think it would be much more commonly used than tailwheel lock, but if there are general objections (from DC-3 users?) I can swap the two around so that tailwheel lock goes back to 'l'. Let me know what you think. /quote I or anyone else with access can change it again once there's a consensus -- remember that CVS is the experimentation branch, not the release branch. All the best, David Oh, i am only like the dog which try to catch his tail. Since we had the 'L used with carrier , (this was talked before), i only wonder if it would not have been better to find a global agreement on which key can do what, before to make that update. There is some aircraft within CVS which are carrier compatible. With that update the launchbar will not work now. Regards -- Gérard http://pagesperso-orange.fr/GRTux/ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: data keyboard.xml, 1.99, 1.100
gerard robin Sent: 10 November 2007 18:37 To: FlightGear developers discussions Subject: Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: data keyboard.xml,1.99, 1.100 On sam 10 novembre 2007, David Megginson wrote: On 10/11/2007, gerard robin [EMAIL PROTECTED] wrote: I can notice the update has been done , before we could give any opinion on the topic. Does it mean , that there is not any other alternative, and the CHOICE is that way nothing else :) :) :) From my original message: quote I just moved tailwheel-lock from lowercase 'l' to uppercase 'L', and reassigned lowercase 'l' to toggle lighting (for easy night starts without searching for switches). I assigned lighting to the lowercase 'l' because I think it would be much more commonly used than tailwheel lock, but if there are general objections (from DC-3 users?) I can swap the two around so that tailwheel lock goes back to 'l'. Let me know what you think. /quote I or anyone else with access can change it again once there's a consensus -- remember that CVS is the experimentation branch, not the release branch. All the best, David Oh, i am only like the dog which try to catch his tail. Since we had the 'L used with carrier , (this was talked before), i only wonder if it would not have been better to find a global agreement on which key can do what, before to make that update. There is some aircraft within CVS which are carrier compatible. With that update the launchbar will not work now. Should be OK, the carrier bindings will over-write the keyboard bindings. It will be a problem if there is an aircraft with both tail wheel lock _and_ carrier launch bar (F4U?) I haven't checked that. And perhaps we can come up with a long term solution. I'm sure Melchior's little grey cells are working overtime. Still, perhaps we shouldn't be making changes until we are clearer about the consequences. Vivian - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Minor keyboard reassignment
David Megginson wrote: Switches are hard to find, especially (a) if you're not a real pilot, or (b) if you're not familiar with the aircraft. A single key to turn on all the lights can be very useful for a new user, or even for an experienced user who just wants to fly at night and doesn't know the aircraft or doesn't want to pan around the panel. snip So, in summary, I think a single switch to turn on all required interior and exterior lights for night flying can be a big win for FlightGear. Hi Dave, I just looked at the changes in cvs. There is a significant problem with at least this implementation of one key to turn on all the lights for all AC. There is no standard followed for how to implement nasal electrical systems. The patches you made to cvs will accomplish your stated goal for the pa24 and pa28, but not for the SenecaII or the dhc2. This is because when I wrote electrical.nas for the pa28, I started from the eleictrical.nas for the pa24. Some of the nasal electrical systems bypass switches all together and toggle properties such as /electrical/landinglights. Others include functional circuit breakers that would need to be verified. A second observation is that I virtually never turn on the white cabin light or the map light because I don't want to ruin my night vision. So even for the pa24, I would not want to have all the light on for most flights. For both the pa24 and the pa28, the keys assigned to toggle the switches are in the same order on the keyboard as in the AC. This was to make it easier to quickly turn on or off the switches you want w/o moving the mouse or view. Also, the Help Aircraft Help menu for the pa24 or pa28 gives complete switch info and starting procedure. What frustrates me with some AC is that I am left in the cockpit with no hot spots and also no help to allow me to find the magneto switch(es) or fuel valve. My vote would be to require either (1) hot start with engine running and all normal things turned on, or (2) a clearly written Help Aircraft Help that gets you started with what you need to be ready to take-off. Regards, Dave Perry - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Minor keyboard reassignment
On 10/11/2007, dave perry [EMAIL PROTECTED] wrote: I just looked at the changes in cvs. There is a significant problem with at least this implementation of one key to turn on all the lights for all AC. There is no standard followed for how to implement nasal electrical systems. The patches you made to cvs will accomplish your stated goal for the pa24 and pa28, but not for the SenecaII or the dhc2. This is because when I wrote electrical.nas for the pa28, I started from the eleictrical.nas for the pa24. Some of the nasal electrical systems bypass switches all together and toggle properties such as /electrical/landinglights. Others include functional circuit breakers that would need to be verified. This sounds like a pretty big problem beyond just my patch. Nasal has been great for letting people add functionality to FlightGear, but it causes a lot of problems for the property system, especially when people use different property names, override stuff, etc. It might be time for a refactoring pass through some of the models. A second observation is that I virtually never turn on the white cabin light or the map light because I don't want to ruin my night vision. So even for the pa24, I would not want to have all the light on for most flights. I know -- I don't turn them on either -- but I put them in just for completeness for now. I have no problem pulling them out, once we agree on a common subset (and fix some of the property inconsistencies). All the best, David - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] [ANN] - Buccaneer - Back seat ride
Hi, Tonight we carried out our first ride in the backseat of a Buccaneer over MP, thanks to some excellent recent work by Melchior and Anders. AJ was the intrepid Observer/passenger, and reported himself well pleased with the experience. To try it you need the Pilot and Observer on MP in the Buccaneer, and then the Observer selects the Model Cockpit View (V/v), then cycles through the cockpit views (Q/q) until he reaches the back seat of the Buccaneer. That's it - the Pilot can then fly with his Observer aboard. Sick bag might be necessary :-). Only available in cvs, of course, and there's much work to be done to both generalise this to all mp aircraft, and to provide the appropriate facilities and connectivity in the backseat so that the Observer can be more than just a passenger. AJ was navigating using the MPMap, so that's a start. Anders is hard at work extending this into a co-pilot facility - watch this space. Meanwhile - if you are on MP we're aboard and watching you :-). Regards Vivian - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [ANN] - Buccaneer - Back seat ride
I wrote: -Original Message- From: Vivian Meazza [mailto:[EMAIL PROTECTED] Sent: 10 November 2007 23:20 To: 'FlightGear developers discussions' Subject: [ANN] - Buccaneer - Back seat ride Hi, Tonight we carried out our first ride in the backseat of a Buccaneer over MP, thanks to some excellent recent work by Melchior and Anders. AJ was the intrepid Observer/passenger, and reported himself well pleased with the experience. To try it you need the Pilot and Observer on MP in the Buccaneer, and then the Observer selects the Model Cockpit View (V/v), then cycles through the cockpit views (Q/q) until he reaches the back seat of the Buccaneer. That's it - the Pilot can then fly with his Observer aboard. Sick bag might be necessary :-). Only available in cvs, of course, and there's much work to be done to both generalise this to all mp aircraft, and to provide the appropriate facilities and connectivity in the backseat so that the Observer can be more than just a passenger. AJ was navigating using the MPMap, so that's a start. Anders is hard at work extending this into a co-pilot facility - watch this space. Meanwhile - if you are on MP we're aboard and watching you :-). Regards Vivian P.S. Clipping plane problems mean that this only works properly in OSG. We can probably fix it quite quickly in plib, but haven't thought through the consequences yet. V. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [ANN] - Buccaneer - Back seat ride
On Saturday 10 November 2007 23:20, Vivian Meazza wrote: Hi, Tonight we carried out our first ride in the backseat of a Buccaneer over MP, thanks to some excellent recent work by Melchior and Anders. AJ was the intrepid Observer/passenger, and reported himself well pleased with the experience. To try it you need the Pilot and Observer on MP in the Buccaneer, and then the Observer selects the Model Cockpit View (V/v), then cycles through the cockpit views (Q/q) until he reaches the back seat of the Buccaneer. That's it - the Pilot can then fly with his Observer aboard. Sick bag might be necessary :-). Only available in cvs, of course, and there's much work to be done to both generalise this to all mp aircraft, and to provide the appropriate facilities and connectivity in the backseat so that the Observer can be more than just a passenger. AJ was navigating using the MPMap, so that's a start. Anders is hard at work extending this into a co-pilot facility - watch this space. Meanwhile - if you are on MP we're aboard and watching you :-). Regards Vivian Nice work:) LeeE - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Weekly CVS Changelog Summary: SimGear
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-11-08_23:52:58 (frohlich) /var/cvs/SimGear-0.3/source/simgear/scene/util/SGNodeMasks.hxx Update node masks 2f585eeea02e2c79d7b1d8c4963bae2d - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Weekly CVS Changelog Summary: FlightGear source
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-11-05_16:12:01 (mfranz) /var/cvs/FlightGear-0.9/source/src/Main/viewer.cxx revert swapping of x y offsets in lookat mode This was correct in the old repository and in revision 1.1 of the new, but then broken in revision 1.2. After that, lookat and lookfrom mode used different coordinate systems, and the Adjust View Distance didn't work correctly in lookat mode. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-11-06_06:01:11 (mfranz) /var/cvs/FlightGear-0.9/source/src/Main/main.cxx change update order to fdm - events - viewmanager This removes some jitter in cases where Nasal is used to set up view parameters from FDM data, such as position and orientation. (The event subsystem handles Nasal's settimer() calls.) =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-11-06_15:07:02 (mfranz) /var/cvs/FlightGear-0.9/source/src/Main/main.cxx move event_mgr and view_mgr bundle right before the requestRedraw() This fixes the last jitter problems with views attached to MP/AI objects, and doesn't seem to cause any new ones. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-11-07_09:52:28 (mfranz) /var/cvs/FlightGear-0.9/source/src/Main/main.cxx mainloop: move event_mgr and viewmgr updated before spatial sound calculations =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-11-07_11:43:39 (mfranz) /var/cvs/FlightGear-0.9/source/src/Network/native_fdm.cxx don't overwrite rudder position with nose wheel position =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-11-09_06:45:23 (mfranz) /var/cvs/FlightGear-0.9/source/src/AIModel/AIAircraft.cxx /var/cvs/FlightGear-0.9/source/src/AIModel/AIAircraft.hxx /var/cvs/FlightGear-0.9/source/src/AIModel/AIBase.cxx /var/cvs/FlightGear-0.9/source/src/AIModel/AIBase.hxx /var/cvs/FlightGear-0.9/source/src/AIModel/AIMultiplayer.cxx /var/cvs/FlightGear-0.9/source/src/AIModel/AIMultiplayer.hxx backport callsign handling from fg/osg, so that traffic manager aircraft show up with proper callsign =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-11-09_11:39:43 (mfranz) /var/cvs/FlightGear-0.9/source/src/Main/viewmgr.cxx also copy name type to /sim/current-view That's useful for animations, and we can't rely on numbers. And shouldn't. 2f585eeea02e2c79d7b1d8c4963bae2d - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
