Re: [Flightgear-devel] AN-225 patch
On Thursday 24 May 2007 19:40, Joacim Persson wrote: Patch attached. Added steering to the four aftmost main gear axels -- with animations! Found out just the other day that the AN-225 indeed steers on some of the main gear wheels. The minimum turning radius is a wild guess however. (Assumed a 45 deg average on the nose gears.) It now turns (quite effortlessly) around a point straight out to the side from the second main gear axel (nr 2 of the 3 non-steerable main gear axels), with a minimum radius of 25.75 meters. (i.e. near engine nr 1 or 6) The option squared was removed on steering. (Squaring radians messed up my calculations of the turning angle of the respective wheels. Not that it's a perfect calculation now either.) Ground wheel steering should, rather, not be connected to directly the rudder pedals I think... Also added transition-time(s) for the steering. Hi Joachim, Yes, the AN-225 does incorporate steering on some of the main units - according to http://www.air-and-space.com/Antonov%20An-225%20Mriya.htm it's the rear four sets. This site also has some nice pics of the main gear, which show that the front three and rear four units are different, if anyone would like to make more detailed and accurate main gear units:) The AN-225 also has a max taxiing weight but I couldn't find the doc which stated what it was:( Basically, it means that the AN-225 cannot make ground turns above this weight and so for mtow takeoffs it has to be lined up on the runway and then loaded. Unlike the AN-124, from which it was developed, it was never intended for short-field operation. One new 'fact' I found while trying to find the max taxi weight was that the takeofff run at mtow is 3500m (11500ft). I think the FG AN-225, at mtow, gets off the ground a little shorter than this - iirc, I tried to tune it so that it could just, and only just, get over the hills after leaving on KSFO 27, figuring that it would be in the right ball park and that it had to work at the default FG airport. LeeE - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] patch for osgViewer: more keys supported
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stuart Buchanan wrote:
I think you need a break statement on the delete line, otherwise it'll just
get picked up as a left key press.
-Stuart
Whoops! Right you are. Here's the amended patch.
- Original Message
From: Tim Moore [EMAIL PROTECTED]
To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net
Sent: Friday, 25 May, 2007 6:41:07 AM
Subject: [Flightgear-devel] patch for osgViewer: more keys supported
Hi,
This adds support for the keypad and the ever-important backspace and
delete (!) to the osgViewer code.
Tim
___
Yahoo! Mail is the world's favourite email. Don't settle for less, sign
up for
your free account today
http://uk.rd.yahoo.com/evt=44106/*http://uk.docs.yahoo.com/mail/winter07.html
- -
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
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)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFGVpameDhWHdXrDRURAqJ8AJ9HvoVxGsgwvcIcwd4nQG8d7KBHBQCgu+VY
VHfQwb6zM9A412kGXqci15o=
=layk
-END PGP SIGNATURE-
Index: src/Main/FGManipulator.cxx
===
RCS file: /var/cvs/FlightGear-0.9/source/src/Main/FGManipulator.cxx,v
retrieving revision 1.3
diff -d -u -r1.3 FGManipulator.cxx
--- src/Main/FGManipulator.cxx 23 May 2007 17:57:05 - 1.3
+++ src/Main/FGManipulator.cxx 25 May 2007 05:38:19 -
@@ -152,6 +152,8 @@
switch (key) {
case osgGA::GUIEventAdapter::KEY_Escape: key = 0x1b; break;
case osgGA::GUIEventAdapter::KEY_Return: key = '\n'; break;
+case osgGA::GUIEventAdapter::KEY_BackSpace: key = '\b'; break;
+case osgGA::GUIEventAdapter::KEY_Delete: key = 0x7f; break;
case osgGA::GUIEventAdapter::KEY_Left: key = PU_KEY_LEFT; break;
case osgGA::GUIEventAdapter::KEY_Up: key = PU_KEY_UP;break;
case osgGA::GUIEventAdapter::KEY_Right:key = PU_KEY_RIGHT; break;
@@ -173,6 +175,17 @@
case osgGA::GUIEventAdapter::KEY_F10: key = PU_KEY_F10; break;
case osgGA::GUIEventAdapter::KEY_F11: key = PU_KEY_F11; break;
case osgGA::GUIEventAdapter::KEY_F12: key = PU_KEY_F12; break;
+case osgGA::GUIEventAdapter::KEY_KP_0: key = 364; break;
+case osgGA::GUIEventAdapter::KEY_KP_1: key = 363; break;
+case osgGA::GUIEventAdapter::KEY_KP_2: key = 359; break;
+case osgGA::GUIEventAdapter::KEY_KP_3: key = 361; break;
+case osgGA::GUIEventAdapter::KEY_KP_4: key = 356; break;
+case osgGA::GUIEventAdapter::KEY_KP_5: key = 309; break;
+case osgGA::GUIEventAdapter::KEY_KP_6: key = 358; break;
+case osgGA::GUIEventAdapter::KEY_KP_7: key = 362; break;
+case osgGA::GUIEventAdapter::KEY_KP_8: key = 357; break;
+case osgGA::GUIEventAdapter::KEY_KP_9: key = 360; break;
+case osgGA::GUIEventAdapter::KEY_KP_Enter: key = 269; break;
}
modifiers = osgToFGModifiers(ea.getModKeyMask());
currentModifiers = modifiers;
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] transition-time, Was: AN-225 patch
On Thu, 24 May 2007, Andy Ross wrote: Joacim Persson wrote: README.yasim says the semi-deprecated transition-time is Time in seconds to slew through input range. I'm not quite sure what it is, but it's not that. ;) It's coded to assume that the input range is 0-1. From experimenting with it, I gathered it also assumes an /output/ range of the same scale. To have a movement over one second with an input range of 0--1 and an output range of 0.0--0.1 (using src/dst tweaks), the transition-time value have to be set 10 seconds. From the docs, however, one would expect the value to stay at 1.0 seconds regardless of how the output range is tweaked. So docs and code doesn't agree here and that may cause some confusion for the users. It was really written for landing gear. If you want to model hydraulic delays (which is what I think is happening here) you'd probably be happier with some Nasal anyway. Thus the semi-deprecated note: this feature still works as intended, but there are far more robust ways to solve the same problem in the modern environment. Yes synchronising multiple steering wheels accurately -- make all the 20 steerable wheel hubs point at exactly the same spot on the tarmac throughout the full interval -- would take scripting anyway, involving atan() and other evil trigonometric chants. ;) - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: source/src/Traffic TrafficMgr.cxx, 1.13.2.3, 1.13.2.4
* Durk Talsma -- 5/25/2007 9:20 AM: Log Message: Don't fix what ain't broke. - runCount = 0; + //runCount = 0 I explained why I reset that counter. Could you explain why you changed it back? This counter wasn't my idea, but yours. It could/should have been used to make the traffic manager stuff not run in every frame. (Traffic does probably not have to be reconsidered 60 times per second, one would assume.) Before my change the whole counter setup was dead code, and now you made it dead code again. Why not remove it, if it has no purpose? m. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] AN-225 patch
On Fri, 25 May 2007, leee wrote: http://www.air-and-space.com/Antonov%20An-225%20Mriya.htm it's the rear four sets. This site also has some nice pics of the main gear, which show that the front three and rear four units are different, if anyone would like to make more detailed and accurate main gear units:) (I can barely make a cube in Blender -- so don't look at me ;) I suspect it can also kneel like the An-124. Looks like that on some of the pictures too. But the 124 has a different setup with the main gear steering, with the two forward axels steerable instead. And rumor has it they are working on finishing the second 225 down in Kiev now. The one they have in operation is booked up most of the time. The AN-225 also has a max taxiing weight but I couldn't find the doc which stated what it was:( Basically, it means that the AN-225 cannot make ground turns above this weight and so for mtow takeoffs it has to be lined up on the runway and then loaded. Unlike the AN-124, from which it was developed, it was never intended for short-field operation. That information ought to be in the 2001 civil type certificate. (which may have been published in Ukranian only though) I found the type certificate number for it: (in latin-faked kyrillic) CTOK200-AH-225, but not the document itself. (well, I can't google in non-latin alphabets) We should add some more hard points to it. One can easily dip a wingtip or engine in the ground now by turning too hard at too high taxi speed. Max taxi speed is probably also specified in the type cert. And CG limits, and other goodies... - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 737-300 FDM patch for gear location
Martin Spott wrote: Berndt, Jon S wrote: Reagan Thomas wrote: Short version: Here is the link to an updated patch which (a) corrects the VRP precisely as Anders did with the F80C while removing the somewhat incorrect Z offset in /Models and (b) adds several contact points. It does not change any other pre-existing gear, etc coordinates: The VRP is supposed to be a way for the 3D modeler and the FDM modeler to agree on a way to make sure that the 3D model is placed exactly where it is supposed to be placed. Did you get to an agreement wether the patch is correct or not ? Martin. To the best of my newbie ability, I think I've gotten it correct. However, I've moved the patch to a different link :( New URL: http://139.78.95.188/flightgear/VRP/737-300/ FYI I've identified about 30 aircraft that look like they might have similar issues. Most of them I have only tagged because I found that the origin in the 3D model was not at the nose and didn't find complementary offsets in loading the model or VRP. I've been right about all but one that I've checked into further so far, but that doesn't mean much. If anyone else would like to peruse this (probably flawed) list: http://139.78.95.188/flightgear/AircraftAlign.txt -- Reagan Thomas - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] PATCH: building 0.9.11-pre1 on ppc
2007/5/24, Andy Ross [EMAIL PROTECTED]: Can you provide more details about your platform? I was under the impression that OS X on PowerPC used the __ppc__ symbol, but I don't have a box to test against. If your compiler is gcc, can you post the results of: echo | gcc -E -dM - Yes I can. I'm building RPM on SUSE Linux. + echo + gcc -E -dM - #define __DBL_MIN_EXP__ (-1021) #define __FLT_MIN__ 1.17549435e-38F #define __CHAR_BIT__ 8 #define __WCHAR_MAX__ 2147483647 #define __DBL_DENORM_MIN__ 4.9406564584124654e-324 #define __FLT_EVAL_METHOD__ 0 #define __DBL_MIN_10_EXP__ (-307) #define __FINITE_MATH_ONLY__ 0 #define __GNUC_PATCHLEVEL__ 3 #define __SHRT_MAX__ 32767 #define __LDBL_MAX__ 1.79769313486231580793728971405301e+308L #define __UINTMAX_TYPE__ long long unsigned int #define __linux 1 #define __CHAR_UNSIGNED__ 1 #define __LDBL_MAX_EXP__ 1024 #define __linux__ 1 #define __SCHAR_MAX__ 127 #define __USER_LABEL_PREFIX__ #define __STDC_HOSTED__ 1 #define __LDBL_HAS_INFINITY__ 1 #define __DBL_DIG__ 15 #define __FLT_EPSILON__ 1.19209290e-7F #define _CALL_SYSV 1 #define __LDBL_MIN__ 2.00416836000897277799610805135016e-292L #define __unix__ 1 #define __DECIMAL_DIG__ 33 #define __gnu_linux__ 1 #define __LDBL_HAS_QUIET_NAN__ 1 #define __GNUC__ 4 #define __DBL_MAX__ 1.7976931348623157e+308 #define __DBL_HAS_INFINITY__ 1 #define __DBL_MAX_EXP__ 1024 #define __LONG_LONG_MAX__ 9223372036854775807LL #define __PPC__ 1 #define __GXX_ABI_VERSION 1002 #define __FLT_MIN_EXP__ (-125) #define __DBL_MIN__ 2.2250738585072014e-308 #define __DBL_HAS_QUIET_NAN__ 1 #define __REGISTER_PREFIX__ #define __NO_INLINE__ 1 #define _ARCH_PPC 1 #define __FLT_MANT_DIG__ 24 #define __VERSION__ 4.1.3 20070430 (prerelease) (SUSE Linux) #define __BIG_ENDIAN__ 1 #define __powerpc__ 1 #define unix 1 #define __SIZE_TYPE__ unsigned int #define __ELF__ 1 #define __FLT_RADIX__ 2 #define __LDBL_EPSILON__ 4.94065645841246544176568792868221e-324L #define __LDBL_DIG__ 31 #define __FLT_HAS_QUIET_NAN__ 1 #define __FLT_MAX_10_EXP__ 38 #define __LONG_MAX__ 2147483647L #define __FLT_HAS_INFINITY__ 1 #define __unix 1 #define _BIG_ENDIAN 1 #define linux 1 #define __PPC 1 #define __LDBL_MANT_DIG__ 106 #define __WCHAR_TYPE__ long int #define __FLT_DIG__ 6 #define __powerpc 1 #define __INT_MAX__ 2147483647 #define __LONG_DOUBLE_128__ 1 #define __FLT_MAX_EXP__ 128 #define __DBL_MANT_DIG__ 53 #define __WINT_TYPE__ unsigned int #define __LDBL_MIN_EXP__ (-968) #define __LDBL_MAX_10_EXP__ 308 #define __DBL_EPSILON__ 2.2204460492503131e-16 #define PPC 1 #define powerpc 1 #define __INTMAX_MAX__ 9223372036854775807LL #define __FLT_DENORM_MIN__ 1.40129846e-45F #define __FLT_MAX__ 3.40282347e+38F #define __FLT_MIN_10_EXP__ (-37) #define __INTMAX_TYPE__ long long int #define __GNUC_MINOR__ 1 #define __DBL_MAX_10_EXP__ 308 #define __LDBL_DENORM_MIN__ 4.94065645841246544176568792868221e-324L #define __STDC__ 1 #define __PTRDIFF_TYPE__ int #define __LDBL_MIN_10_EXP__ (-291) #define __GNUC_GNU_INLINE__ 1 Regards Ladislav. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] PATCH: building 0.9.11-pre1 on ppc
Ladislav Michnovič wrote: 2007/5/24, Andy Ross [EMAIL PROTECTED]: Can you provide more details about your platform? I was under the impression that OS X on PowerPC used the __ppc__ symbol, but I don't have a box to test against. If your compiler is gcc, can you post the results of: echo | gcc -E -dM - Yes I can. I'm building RPM on SUSE Linux. Ah, OK. Apparently GCC/linux and the OS X folks picked a different set of architecture symbols. Should be fixed in CVS (both branches, and in the Nasal upstream). Andy - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] patch for osgViewer and statistics
Nick Warne wrote: On Friday 25 May 2007 03:59:55 Laurence Vanek wrote: ./configure CXXFLAGS=-O3 ... If you wish to include further flags, they need to enclosed in double quotes: ./configure CXXFLAGS=-march=athlon-tbird -O3 This is my full FG configure option: ./configure CXXFLAGS=-march=athlon-tbird -O3 --prefix=/usr --enable-sdl Nick wow! I can confirm the frame rate increase on this system as well using the above suggestions. It approx. doubled my frame rates. thank you gentlemen. Yes, wow. The 'cmake -i .' is what done it for me - all this time I thought you had to especially build a debug OSG, not the other way around. Confirmed here too. Seems like they have their defaults the wrong way round, but now I've changed it I'm seeing framerates way beyond anything ever achieved with plib. It looks like Release mode includes -O3 optimisation. You'll only need to play with the compiler flags if you want any extra architecture specific optimisations (probably best avoided for anyone building packages). -- Jon Stockill [EMAIL PROTECTED] - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] patch for osgViewer and statistics
On Friday 25 May 2007 03:59:55 Laurence Vanek wrote: ./configure CXXFLAGS=-O3 ... If you wish to include further flags, they need to enclosed in double quotes: ./configure CXXFLAGS=-march=athlon-tbird -O3 This is my full FG configure option: ./configure CXXFLAGS=-march=athlon-tbird -O3 --prefix=/usr --enable-sdl Nick wow! I can confirm the frame rate increase on this system as well using the above suggestions. It approx. doubled my frame rates. thank you gentlemen. Yes, wow. The 'cmake -i .' is what done it for me - all this time I thought you had to especially build a debug OSG, not the other way around. Nick - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] PATCH: building 0.9.11-pre1 on ppc
2007/5/25, Andy Ross [EMAIL PROTECTED]: Ah, OK. Apparently GCC/linux and the OS X folks picked a different set of architecture symbols. Should be fixed in CVS (both branches, and in the Nasal upstream). Andy O.K. Thanks. Ladislav. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: source/src/Traffic TrafficMgr.cxx, 1.13.2.3, 1.13.2.4
On Friday 25 May 2007 10:37, Melchior FRANZ wrote: * Durk Talsma -- 5/25/2007 9:20 AM: Log Message: Don't fix what ain't broke. - runCount = 0; + //runCount = 0 I explained why I reset that counter. Could you explain why you changed it back? This counter wasn't my idea, but yours. It could/should have been used to make the traffic manager stuff not run in every frame. (Traffic does probably not have to be reconsidered 60 times per second, one would assume.) Before my change the whole counter setup was dead code, and now you made it dead code again. Why not remove it, if it has no purpose? Hi Melchior, I barely managed to get this fix into CVS before heading out to work this morning, making sure above all that this wouldn't get into the final release, as the side effects will not be favorable. So, sorry I didn't have time for a more elaborate explanation. ;-) I added the counter to skip the first number of frames (more of less arbitrarily set to 1000) after initialization, because the AI system needs some time until all the right weather is loaded. If not the first AI aircraft may taxi to a different runway than those departing later. Once frame count is reaching 1000, whether is usually initialized, and from that point on the update code needs to run once everyframe, otherwise it's going to take much too long between the processing of two successive aircraft. Admittedly, the skipping the first 1000 frames is rather arbitrary, and should probably be replaced by checking a metar related property, but that's a different issue. :-) Cheers, Durk - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] patch for osgViewer: more keys supported
Hi Tim, On Friday 25 May 2007, Tim Moore wrote: This adds support for the keypad and the ever-important backspace and delete (!) to the osgViewer code. Thanks applied! Greetings Mathias - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] small thread safe patch
Hi, On Thursday 24 May 2007, Tim Moore wrote: OSG reference counting doesn't need to be thread safe, even in the multi-threaded OSG modes, unless you're doing something very tricky. In any event, it shouldn't be turned on in the model reader initialization. Please don't! It is there by intention. I have a multithreaded viewer in the works and for that it is still useful to have thread safe reference counting in place. Also Having the database pager set up once we have the osgviewer code settled we will do model loading in a thread that runs in parallel to the rest of the application. And remember that we share some data across models. That model cloning will need thread safe reference counting. It does not cost much OTOH. Greetings Mathias - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
