Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: data/Aircraft/Instruments-3d/zkv500 MainScreens.nas, 1.7, 1.8 TaskScreens.nas, 1.3, 1.4 TurnpointScreens.nas, 1.5, 1.6
On 9 Dec 2009, at 00:25, Sébastien MARQUE wrote: I've got an suggestion for the gps code: a command nearest-coord (or better name) which would give nearest navaid for arbitrary coordinates, given by scratch/longitude-deg and scratch/latitude-deg. It will allow to implement a simple navaid-to-navaid flight-plan in a FG session. I tried already months ago, but I can't get it to work properly. This doesn't even need a new command - I shall just update the code so that if you optionally set a valid lat/lon when executing 'nearest', it uses that position instead of the current GPS position. I will hopefully get this into CVS today. If it's useful, there's several commands that could be updated to have this behaviour. Regards, James -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [GIT] misc fixes
Csaba Halász wrote: 2) fix a crash in SGSoundMgr::stop() due to invalid iterator usage: http://gitorious.org/~jester/fg/jesters-sg-clone/commit/12604fb231631252b13af1338020926e2ca1a605 Thanks to Vivian for reporting. That one still bites me once in a while. I don't like itterators all that much because of it. Thanks for reporting (and the fix). Erik -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Debug Assertion Failed in Sample_opneal.hxx
Alan Teeder wrote: Eric Yes, both are 32 bit with identical Visual C++ 2008 (VC09) and Flightgear library setups. OpenALand Alut are from the Creative site. The Vista laptop is Intel dual core, the XP box is an ancient Athlon. I've updated the code slightly to not assign the sample data to the SGSoundSample class in case of loading a file. Could you test if this solves the problem for you? Erik -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Compile Simgear error
From: hujingfei...@sina.com Compile Simgear error Tools: Visual studio 2008 ... .../sgmisc.hxx(29) : warning C4002: “min”宏的实参太多 ... Hi Hu, I am not sure this will solve all your problems, but certainly those related to 'min' and 'max', which may be all of them... You must define NOMINMAX in the Visual Studio IDE - In Properties - Configuration Properties - C/C++ - Preprocessor - Preprocessor Definitions just add NOMINMAX to the semicolon (;) separated list... This list should also include things like _USE_MATH_DEFINES; _CRT_SECURE_NO_DEPRECIATE;_CRT_SECURE_NO_WARNINGS;HAVE_CONFIG_H as well as this NOMINMAX And please note the simgear cvslogs is _NOT_ the correct place for user messages. Use this flightgear-devel@lists.sourceforge.net or flightgear-us...@lists.sourceforge.net Hope this helps... Regards, Geoff. -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] GPS find nearest.
On Wed, 2009-12-09 at 08:27 +, James Turner wrote: I second this. Something I was playing around with a few months back I thought, if only I could find the nearest VOR/NDB/FIX/APT to some point that I am not at but will be in the near future, unfortunately I've forgotten what it was I was trying to do, but I'm sure it was a good idea ;) Off-topic is there anyway in Nasal to find the ILS frequencies and optionally the name, for a particular airport and runway? S. On 9 Dec 2009, at 00:25, Sébastien MARQUE wrote: I've got an suggestion for the gps code: a command nearest-coord (or better name) which would give nearest navaid for arbitrary coordinates, given by scratch/longitude-deg and scratch/latitude-deg. It will allow to implement a simple navaid-to-navaid flight-plan in a FG session. I tried already months ago, but I can't get it to work properly. This doesn't even need a new command - I shall just update the code so that if you optionally set a valid lat/lon when executing 'nearest', it uses that position instead of the current GPS position. I will hopefully get this into CVS today. If it's useful, there's several commands that could be updated to have this behaviour. Regards, James -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Debug Assertion Failed in Sample_opneal.hxx
Eric No improvement, sorry :-( To compile I had to remove one of the = in line 440 of soundmgr_openal.cxx (void *sample_data == NULL;) . On the problematic Vista laptop, when I run fgfs release with --disable-sound there is no problem. Once sound is enabled the program fails. In debug the program now fails in sample_openal.cxx at line 477 (if(sample-is_file() ) free (sample_data) ;) , reporting a possible heap corruption. The XP box continues to perform with fgfs release as expected, complete with sound. However the XP box with fgfs debug fails at the same point as the Vista laptop. On the bright side (always look for that) I no longer have failures on either machine when Flightgear is exited. Alan -- From: Erik Hofman e...@ehofman.com Sent: Wednesday, December 09, 2009 10:13 AM To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] Debug Assertion Failed in Sample_opneal.hxx at line Alan Teeder wrote: Eric Yes, both are 32 bit with identical Visual C++ 2008 (VC09) and Flightgear library setups. OpenALand Alut are from the Creative site. The Vista laptop is Intel dual core, the XP box is an ancient Athlon. I've updated the code slightly to not assign the sample data to the SGSoundSample class in case of loading a file. Could you test if this solves the problem for you? Erik -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] GPS find nearest.
On 9 Dec 2009, at 13:47, Scott Hamilton wrote: Something I was playing around with a few months back I thought, if only I could find the nearest VOR/NDB/FIX/APT to some point that I am not at but will be in the near future, unfortunately I've forgotten what it was I was trying to do, but I'm sure it was a good idea ;) Yep, agreed, it's an obvious thing to support. And easy to do, as well! Off-topic is there anyway in Nasal to find the ILS frequencies and optionally the name, for a particular airport and runway? Yes, the airportinfo function returns you a Nasal hash with all this and more. Also, although it's not exposed in the current GPS GUI dialog, when you search for an airport, the GPS scratch data contains the runways, including ILS frequencies, headings and names. You can see them in the property browser. James -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Debug Assertion Failed in Sample_opneal.hxx
Alan Teeder wrote: In debug the program now fails in sample_openal.cxx at line 477 (if(sample-is_file() ) free (sample_data) ;) , reporting a possible heap corruption. That's virtually impossible. You might check the code if you see a problem but this starts to look like a compiler bug. MSV9 seemed to work for everybody who uses it. Erik -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] releases +- bugs
On Tue, 8 Dec 2009, dave perry wrote: On 12/01/2009 11:38 AM, John Denker wrote: On 12/01/2009 11:19 AM, Heiko Schulz wrote: To your note: So the c172p has now: -struts animation The reported bug http://www.av8n.com/fly/fgfs/htm/bug-list.htm#bug-x1768 concerns the nutcracker, which as of 1 Dec 2009 looks quite weird because it doesn't fold; it just gets shoved rigidly up into the cowling. I just submitted a patch that animates the c172p nose gear nutcracker so it folds as the strut is compressed. It's called an oleo strut. :) g. -- Proud owner of F-15C 80-0007 http://www.f15sim.com - The only one of its kind. ScarletDME - The red hot Data Management Environment A Multi-Value database for the masses, not the classes. http://www.scarletdme.org - Get it _today_! -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Inadvertant change to c172p p_factor
I just noticed that the patch to animate the c172p nose gear strut scissors that I sent to James Turner to commit also picked up a local change I made to decrease the p_factor. RCS file: /var/cvs/FlightGear-0.9/data/Aircraft/c172p/c172p.xml,v retrieving revision 1.24 diff -u -p -r1.24 c172p.xml --- c172p.xml6 Dec 2009 19:12:23 -1.24 +++ c172p.xml9 Dec 2009 03:31:22 - @@ -209,7 +209,7 @@ yaw 0.0 /yaw /orient sense 1 /sense - p_factor 10 /p_factor + p_factor 5 /p_factor /thruster /engine tank type=FUEL !-- Tank number 0 -- Index: initfile.xml === This can be changed back to 10 easily. I have many hours in real c172's and the value of p_factor = 10 feels to me unrealistic. That is why my local copy was changed to p_factor = 5. Regards, Dave P. -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] releases +- bugs
I am not exactly sure what you guys are talking about with the nut cracker reference, but the Oleo Strut the vertical assembly with compressed air (or Nitrogen) and hydraulic oil. There is a piston assembly and a metered orifice arrangement, allowing this assembly to act as a shock-absorbing device. The scissors assembly is a torque link, and helps dampen/resist torque moments imposed on the nose landing gear. AP school was a while ago for me, but generally speaking, I believe the torque link is considered a part of the entire Oleo assembly. TB On Dec 9, 2009, at 8:13 AM, Gene Buckle wrote: On Tue, 8 Dec 2009, dave perry wrote: On 12/01/2009 11:38 AM, John Denker wrote: On 12/01/2009 11:19 AM, Heiko Schulz wrote: To your note: So the c172p has now: -struts animation The reported bug http://www.av8n.com/fly/fgfs/htm/bug-list.htm#bug-x1768 concerns the nutcracker, which as of 1 Dec 2009 looks quite weird because it doesn't fold; it just gets shoved rigidly up into the cowling. I just submitted a patch that animates the c172p nose gear nutcracker so it folds as the strut is compressed. It's called an oleo strut. :) g. -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] missing 737-BmiBaby referenced by AI traffic file
Relaying a report from IRC (by blucher): data/AI/Traffic/B/BMI.xml in cvs is referencing Aircraft/737/737-BmiBaby.xml which is not in cvs. -- Csaba/Jester -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] releases +- bugs
A quick follow-up on my previous post... While researching this a bit more, I found a very interesting engineering document on the mechanics of landing gear systems: http://www.mecheng.adelaide.edu.au/~marjom01/Aeronautical%20Engineering%20Projects/2006/group11.pdf The PDF is just over 6mb in size, but well worth the download. There are very good descriptions of the mechanics involved with different gear systems--and included is some c172-specific information as well, in Chapter 8 (Page 38). The author also shows a calculation showing that a typical nose strut in a 172 compresses about 9.3 on landing. TB On Dec 9, 2009, at 9:02 AM, Thomas Betka wrote: I am not exactly sure what you guys are talking about with the nut cracker reference, but the Oleo Strut the vertical assembly with compressed air (or Nitrogen) and hydraulic oil. There is a piston assembly and a metered orifice arrangement, allowing this assembly to act as a shock-absorbing device. The scissors assembly is a torque link, and helps dampen/resist torque moments imposed on the nose landing gear. AP school was a while ago for me, but generally speaking, I believe the torque link is considered a part of the entire Oleo assembly. TB On Dec 9, 2009, at 8:13 AM, Gene Buckle wrote: On Tue, 8 Dec 2009, dave perry wrote: On 12/01/2009 11:38 AM, John Denker wrote: On 12/01/2009 11:19 AM, Heiko Schulz wrote: To your note: So the c172p has now: -struts animation The reported bug http://www.av8n.com/fly/fgfs/htm/bug-list.htm#bug-x1768 concerns the nutcracker, which as of 1 Dec 2009 looks quite weird because it doesn't fold; it just gets shoved rigidly up into the cowling. I just submitted a patch that animates the c172p nose gear nutcracker so it folds as the strut is compressed. It's called an oleo strut. :) g. -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] releases +- bugs
On 12/01/2009 11:38 AM, John Denker wrote: On 12/01/2009 11:19 AM, Heiko Schulz wrote: To your note: So the c172p has now: -struts animation The reported bug http://www.av8n.com/fly/fgfs/htm/bug-list.htm#bug-x1768 concerns the nutcracker, which as of 1 Dec 2009 looks quite weird because it doesn't fold; it just gets shoved rigidly up into the cowling. I just submitted a patch that animates the c172p nose gear nutcracker so it folds as the strut is compressed. I wrote a wiki article some time ago to do the animation of the nutcracker oleo scissor without the need for nasal: http://wiki.flightgear.org/index.php/Howto:_Animate_gear_scissors Enjoy, Torsten -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] missing 737-BmiBaby referenced by AI traffic file
Hi Csaba, On Wednesday 09 December 2009 04:56:12 pm Csaba Halász wrote: Relaying a report from IRC (by blucher): data/AI/Traffic/B/BMI.xml in cvs is referencing Aircraft/737/737-BmiBaby.xml which is not in cvs. Thanks for the report. It's correct that not all the liveries that are included in the EHAM traffic demo are done yet. IIRC, I still have to do approx 10-15 repaints of AI aircraft. I'm not sure whether BmiBaby is still missing as a repaint, of whether this is a typo in referencing to this file. I'll put it on my todo list. Cheers, Durk -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] fgfs compile error, today's cvs
I am getting the following error compiling fgfs from cvs today on two different systems. $ make Making all in tests make[1]: Entering directory `/home/dad/source-osg/source-fgfs/tests' make[1]: *** No rule to make target `est-epsilon.c', needed by `est-epsilon.o'. Stop. make[1]: Leaving directory `/home/dad/source-osg/source-fgfs/tests' make: *** [all-recursive] Error 1 $ -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] fgfs compile error, today's cvs
I'm not sure the best way to handle this but if you start at the top and run ./autogen.sh followed by ./configure --options I think the error will be cleaned up. Switching files from abc.c to abc.cxx confuses the dependency tracking of automake. Curt. On Wed, Dec 9, 2009 at 7:33 PM, dave perry skida...@mindspring.com wrote: I am getting the following error compiling fgfs from cvs today on two different systems. $ make Making all in tests make[1]: Entering directory `/home/dad/source-osg/source-fgfs/tests' make[1]: *** No rule to make target `est-epsilon.c', needed by `est-epsilon.o'. Stop. make[1]: Leaving directory `/home/dad/source-osg/source-fgfs/tests' make: *** [all-recursive] Error 1 $ -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Curtis Olson: http://baron.flightgear.org/~curt/ -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
