Re: [Flightgear-devel] Improved chat interface patch
Hi All, I now have a working chat menu system, which will generate canned chat messages by using a simple menu system, access by the numbers on your keyboard. The canned messages are somewhat dynamic, in that they pick up the current airport, and your own callsign and altitude. You will need to pick up the tarball from http://www.nanjika.co.uk/flightgear/chatmenu.tar.gz. This contains the following files: - multiplayer.nas to put in your Nasal directory (this is updated from my previous patch) - chat-menu.xml to put in your gui/dialogs directory. - chat-menu-entries.xml to put in your ATC directory. In addition, you will need to do the following: - Apply the keyboard.xml patch below. This maps "-" to open the chat menu and "_" to open free-form chat using the simply chat widget I created earlier. - Edit your preferences.xml file to pick up the chat-menu-entries.xml file under /sim/multiplay. As we all have much modified preferences, this is probably best shown by example rather than patch: Hello 11850 true I.e. you need to add a line within the section. To use, simply press "-" to open the menu - you will see a set of numbered options. They can be accessed using the obvious numeric key assignments. Some of the options open sub-menus, and you can navigate backwards using "0", or press "1" to immediately open the chat widget with the current message. As always, you can modify the menu tree to include your favourite messages, simply by editing the ATC/chat-menu-entries.xml file. The one I've created is very much a starting point, and submissions/improvements are most welcome. We may need to standardize on an FG phraseology, due to the differences in ATC phraseology across the globe. The number of subsitutions available within the messages is very limited, and the message parser also very simple. There is quite a bit of room for improvement in this regard. For example, it would be nice to substitute in a guess of the current runway in use. Assuming this passes muster, if someone could commit it, I'd be grateful. Comments as always are welcome. -Stuart Index: keyboard.xml === RCS file: /var/cvs/FlightGear-0.9/data/keyboard.xml,v retrieving revision 1.101 diff -u -r1.101 keyboard.xml --- keyboard.xml13 Nov 2007 14:42:44 -1.101 +++ keyboard.xml23 Nov 2007 00:58:21 - @@ -354,7 +354,17 @@ - + +- +false +Compose Chat + + dialog-show + chat-menu + + + + . Right brake @@ -754,6 +764,16 @@ + +_ +false +Compose Chat + + nasal + multiplayer.compose_message() + + + a Increase speed-up. ___ 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: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] R22 broken with keyboard (was: Problems with R22)
On Thu, 22 Nov 2007 22:12:13 +0100 (CET) Heiko Schulz <[EMAIL PROTECTED]> wrote: > > --- gerard robin <[EMAIL PROTECTED]> schrieb: > > > On jeu 22 novembre 2007, Syd&Sandy wrote: > > > On Thu, 22 Nov 2007 20:47:29 +0100 > > > > > > AnMaster <[EMAIL PROTECTED]> wrote: > > > > -BEGIN PGP SIGNED MESSAGE- > > > > Hash: SHA512 > > > > > > > > He might have remapped PgUp/Down to.. > > > > Yep.. that is what's up.. > > > > Hmm.. that means (AFAIKS) there is no > > keyboard collective > > > > anymore.. :-/ And I don't have a joystick. > > Consider this a bug report. > > > > > > > > Regards, > > > > AnMaster > > > > > > > > AnMaster wrote: > > > > > I may may have missed something obvious but > > when I was trying out the > > > > > R22 in CVS I never got it off ground. I got > > the engine started just > > > > > fine, but the throttle doesn't seem to map to > > collective as in other > > > > > aircrafts nor can I find any key that does, so > > how does one take off in > > > > > it? Tried with both fg/plib/glut and > > fg/osg/glut. Did also look in > > > > > aircraft help and the aircraft xml files > > without finding anything > > > > > useful. > > > > > > > > > > Regards, > > > > > > > > > > Anmaster > > > > > > Sorry about that guys , I didn't think anyone was > > foolish enough to try to > > > fly a helicopter without joystick and rudder > > control ;) I'll remove that as > > > soon as I'm finish work (about 4 hours from now ) > > Cheers > > > > > > Hello, Sandy > > > > I am, too, a member of that "foolish Club" > > whoflychopperswithamouseonly :) > > > > Regards > > > > > > -- > > Gérard > > http://pagesperso-orange.fr/GRTux/ > > > > > > > - > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio > > 2005. > > > http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ > > ___ > > Flightgear-devel mailing list > > Flightgear-devel@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > > > > > Yes- Me too! And the mouse is a very sensible tool! I > just wish I would have rudders! :-) > > Regards > HHS > > > Machen Sie Yahoo! zu Ihrer Startseite. Los geht's: > http://de.yahoo.com/set > Well , OK , I admit it , I find the mouse a much better cyclic control than the joystick. (Because it fairly new , i dont want to take the centering spring out just yet :) ) Cheers... oh , and Sandy is my better half , the one that occasionally has to say "get off that damn computer ! " -- Syd&Sandy <[EMAIL PROTECTED]> - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
Hi Durk and John, > > Please note that this server runs from home, on a private ADSL connection, > using a wireless lan. So please be aware that downloads will be slow and that > a stable connection can't always be guaranteed. Curt and I are currently > working out a way to transfer these files to Curt's server. Thank you, John W., for the fast mirror site :-) > In the mean time, > it would be great if a few people could try out this pre-release. The more > issues we can fix, the better. > > Cheers, > Durk > > Just as a first feedback: Compiles on OpenSUSE 10.2 x86_64 without problems. I did some first testflights, generally seems to work fine. Will do some more testing over the weekend. Thank you for your work so far. Regards Georg EDDW - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] slip angle (was: yaw)
On Thursday 22 November 2007 13:52, John Denker wrote: Sorry - couldn't resist this But... > If you think you've got problems when the heading angle goes to 180 > degrees, think about what happens when the pitch angle goes to ±90 > degrees. Been there - done that. But seriously, I have done some stuff in that specific area - control when pitch and roll reverse. Haven't released anything yet (mostly related to the SU-37 and YF-23), of course, because it didn't work all the time:) I've read through all the responses on this subject, so far, and in some ways it seems as though it's being over-complicated. I don't think that there is a bug in either YASim or JSBSim in relation to this issue - the data is already being passed to the old original hard-coded hud. This means that the data is already being produced and it is not an FDM issue about producing the data but about how the data already being successfully produced is being handled and routed, and eventually being exposed in the property-tree. Oh yeah - and what it's going to be called ;-) LeeE - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
Durk, Thanks for building the official pre2 source packages. I tried your pre2 sources on my MacBook Pro and I successfully built it with no problem. so there's no urgent patches for Mac OS X port. Let me give you quick feedback on 0.9.11-pre2. I already found the following two bugs in pre2, which are also seen in pre1. 1. Aircraft shows up under a carrier on reset. (almost 100% reproducible) This happens when I reset FlightGear (Shift-ESC). I tested it with p51d, c172p, and A6M2(from 0.9.10) on Nimitz. There was a discussion on the carrier issue (FlightGear-0.9.11-pre1---Carriers are flying) in the list. It might have something to do with this issue. 2. Flying instruments (seen only twice) After I saw c172p under Nimitz, I reset FlightGear (perphaps) twice. Then the instruments suddenly started flying out the cockpit as shown below. There was a DList stack overflow bug in pre1 (when resetting several times), but I didn't see this yet so far. I'll give you additional feedback after several more test flights. Best, Tat On Nov 23, 2007, at 5:06 AM, Durk Talsma wrote: > On Thursday 22 November 2007 07:36, I wrote: >> This is a quick note to everybody: I'm planning to build an >> "official" >> FlightGear pre-release tonight. I did a full dress rehearsal last >> sunday >> and that all seemed to work well, but I still needed Curt's okay >> for a few >> remaining issues. In the mean time, if there are any *urgent* patches >> remaining please try to get them into CVS ASAP. >> > > For those who feel adventurous: The prerelease tar files can now be > found > here: > > http://durktalsma.xs4all.nl/FlightGear/fgfs-base-0.9.11-pre2.tar.bz2 > http://durktalsma.xs4all.nl/FlightGear/SimGear-0.3.11-pre2.tar.gz > http://durktalsma.xs4all.nl/FlightGear/FlightGear-0.9.11-pre2.tar.gz > > Please note that this server runs from home, on a private ADSL > connection, > using a wireless lan. So please be aware that downloads will be slow > and that > a stable connection can't always be guaranteed. Curt and I are > currently > working out a way to transfer these files to Curt's server. In the > mean time, > it would be great if a few people could try out this pre-release. > The more > issues we can fix, the better. > > Cheers, > Durk > > - > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ > ___ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Mirror site
Hi, The pre-release tar files have been uploaded to an alternate site for the interim to relieve the load on Durk's machine. Files are at http://www.lfstech.com/pub/flightgear or ftp://www.lfstech.com/pub/flightgear. Should also be quite a bit faster. JW - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Improved chat interface patch
Hi All,
Inspired by Melchior's new property interface (and copying most of his
techniques), I've written an enhancement to the chat interface that allows
users to write chat messages much more easily. The patches below binds a
keyboard handler to the "-" key, creating a nice easy way to compose chat
messages without needing the normal chat window.
This feature was suggested on the IRC channel a couple of nights ago. I don't
remember who it was - but they have my thanks for suggesting it.
I fully expect that the key will be re-assigned later as part of the general
discussion of keyboard bindings, but there is at least some logic to it: I'm
planning a menu-system for the chat allowing people to compose canned messages
("KSFO Traffic, G-MWLX is downwind, runway 28L") with a couple of key presses,
for which I'm hoping to use the 1-9 keys.
If someone could review it and commit to CVS, I would be very grateful.
As always, comments are very welcome - my aim it to make the text-based chat
interface usable for the 0.9.11 release as a stop-gap until the FG-COM becomes
the standard.
Best regards to all - and a happy Thanksgiving for those celebrating it!
-Stuart
Index: keyboard.xml
===
RCS file: /var/cvs/FlightGear-0.9/data/keyboard.xml,v
retrieving revision 1.101
diff -u -r1.101 keyboard.xml
--- keyboard.xml13 Nov 2007 14:42:44 -1.101
+++ keyboard.xml22 Nov 2007 21:01:55 -
@@ -354,7 +354,17 @@
-
+
+-
+false
+Compose Chat
+
+ nasal
+ multiplayer.compose_message()
+
+
+
+
.
Right brake
Index: multiplayer.nas
===
RCS file: /var/cvs/FlightGear-0.9/data/Nasal/multiplayer.nas,v
retrieving revision 1.3
diff -u -r1.3 multiplayer.nas
--- multiplayer.nas15 Oct 2007 18:27:42 -1.3
+++ multiplayer.nas22 Nov 2007 21:53:40 -
@@ -72,7 +72,6 @@
}
}
-
settimer(func {
# Call-back to ensure we see our own messages.
setlistener("/sim/multiplay/chat", func(n) { echo_message(n.getValue(),
getprop("/sim/multiplay/callsign")); });
@@ -82,4 +81,71 @@
}, 1);
+# Message composition function, activated using the - key.
+var prefix = "Chat Message:";
+var input = "";
+var kbdlistener = nil;
+
+compose_message = func()
+{
+ input = prefix;
+ gui.popupTip(input, 100);
+
+ kbdlistener = setlistener("/devices/status/keyboard/event", func {
+var event = cmdarg();
+var key = event.getNode("key");
+
+# Only check the key when pressed.
+if (!event.getNode("pressed").getValue())
+return;
+
+if (handle_key(key.getValue()))
+key.setValue(0); # drop key event
+ });
+}
+handle_key = func(key)
+{
+ if (key == `\n` or key == `\r`)
+ {
+# CR/LF -> send the message
+
+# Trim off the prefix
+input = substr(input, size(prefix), size(input) - size(prefix));
+# Send the message and switch off the listener.
+setprop("/sim/multiplay/chat", input);
+removelistener(kbdlistener);
+gui.popdown();
+return 1;
+ }
+ elsif (key == 8)
+ {
+# backspace -> remove a character
+
+if (size(input) > size(prefix))
+{
+ input = substr(input, 0, size(input) - 1);
+ gui.popupTip(input, 100);
+ return 1;
+}
+ }
+ elsif (key == 27)
+ {
+# escape -> cancel
+removelistener(kbdlistener);
+gui.popdown();
+return 1;
+ }
+ elsif ((key > 31) and (key < 128))
+ {
+# Normal character - add it to the input
+input ~= chr(key);
+gui.popupTip(input, 100);
+return 1;
+ }
+ else
+ {
+# Unknown character - pass through
+return 0;
+ }
+}
___
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: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] FGCOM again, mixer mess
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 So I tried FGCOM with OSS emulation, at last it compiled with jester's patch at http://pastebin.ca/794075. Now I tried it. Error. Ok, so I need to edit some files it turns out after asking on IRC channel to change prefix (whatever happened to ./configure --prefix? or cmake?). After many errors at last I got it to run. The first things it does is messing up the mixer settings I like by changing volume upwards almost causing my "ears to burst". After that it turns the master off. What is the point in that? I wish it would leave the mixer settings I use alone. I will wait for this bug to get fixed before I try it again. Regards, AnMaster -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFHRfihWmK6ng/aMNkRCr6wAKDFCAJn5qlzmSiaivUyxB0ZkpGQpwCfaOP8 gmMGLcoxXWUoM+CzfYe+y0I= =CG4O -END PGP SIGNATURE- - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] R22 broken with keyboard (was: Problems with R22)
--- gerard robin <[EMAIL PROTECTED]> schrieb: > On jeu 22 novembre 2007, Syd&Sandy wrote: > > On Thu, 22 Nov 2007 20:47:29 +0100 > > > > AnMaster <[EMAIL PROTECTED]> wrote: > > > -BEGIN PGP SIGNED MESSAGE- > > > Hash: SHA512 > > > > > > He might have remapped PgUp/Down to.. > > > Yep.. that is what's up.. > > > Hmm.. that means (AFAIKS) there is no > keyboard collective > > > anymore.. :-/ And I don't have a joystick. > Consider this a bug report. > > > > > > Regards, > > > AnMaster > > > > > > AnMaster wrote: > > > > I may may have missed something obvious but > when I was trying out the > > > > R22 in CVS I never got it off ground. I got > the engine started just > > > > fine, but the throttle doesn't seem to map to > collective as in other > > > > aircrafts nor can I find any key that does, so > how does one take off in > > > > it? Tried with both fg/plib/glut and > fg/osg/glut. Did also look in > > > > aircraft help and the aircraft xml files > without finding anything > > > > useful. > > > > > > > > Regards, > > > > > > > > Anmaster > > > > Sorry about that guys , I didn't think anyone was > foolish enough to try to > > fly a helicopter without joystick and rudder > control ;) I'll remove that as > > soon as I'm finish work (about 4 hours from now ) > Cheers > > > Hello, Sandy > > I am, too, a member of that "foolish Club" > whoflychopperswithamouseonly :) > > Regards > > > -- > Gérard > http://pagesperso-orange.fr/GRTux/ > > > - > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio > 2005. > http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ > ___ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > Yes- Me too! And the mouse is a very sensible tool! I just wish I would have rudders! :-) Regards HHS Machen Sie Yahoo! zu Ihrer Startseite. Los geht's: http://de.yahoo.com/set - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] FGCOM fails to compile. Still.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 When trying to compile FGCOM (Gentoo Linux 64-bit) revision 64: [...] cc -I. -Igsm/inc -Iportaudio/include -Iportaudio/src/common -Iportaudio/pablio - -Iportmixer/px_common -Ilibspeex/include --std=c99 -Wall -Wmissing-noreturn -g - -O2 -DLIBVER='"SVN 42M"' -DSPEEX_PREPROCESS=1 -DNEWJB -Iportaudio/src/os/unix - -DAUDIO_ALSA -Ilibiax2/src -DLIBIAX -DSPEEX_EC=1 -DLINUX -c -o portaudio/pablio/ringbuffer.o portaudio/pablio/ringbuffer.c cc -I. -Igsm/inc -Iportaudio/include -Iportaudio/src/common -Iportaudio/pablio - -Iportmixer/px_common -Ilibspeex/include --std=c99 -Wall -Wmissing-noreturn -g - -O2 -DLIBVER='"SVN 42M"' -DSPEEX_PREPROCESS=1 -DNEWJB -Iportaudio/src/os/unix - -DAUDIO_ALSA -Ilibiax2/src -DLIBIAX -DSPEEX_EC=1 -DLINUX -c -o audio_alsa.o audio_alsa.c In file included from /usr/include/alsa/asoundlib.h:44, from audio_alsa.c:20: /usr/include/alsa/global.h:134: error: redefinition of 'struct timeval' /usr/include/alsa/global.h:139: error: redefinition of 'struct timespec' audio_alsa.c: In function 'alsa_output': audio_alsa.c:91: warning: format '%d' expects type 'int', but argument 2 has type 'long int' audio_alsa.c: In function 'alsa_initialize': audio_alsa.c:137: warning: unused variable 'buf' audio_alsa.c:135: warning: unused variable 'i' make[1]: *** [audio_alsa.o] Error 1 make[1]: Leaving directory `/mnt/src/arvid/fgcom/iaxclient/lib' make: *** [iaxstatic] Error 2 I tried the native ALSA support. Regards, AnMaster -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFHRfAPWmK6ng/aMNkRCr1lAKC4foM28Xmw+PvdB97ltZAhGsNtDwCfYVf4 Ib4lt6UCDgYz37AyLkF+aoA= =hhNf -END PGP SIGNATURE- - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] R22 broken with keyboard (was: Problems with R22)
On jeu 22 novembre 2007, Syd&Sandy wrote: > On Thu, 22 Nov 2007 20:47:29 +0100 > > AnMaster <[EMAIL PROTECTED]> wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA512 > > > > He might have remapped PgUp/Down to.. > > Yep.. that is what's up.. > > Hmm.. that means (AFAIKS) there is no keyboard collective > > anymore.. :-/ And I don't have a joystick. Consider this a bug report. > > > > Regards, > > AnMaster > > > > AnMaster wrote: > > > I may may have missed something obvious but when I was trying out the > > > R22 in CVS I never got it off ground. I got the engine started just > > > fine, but the throttle doesn't seem to map to collective as in other > > > aircrafts nor can I find any key that does, so how does one take off in > > > it? Tried with both fg/plib/glut and fg/osg/glut. Did also look in > > > aircraft help and the aircraft xml files without finding anything > > > useful. > > > > > > Regards, > > > > > > Anmaster > > Sorry about that guys , I didn't think anyone was foolish enough to try to > fly a helicopter without joystick and rudder control ;) I'll remove that as > soon as I'm finish work (about 4 hours from now ) Cheers Hello, Sandy I am, too, a member of that "foolish Club" whoflychopperswithamouseonly :) Regards -- Gérard http://pagesperso-orange.fr/GRTux/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] R22 broken with keyboard (was: Problems with R22)
On Thu, 22 Nov 2007 20:47:29 +0100 AnMaster <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > He might have remapped PgUp/Down to.. > Yep.. that is what's up.. > Hmm.. that means (AFAIKS) there is no keyboard collective anymore.. > :-/ > And I don't have a joystick. Consider this a bug report. > > Regards, > AnMaster > > AnMaster wrote: > > I may may have missed something obvious but when I was trying out the R22 > > in CVS > > I never got it off ground. I got the engine started just fine, but the > > throttle > > doesn't seem to map to collective as in other aircrafts nor can I find any > > key > > that does, so how does one take off in it? Tried with both fg/plib/glut and > > fg/osg/glut. Did also look in aircraft help and the aircraft xml files > > without > > finding anything useful. > > > > Regards, > > > > Anmaster Sorry about that guys , I didn't think anyone was foolish enough to try to fly a helicopter without joystick and rudder control ;) I'll remove that as soon as I'm finish work (about 4 hours from now ) Cheers -- Syd&Sandy <[EMAIL PROTECTED]> - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
On Thursday 22 November 2007 07:36, I wrote: > This is a quick note to everybody: I'm planning to build an "official" > FlightGear pre-release tonight. I did a full dress rehearsal last sunday > and that all seemed to work well, but I still needed Curt's okay for a few > remaining issues. In the mean time, if there are any *urgent* patches > remaining please try to get them into CVS ASAP. > For those who feel adventurous: The prerelease tar files can now be found here: http://durktalsma.xs4all.nl/FlightGear/fgfs-base-0.9.11-pre2.tar.bz2 http://durktalsma.xs4all.nl/FlightGear/SimGear-0.3.11-pre2.tar.gz http://durktalsma.xs4all.nl/FlightGear/FlightGear-0.9.11-pre2.tar.gz Please note that this server runs from home, on a private ADSL connection, using a wireless lan. So please be aware that downloads will be slow and that a stable connection can't always be guaranteed. Curt and I are currently working out a way to transfer these files to Curt's server. In the mean time, it would be great if a few people could try out this pre-release. The more issues we can fix, the better. Cheers, Durk - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] R22 broken with keyboard (also concorde...)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Not sure why there were two copies of this, sorry for that. However another aircraft with bad keyboard binding is Concorde with Ctrl-M/Enter for menu, that blocks changing rudder with keyboard, locally I moved that to - for concorde, - is unused in global keyboard bindings according to data/Docs/keyboard/map.pdf. I think aircraft developers should consider those who don't own joysticks when they select key bindings. Regards, AnMaster AnMaster wrote: > He might have remapped PgUp/Down to.. > Yep.. that is what's up.. > Hmm.. that means (AFAIKS) there is no keyboard collective anymore.. > :-/ > And I don't have a joystick. Consider this a bug report. > > Regards, > AnMaster > > AnMaster wrote: >> I may may have missed something obvious but when I was trying out the R22 in >> CVS >> I never got it off ground. I got the engine started just fine, but the >> throttle >> doesn't seem to map to collective as in other aircrafts nor can I find any >> key >> that does, so how does one take off in it? Tried with both fg/plib/glut and >> fg/osg/glut. Did also look in aircraft help and the aircraft xml files >> without >> finding anything useful. > >> Regards, > >> Anmaster -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFHRd3/WmK6ng/aMNkRCqNIAJ9F9ETpd/Y0qnnNvJmzQUX9/m8rLgCffZP5 bkZzeBrYEmy/OZ3PdjhTlTY= =WPnE -END PGP SIGNATURE- - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] R22 broken with keyboard (was: Problems with R22)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 He might have remapped PgUp/Down to.. Yep.. that is what's up.. Hmm.. that means (AFAIKS) there is no keyboard collective anymore.. :-/ And I don't have a joystick. Consider this a bug report. Regards, AnMaster AnMaster wrote: > I may may have missed something obvious but when I was trying out the R22 in > CVS > I never got it off ground. I got the engine started just fine, but the > throttle > doesn't seem to map to collective as in other aircrafts nor can I find any key > that does, so how does one take off in it? Tried with both fg/plib/glut and > fg/osg/glut. Did also look in aircraft help and the aircraft xml files without > finding anything useful. > > Regards, > > Anmaster - - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFHRdzRWmK6ng/aMNkRCnEgAJ9TGZxTzitV0KgW/mw0Gquta0IyWwCfZmwR hUEQeNB0Jq3pStG7hI3ZpYc= =d7pF -END PGP SIGNATURE- - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] R22 broken with keyboard (was: Problems with R22)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 He might have remapped PgUp/Down to.. Yep.. that is what's up.. Hmm.. that means (AFAIKS) there is no keyboard collective anymore.. :-/ And I don't have a joystick. Consider this a bug report. Regards, AnMaster AnMaster wrote: > I may may have missed something obvious but when I was trying out the R22 in > CVS > I never got it off ground. I got the engine started just fine, but the > throttle > doesn't seem to map to collective as in other aircrafts nor can I find any key > that does, so how does one take off in it? Tried with both fg/plib/glut and > fg/osg/glut. Did also look in aircraft help and the aircraft xml files without > finding anything useful. > > Regards, > > Anmaster - - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFHRdrDWmK6ng/aMNkRCglrAKC0CpNgKlhBV73R1LkVg/Zzoq1hswCgxRjd /d/3IcsHWMOyI9tOmcvznlA= =nXZP -END PGP SIGNATURE- - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] slip angle
> Maybe it would help to talk to the CDM guys instead of the > FDM guys. > http://www.google.com/search?q=car-dynamics-model > http://www.google.com/search?q=car-dynamics-model+nascar > > I reckon the car-dynamics guys have a pretty good model of > static friction and quasi-static rolling friction. After > all, that is their raison d'tre. Whatever they've got > is surely more than good enough for our purposes. Yes. I have looked at car dynamics casually. It would be nice to get one of those guys onboard. > That's a very reasonable compromise for the interim. The > airspeed vector (i.e. relative wind vector) exposed via > the public interface (i.e. the property tree) should be > the honest-to-goodness airspeed, including nature's wind, > even while parked. I'll try and put that on my list. Jon - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Problems with R22
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I may may have missed something obvious but when I was trying out the R22 in CVS I never got it off ground. I got the engine started just fine, but the throttle doesn't seem to map to collective as in other aircrafts nor can I find any key that does, so how does one take off in it? Tried with both fg/plib/glut and fg/osg/glut. Did also look in aircraft help and the aircraft xml files without finding anything useful. Regards, Anmaster -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFHRdHCWmK6ng/aMNkRCpMtAKC0Pxg5Hm3V2L7jSlq+4PzKczZaxACdHE0H j7vvtCwJSX9cP15V/nBXw28= =Z6XA -END PGP SIGNATURE- - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] slip angle
On 11/22/2007 12:59 PM, Jon S. Berndt wrote: > What happens if > the combined moment on the vehicle and the translational force causes only > one gear to go past its ability to hold traction on the ground? Well, that's pretty far down on the priority list, but since you asked: That happens sometimes. It happens more often than I would like, but it happens. For example, suppose the student pilot applies the brakes too much and/or unevenly. The result is that the aircraft turns like crazy. This is a good recipe for a ground-loop. This is particularly nasty because the instructor's options are limited. The instructor cannot un-apply the brakes. (This stands in unpleasant contrast to, say, the student pulling on the yoke; the instructor at least has a fighting chance of pushing on the yoke so as to overpower the student.) Much higher on the priority list are -- parking with the parking brake set and not slipping under ordinary non-extreme conditions. -- Weathervaning (yaw and roll) during taxi and during the initial takeoff run. > When you > start programming this to take care of the general case, it just gets out of > hand. Maybe it would help to talk to the CDM guys instead of the FDM guys. http://www.google.com/search?q=car-dynamics-model http://www.google.com/search?q=car-dynamics-model+nascar I reckon the car-dynamics guys have a pretty good model of static friction and quasi-static rolling friction. After all, that is their raison d'être. Whatever they've got is surely more than good enough for our purposes. > it did occur to me that it should be possible to use one set > of data to do gear modeling, and another set to report values (such as > sideslip) for instrumentation. That's a very reasonable compromise for the interim. The airspeed vector (i.e. relative wind vector) exposed via the public interface (i.e. the property tree) should be the honest-to-goodness airspeed, including nature's wind, even while parked. If the FDM finds it convenient to use some notion of "pseudo-wind" as part of a scheme to avoid modeling the ground/tire interaction, then that should be kept strictly separate ... and maybe kept private, internal to the FDM. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] [ANNOUNCEMENT] TerraGear-"fork" GIT repository
Hello all, I just wanted to let all of you know that a read-only GIT repository of the TerraGear "fork" is now available unter http://mapserver.flightgear.org/git/terragear/. A gitweb environment for browsing online is to be found at http://mapserver.flightgear.org/git/ Thanks to Martin Spott for setup and maintenance :-) Cheers, Ralf - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] X52.xml file, and cheap rudder pedal :-p
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I'm planning to get an X52 Pro, so I wonder what is wrong with current x52 config file in CVS. Also, what driver is needed in linux for it (if any)? I don't have rudder pedals, and that won't be in the X52.xml right? Regards AnMaster Tatsuhiro Nishioka wrote: > Hi there, > > I modified X52.xml for Saitek X52 controller. You can download it from: > http://macflightgear.sourceforge.net/home/development-notes/devnote-nov-22-2007 > > I also use the gas/brake pedal of WingMan formula force GP (Yes, a > racing controller) for rudder control. > you can also use its xml file from the link above. This file provides > the control only for the pedal :-p > > I'll enjoy my gas/brake pedal by the time I get the real rudder > pedal ;-) > > By the way, X52's wheel scrolls are recognized as button 1 and 2. > This causes a problem like unexpectedly unlocking the parking brake, > so be careful. > > Feedbacks and better ideas are always welcome. > I want to add more functions to Mode2 / 3 but am not sure what > functions to be added yet. > > Best, > > Tat > > -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFHRcUOWmK6ng/aMNkRCsTJAKCMLU2y442673DAApFV16wsGV30QwCeOPf0 +5/WP1JDHvT5soFFOKIH19c= =geKN -END PGP SIGNATURE- - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] slip angle
> On 11/22/2007 09:10 AM, Jon S. Berndt wrote: > > > At this time, JSBSim zeroes out the wind velocities while at rest on > > the ground, to prevent slippage. > John Denker replied: > Aha. Thanks for the info. > > FWIW that sounds like *two* bugs to me. > 1) Maybe we need a better model of static friction and quasi-static > rolling friction so as to properly handle the behavior of tires > gripping the ground. > 2) We do need the real wind and real airspeed vector while on the > ground. There are many reasons for this, including things like > the weathervaning tendency, which is an important part of real > crosswind takeoffs and landings. For the best ground handling performance in JSBSim, ALL forces that act on the vehicle are zeroed out at rest on the ground, and wind effects are ramped in as velocity increases. Trust me, I've looked at this problem for years, read various tech papers on it, seen how other sims do it, and talked to experts. There's always a workaround of some kind. If you really think about all aspects of this, it quickly becomes a big headache. What happens when you are at rest, and you have wind forces acting on the aircraft? The wind can come from any angle, so the aero model has to be very good and all-aspect. The normal force at each gear can then be different than simply distributing the normal forces based on a static analysis. What happens if the combined moment on the vehicle and the translational force causes only one gear to go past its ability to hold traction on the ground? When you start programming this to take care of the general case, it just gets out of hand. With that said, it did occur to me that it should be possible to use one set of data to do gear modeling, and another set to report values (such as sideslip) for instrumentation. I'm thinking off the top of my head, now (as I'm in the middle of cooking and baking with my wife for Thanksgiving), but it seems we ought to be able to separate out the values used for gear modeling and those reported as output for display. I'll try to remember to look into that. Jon - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] OSGEdit
Hello, If you wants a tool which help to make any OSG object, here the very last version of OSGEdit which is usable http://osgedit.sourceforge.net/. It looks to be better than the previous version, with a lot of improvements. Regards BTW: you could notice on that page the name of Heiko Schulz:) -- Gérard http://pagesperso-orange.fr/GRTux/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] slip angle
On 11/22/2007 09:10 AM, Jon S. Berndt wrote: > At this time, JSBSim zeroes out the wind velocities while at rest on > the ground, to prevent slippage. Aha. Thanks for the info. FWIW that sounds like *two* bugs to me. 1) Maybe we need a better model of static friction and quasi-static rolling friction so as to properly handle the behavior of tires gripping the ground. 2) We do need the real wind and real airspeed vector while on the ground. There are many reasons for this, including things like the weathervaning tendency, which is an important part of real crosswind takeoffs and landings. > At this time, JSBSim zeroes out the wind velocities How strongly time-dependent are these bugs? The workaround (below) is not particularly arduous, but nobody wants to implement a workaround if the bugs are going to be fixed Real Soon. = LeeE: It is not hard to work around these bugs. If you want the slip angle (which may or may not be everything you want), all it takes is ye olde wind-triangle calculation. Start by getting the true wind vector components from /environment/wind-from-north-fps /environment/wind-from-east-fps I assume the FDM is not messing with the environment's copy of this vector. Rotate that into the aircraft frame using the usual rotation operator. The rotation angle is the true heading. Add that vector to the groundspeed vector u = /fdm/jsbsim/velocities/u-fps v = /fdm/jsbsim/velocities/v-fps The resulting sum is the airspeed vector, in the aircraft frame, i.e. relative to the aircraft axes. If desired, take the atan2(v, u) as previously described. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] slip angle
John Denker a écrit : > On 11/22/2007 07:28 AM, LeeE wrote: > > > FWIW I also spotted that the coded hard-coded hud has problems > > around headings of 180 deg so that if you are heading slightly to > > one side of 180 deg and there's enough of a cross-wind to swing the > > direction indicator to the other side of 180 deg it disappears, > > probably due to a wrap-around type error. > > Sounds like a bug to me. It could be a bug in the FDM (which seems > kinda unlikely) or it could be a bug in how the HUD uses the > information. > > Bugs like this are par for the course when such things are quantified > in the Euler-angle representation or the axis-angle representation. > For a lumbering bomber you can get away with using a lame > representation, but for something more maneuverable you would be much > better off using the geometric algebra representation aka Clifford > algebra aka multivectors aka quaternions. If you think you've got > problems when the heading angle goes to 180 degrees, think about what > happens when the pitch angle goes to ±90 degrees. > > > Yaw, to me means the difference between the direction that the > > aircraft is pointing and the direction that it is moving. > > Moving? From what follows I gather that means moving relative to the > airmass (not moving relative to the ground). It is important to > think clearly and speak clearly, so as to not blur this distinction. > > > Flying directly into, or with, any wind would produce no yaw but > > flying in a cross-wind would produce yaw. When sitting stationary > > on the ground, any cross-winds would result in an effective > > airspeed, so yes, I would expect there to be a large yaw element > > under those circumstances. > > That's the slip angle. It is almost universally denoted by β (beta). > It's in the tree as /orientation/side-slip-deg > /orientation/side-slip-rad which are computed by the FDM. > > If that variable doesn't show a large slip angle when parked in a > crosswind, that's a nasty bug. > > You can easily enough check whether the FDM is calculating this > correctly by recomputing it yourself. It's just the angle between > the relative wind vector (projected onto the XY plane) and the > heading vector. It's trivial to calculate: u = > /fdm/jsbsim/velocities/u-aero-fps v = > /fdm/jsbsim/velocities/v-aero-fps beta = atan2(v, u) convert from > radians to degrees if you wish ... although (as mentioned above) for > most purposes you're better off using the (u,v) vector as a vector, > rather than converting it to an angle. > > If the FDM is not calculating u-aero and v-aero properly and/or not > calculating β properly and/or not putting β in > /orientation/side-slip-rad then it is a very serious bug. > > Please don't call it the yaw angle. Please call it either slip angle > or β. Note that the thing some pilots call a yaw string really > should be called a /slip string/. > http://www.av8n.com/how/htm/multi.html#sec-slip-string > > > As to what I would do with it - I assume you are asking out of > > curiosity - it's needed to set the steering in tandam/quadracyle > > landing gear aircraft so that they can take-off and land in > > cross-winds. > > For that you need the motion of the airplane relative to the *ground* > not relative to the airmass. That's different. That's why I asked > what it would be used for. > > I'm not sure what that quantity should be called. It's not the yaw > angle. I reckon it's just the difference between the slip angle and > the wind-correction angle. This item you need to calculate for > yourself, since it's not in the tree AFAICT. It's trivial to > calculate u = /fdm/jsbsim/velocities/u-fps v = > /fdm/jsbsim/velocities/v-fps angle = atan2(v, u) ... although (as > mentioned above) for most purposes you're better off using the (u,v) > vector as a vector, rather than converting it to an angle. Just to add my two cents, I added a Doppler panel to the A-6E (on the navigator's right console) showing the angle between _heading_ and _true track_ which mostly corresponds to the wind induced drift. You can see the nasal code in data/Aircraft/A-6E/Nasal/doppler.nas. All the best, Alexis - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] slip angle (was: yaw)
> If that variable doesn't show a large slip angle when parked > in a crosswind, that's a nasty bug. > > You can easily enough check whether the FDM is calculating > this correctly by recomputing it yourself. It's just the > angle between the relative wind vector (projected onto the > XY plane) and the heading vector. It's trivial to calculate: > u = /fdm/jsbsim/velocities/u-aero-fps > v = /fdm/jsbsim/velocities/v-aero-fps > beta = atan2(v, u) > convert from radians to degrees if you wish > ... although (as mentioned above) for most purposes you're > better off using the (u,v) vector as a vector, rather than > converting it to an angle. At this time, JSBSim zeroes out the wind velocities while at rest on the ground, to prevent slippage. Jon - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] X52.xml file, and cheap rudder pedal :-p
Hi there, I modified X52.xml for Saitek X52 controller. You can download it from: http://macflightgear.sourceforge.net/home/development-notes/devnote-nov-22-2007 I also use the gas/brake pedal of WingMan formula force GP (Yes, a racing controller) for rudder control. you can also use its xml file from the link above. This file provides the control only for the pedal :-p I'll enjoy my gas/brake pedal by the time I get the real rudder pedal ;-) By the way, X52's wheel scrolls are recognized as button 1 and 2. This causes a problem like unexpectedly unlocking the parking brake, so be careful. Feedbacks and better ideas are always welcome. I want to add more functions to Mode2 / 3 but am not sure what functions to be added yet. Best, Tat - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Now only 3 steps for fgcom!
1.) fetch fgcom (a copy of a working iaxclient is inside) svn checkout svn://svn.dfn.de:/fgcom Optional: edit iaxclient/lib/Makefile To use oss emulation (recommended and the default for now) USE_PA_OSS=1 USE_PA_ALSA=0 USE_PA_JACK=0 AUDIO_ALSA=0 To use native alsa (WARNING: PTT won't work) USE_PA_OSS=0 USE_PA_ALSA=0 USE_PA_JACK=0 AUDIO_ALSA=1 To use portaudio alsa (WARNING: only if your card natively supports 8000Hz sample rate) USE_PA_OSS=0 USE_PA_ALSA=1 USE_PA_JACK=0 AUDIO_ALSA=0 2.) Compile iaxclient and fgcom. To do so, do the following: cd fgcom/src && make 3.) Install make install Regards, Holger -- # ## ## Holger Wirtz Phone : (+49 30) 884299-40 ## ## ## ### ## DFN-Verein Fax : (+49 30) 884299-70 ## ## ## Stresemannstr. 78E-Mail: [EMAIL PROTECTED] ## ## ## ## ### 10963 Berlin # ## ## ## GERMANY WWW : http://www.dfn.de GPG-Fingerprint: ABFA 1F51 DD8D 503C 85DC 0C51 E961 79E2 6685 9BCF - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 7 easy steps to get fgcom running
Holger Wirtz wrote: > Ok, I see the problem. And if the mic input is not used as a signal > source but a "silent stream"? That may simulate a PTT function without > hardware muting the mic. Yes, that would maintain the outbound stream for use as a clock source. > If I want to place two calls - one for intercom (without any muting) and > one for the ATC (with muting) I cannot mute the mic - only the data > stream of the VoIP-session... > > We will see. Thanks for your hint! First of all fgcom has to run with > the basic functionality on as many platforms as it can. Yes - there were a lot of people who were excited about it - but very few could actually build it hopefully these changers will open it up to a wider audience and you'll get a lot more feedback - it's certainly a very valuable feature. Jon - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 7 easy steps to get fgcom running
[...] > But: > > --- cut here --- > $ ./fgcom -f910.000 > ./fgcom - a communication radio based on VoIP with IAX/Asterisk > (c)2007 by H. Wirtz <[EMAIL PROTECTED]> > Version 1.0.1 build 36:37M > Using iaxclient library Version SVN 1075M > > IAXCLIENT: Fatal error: can't allocate memory > Segmentation fault > --- cut here --- Got it! Time for going home. I have just included the wrong iaxclient.h... Regards, Holger -- # ## ## Holger Wirtz Phone : (+49 30) 884299-40 ## ## ## ### ## DFN-Verein Fax : (+49 30) 884299-70 ## ## ## Stresemannstr. 78E-Mail: [EMAIL PROTECTED] ## ## ## ## ### 10963 Berlin # ## ## ## GERMANY WWW : http://www.dfn.de GPG-Fingerprint: ABFA 1F51 DD8D 503C 85DC 0C51 E961 79E2 6685 9BCF - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] slip angle (was: yaw)
On 11/22/2007 07:28 AM, LeeE wrote: > FWIW I also spotted that the coded hard-coded hud has problems around > headings of 180 deg so that if you are heading slightly to one side of > 180 deg and there's enough of a cross-wind to swing the direction > indicator to the other side of 180 deg it disappears, probably due to a > wrap-around type error. Sounds like a bug to me. It could be a bug in the FDM (which seems kinda unlikely) or it could be a bug in how the HUD uses the information. Bugs like this are par for the course when such things are quantified in the Euler-angle representation or the axis-angle representation. For a lumbering bomber you can get away with using a lame representation, but for something more maneuverable you would be much better off using the geometric algebra representation aka Clifford algebra aka multivectors aka quaternions. If you think you've got problems when the heading angle goes to 180 degrees, think about what happens when the pitch angle goes to ±90 degrees. > Yaw, to me means the difference between the direction that the aircraft > is pointing and the direction that it is moving. Moving? From what follows I gather that means moving relative to the airmass (not moving relative to the ground). It is important to think clearly and speak clearly, so as to not blur this distinction. > Flying directly into, > or with, any wind would produce no yaw but flying in a cross-wind would > produce yaw. When sitting stationary on the ground, any cross-winds > would result in an effective airspeed, so yes, I would expect there to > be a large yaw element under those circumstances. That's the slip angle. It is almost universally denoted by β (beta). It's in the tree as /orientation/side-slip-deg /orientation/side-slip-rad which are computed by the FDM. If that variable doesn't show a large slip angle when parked in a crosswind, that's a nasty bug. You can easily enough check whether the FDM is calculating this correctly by recomputing it yourself. It's just the angle between the relative wind vector (projected onto the XY plane) and the heading vector. It's trivial to calculate: u = /fdm/jsbsim/velocities/u-aero-fps v = /fdm/jsbsim/velocities/v-aero-fps beta = atan2(v, u) convert from radians to degrees if you wish ... although (as mentioned above) for most purposes you're better off using the (u,v) vector as a vector, rather than converting it to an angle. If the FDM is not calculating u-aero and v-aero properly and/or not calculating β properly and/or not putting β in /orientation/side-slip-rad then it is a very serious bug. Please don't call it the yaw angle. Please call it either slip angle or β. Note that the thing some pilots call a yaw string really should be called a /slip string/. http://www.av8n.com/how/htm/multi.html#sec-slip-string > As to what I would do with it - I assume you are asking out of > curiosity - it's needed to set the steering in tandam/quadracyle > landing gear aircraft so that they can take-off and land in > cross-winds. For that you need the motion of the airplane relative to the *ground* not relative to the airmass. That's different. That's why I asked what it would be used for. I'm not sure what that quantity should be called. It's not the yaw angle. I reckon it's just the difference between the slip angle and the wind-correction angle. This item you need to calculate for yourself, since it's not in the tree AFAICT. It's trivial to calculate u = /fdm/jsbsim/velocities/u-fps v = /fdm/jsbsim/velocities/v-fps angle = atan2(v, u) ... although (as mentioned above) for most purposes you're better off using the (u,v) vector as a vector, rather than converting it to an angle. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 7 easy steps to get fgcom running
Jon, On Thu, Nov 22, 2007 at 11:49:59AM +, Jon Stockill wrote: > Holger Wirtz wrote: > > > The PTT emulation is currently only a mic mute - very bad hack. I will > > try to fix this inside iaxclient (so that the audio stream is blocked > > inside the VoIP client) but I have to discuss this on the iaxclient-dev > > list. > > I think you'll run into problems if you do this - last time I was doing > lots of work on asterisk it used the incoming data stream to clock the > outgoing stream, resulting in you not receiving anything if you weren't > transmitting (enabling silence suppression on some phones would cause > this problem). Ok, I see the problem. And if the mic input is not used as a signal source but a "silent stream"? That may simulate a PTT function without hardware muting the mic. If I want to place two calls - one for intercom (without any muting) and one for the ATC (with muting) I cannot mute the mic - only the data stream of the VoIP-session... We will see. Thanks for your hint! First of all fgcom has to run with the basic functionality on as many platforms as it can. Regards, Holger -- # ## ## Holger Wirtz Phone : (+49 30) 884299-40 ## ## ## ### ## DFN-Verein Fax : (+49 30) 884299-70 ## ## ## Stresemannstr. 78E-Mail: [EMAIL PROTECTED] ## ## ## ## ### 10963 Berlin # ## ## ## GERMANY WWW : http://www.dfn.de GPG-Fingerprint: ABFA 1F51 DD8D 503C 85DC 0C51 E961 79E2 6685 9BCF - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 7 easy steps to get fgcom running
[...] > Please review and apply. [...] Ok, patches are added. Thanks again! My own version runs fine with my dynamic iaxclient-2.x library... I have to check why I get errors with static linking against the SVN checkout of the iaxclient. Regards, Holger -- # ## ## Holger Wirtz Phone : (+49 30) 884299-40 ## ## ## ### ## DFN-Verein Fax : (+49 30) 884299-70 ## ## ## Stresemannstr. 78E-Mail: [EMAIL PROTECTED] ## ## ## ## ### 10963 Berlin # ## ## ## GERMANY WWW : http://www.dfn.de GPG-Fingerprint: ABFA 1F51 DD8D 503C 85DC 0C51 E961 79E2 6685 9BCF - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 7 easy steps to get fgcom running
Hi Csaba,
On Thu, Nov 22, 2007 at 04:50:57AM +0100, Csaba Halász wrote:
> Requirements: alsa headers plus standard development tools (gcc, make,
> etc) Nothing fancy :)
>
> 1.) fetch a known good revision of iaxclient:
> svn co https://iaxclient.svn.sourceforge.net/svnroot/iaxclient/branches/1.0
> -r '{2007-07-21}' iaxclient
done.
> 2.) fetch fgcom into the same directory
> svn checkout svn://svn.dfn.de:/fgcom
:-) Not done
> 3.) edit iaxclient/lib/Makefile
>
> To use oss emulation (recommended for now)
>
> USE_PA_OSS=1
> USE_PA_ALSA=0
> USE_PA_JACK=0
> AUDIO_ALSA=0
done.
> 4.) make iaxclient (run make from the lib dir, no need to install)
done.
> 5.) patch fgcom with attached diff
done (just not commited to svn...)
> 6.) make fgcom
done.
But:
--- cut here ---
$ ./fgcom -f910.000
./fgcom - a communication radio based on VoIP with IAX/Asterisk
(c)2007 by H. Wirtz <[EMAIL PROTECTED]>
Version 1.0.1 build 36:37M
Using iaxclient library Version SVN 1075M
IAXCLIENT: Fatal error: can't allocate memory
Segmentation fault
--- cut here ---
OoooK. My PC thinks he is someone special... I have to
search for the problems.
Regards, Holger
--
# ## ## Holger Wirtz Phone : (+49 30) 884299-40
## ## ## ### ## DFN-Verein Fax : (+49 30) 884299-70
## ## ## Stresemannstr. 78E-Mail: [EMAIL PROTECTED]
## ## ## ## ### 10963 Berlin
# ## ## ## GERMANY WWW : http://www.dfn.de
GPG-Fingerprint: ABFA 1F51 DD8D 503C 85DC 0C51 E961 79E2 6685 9BCF
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Yaw
On Thursday 22 November 2007 12:03, John Denker wrote: > On 11/22/2007 04:58 AM, LeeE wrote: > > I've slowly been fixing the aircraft I've done that have been > > broken by updates in the FG code and I've noticed that we no longer > > seem to have access to the aircraft yaw in the property tree. > > > > When I first set up the rear-wheel steering for the B-52F I was > > told to use /orientation/side-slip-deg and not > > /orientation/yaw-deg, which is in the tree but doesn't seem to be > > updated. Using the side-slip-deg node worked ok though, so it > > seemed fine at the time. > > > > However, now that property only seems to give the side-slip in > > turns, which is perhaps correct, given it's name but that means > > we're back to not being able to access the yaw value. > > > > Co-incidentally, the original hard-coded hud still shows yaw but > > the newer xml hud does not - perhaps this is not too surprising if > > it's trying to use yaw-deg. > > > > Anyone know what's going on? > > First, please clarify what "yaw" means to you, and what you plan > to do with it once you have it. > -- For example, do you want the angle that would be indicated > (approximately) by a yaw string? That's properly called the > slip angle, and commonly called the sideslip angle, but should > not be called the yaw angle. This angle should be very large > when parked with a crosswind or tailwind; if not, that's a > nasty bug, and should be called a slip angle bug, not a yaw > bug. > -- Or do you want aircraft heading relative to North? That's > properly called the heading, and is available in the tree. > -- Or do you want the yaw /rate/ in degrees per second? That's > in the tree. Yaw, to me means the difference between the direction that the aircraft is pointing and the direction that it is moving. Flying directly into, or with, any wind would produce no yaw but flying in a cross-wind would produce yaw. When sitting stationary on the ground, any cross-winds would result in an effective airspeed, so yes, I would expect there to be a large yaw element under those circumstances. As to what I would do with it - I assume you are asking out of curiosity - it's needed to set the steering in tandam/quadracyle landing gear aircraft so that they can take-off and land in cross-winds. I would also use it for off-setting terrain elevation look-ahead scans, so that I'm scanning the terrain that I will actually be passing over and not the terrain slightly to one side of the true course. FWIW I also spotted that the coded hard-coded hud has problems around headings of 180 deg so that if you are heading slightly to one side of 180 deg and there's enough of a cross-wind to swing the direction indicator to the other side of 180 deg it disappears, probably due to a wrap-around type error. LeeE - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Yaw
On 11/22/2007 04:58 AM, LeeE wrote: > I've slowly been fixing the aircraft I've done that have been broken by > updates in the FG code and I've noticed that we no longer seem to have > access to the aircraft yaw in the property tree. > > When I first set up the rear-wheel steering for the B-52F I was told to > use /orientation/side-slip-deg and not /orientation/yaw-deg, which is > in the tree but doesn't seem to be updated. Using the side-slip-deg > node worked ok though, so it seemed fine at the time. > > However, now that property only seems to give the side-slip in turns, > which is perhaps correct, given it's name but that means we're back to > not being able to access the yaw value. > > Co-incidentally, the original hard-coded hud still shows yaw but the > newer xml hud does not - perhaps this is not too surprising if it's > trying to use yaw-deg. > > Anyone know what's going on? First, please clarify what "yaw" means to you, and what you plan to do with it once you have it. -- For example, do you want the angle that would be indicated (approximately) by a yaw string? That's properly called the slip angle, and commonly called the sideslip angle, but should not be called the yaw angle. This angle should be very large when parked with a crosswind or tailwind; if not, that's a nasty bug, and should be called a slip angle bug, not a yaw bug. -- Or do you want aircraft heading relative to North? That's properly called the heading, and is available in the tree. -- Or do you want the yaw /rate/ in degrees per second? That's in the tree. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 7 easy steps to get fgcom running
Holger Wirtz wrote: > The PTT emulation is currently only a mic mute - very bad hack. I will > try to fix this inside iaxclient (so that the audio stream is blocked > inside the VoIP client) but I have to discuss this on the iaxclient-dev > list. I think you'll run into problems if you do this - last time I was doing lots of work on asterisk it used the incoming data stream to clock the outgoing stream, resulting in you not receiving anything if you weren't transmitting (enabling silence suppression on some phones would cause this problem). Jon - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Yaw
Hi all, I've slowly been fixing the aircraft I've done that have been broken by updates in the FG code and I've noticed that we no longer seem to have access to the aircraft yaw in the property tree. When I first set up the rear-wheel steering for the B-52F I was told to use /orientation/side-slip-deg and not /orientation/yaw-deg, which is in the tree but doesn't seem to be updated. Using the side-slip-deg node worked ok though, so it seemed fine at the time. However, now that property only seems to give the side-slip in turns, which is perhaps correct, given it's name but that means we're back to not being able to access the yaw value. Co-incidentally, the original hard-coded hud still shows yaw but the newer xml hud does not - perhaps this is not too surprising if it's trying to use yaw-deg. Anyone know what's going on? LeeE - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
