Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: data keyboard.xml, 1.99, 1.100
Hello Vivian, Am Samstag, den 10.11.2007, 19:37 + schrieb Vivian Meazza: 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. The F4U-1 doesn't use the launchbar. It toggles the Tailwheel lock by Ctrl-L, so l for lighting, L for Launchbar and Ctrl-l for Tailwheel lock would work. However I would follow every agreement on key usage. 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 Greetings Detlef - 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] Minor keyboard reassignment
* SydSandy -- Saturday 10 November 2007: Melchior FRANZ [EMAIL PROTECTED] wrote: Ctrl-l ... liveries (l for liveries is a bit exaggerated, anyway) Im not sure what you mean by exaggerated , Keys that don't require you to also press a modifier key are (very obviously) easier to access than key combinations. And a livery change is the last thing where we need quick and easy access. This could be on one of the F[0-9]* keys, or even a menu only function. 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] Weekly CVS Changelog Summary: FlightGear data
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-11-04_01:02:17 (sydadams) /var/cvs/FlightGear-0.9/data/Aircraft/R22/R22-sound.xml /var/cvs/FlightGear-0.9/data/Aircraft/R22/Nasal/R22.nas Added fuel consumption and low fuel annunciator... Added audible warning (rpm less than 95%) =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-11-04_01:03:13 (sydadams) /var/cvs/FlightGear-0.9/data/Sounds/beep.wav *** empty log message *** =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-11-04_08:04:09 (gerard) /var/cvs/FlightGear-0.9/data/Aircraft/P-38-Lightning/F-5B-set.xml Global update, mostly model reorganisation, and nasal script bug solved =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-11-04_08:04:10 (gerard) /var/cvs/FlightGear-0.9/data/Aircraft/P-38-Lightning/P38-SetBase.xml /var/cvs/FlightGear-0.9/data/Aircraft/P-38-Lightning/README-FIRST /var/cvs/FlightGear-0.9/data/Aircraft/P-38-Lightning/Models/P38-base-model.xml /var/cvs/FlightGear-0.9/data/Aircraft/P-38-Lightning/Models/Propellers/P38_CasserolleHelice.xml /var/cvs/FlightGear-0.9/data/Aircraft/P-38-Lightning/Models/Propellers/P38_CasserollePropdisk.xml /var/cvs/FlightGear-0.9/data/Aircraft/P-38-Lightning/Models/Propellers/P38_Propdisk.xml /var/cvs/FlightGear-0.9/data/Aircraft/P-38-Lightning/System/crash.nas /var/cvs/FlightGear-0.9/data/Aircraft/P-38-Lightning/System/nav.nas Global update, mostly model reorganisation, and nasal script bug solved =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-11-04_08:28:41 (gerard) /var/cvs/FlightGear-0.9/data/Aircraft/P-38-Lightning/LIS-MOI_GNU-GPL added terrain detection =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-11-04_08:28:42 (gerard) /var/cvs/FlightGear-0.9/data/Aircraft/P-38-Lightning/Models/Propellers/casserolle-fr.rgb /var/cvs/FlightGear-0.9/data/Aircraft/P-38-Lightning/Models/Propellers/p38-prop1.rgb added terrain detection =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-11-04_08:28:43 (gerard) /var/cvs/FlightGear-0.9/data/Aircraft/P-38-Lightning/System/terrain.nas added terrain detection =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-11-04_08:39:16 (gerard) /var/cvs/FlightGear-0.9/data/Aircraft/Noratlas/LIS-MOI_GNU-GPL /var/cvs/FlightGear-0.9/data/Aircraft/Noratlas/N2501-set.xml /var/cvs/FlightGear-0.9/data/Aircraft/Noratlas/Noratlas-SetBase.xml /var/cvs/FlightGear-0.9/data/Aircraft/Noratlas/Nord-2501-splash.rgb The 2501 variant is added, the detection terrain type is included in the FDM =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-11-04_08:39:17 (gerard) /var/cvs/FlightGear-0.9/data/Aircraft/Noratlas/README-FIRST /var/cvs/FlightGear-0.9/data/Aircraft/Noratlas/n2501.xml The 2501 variant is added, the detection terrain type is included in the FDM =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-11-04_08:39:18 (gerard) /var/cvs/FlightGear-0.9/data/Aircraft/Noratlas/Help/Nord-2501-help.xml /var/cvs/FlightGear-0.9/data/Aircraft/Noratlas/Help/Nord-2502-help.xml The 2501 variant is added, the detection terrain type is included in the FDM =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-11-04_08:39:19 (gerard) /var/cvs/FlightGear-0.9/data/Aircraft/Noratlas/Instruments/Models/ai-pby.ac /var/cvs/FlightGear-0.9/data/Aircraft/Noratlas/Models/Lumiere.xml /var/cvs/FlightGear-0.9/data/Aircraft/Noratlas/Models/N2501_Base.xml /var/cvs/FlightGear-0.9/data/Aircraft/Noratlas/Models/N2502_Base.xml /var/cvs/FlightGear-0.9/data/Aircraft/Noratlas/Models/Noratlas-base-model.xml The 2501 variant is added, the detection terrain type is included in the FDM =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-11-04_08:39:21 (gerard) /var/cvs/FlightGear-0.9/data/Aircraft/Noratlas/Models/Noratlas_DCasserolle.xml /var/cvs/FlightGear-0.9/data/Aircraft/Noratlas/Models/Noratlas_DHelice.xml /var/cvs/FlightGear-0.9/data/Aircraft/Noratlas/Models/Noratlas_DPropdisk.xml /var/cvs/FlightGear-0.9/data/Aircraft/Noratlas/Models/Noratlas_GCasserolle.xml /var/cvs/FlightGear-0.9/data/Aircraft/Noratlas/Models/Noratlas_GHelice.xml /var/cvs/FlightGear-0.9/data/Aircraft/Noratlas/Models/Noratlas_GPropdisk.xml /var/cvs/FlightGear-0.9/data/Aircraft/Noratlas/Models/Noratlas_Pilote.xml The 2501 variant is added, the detection terrain type is included in the FDM =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-11-04_08:39:22 (gerard) /var/cvs/FlightGear-0.9/data/Aircraft/Noratlas/Models/Nord-2501-model.xml /var/cvs/FlightGear-0.9/data/Aircraft/Noratlas/Models/Nord-2501_Cockpit.xml /var/cvs/FlightGear-0.9/data/Aircraft/Noratlas/Models/Nord-2502_DHelice_mod.xml /var/cvs/FlightGear-0.9/data/Aircraft/Noratlas/Models/Nord-2502_GHelice_mod.xml /var/cvs/FlightGear-0.9/data/Aircraft/Noratlas/Models/lumiere.ac /var/cvs/FlightGear-0.9/data/Aircraft/Noratlas/Models/noratlas-casserolle.ac
Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: data keyboard.xml, 1.99, 1.100
On sam 10 novembre 2007, Vivian Meazza wrote: 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 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 I did not check it , but your Seafire has both Launchbar and tailwheel lock, What is the matter now with the keyboard updated ? Regard -- 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: 11 November 2007 13:18 To: FlightGear developers discussions Subject: Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: data keyboard.xml,1.99, 1.100 On sam 10 novembre 2007, Vivian Meazza wrote: 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 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 I did not check it , but your Seafire has both Launchbar and tailwheel lock, What is the matter now with the keyboard updated ? Regard Not really, later on in the YASim config, it's ignored. 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] [Flightgear-cvslogs] CVS: data keyboard.xml, 1.99, 1.100
On dim 11 novembre 2007, Vivian Meazza wrote: gerard robin Sent: 11 November 2007 13:18 To: FlightGear developers discussions Subject: Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: data keyboard.xml,1.99, 1.100 On sam 10 novembre 2007, Vivian Meazza wrote: 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 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 I did not check it , but your Seafire has both Launchbar and tailwheel lock, What is the matter now with the keyboard updated ? Regard Not really, later on in the YASim config, it's ignored. Vivian Oh, right, thanks. So the nice way, mainly for carrier is to ignore the keyboard.xml , and to create some specific key dedicated to the Aircraft. My apologizes (mainly to David) for that noise which came first from me. In that case the L l could be used for any other features: = light , livery and so on. 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
While you are re-assigning keys, can I suggest that we remove t/T for the time-warp and reassign that to either a ctrl combo or a menu item. It doesnt strike me that this is a function thats needed in a hurry like a flight control or switch. Possibly ''t and its friends could get re-assigned to turbine start/shutdown? Its not the first time Ive screwed up a long flight by accidentally hitting 't' and getting thoroughly confused. A standard keyboard assignment for carb heat would be useful too (and much more relevant for myself and Im guessing 90+% of the users who actually get to fly real aircraft) and add greatly to the realism. I know there are aircraft where we have a clickable hot-spot for the carb heat but its usually difficult to find and a hassle. Carb heat should be like backups -- make it easy and folk will do it - forget about it and you will have big trouble sooner or later. --- Best Regards Willie Fleming [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] New aircraft for CVS - Pitts S1C
Hi Stuart, nice aircraft. One comment regarding the fdm: The aerotow hook is missing. Maik Stuart Buchanan schrieb am 10.11.2007 18:12: 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 - 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
Willie Fleming schrieb: While you are re-assigning keys, can I suggest that we remove t/T for the time-warp and reassign that to either a ctrl combo or a menu item. It doesnt strike me that this is a function thats needed in a hurry like a flight control or switch. Possibly ''t and its friends could get re-assigned to turbine start/shutdown? Its not the first time Ive screwed up a long flight by accidentally hitting 't' and getting thoroughly confused. Yes, Willie, I can only agree as the accidentally time-warping by blind-typing on the keyboard (and missing ..) was a nuisance for me several times. And to be honest, I do not know until now how to set it to the normal value back with one keystroke. So I always had to cancel the flight. This dangerous key assignment should be changed for some more beneficial for daily use. Georg EDDW - 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] Bug in SGBinObject write_bin() function?
Hi,
I am trying to understand the SGBinObject binary format (BTG files) and for
this purpose I wrote a short test program to load a file and save it back to
disk.
SGBinObject source;
bool result = source.read_bin
(S:\\scenery\\Terrain\\w090n30\\w087n39\\1532019.btg);
if (result == true)
{
SGBucket bucket(SGGeod::fromCart(SGVec3double(
source.get_gbs_center2().sg(;
source.write_bin(C:\\, test.btg, bucket);
}
This code loads the largest (non-airport) BTG file from the World scenery
disk 1 (mounted on drive S: on Windows) and tries to save it back.
The program crashes in line 1015 of sg_binobj.cxx trying to access the
member variable fans_n[i][j] with a vector subscript out of range debug
error inside the STL vector class.
I was kind of wondering if my use of write_bin is incorrect, or if there is
a serious bug in the write_bin() implementation. Maybe this function is used
so seldom that no-one noticed so far?
I was trying this on Windows based on the CVS/HEAD SimGear release under
Visual C++ 2005 Express Edition. The flightgear binary produced with this
compiler works just fine.
My mid term goal is to come up with a more efficiently compressed binary
format to save some disk space and possible squeeze the world scenery on two
DVDs or less. I plan to achieve this goal by using some quantization and
entropy coding. It might also be possible to obtain some LOD support by
encoding the mesh progressively (i.e. from coarse to full precision) and by
specifying a cutoff point during read_bin()
-
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
Maik Justus wrote: Hi Stuart, nice aircraft. One comment regarding the fdm: The aerotow hook is missing. I didn't add the aerotow hook because I'm pretty sure no-one would try to tow a glider with a Pitts, and it's enough trouble trying to handle on its own, without the challenge of a glider as well! That said, I know there are currently a very limited number of aircraft that are useful for aero-towing, so if you want to re-add it, go ahead. Or maybe we need to convince someone to create a proper YASim tug... -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
* Georg Vollnhals -- Sunday 11 November 2007: I can only agree as the accidentally time-warping by blind-typing on the keyboard (and missing ..) was a nuisance for me several times. And to be honest, I do not know until now how to set it to the normal value back with one keystroke. Just press the t-key longer than a second. :-) And before someone complains that this isn't documented: It was only a little test to see if such time-dependent key presses could be useful for some things. You can also call it an Easter egg, if you want. 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
So much as I know, there are some clubs using a Pitts for aerotowing. Regards HHS --- Stuart Buchanan [EMAIL PROTECTED] schrieb: Maik Justus wrote: Hi Stuart, nice aircraft. One comment regarding the fdm: The aerotow hook is missing. I didn't add the aerotow hook because I'm pretty sure no-one would try to tow a glider with a Pitts, and it's enough trouble trying to handle on its own, without the challenge of a glider as well! That said, I know there are currently a very limited number of aircraft that are useful for aero-towing, so if you want to re-add it, go ahead. Or maybe we need to convince someone to create a proper YASim tug... -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 Heute schon einen Blick in die Zukunft von E-Mails wagen? Versuchen Sie´s mit dem neuen Yahoo! Mail. www.yahoo.de/mail - 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 schrieb: * Georg Vollnhals -- Sunday 11 November 2007: I can only agree as the accidentally time-warping by blind-typing on the keyboard (and missing ..) was a nuisance for me several times. And to be honest, I do not know until now how to set it to the normal value back with one keystroke. Just press the t-key longer than a second. :-) And before someone complains that this isn't documented: It was only a little test to see if such time-dependent key presses could be useful for some things. You can also call it an Easter egg, if you want. m. Thank you for this clarification which can save my day sometime in the future but thinking of many other users not reading this list it could be a good idea to hide the time-warping function a little more. Georg - 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 -- Sunday 11 November 2007: Just press the t-key longer than a second. :-) That doesn't mean that I want to keep warp on the t-key. I also find that these unrealistic development functions shouldn't waste the good keys. I also find that the r (replay) key is much too exposed. But traditionally, discussions about the keyboard layout are only about where people *don't* want certain keys, not *where* they want them instead, and therefore aren't very productive. So, traditionally, everything remains the same afterwards. ;-) 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
Heiko Schulz wrote: So much as I know, there are some clubs using a Pitts for aerotowing. I didn't know that - but know knowledge of glider towing is limited to the small number of clubs around our airfield. Thanks for pointing it out. I'm glad there is another use for the Pitts! Maik - please go ahead and add aerotow if you have time/inclination. I've just about used up my FlightGear dev time for the month ;) Heiko: Any chance you could reply to the _bottom_ of posts rather than the _top_? As someone once said: A: Because it makes the reply difficult to understand Q: Why is top-posting bad? Thanks. -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] Minor keyboard reassignment
On Sun, 11 Nov 2007 11:06:42 +0100 Melchior FRANZ [EMAIL PROTECTED] wrote: * SydSandy -- Saturday 10 November 2007: Melchior FRANZ [EMAIL PROTECTED] wrote: Ctrl-l ... liveries (l for liveries is a bit exaggerated, anyway) Im not sure what you mean by exaggerated , Keys that don't require you to also press a modifier key are (very obviously) easier to access than key combinations. And a livery change is the last thing where we need quick and easy access. This could be on one of the F[0-9]* keys, or even a menu only function. m. ok , I understand now . It was mainly meant for testing ... I tried to use the material animation based on a /sim/model/variant condition , but that only works once , in one direction , that is , liveries will change until you toggle the last one , then that's where it stays . I'm guessing tthats because of the material animations limitation on changing the same object(s) more than once ... But I'm still working on it (and lets face it , its easier to get a response when I screw things up, rather than ask a question ;) ) 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] Minor keyboard reassignment
On Sun, 11 Nov 2007 19:06:14 +0100 Georg Vollnhals [EMAIL PROTECTED] wrote: Melchior FRANZ schrieb: * Georg Vollnhals -- Sunday 11 November 2007: I can only agree as the accidentally time-warping by blind-typing on the keyboard (and missing ..) was a nuisance for me several times. And to be honest, I do not know until now how to set it to the normal value back with one keystroke. Just press the t-key longer than a second. :-) And before someone complains that this isn't documented: It was only a little test to see if such time-dependent key presses could be useful for some things. You can also call it an Easter egg, if you want. m. Thank you for this clarification which can save my day sometime in the future but thinking of many other users not reading this list it could be a good idea to hide the time-warping function a little more. Georg Just here to add my vote I've done the accidental time warp too , very confusing if you hit it once and dont have a clock installed yet :) .I agree that it should be moved out of the way ... or removed completely , since you can set the time of day on the commandline or FGrun ... 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
[Flightgear-devel] [Fwd: Re: Minor keyboard reassignment]
Original-Nachricht Betreff:Re: [Flightgear-devel] Minor keyboard reassignment Datum: Sun, 11 Nov 2007 19:54:34 +0100 Von:Georg Vollnhals [EMAIL PROTECTED] An: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Referenzen: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Melchior FRANZ schrieb: * Melchior FRANZ -- Sunday 11 November 2007: Just press the t-key longer than a second. :-) That doesn't mean that I want to keep warp on the t-key. I also find that these unrealistic development functions shouldn't waste the good keys. I also find that the r (replay) key is much too exposed. But traditionally, discussions about the keyboard layout are only about where people *don't* want certain keys, not *where* they want them instead, and therefore aren't very productive. So, traditionally, everything remains the same afterwards. ;-) m. Would be bad for the time-warping. Just some thoughts after looking into some FG files: I am used - to be honest from my old Win$ times - to have the extraordinary functions on a combination together with the ALT key. But I doubt that this is possible for FlightGear as looking into the keyboard.xml and freeglut_std.h there are only definitions for the function, arrow and page keys as special keys. I assume that some O/S don't know the ALT key? Or combinations like CTRL+SHIFT + keyvalue? Could it be a solution to have several seldom used function on ONE key - together with a switching menu entry in the developer key menu part. So that ie the * is either used for timewarping or ... or ... dependant on the menu selection? Just to mention, the more functions you get in a sim, the more complicated it is to have a standard key table. I always liked the possibility of the old FLY! sim to (re-) assign your own keys to functions. Every simmer has his own likings due to his use of the flightsim. But this means that not pure keyvalues are handled within the sim but messages independant from the keyboard use. As I am not a FG coder I don't know how it is handled in our sim. But this would solve a lot of problems. Regards Georg - 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 [EMAIL PROTECTED] schrieb: Heiko: Any chance you could reply to the _bottom_ of posts rather than the _top_? As someone once said: A: Because it makes the reply difficult to understand Q: Why is top-posting bad? Thanks. -Stuart Yes, I can. But I find this more difficult to read. Sometimes I'm lost between qoutes and anwsers of other postings here... __ Ihr erstes Baby? Holen Sie sich Tipps von anderen Eltern. www.yahoo.de/clever - 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 Sunday 11 November 2007 18:07:24 Melchior FRANZ wrote: * Melchior FRANZ -- Sunday 11 November 2007: Just press the t-key longer than a second. :-) That doesn't mean that I want to keep warp on the t-key. I also find that these unrealistic development functions shouldn't waste the good keys. I also find that the r (replay) key is much too exposed. But traditionally, discussions about the keyboard layout are only about where people *don't* want certain keys, not *where* they want them instead, and therefore aren't very productive. So, traditionally, everything remains the same afterwards. ;-) OK I _WANT_ turbine start/shutdown assigned to t/T and carb heat assigned to 'h' toggle heat on/off and I _WANT_ time warp reassigned to a menu item :-) Reasoning behind the toggle - for proper use of the carb heat you want to have it on for 30-60 secs in the cruise and on anytime the throttle is less than 50% open. At least thats the way its taught at our club and we haven't lost an aircraft to carb icing since this rule was introduced. Please don't ask what happened before this rule was brought in Anybody else with me on this? --- Best Regards Willie Fleming [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] Minor keyboard reassignment
Willie Fleming schrieb: OK I _WANT_ turbine start/shutdown assigned to t/T and carb heat assigned to 'h' toggle heat on/off and I _WANT_ time warp reassigned to a menu item :-) Reasoning behind the toggle - for proper use of the carb heat you want to have it on for 30-60 secs in the cruise and on anytime the throttle is less than 50% open. At least thats the way its taught at our club and we haven't lost an aircraft to carb icing since this rule was introduced. Please don't ask what happened before this rule was brought in Anybody else with me on this? My vote for it Georg --- Best Regards Willie Fleming - 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
Hi, Stuart Buchanan schrieb am 11.11.2007 19:17: Heiko Schulz wrote: So much as I know, there are some clubs using a Pitts for aerotowing. Yes, I am sure I saw it myself. I didn't know that - but know knowledge of glider towing is limited to the small number of clubs around our airfield. Thanks for pointing it out. I'm glad there is another use for the Pitts! Maik - please go ahead and add aerotow if you have time/inclination. I've just about used up my FlightGear dev time for the month ;) Please find enclosed a diff. (I am not sure about the correct position of the hitch) . Maik ? pittss1c.diff Index: pittss1c-set.xml === RCS file: /var/cvs/FlightGear-0.9/data/Aircraft/pittss1c/pittss1c-set.xml,v retrieving revision 1.1 diff -u -p -r1.1 pittss1c-set.xml --- pittss1c-set.xml10 Nov 2007 17:18:47 - 1.1 +++ pittss1c-set.xml11 Nov 2007 19:12:15 - @@ -45,6 +45,14 @@ model, instrument panel, and external 3D help titlePitts S1C/title line/line + key + nameo/name + descconnect tow cable/desc + /key + key + nameO/name + descdisconnect tow cable/desc + /key lineAerobatic Biplane, with 180hp Lycoming O-360/line line/line lineStall: 57mph/line @@ -52,6 +60,30 @@ model, instrument panel, and external 3D lineVne: 203/line lineRate of climb: 2650fpm/line /help +hitches +!-- make sure some properties do exist, when the list for multiplayer transfere is defined-- +!-- they need to be in the same value, as they are initilized in the FDM, to get the same values after reset-- + aerotow +tow + length type=float60/length + elastic-constant type=float1/elastic-constant + weight-per-m-kg-m type=float1/weight-per-m-kg-m + dist type=float1/dist + connected-to-property-node type=bool/connected-to-property-node + brake-force type=float10/brake-force + connected-to-ai-or-mp-callsign type =string*/connected-to-ai-or-mp-callsign + end-force-x type =float0/end-force-x + end-force-y type =float0/end-force-y + end-force-z type =float0/end-force-z +/tow +speed-in-tow-direction type=float0/speed-in-tow-direction +open type=booltrue/open +local-pos-x type=float0/local-pos-x +local-pos-y type=float0/local-pos-y +local-pos-z type=float0/local-pos-z +is-slave type=boolfalse/is-slave + /aerotow +/hitches /sim yasim @@ -104,5 +136,27 @@ model, instrument panel, and external 3D pilot-gmin1.0/pilot-gmin pilot-gmax1.0/pilot-gmax /accelerations +input + keyboard +key n=79 + nameO/name + descOpen aerotow hook/desc + binding +commandproperty-assign/command +property/sim/hitches/aerotow/open/property +value type=booltrue/value + /binding +/key +key n=111 + nameo/name + descLock aerotow hook/desc + binding +commandproperty-assign/command +property/sim/hitches/aerotow/open/property +value type=boolfalse/value + /binding +/key + /keyboard +/input /PropertyList Index: pittss1c.xml === RCS file: /var/cvs/FlightGear-0.9/data/Aircraft/pittss1c/pittss1c.xml,v retrieving revision 1.1 diff -u -p -r1.1 pittss1c.xml --- pittss1c.xml10 Nov 2007 17:18:47 - 1.1 +++ pittss1c.xml11 Nov 2007 19:12:16 - @@ -113,4 +113,8 @@ YASim aerodynamic model for a Pitts S1C !-- pilot -- weight x=-2.4 y=0 z=-0.0 mass-prop=/yasim/pitts/pilot-lb/ + hitch name=aerotow x=-4.5 y=0 z=-0.3 force-is-calculated-by-other=1 +tow length=60 weight-per-meter=0.035 elastic-constant=9000 break-force=1 mp-auto-connect-period=1.0/ + /hitch + /airplane - 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 Nov 11, 2007 12:30 PM, Willie Fleming wrote: OK I _WANT_ turbine start/shutdown assigned to t/T and carb heat assigned to 'h' toggle heat on/off and I _WANT_ time warp reassigned to a menu item :-) I don't disagree with any of this, timewarp probably doesn't deserve it's own pair of keystrokes. However, blindly assigning it to a menu item might cause us to lose the ability to do any fine grain nudging of the time forward or back. Maybe I'm the only one that does that? But for whomever decides to reassign this functionality to a menu entry, I'd like to see maybe a dialog box where you can advance/rewind the time by 60 seconds, 5 minutes, 1 hour, etc. along with setting the time to specific periods of the day (noon, dusk, etc.) Perhaps even be able to manually enter a time offset (warp value) in seconds. Regards, Curt. -- Curtis Olson: http://baron.flightgear.org/~curt/ Unique text: 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
Re: [Flightgear-devel] Minor keyboard reassignment
On Sunday 11 November 2007 19:07, Melchior FRANZ wrote: * Melchior FRANZ -- Sunday 11 November 2007: Just press the t-key longer than a second. :-) That doesn't mean that I want to keep warp on the t-key. I also find that these unrealistic development functions shouldn't waste the good keys. I also find that the r (replay) key is much too exposed. But traditionally, discussions about the keyboard layout are only about where people *don't* want certain keys, not *where* they want them instead, and therefore aren't very productive. So, traditionally, everything remains the same afterwards. ;-) m. Funny, I was thinking exactly the same earlier this week. The t/T combination dates back from the very early days of FlightGear, when they had their use. Those days are long gone. To me it seems that this would be something useful for a menu or dialog box. Not something for an easy accessible hotkey. Cheers, Durk - 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] Patches, Cleanups, and Release planning
Folks, This is just a quick notification: I still have a number of patches floating around in the wake of the stutter bug (cleaning up the timing alerts, etc) and FSWeekend. I had hoped to begin committing some of that stuff to CVS this weekend, but home improvement chores kept be busy all weekend long. Hopefully I can have a go at it this week / next weekend. I'm also hoping that we can schedule a release around christmas. I seems this might work both in terms of my agenda and Curt's. I also hope to get back to that sometime this week. Cheers, Durk - 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
* Curtis Olson -- Sunday 11 November 2007: I don't disagree with any of this, timewarp probably doesn't deserve it's own pair of keystrokes. I use this often and definitely want a key for it. Only 't' seems a bit too wasteful and dangerous. (But I can also make my own local key definition for it. I have lots of free keys, thanks to my use of the Meta modifier. :-) 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
* Willie Fleming -- Sunday 11 November 2007: OK I _WANT_ turbine start/shutdown assigned to t/T and carb heat assigned to 'h' toggle heat on/off and I _WANT_ time warp reassigned to a menu item :-) Of course you have to offer solutions for the keys that you want replaced. h is the HUD. And what are your plans for the former t/T warp function? It quickly becomes less fun when you have to consider that. Have a look at $FG_ROOT/Docs/keyboard/map.pdf for inspiration. :-) 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
Stuart Buchanan wrote: 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. Stuart, this is a really nice addition. Taking you at your word, I spent some enjoyable time last evening tweaking the yasim fdm. Since this activity can be subject to personal preferences, I am attaching a diff file and will comment on the changes, and my reasons for each. I have never flown the real pitts, but have had several extended discussions with several pilots at my field that fly it regularly. 1. CG location - It seemed to be very tail heavy on my first flight, so I googled to find where the CG should be. Could not find the plan numbers, but did find a 1/3 scale RC CG recommendation. So added ballast to move the CG to x= -1.37 m which should be very similar to the location recommended for the RC pitts. I always use the 3d model and $FG_ROOT/bin/yasim to get the CG where documentation says it should be. This made a very big difference. 2. Approach configuration - In spite of the documentation, this needs to be the landing stall configuration. I found the landing stall speed using google and estimated the aoa. 3. Increased the roll rate - more flap0 lift and decreased twist. Decreasing the twist also makes stalls quicker, more positive which helps the snap rolls and spins. 4. The real AC snap rolls easily and spins easily (aerobatics). So decreased the wing and mstab stall widths. 5. Adjusted the cruise and take-off rpms so the engine behaves more like a fixed pitch prop should (i.e at full throttle, the rpm should increase as the AC accelerates. Hope this is helpful, Dave Perry ? pitts.diff Index: pittss1c.xml === RCS file: /var/cvs/FlightGear-0.9/data/Aircraft/pittss1c/pittss1c.xml,v retrieving revision 1.1 diff -p -u -r1.1 pittss1c.xml --- pittss1c.xml 10 Nov 2007 17:18:47 - 1.1 +++ pittss1c.xml 11 Nov 2007 21:38:47 - @@ -9,13 +9,13 @@ YASim aerodynamic model for a Pitts S1C airplane mass=720 !-- Approach configuration -- - approach speed=100 aoa=5 + approach speed=50 aoa=12 control-setting axis=/controls/engines/engine[0]/throttle value=0.5/ control-setting axis=/controls/engines/engine[0]/mixture value=1.0/ /approach !-- Cruise configuration -- - cruise speed=160 alt=0 + cruise speed=160 alt=7000 control-setting axis=/controls/engines/engine[0]/throttle value=0.75/ control-setting axis=/controls/engines/engine[0]/mixture value=0.75/ control-setting axis=/controls/flight/elevator-trim value=0.1/ @@ -27,10 +27,10 @@ YASim aerodynamic model for a Pitts S1C fuselage ax=0 ay=0 az=0 bx=-4.22 by=0 bz=-0.0 width=0.9 taper=0.8 midpoint=0.3/ - wing x=-1.87 y=0.31 z=-0.44 taper=1.0 incidence=0 twist=-3.0 + wing x=-1.87 y=0.31 z=-0.44 taper=1.0 incidence=0 twist=-1.0 length=2.3 chord=0.9 sweep=0 dihedral=2.7 camber=0.1 -stall aoa=22 width=4 peak=1.5/ -flap0 start=0.31 end=0.85 lift=1.3 drag=1.1/ +stall aoa=12 width=2.0 peak=1.5/ +flap0 start=0.31 end=0.85 lift=1.6 drag=1.1/ control-input axis=/controls/flight/aileron control=FLAP0 split=true/ control-input axis=/controls/flight/aileron-trim control=FLAP0 split=true/ control-output control=FLAP0 side=left @@ -39,26 +39,26 @@ YASim aerodynamic model for a Pitts S1C prop=/surface-positions/right-aileron-pos-norm/ /wing - hstab x=-3.91 y=0.1 z=0.04 taper=0.8 effectiveness=1.24 + hstab x=-3.91 y=0.1 z=0.04 taper=0.8 effectiveness=1.5 length=1.0 chord=1.0 sweep=0 -stall aoa=25 width=4 peak=1.5/ -flap0 start=0.5 end=1 lift=1.3 drag=1.2/ +stall aoa=20 width=4 peak=1.5/ +flap0 start=0.1 end=1 lift=1.65 drag=1.2/ control-input axis=/controls/flight/elevator control=FLAP0/ control-input axis=/controls/flight/elevator-trim control=FLAP0/ control-output control=FLAP0 prop=/surface-positions/elevator-pos-norm/ /hstab mstab x=-1.37 y=0 z=0.5 - taper=0.0 dihedral=0 twist=-3.0 + taper=0.0 dihedral=0 twist=-1.0 length=2.62 chord=0.9 sweep=6 incidence=0.0 -stall aoa=20 width=4 peak=1.5/ +stall aoa=12 width=2.0 peak=1.5/ /mstab !-- rudder -- vstab x=-3.9 y=0 z=-0.1 taper=0.8 effectiveness=2.0 length=0.65 chord=1.0 sweep=30 incidence=0.0 stall aoa=30 width=4 peak=1.5/ -flap0 start=0.2 end=0.8 lift=1.2 drag=1.1/ +flap0 start=0.0 end=0.1 lift=2.0 drag=1.1/ control-input axis=/controls/flight/rudder control=FLAP0 invert=true/ control-input axis=/controls/flight/rudder-trim control=FLAP0 invert=true/ control-output control=FLAP0 prop=/surface-positions/rudder-pos-norm @@ -66,16 +66,16 @@ YASim aerodynamic model for a Pitts S1C /vstab propeller radius=0.65 -
Re: [Flightgear-devel] New aircraft for CVS - Pitts S1C
dave perry wrote: Stuart Buchanan wrote: 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. Stuart, this is a really nice addition. Taking you at your word, I spent some enjoyable time last evening tweaking the yasim fdm. Since this activity can be subject to personal preferences ... You may want to try setting the twist to zero for both the wing and mstab. This makes the inverted maneuvers as easy as the normal maneuvers and reduces the tendency to immediately snap roll when inverted and adding down elevator to climb inverted. It is great fun to roll inverted soon after lift off and climb out inverted. Takes gentile control movements though. From KSFO, I flew inverted to the Golden Gate and still inverted flew under the bridge and then into an inverted loop. Another challenge, after take-off and initial climb out to about 500 ft, roll inverted, turn back and fly down the runway inverted at about 50 ft. Climb inverted to about 1500 ft, pull the power and ease back on the stick to do the 2nd half of a loop to the runway and land. With the patch, this is not that difficult. Even easier with the twists set to zero. Nice to have a really aerobatic AC in FlightGear! Thanks again Stuart. - 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] HUP Retriever , an other Piasecki helicopter
Hello An other model of an ancestor helicopter, the HUP Retriever ,which was developed by Piasecki, is available on CVS. It was a rescue helicopter, with To provide rescue without crew assistance, a door (under the copilot seat) , available after folding the copilot’s seat forward, opened through which a rescue sling could be lowered from an overhead winch. That helicopter was used by the U.S. Navy and Army (from 1949 to 1964), it was also delivered to the Canadian and French Navies (in service from 1953 to 1965) The model is under construction. The FDM is a guess. Mainly to do: -the instruments, -the landing gear animations -liveries variant Here snapshots http://pagesperso-orange.fr/GRTux/HUP-img1.jpg http://pagesperso-orange.fr/GRTux/HUP-img2.jpg Cheers -- 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
[Flightgear-devel] Keyboard reorg
This is a good discussion that we've started. Way back when, we didn't have menus (or scripting), so every function had to be accessible from the keyboard (and all the assignments were hard-coded in C++ to boot). I think that we need to take a few steps: 1. Come up with a prioritized list of functions that should have global keyboard assignments (e.g. switch view, lower flaps, raise gear, etc.). 2. Decide on a block of keys to be set aside for per-aircraft key assignment. 3. Agree on a useful set of core bindings for the remainder, which no model should touch. This will be not be easy, but it will be very beneficial. There should be some logic to it, e.g. function keys used for one kind of thing, alphabetic for another, etc. As people have noted, a lot of stuff currently assigned to keys should move to menus and dialogs. 4. Provide a GUI for a user to change keyboard assignments while the sim is running and to save the changes. The user's local changes should override everything else, including per-model assignments. (If we're really sophisticated, we could let the user make his/her own per-model assignments.) Anyone game to start? Does someone already have a first draft of a prioritized function list? 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] Keyboard reorg
On Sun, 11 Nov 2007 21:36:35 -0500 David Megginson [EMAIL PROTECTED] wrote: This is a good discussion that we've started. Way back when, we didn't have menus (or scripting), so every function had to be accessible from the keyboard (and all the assignments were hard-coded in C++ to boot). I think that we need to take a few steps: 1. Come up with a prioritized list of functions that should have global keyboard assignments (e.g. switch view, lower flaps, raise gear, etc.). 2. Decide on a block of keys to be set aside for per-aircraft key assignment. 3. Agree on a useful set of core bindings for the remainder, which no model should touch. This will be not be easy, but it will be very beneficial. There should be some logic to it, e.g. function keys used for one kind of thing, alphabetic for another, etc. As people have noted, a lot of stuff currently assigned to keys should move to menus and dialogs. 4. Provide a GUI for a user to change keyboard assignments while the sim is running and to save the changes. The user's local changes should override everything else, including per-model assignments. (If we're really sophisticated, we could let the user make his/her own per-model assignments.) Anyone game to start? Does someone already have a first draft of a prioritized function list? All the best, David Well just to get the ball rolling , and thinking out loud ... the keyboard 1 - 0 could go to cockpit switches , battery , lights, etc , since not all aircraft have hotspots yet and if it's do-able (will it interfere with the keypad trim keys ?) Autopilot already has a dialogue , could be updated ... I can never remember the keys for that anyway ... just some ideas beginning in my head :) Im willing to do what I can if we can all come to an acceptable solution... Ive started on a keyboard image with key layout for myself ... maybe could be included down the road if things turn out... 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
