[Flightgear-devel] Velocity-XL - kx165.ac, xml and png
Tortoise CVS (Windows XP) reports the following error with these 3 files Cvs update: move away Aircraft/Velocity-XL/Models/Interior/Panel/Instruments/kx165/KX165.ac,it is in the way Is this perhaps due to an upper-lower case windows file-name conflict? Alan -- The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Velocity-XL - kx165.ac, xml and png
Michael. Thanks Have tried deleting those files, and even deleting the whole Velocity-XL aircraft folder, but either way Tortoise CVS still reports the same error. The problem is only there for these 3 files, the rest of Data is OK. Alan -- The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Reverse for 737-300 model (patch)
-Original Message- From: Bertrand Coconnier [mailto:bcoco...@gmail.com] So I can hardly believe there is no indication of the correct deployment of the T/Rs on the cockpit panel. Cheers, Bertrand. -- It is quite obvious to the pilot when he has selected reverse thrust. The whole of the top of the throttle levers is opened backwards. It isn't an insignificant toggle switch which could have been inadvertently operated. The only need for a panel indication is to show that the reverse-thrust buckets have deployed (or not). Similarly it is not usual to have a panel indication of the control column or the rudder pedals, although some modern aircraft may indicate the control surface positions. Flightsim on a PC without a complete cockpit is a different thing altogether, and here an indication would have practical benefit. Alan -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [Simgear-cvslogs] CVS:source/simgear/propsprops.cxx, 1.44, 1.45 props.hxx, 1.32, 1.33
Thanks for the quick reply, and best wishes with the solution. Why oh why are MS compliers so pernickety? -Original Message- From: Vivian Meazza [mailto:vivian.mea...@lineone.net] Sent: 19 July 2009 09:19 To: 'FlightGear developers discussions' Subject: Re: [Flightgear-devel] [Simgear-cvslogs] CVS:source/simgear/propsprops.cxx, 1.44, 1.45 props.hxx, 1.32, 1.33 Alan Teeder RE: [Simgear-cvslogs] CVS: source/simgear/props props.cxx, 1.44,1.45 props.hxx, 1.32, 1.33 Sadly, props.hxx is still getting me errors with MSVC 2008 - see attached error log. -Original Message- From: Tim Moore [mailto:timo...@baron.flightgear.org mailto:timo...@baron.flightgear.org ] Sent: 17 July 2009 11:12 To: simgear-cvsl...@lists.sf.net Subject: [Simgear-cvslogs] CVS: source/simgear/props props.cxx, 1.44,1.45 props.hxx, 1.32, 1.33 Update of /var/cvs/SimGear-0.3/source/simgear/props In directory baron.flightgear.org:/tmp/cvs-serv901/simgear/props Modified Files: props.cxx props.hxx Log Message: Changed SGRawValue::DefaultValue to an inline function. This avoids MSVC bugs in declaring templated specializations of static members. Unfortunately, there are still errors in the MSVC9 compile. Tim and I have been working to correct them, but we are still some way off. We are down to 1 right now, but it is proving rather intractable. Tim is unavailable atm, as is Fred, so do not expect an early resolution of this one. Vivian -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [Simgear-cvslogs]CVS:source/simgear/propsprops.cxx, 1.44, 1.45 props.hxx, 1.32, 1.33
It is one thing to bring out a new software tool, in this case a compiler, that enables the use of new technologies (.NET for example), but to completely disregard the principles of backwards compatibility, forcing software to be extensively re-written, is another. _ From: Curtis Olson [mailto:curtol...@gmail.com] Sent: 19 July 2009 15:30 To: FlightGear developers discussions Subject: Re: [Flightgear-devel] [Simgear-cvslogs]CVS:source/simgear/propsprops.cxx, 1.44, 1.45 props.hxx, 1.32, 1.33 On Sun, Jul 19, 2009 at 7:10 AM, Arnt Karlsen a...@c2i.net wrote: On Sun, 19 Jul 2009 09:27:57 +0100, Alan wrote in message 5fe353c04d92459a9dbf8d42d1b97...@ajtmain: Thanks for the quick reply, and best wishes with the solution. Why oh why are MS compliers so pernickety? ..business strategy: http://grokdoc.net/index.php/Dirty_Tricks_history#C.2B.2B http://grokdoc.net/index.php/Dirty_Tricks_history#OpenGL (...and only then, the next 3 immediately below #OpenGL: http://grokdoc.net/index.php/Dirty_Tricks_history#C.23.2FCLI http://grokdoc.net/index.php/Dirty_Tricks_history#.NET http://grokdoc.net/index.php/Dirty_Tricks_history#Java , I've seen people talk about doing FG things in C# here.) These are only dirty tricks when the bad guys do them. :-) Even the GPL has a lock you in strategy. Governments have a tendency to consolidate and accumulate power and lock the people into systems that allow the gov't to maintain it's control. If you are a MS employee you probably think MS's strategies are a good thing. If you are an open-source advocate you probably think the GPL strategy is a good thing. We as humans put a big emphasis on judging intent ... so in places like the court room, the final outcome or penalty often has a huge dependence on perceived intent. And our personal views of good lock in strategies versus bad lock in strategies also depend on our personal views and personal judgment of intent. (And that's purely my opinion ... ) :-) MS is only doing the same things that every other company is also doing. It's just that MS has been very successful, and their decisions and policies affect a lot of people and therefore they have drawn a lot more scrutiny and attention than most other businesses. Curt. -- Curtis Olson: http://baron.flightgear.org/~curt/ -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [Simgear-cvslogs]CVS:source/simgear/propsprops.cxx, 1.44, 1.45 props.hxx, 1.32, 1.33
Sorry folks, I seem to have started a flame war. This is not the right place. Alan _ From: Nicolas Quijano [mailto:nquij...@gmail.com] Sent: 19 July 2009 17:23 To: FlightGear developers discussions Subject: Re: [Flightgear-devel][Simgear-cvslogs]CVS:source/simgear/propsprops.cxx, 1.44,1.45 props.hxx, 1.32, 1.33 cl.exe which compiles C and C++ has nothing in common with the CLR compiler (.NET). Unrelated issues, and what Curtis said : a bit of perspective, gcc is NOT 100% compliant either. The issue has to do with standards compliance and C++ idioms, not MS business strategy Funny how any sense of perspective is thrown out the window with the opportunity to rag on MS... Sheesh !! P.S : if warnings prevented building, no one would be flying today or tomorrow :) yeah, you're talking about backwards compatibility but obviously don't have a clue : you can use old standard unsafe versions of the routines if you want to, program will run fine on all versions of windows... On Sun, Jul 19, 2009 at 11:27 AM, Alan Teeder ajtee...@v-twin.org.uk wrote: It is one thing to bring out a new software tool, in this case a compiler, that enables the use of new technologies (.NET for example), but to completely disregard the principles of backwards compatibility, forcing software to be extensively re-written, is another. _ -- Be Kind. Remember, everyone is fighting a hard battle. -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [Simgear-cvslogs]CVS:source/simgear/propsprops.cxx, 1.44, 1.45 props.hxx, 1.32, 1.33
No problems. My code-writing skills are even worse than they were when I retired. Once upon a time I thought that I had the hang of C++, but these days I think that I must have been mistaken. _ From: Nicolas Quijano [mailto:nquij...@gmail.com] Sent: 19 July 2009 17:44 To: FlightGear developers discussions Subject: Re: [Flightgear-devel][Simgear-cvslogs]CVS:source/simgear/propsprops.cxx, 1.44,1.45 props.hxx, 1.32, 1.33 Sorry about calling you clueless, btw, I mistakenly thought your post was from the same person who linked to the propaganda bullshit site on MS : I'm no fan of MS, but I'm tired of falsehoods being used to critique them. Especially as all those examples were null or so badly distorted to be absolutely pointless. Not a flame war :) Incidentallly, I've been also failing miserably at fixing this : my code rustiness shows badly in this instance :) Cheers, Nic On Sun, Jul 19, 2009 at 12:35 PM, Alan Teeder ajtee...@v-twin.org.uk wrote: Sorry folks, I seem to have started a flame war. This is not the right place. Alan _ From: Nicolas Quijano [mailto:nquij...@gmail.com] Sent: 19 July 2009 17:23 To: FlightGear developers discussions Subject: Re: [Flightgear-devel][Simgear-cvslogs]CVS:source/simgear/propsprops.cxx, 1.44,1.45 props.hxx, 1.32, 1.33 cl.exe which compiles C and C++ has nothing in common with the CLR compiler (.NET). Unrelated issues, and what Curtis said : a bit of perspective, gcc is NOT 100% compliant either. The issue has to do with standards compliance and C++ idioms, not MS business strategy Funny how any sense of perspective is thrown out the window with the opportunity to rag on MS... Sheesh !! P.S : if warnings prevented building, no one would be flying today or tomorrow :) yeah, you're talking about backwards compatibility but obviously don't have a clue : you can use old standard unsafe versions of the routines if you want to, program will run fine on all versions of windows... On Sun, Jul 19, 2009 at 11:27 AM, Alan Teeder ajtee...@v-twin.org.uk wrote: It is one thing to bring out a new software tool, in this case a compiler, that enables the use of new technologies (.NET for example), but to completely disregard the principles of backwards compatibility, forcing software to be extensively re-written, is another. _ -- Be Kind. Remember, everyone is fighting a hard battle. -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Be Kind. Remember, everyone is fighting a hard battle. -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [Simgear-cvslogs]CVS:source/simgear/propsprops.cxx, 1.44, 1.45 props.hxx, 1.32, 1.33
Vivian I have managed a compile of Flightgear. Nic was correct, props .hxx, not props.cxx. Flightgear and Simgear both now have NOMINMAX in my pre-processor defines. Flightgear needed most of the new modules from simgear\scene\material to be added to Simgear library before it would link. Unfortunately Flightgear now crashes during loading subsystems when it is run. Alan _ From: Vivian Meazza [mailto:vivian.mea...@lineone.net] Sent: 20 July 2009 13:50 To: 'FlightGear developers discussions' Subject: Re: [Flightgear-devel][Simgear-cvslogs]CVS:source/simgear/propsprops.cxx, 1.44,1.45 props.hxx, 1.32, 1.33 Alan, simgear-config.h cannot be used in SGMisc.cxx because it is called from fg as well as sg. SGMisc will not compile without NOMINMAX , so you need it in your pre-processor definitions. Unless you have a better way . The error you report is the very one that replacing the SGMathFwd.hxx include with the SGMath.hxx include is meant to fix. I have just checked SG CVS Head and AFAIKS it still has the SGMathFwd.hxx include. I have discussed this with Tim, and he doesn't want to change it for now while he looks for a work around. Vivian -Original Message- From: Alan Teeder [mailto:ajtee...@v-twin.org.uk] Sent: 20 July 2009 13:13 To: vivian.mea...@lineone.net; 'FlightGear developers discussions' Subject: Re: [Flightgear-devel][Simgear-cvslogs]CVS:source/simgear/propsprops.cxx, 1.44,1.45 props.hxx, 1.32, 1.33 Vivian Thanks, the number of errors has reduced, but I still see the attached for every file that includes props.hxx Also CVS now has the SGMath.hxx include, and NOMINMAX is already defined in simgear_config.h-msvc71 and hence in simgear_config.h, so I think that it is not needed in pre-processor defines. Alan _ From: Vivian Meazza [mailto:vivian.mea...@lineone.net] Sent: 20 July 2009 00:16 To: vivian.mea...@lineone.net; 'FlightGear developers discussions' Subject: Re: [Flightgear-devel][Simgear-cvslogs]CVS:source/simgear/propsprops.cxx, 1.44,1.45 props.hxx, 1.32, 1.33 And I forgot - you need to change #include simgear/math/SGMathFwd.hxx to #include simgear/math/SGMath.hxx in props.cxx -Original Message- From: Vivian Meazza [mailto:vivian.mea...@lineone.net] Sent: 19 July 2009 23:47 To: 'FlightGear developers discussions' Subject: Re: [Flightgear-devel][Simgear-cvslogs]CVS:source/simgear/propsprops.cxx, 1.44,1.45 props.hxx, 1.32, 1.33 Alan, Tim's fixes are now in CVS although not quite finished: you might have to add NOMINMAX to your pre-processor definitions. I'd be interested to hear how you get on. Vivian -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Automated builds tests
Are we talking about validating the build process and checking that FG runs, or about checking the validity of the simulation? For the former the suggested buildbot , or similar, approach, perhaps with a very simple autopilot guided flight, would be adequate. Simulation validity checking is another issue, and given the (I hope I do not offend anyone) rather basic flight models used for most aircraft models in the FG library as well as the limited availability of accurate predicted response data is probably not attainable by a project such as Flightgear. As a now retired flight simulator professional most of my time was devoted to checking and validating my simulations before they would be accepted for training (by CAA/FAA) or for flight handling research (by my company's aerodynamics department). Each aircraft model required tests tailored to the use that the simulation was designed for. _ From: Curtis Olson [mailto:curtol...@gmail.com] Sent: 04 August 2009 12:37 To: FlightGear developers discussions Subject: Re: [Flightgear-devel] Automated builds tests On Tue, Aug 4, 2009 at 2:00 AM, Tom P zomm...@gmail.com wrote: Hi everybody I'd like to hear thoughts from the FG community about setting up a system to perform builds execute a suite of tests on FlightGear, all automatically. Right now I've experimented a bit with buildbot, a neat continuous integration tool used by Mozilla and other projects, and I have a system that can: * check-out from various repositories * build all FlightGear components * perform rudimentary tests on the FG simulator just built, like verifing the output on the command line and starting the simulator. Now the next step would be to go airborne! And there are two issues to resolve before take-off: 1) how to drive the input of the simulator 2) how to read its state For the second one, I've seen examples of reading the property tree from an external process, so we should be set, but the solution to driving the sim's input is still not clear. Specifically, I'd want to drive it as similarly as possible as when it's controlled from a keyboard, not go through the property tree to force FGFS into certain conditions. By the way, the current setup works on Ubuntu x86-64, but buildbot is easily extensible and supports Windows and MacOS platforms, so this could become a cross-platform testing tool for the project. Hi Tom, Because, of variations in flight dynamics models, possible variations in weather conditions, possible variations in frame rates, etc., simply replaying a series of keyboard commands is probably not going to lead to repeatable results. I suspect the replayed flight could diverge quite quickly and quite substantially from the original flight. If you want to test the simulator during flight, I really think you will have the most luck under some sort of scripted autopilot control. You should think about exactly what you are trying to measure and validate. As soon as you fire up the sim and start the aircraft moving, you've suddenly moved into the world of flight dynamics and you are looking at the physics/mathematics model of the aircraft. That's a good thing to look at though. One idea to consider is to setup a series of scripted flight tests that parallel the FAA simulator certification tests. I've gone through the Level 3 FTD set of tests and automated them for work (so I can't share the resulting scripts unfortunately) but it was an interesting process. For instance, configure some specific weather conditions, start the aircraft out at some particular altitude and speed. Setup the aircraft with a specific weight and CG. Configure the throttle for some particular RPM, keep the wings straight and level. Now measure the rate of climb (descent) you observe once the phugoid settles out. Another test involved setting up straight and level flight at certain known conditions, then commanding full rudder input while maintaining the same heading and altitude (steady state side slip.) Measure the resulting bank angle, amount of required aileron input, and side slip angle. This is all very interesting stuff, but it tends to focus you more on the validity of the aircraft model and less on the validity of the simulator code. The complexity of this in combined with the complexity of everything else you could be testing and evaluating is quite staggering. That said, having a few key spot or sanity checks can't hurt either. Regards, Curt. -- Curtis Olson: http://baron.flightgear.org/~curt/ -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july___ Flightgear-devel mailing list
Re: [Flightgear-devel] Potential issue with magnetic variation?
Torsten Thanks - the CVS fix has arrived already. Alan -Original Message- From: Alan Teeder [mailto:ajtee...@v-twin.org.uk] Sent: 20 August 2009 16:05 To: 'FlightGear developers discussions' Subject: Re: [Flightgear-devel] Potential issue with magnetic variation? Torsten Well done!! Except line 88 of RenderTexture.cpp is not complete for the non GNUC case. (sorry) VC++ 2008 is still giving a few warnings for other source files, but nowhere near as many as before. Alan -Original Message- From: Torsten Dreyer [mailto:tors...@t3r.de] Sent: 20 August 2009 14:27 To: FlightGear developers discussions Subject: Re: [Flightgear-devel] Potential issue with magnetic variation? I agree, we are due for an aggressive -Wall clean up and I'd like to remind our active developers that they should consider always compiling with warning flags activated. The following is pretty standard for me ... CFLAGS=-Wall -O2 CXXFLAGS=-Wall -O2 ./configure There is a lot of avoidable warnings that have crept into our code in the past few months. Message copied ;-) I just cleaned up all the compiler warnings for SimGear, so it now compiles without a single warning. At least here on 'gcc (SUSE Linux) 4.3.2 [gcc-4_3-branch revision 141291]' One actual bug (write behind array size) and one possible bug (use of uninitialized variable) were discovered and removed. While at it, I also commented out the building of tabbed_value_test and swap_test in simgear/misc and openal_test[12] in simgear/sound in Makefile.am If this hurts in any way, they are easily reenabled. Greetings, Torsten -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Potential issue with magnetic variation?
Torsten Well done!! Except line 88 of RenderTexture.cpp is not complete for the non GNUC case. (sorry) VC++ 2008 is still giving a few warnings for other source files, but nowhere near as many as before. Alan -Original Message- From: Torsten Dreyer [mailto:tors...@t3r.de] Sent: 20 August 2009 14:27 To: FlightGear developers discussions Subject: Re: [Flightgear-devel] Potential issue with magnetic variation? I agree, we are due for an aggressive -Wall clean up and I'd like to remind our active developers that they should consider always compiling with warning flags activated. The following is pretty standard for me ... CFLAGS=-Wall -O2 CXXFLAGS=-Wall -O2 ./configure There is a lot of avoidable warnings that have crept into our code in the past few months. Message copied ;-) I just cleaned up all the compiler warnings for SimGear, so it now compiles without a single warning. At least here on 'gcc (SUSE Linux) 4.3.2 [gcc-4_3-branch revision 141291]' One actual bug (write behind array size) and one possible bug (use of uninitialized variable) were discovered and removed. While at it, I also commented out the building of tabbed_value_test and swap_test in simgear/misc and openal_test[12] in simgear/sound in Makefile.am If this hurts in any way, they are easily reenabled. Greetings, Torsten -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] CVS HEAD - am 19 Sep
Can NOMINMAX be added to all the MSVC9 projects that need it at the same time please? -Original Message- From: Vivian Meazza [mailto:vivian.mea...@lineone.net] Sent: 19 September 2009 12:05 To: 'FlightGear developers discussions' Subject: [Flightgear-devel] CVS HEAD - am 19 Sep Hi, This morning's FG CVS head fails to compile under MSVC9 (nothing new there then!). Flightgear/source/src/ATCDCL/ATCVoice.cxx and ATIS.cxx are the problems. There's a fix here: http://gitorious.org/~vivian/fg/vivians-clone for those who want to attempt git. It works, but unfortunately it uses alloca() which is deprecated, and does who knows what to FG. Hopefully we (Fred) can come up with a better solution in the next couple of days. Vivian -- Come build with us! The BlackBerryreg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9#45;12, 2009. Register now#33; http://p.sf.net/sfu/devconf ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Come build with us! The BlackBerryreg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9#45;12, 2009. Register now#33; http://p.sf.net/sfu/devconf ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Another FlightGear Package for Sale: Illegal?
How about naming and shaming all of these profiteers on the main website, warning newcomers that they can get an up to date version for free (and contribute should they wish). _ From: Gijs de Rooy [mailto:gijsr...@hotmail.com] Sent: 25 September 2009 18:05 To: FlightGear Development list Subject: Re: [Flightgear-devel] Another FlightGear Package for Sale: Illegal? Hi, I've just created a ticket on the www.flightprosim.com website. In other words, I have tried to contact the webmaster/seller. I asked him if the package is released under GNU GPL. Also I kindly asked him to remove the images or place clear sources. If the situation doesn't improve within 7 days (which is very likely I think) I will contact the hosting company and ask them to remove the images or even his entire website. Curt, you are the maintainer of the list? You might have received an email with details about my ticket. Would you be so kind to forward them to me? That way we could see the status of our request. Regards, Gijs _ Alle tips en trics. Ontdek nu de nieuwe Windows Live http://www.microsoft.com/netherlands/windowslive/Views/tipsItemDetail.aspx -- Come build with us! The BlackBerryreg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9#45;12, 2009. Register now#33; http://p.sf.net/sfu/devconf___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] New Sound system committed
Sorry to be the messenger, but compilation of soundmgr_openal.cxx and all flightgear files using soundmgr_openal.hxx fails under VC90. See attached build log. I am using the 3rd part libraries as per flightgear/source/projects/VC90/README.msvc. i.e. (Precompiled librairies and headers for compiling Win32 executables with VS2008 : ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/MSVC/fgfs-win32-VS90-3rdParty +OSG-20090628.zip) Same error with more recent fgfs-win32-VS90-3rdParty+OSG-20090820. Do I need a more recent version of OpenAL? Alan -Original Message- From: Erik Hofman [mailto:e...@ehofman.com] Sent: 05 October 2009 08:45 To: FlightGear developers discussions Subject: Re: [Flightgear-devel] New Sound system committed Curtis Olson wrote: Hi Erik, One quick question: will the sound configuration xml files need to change to match the new system or will there be backwards compatibility? It's backwards compatible. I do plan a new format change to be able to position the sounds in 3d-model space instead of OpenAL/OpenGL space. That will require adding a a new version/ xml tag but the omission of it will still mean the previous format. Erik -- Come build with us! The BlackBerryreg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9#45;12, 2009. Register now#33; http://p.sf.net/sfu/devconf ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel ÿþ< h t m l > < h e a d > < M E T A H T T P - E Q U I V = " C o n t e n t - T y p e " c o n t e n t = " t e x t / h t m l ; c h a r s e t = u t f - 1 6 " > < / h e a d > < b o d y > < p r e > < t a b l e w i d t h = 1 0 0 % b g c o l o r = # C F C F E 5 > < t r > < t d > < f o n t f a c e = a r i a l s i z e = + 3 > B u i l d L o g < / f o n t > < / t a b l e > < t a b l e w i d t h = * c e l l s p a c i n g = 0 c e l l p a d d i n g = 0 > < t r > < t d w i d t h = 0 b g c o l o r = # E D E D F 5 > & n b s p ; < / t d > < t d w i d t h = 0 b g c o l o r = # F F F F F F > & n b s p ; < / t d > < t d w i d t h = * > < p r e > < h 3 > B u i l d s t a r t e d : P r o j e c t : S i m G e a r , C o n f i g u r a t i o n : R e l e a s e | W i n 3 2 < / h 3 > < / p r e > < / t a b l e > < t a b l e w i d t h = 1 0 0 % b g c o l o r = # D F D F E 5 > < t r > < t d > < f o n t f a c e = a r i a l s i z e = + 2 > C o m m a n d L i n e s < / f o n t > < / t a b l e > < t a b l e w i d t h = * c e l l s p a c i n g = 0 c e l l p a d d i n g = 0 > < t r > < t d w i d t h = 0 b g c o l o r = # E D E D F 5 > & n b s p ; < / t d > < t d w i d t h = 0 b g c o l o r = # F F F F F F > & n b s p ; < / t d > < t d w i d t h = * > < p r e > C r e a t i n g t e m p o r a r y f i l e " d : \ f g \ S i m G e a r \ p r o j e c t s \ V C 9 0 \ W i n 3 2 \ R e l e a s e \ R S P 0 0 0 0 0 7 5 6 9 6 5 1 2 4 . r s p " w i t h c o n t e n t s [ / O b 1 / I & q u o t ; . . \ . . & q u o t ; / I & q u o t ; . . \ . . \ s i m g e a r & q u o t ; / I & q u o t ; . . \ . . \ . . & q u o t ; / I & q u o t ; . . \ . . \ . . \ i n s t a l l \ m s v c 9 0 \ O p e n S c e n e G r a p h \ i n c l u d e & q u o t ; / I & q u o t ; . . \ . . \ . . \ 3 r d p a r t y \ i n c l u d e & q u o t ; / I & q u o t ; . . \ . . \ . . \ b o o s t _ 1 _ 3 9 _ 0 & q u o t ; / D & q u o t ; H A V E _ C O N F I G _ H & q u o t ; / D & q u o t ; N D E B U G & q u o t ; / D & q u o t ; W I N 3 2 & q u o t ; / D & q u o t ; _ U S E _ M A T H _ D E F I N E S & q u o t ; / D & q u o t ; _ C R T _ S E C U R E _ N O _ W A R N I N G S & q u o t ; / D & q u o t ; N O M I N M A X & q u o t ; / D & q u o t ; _ C R T _ N O N S T D C _ N O _ W A R N I N G S & q u o t ; / D & q u o t ; _ V C 8 0 _ U P G R A D E = 0 x 0 7 1 0 & q u o t ; / D & q u o t ; _ M B C S & q u o t ; / G F / F D / E H s c / M D / G y / F o & q u o t ; W i n 3 2 \ R e l e a s e \ \ & q u o t ; / F d & q u o t ; W i n 3 2 \ R e l e a s e \ v c 9 0 . p d b & q u o t ; / W 3 / c / Z i . . \ . . \ s i m g e a r \ s o u n d \ s o u n d m g r _ o p e n a l . c x x . . \ . . \ s i m g e a r \ s o u n d \ s a m p l e _ o p e n a l . c x x ] C r e a t i n g c o m m a n d l i n e " c l . e x e ...@ d : \ f g \ S i m G e a r \ p r o j e c t s \ V C 9 0 \ W i n 3 2 \ R e l e a s e \ R S P 0 0 0 0 0 7 5 6 9 6 5 1 2 4 . r s p / n o l o g o / e r r o r R e p o r t : p r o m p t " < / p r e > < / t a b l e > < t a b l e w i d t h = 1 0 0 %
Re: [Flightgear-devel] GPS / route-manager landing
Also VC90 also does not this at line 70 of route_mgr.cxx. :- Compiling... route_mgr.cxx ..\..\..\src\Autopilot\route_mgr.cxx(70) : warning C4355: 'this' : used in base member initializer list ..\..\..\src\Autopilot\route_mgr.cxx(229) : error C3861: 'time': identifier not found ..\..\..\src\Autopilot\route_mgr.cxx(233) : error C3861: 'time': identifier not found ..\..\..\src\Autopilot\route_mgr.cxx(234) : error C3861: 'difftime': identifier not found Build log was saved at file://d:\fg\source\projects\VC90\FlightGear\Win32\Release\BuildLog.htm Alan _ From: Nicolas Quijano [mailto:nquij...@gmail.com] Sent: 06 October 2009 17:22 To: FlightGear developers discussions Subject: Re: [Flightgear-devel] GPS / route-manager landing Hi all, this doesn't build on windows, it can't find the time symbol referenced at line 229 and 233 in route_mgr.cxx. Missing header ? Also, there is a reference to std::strncasecmp in positioned.cxx around line 820, which is also not available in windows (at least, not here). Since it's dealing with c strings, I've added locally an #ifdef WIN32 check which uses_stricmp instead in this case. Don't know how you want to deal with this, Cheers, Nic On Mon, Oct 5, 2009 at 3:59 AM, James Turner zakal...@mac.com wrote: On 5 Oct 2009, at 08:33, Dave wrote: That all sounds like good stuff. I'll try and migrate the KLN89 towards using it and depreciating the dclgps stuff - that should give it some testing. Sounds good to me. I've been going through the KLN89 manual, and there's definitely some more subtle options that will require extra features / flags (off the top of my head, resuming LEG mode from OBS mode, and the ability to DTO without recentering the d-bar). Many things should be achievable with a bit of Nasal glue, obviously I've tried to make simple building block functionality as much as I can. If you think an API or design is poor, or missing a feature, let me know and I'm happy to add it - I'd far rather get the core code sensible, than have each GPS device work around the same bug! In terms of API examples, I will be committing a new GPS dialog, which shows off most of the new features, and will also allow the GPS to be used in aircraft without real hardware, if we want that. I'm also going to create a wiki page for the GPS, to document what it can (and can't do). Regards, James -- Come build with us! The BlackBerryreg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9#45;12, 2009. Register now#33; http://p.sf.net/sfu/devconf ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Be Kind. Remember, everyone is fighting a hard battle. -- Come build with us! The BlackBerryreg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9#45;12, 2009. Register now#33; http://p.sf.net/sfu/devconf___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] New Sound system committed
Thanks for fixing this. However the pre-built libraries referenced in README.msvc do have an old version of alut.h which is missing the alcGetError and associated definitions. I don´t know who maintains these useful archives. Alan -Original Message- From: Alan Teeder [mailto:ajtee...@v-twin.org.uk] Sent: 05 October 2009 11:37 To: 'FlightGear developers discussions' Subject: Re: [Flightgear-devel] New Sound system committed Sorry to be the messenger, but compilation of soundmgr_openal.cxx and all flightgear files using soundmgr_openal.hxx fails under VC90. See attached build log. I am using the 3rd part libraries as per flightgear/source/projects/VC90/README.msvc. i.e. (Precompiled librairies and headers for compiling Win32 executables with VS2008 : ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/MSVC/fgfs-win32-VS90-3rdParty +OSG-20090628.zip) Same error with more recent fgfs-win32-VS90-3rdParty+OSG-20090820. Do I need a more recent version of OpenAL? Alan -- Come build with us! The BlackBerryreg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9#45;12, 2009. Register now#33; http://p.sf.net/sfu/devconf ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] New Sound system committed
Erik Sorry, I gave the wrong missing name -- I should have written alutGetError, as this is not in the older alut.h (or al.h or alc.h). Apologies for the confusion. Alan -Original Message- From: Erik Hofman [mailto:e...@ehofman.com] Sent: 06 October 2009 20:48 To: FlightGear developers discussions Subject: Re: [Flightgear-devel] New Sound system committed Alan Teeder wrote: Thanks for fixing this. However the pre-built libraries referenced in README.msvc do have an old version of alut.h which is missing the alcGetError and associated definitions. I don´t know who maintains these useful archives. It's not alut.h that defines these functions but it's alc.h Maybe you need to include it in the project files somewhere? Erik -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] GPS / route-manager landing
James The this fault is fixed. Thanks. To cure the time and difftime under Windows all that is needed is to include time.h Alan _ From: Alan Teeder [mailto:ajtee...@v-twin.org.uk] Sent: 06 October 2009 17:38 To: 'FlightGear developers discussions' Subject: Re: [Flightgear-devel] GPS / route-manager landing Also VC90 also does not this at line 70 of route_mgr.cxx. :- Compiling... route_mgr.cxx ..\..\..\src\Autopilot\route_mgr.cxx(70) : warning C4355: 'this' : used in base member initializer list ..\..\..\src\Autopilot\route_mgr.cxx(229) : error C3861: 'time': identifier not found ..\..\..\src\Autopilot\route_mgr.cxx(233) : error C3861: 'time': identifier not found ..\..\..\src\Autopilot\route_mgr.cxx(234) : error C3861: 'difftime': identifier not found Build log was saved at file://d:\fg\source\projects\VC90\FlightGear\Win32\Release\BuildLog.htm Alan _ From: Nicolas Quijano [mailto:nquij...@gmail.com] Sent: 06 October 2009 17:22 To: FlightGear developers discussions Subject: Re: [Flightgear-devel] GPS / route-manager landing Hi all, this doesn't build on windows, it can't find the time symbol referenced at line 229 and 233 in route_mgr.cxx. Missing header ? Also, there is a reference to std::strncasecmp in positioned.cxx around line 820, which is also not available in windows (at least, not here). Since it's dealing with c strings, I've added locally an #ifdef WIN32 check which uses_stricmp instead in this case. Don't know how you want to deal with this, Cheers, Nic On Mon, Oct 5, 2009 at 3:59 AM, James Turner zakal...@mac.com wrote: On 5 Oct 2009, at 08:33, Dave wrote: That all sounds like good stuff. I'll try and migrate the KLN89 towards using it and depreciating the dclgps stuff - that should give it some testing. Sounds good to me. I've been going through the KLN89 manual, and there's definitely some more subtle options that will require extra features / flags (off the top of my head, resuming LEG mode from OBS mode, and the ability to DTO without recentering the d-bar). Many things should be achievable with a bit of Nasal glue, obviously I've tried to make simple building block functionality as much as I can. If you think an API or design is poor, or missing a feature, let me know and I'm happy to add it - I'd far rather get the core code sensible, than have each GPS device work around the same bug! In terms of API examples, I will be committing a new GPS dialog, which shows off most of the new features, and will also allow the GPS to be used in aircraft without real hardware, if we want that. I'm also going to create a wiki page for the GPS, to document what it can (and can't do). Regards, James -- Come build with us! The BlackBerryreg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9#45;12, 2009. Register now#33; http://p.sf.net/sfu/devconf ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Be Kind. Remember, everyone is fighting a hard battle. -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Autopilot and violent roll
Do you really expect much help after that stuff you lot remark? As a former autopilot designer I would suggest that what is needed is a rate limit on roll angle demand within the autopilot. You could also try to add some roll damping within the autopilot. It is possible that the FDM for your aircraft is making the simulated aircraft over-sensitive to aileron. How this should be implemented within Flightgear I am not in a position to tell you as I am not familiar with the code, sorry. -Original Message- From: Pete Morgan [mailto:ac...@daffodil.uk.com] Sent: 10 October 2009 20:18 To: FlightGear developers discussions Subject: Re: [Flightgear-devel] Autopilot and violent roll Actually my motion platform is at the momnet I am taking it one step at a time.. ie so far its banking left to right by around 10 degree's which kinda exagarrated the sim and is useful.. Anyone as a pilot at the moment can tip the aircfaft to lbank.. However this jerk needs solving.. SO what you are saying is .. stuff FlightGear and its your problem.. pete Curtis Olson wrote: I haven't looked at these autopilot configurations (at least not for a long time) but off the top of my head, I think this can all be fixed by tuning the autopilot. For instance, lowering the max aileron deflection from (-1 ... 1) down to maybe (-0.1 ... 0.1) might be an interesting thing to start with. These are normalized values so +/-1 represents full deflection and 0.1 represents 1/10th of full deflection. If the autopilot is hitting you with full instantaneous aileron deflection that might be part of the issue. The other thing to look at is tuning the actual PID gains. These are obscured a bit given that we are using a slightly different form of the PID algorithm compared to what you might see in a Control Theory-101 class. I believe there is an autopilot tuning README and it just takes some fiddling around to see what changing the different values will accomplish. There's an art (maybe part science) to tuning autopilots ... I've yet to meet an expert in that area, but they must exist ... they are probably locked in the basement of Airbus and Boeing and various UAV companies and not allowed to leave their cells. :-) Curt. On Sat, Oct 10, 2009 at 1:56 PM, Pete Morgan ac...@daffodil.uk.com mailto:ac...@daffodil.uk.com wrote: I'm working on my motion sim for xmas. Its powered by a vacum cleaner atmo.. One BIG BIG problem - am basicng the cockpit on Bravo and 787 The autopilot heading bug is very violent and JERKS to direction.. How can we solve that problem please because on my motion platform, I cant keep up with the drastric movements. Actually I can, but this is where there is a problem.. the behaviour of bank is performing well with the Ardiono/pneumatics card firing off the valves, however the violent values from the autopilot when auto pilot is engaged is causing a problem.. I've damped it down in my arduino/python middle man code, But I think this problem is an actual flightgear problem.. Any one offer me some advice which area of code to look at please... eg I could damp it in nasal script ? pete -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net mailto:Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Curtis Olson: http://baron.flightgear.org/~curt/ http://baron.flightgear.org/%7Ecurt/ -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend
Re: [Flightgear-devel] Autopilot and violent roll
-Original Message- From: leee [mailto:l...@spatial.plus.com] ie if u stick in a new value to the FDM then it will react.. That sucks in my oioiion.. I how have to create my own craqo to make the model. that sucks to me.. pete You really need to chill a bit. Just moaning about things isn't the best way to go about getting stuff fixed. Anyway, in short, this 'problem' such as it is, is largely due to the rates at which the autopilots are run within FG. In real life, autopilot controllers, and the sensors that feed them the data they need to work with, run at much higher frequencies than are possible within the FG framework. Ideally, you want to be able to run the autopilots at several to many kHz but in FG, although you can specify very high rates in the autopilot config, you are effectively limited by the frame rate, so not only do they run much more slowly than is desirable but they also run at varying rates as the frame rate changes. Lee First, thanks for the quick into to Flightgear´s autopilot. I think that your premise that autopilots need to run at very high frame rates is not realistic. When I first got into autopilots and simulation, back in the 60´s, all of our models had as the final element a 0.1 second low pass filter which simulated the control surface actuator. This turns out to be a reasonable approximation for most actuators and is very simple to implement both in a analogue computer (which is all we had then) and in digital ones. As there is such a filter in the inner loop means that there is no need to simulate anything which has a faster response time than this. Therefore there is no need to run the autopilot at high frame rates. 10 or 20 per second is perfectly adequate. Many of the outer loops (e.g. the heading mode) of the autopilot can in practice be run at much slower frame rates as the response of the aircraft is quite slow. Alan -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Autopilot and violent roll
-Original Message- For the faster and more maneuverable military jets though, I found that I really needed guaranteed higher rates to both ensure a crisp response and avoid instabilities. For example, I could tune an altitude-hold cascade that would work fine at speeds up to 400kt say, but which would become unstable above that. The reason was that the rate of deviation increases with aircraft speed as the control surfaces generate more force for a given deflection, so for a given deflection of the control surfaces by the controller, it sees a greater response result in its next sample. Eventually, it can't help but over-correct and go into oscillation. Running the controller at a higher rate though, would mean that it would see a smaller deviation because the aircraft would have moved less in the shorter time period. Did you try scheduling your autoplilot´s height-error to pitch demand gain with 1/V (speed inverse) ? Alan -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Autopilot and violent roll
-Original Message- From: leee [mailto:l...@spatial.plus.com] Did you try scheduling your autoplilot´s height-error to pitch demand gain with 1/V (speed inverse) ? Alan Re-read the end of the paragraph after the one you quoted above ;-) LeeE Red Face (me that is) I can't help thinking that there must be another problem somewhere. It should only be necessary to up the frame rate above 20Hz if you need to simulate vibrations, not aircraft motion and autopilot control loops. A possible cause is if the simulation is not ordered correctly and some equations in the solution are receiving old inputs which relate to a previous time frame. Errors due to this effect would reduce as the frame rate is increased. Anything in the simulation which has a faster response that that provided by a 20Hz frame rate can safely be ignored for man-in-the-loop stuff as the man just won't be capable of seeing or reacting to it. Alan -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] props.hxx - 4 modules not compiling with VC90
A heads up Simgear:- matmodel.cxx, model.cxx and Flightgear:- performancedb.cxx, FGDeviceConfigurationMap.cxx are currently failing to compile here with VC90. In each case the error is reported in props.hxx. Strangely only these 4 modules are failing - the many other modules which use this file have no problem. Alan e.g. for matmodel.cxx Compiling... matmodel.cxx d:\fg\SimGear\simgear/props/props.hxx(666) : error C2079: 'SGRawValueContainerT::_obj' uses undefined class 'SGVec3T' with [ T=SGVec3d ] and [ T=double ] d:\fg\SimGear\simgear/props/props.hxx(672) : see reference to class template instantiation 'SGRawValueContainerT' being compiled with [ T=SGVec3d ] d:\fg\SimGear\simgear/props/props.hxx(671) : while compiling class template member function 'SGRawExtended *SGRawBaseT::makeContainer(void) const' with [ T=SGVec3d ] d:\fg\SimGear\simgear/props/props.hxx(692) : see reference to class template instantiation 'SGRawBaseT' being compiled with [ T=SGVec3d ] d:\fg\SimGear\simgear/props/props.hxx(685) : error C2079: 'value' uses undefined class 'SGVec3T' with [ T=double ] d:\fg\SimGear\simgear/props/props.hxx(684) : while compiling class template member function 'std::istream SGRawBaseT::readFrom(std::istream )' with [ T=SGVec3d ] d:\fg\SimGear\simgear/props/props.hxx(687) : error C2664: 'SGRawValueT::setValue' : cannot convert parameter 1 from 'int' to 'SGVec3d' with [ T=SGVec3d ] Source or target has incomplete type d:\fg\SimGear\simgear/props/props.hxx(666) : error C2079: 'SGRawValueContainerT::_obj' uses undefined class 'SGVec4T' with [ T=SGVec4d ] and [ T=double ] d:\fg\SimGear\simgear/props/props.hxx(672) : see reference to class template instantiation 'SGRawValueContainerT' being compiled with [ T=SGVec4d ] d:\fg\SimGear\simgear/props/props.hxx(671) : while compiling class template member function 'SGRawExtended *SGRawBaseT::makeContainer(void) const' with [ T=SGVec4d ] d:\fg\SimGear\simgear/props/props.hxx(694) : see reference to class template instantiation 'SGRawBaseT' being compiled with [ T=SGVec4d ] d:\fg\SimGear\simgear/props/props.hxx(685) : error C2079: 'value' uses undefined class 'SGVec4T' with [ T=double ] d:\fg\SimGear\simgear/props/props.hxx(684) : while compiling class template member function 'std::istream SGRawBaseT::readFrom(std::istream )' with [ T=SGVec4d ] d:\fg\SimGear\simgear/props/props.hxx(687) : error C2664: 'SGRawValueT::setValue' : cannot convert parameter 1 from 'int' to 'SGVec4d' with [ T=SGVec4d ] Source or target has incomplete type -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] props.hxx - 4 modules not compiling with VC90
Tim Affirmative - Simgear and Flightgear compile and link OK. Thanks. Alan -Original Message- From: Tim Moore [mailto:timo...@redhat.com] Sent: 19 October 2009 15:19 To: FlightGear developers discussions Subject: Re: [Flightgear-devel] props.hxx - 4 modules not compiling with VC90 On 10/19/2009 03:34 PM, Alan Teeder wrote: A heads up Simgear:- matmodel.cxx, model.cxx and Flightgear:- performancedb.cxx, FGDeviceConfigurationMap.cxx are currently failing to compile here with VC90. In each case the error is reported in props.hxx. This is probably my fault, though the code should compile with a properly conforming c++ compiler. Could you try adding #include simgear/math/SGMath.hxx to those files and see if it compiles? Thanks, Tim Strangely only these 4 modules are failing - the many other modules which use this file have no problem. Alan e.g. for matmodel.cxx Compiling... matmodel.cxx d:\fg\SimGear\simgear/props/props.hxx(666) : error C2079: 'SGRawValueContainerT::_obj' uses undefined class 'SGVec3T' with [ T=SGVec3d ] and [ T=double ] d:\fg\SimGear\simgear/props/props.hxx(672) : see reference to class template instantiation 'SGRawValueContainerT' being compiled with [ T=SGVec3d ] d:\fg\SimGear\simgear/props/props.hxx(671) : while compiling class template member function 'SGRawExtended *SGRawBaseT::makeContainer(void) const' with [ T=SGVec3d ] d:\fg\SimGear\simgear/props/props.hxx(692) : see reference to class template instantiation 'SGRawBaseT' being compiled with [ T=SGVec3d ] d:\fg\SimGear\simgear/props/props.hxx(685) : error C2079: 'value' uses undefined class 'SGVec3T' with [ T=double ] d:\fg\SimGear\simgear/props/props.hxx(684) : while compiling class template member function 'std::istream SGRawBaseT::readFrom(std::istream )' with [ T=SGVec3d ] d:\fg\SimGear\simgear/props/props.hxx(687) : error C2664: 'SGRawValueT::setValue' : cannot convert parameter 1 from 'int' to 'SGVec3d' with [ T=SGVec3d ] Source or target has incomplete type d:\fg\SimGear\simgear/props/props.hxx(666) : error C2079: 'SGRawValueContainerT::_obj' uses undefined class 'SGVec4T' with [ T=SGVec4d ] and [ T=double ] d:\fg\SimGear\simgear/props/props.hxx(672) : see reference to class template instantiation 'SGRawValueContainerT' being compiled with [ T=SGVec4d ] d:\fg\SimGear\simgear/props/props.hxx(671) : while compiling class template member function 'SGRawExtended *SGRawBaseT::makeContainer(void) const' with [ T=SGVec4d ] d:\fg\SimGear\simgear/props/props.hxx(694) : see reference to class template instantiation 'SGRawBaseT' being compiled with [ T=SGVec4d ] d:\fg\SimGear\simgear/props/props.hxx(685) : error C2079: 'value' uses undefined class 'SGVec4T' with [ T=double ] d:\fg\SimGear\simgear/props/props.hxx(684) : while compiling class template member function 'std::istream SGRawBaseT::readFrom(std::istream )' with [ T=SGVec4d ] d:\fg\SimGear\simgear/props/props.hxx(687) : error C2664: 'SGRawValueT::setValue' : cannot convert parameter 1 from 'int' to 'SGVec4d' with [ T=SGVec4d ] Source or target has incomplete type -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference
Re: [Flightgear-devel] New Sound system committed
Did another CVS update after reading this post and get same result as Nicolas Alan _ From: Nicolas Quijano [mailto:nquij...@gmail.com] Sent: 19 October 2009 16:24 To: FlightGear developers discussions Subject: Re: [Flightgear-devel] New Sound system committed AIPlane doesn't build here, a problem with conversion from a unsigned char* to the std::auto pointer thingy here : new SGSoundSample((unsigned char*)buf.c_str(), buf.length(), 8000 ); at line 204 Didn't get Alan's errors in SG 'though, even though I use the same compiler as him. Weird. On Mon, Oct 19, 2009 at 11:02 AM, dave perry skida...@mindspring.com wrote: James Sleeman wrote: On 20/10/09 00:07, James Sleeman wrote: On 19/10/09 23:42, Erik Hofman wrote: Ok I think I've ironed out most of the bugs. I hope also the one that James reported but I don't hold my breath for it just yet. So far so good, compiles and runs, and produces sound. Will try a short flight and see if any problems crop up. Seems to be working ok, a bit, umm, stuttery, sort of, particularly background wind, seemed to switch left-right a bit, but those problems might just be me, maybe even just an illusion. With an update this morning from cvs, I still only hear ATC and that with frequency distortion. Did I miss a required library change? I have openal-0.0.9-0.15.20060204cvs.fc9.i386 and freealut-1.1.0-6.fc9.i386 with fc10. -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Be Kind. Remember, everyone is fighting a hard battle. -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [GIT] various fixes including atcvoice, commlist and nans
With the current CVS and VC++ 2008 Express I now get this compilation error: Compiling... fg_init.cxx ..\..\..\src\Main\fg_init.cxx(149) : error C3861: 'gethostname': identifier not found Also, as already discussed here, #include simgear/math/SGMath.hxx is needed before #include simgear/props/props.hxx in perfomancedb.cxx, FGDeviceConfiguration.cxx, and simgear/scene/material/matmodel.cxx and simgear/scene/model/model.cxx -Original Message- From: Csaba Halász [mailto:csaba.hal...@gmail.com] Sent: 26 October 2009 16:47 To: FlightGear developers discussions Subject: Re: [Flightgear-devel] [GIT] various fixes including atcvoice,commlist and nans On Mon, Oct 26, 2009 at 5:18 PM, stefan riemens fgfs.ste...@gmail.com wrote: Unfortunately, this has broken mingw x-compilation for me: ATCVoice.cxx:42: error: expected unqualified-id before '' token Please make sure you don't have a cvs conflict. Line 42 should be using namespace std; and no around there. -- Csaba/Jester -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [GIT] various fixes including atcvoice, commlist and nans
For the missing gethostname, add near the top of fg_init.cxx #if defined (MSC_VER) #include Winsock2.h #endif Alan -Original Message- From: Alan Teeder [mailto:ajtee...@v-twin.org.uk] Sent: 26 October 2009 17:31 To: 'FlightGear developers discussions' Subject: Re: [Flightgear-devel] [GIT] various fixes including atcvoice,commlist and nans With the current CVS and VC++ 2008 Express I now get this compilation error: Compiling... fg_init.cxx ..\..\..\src\Main\fg_init.cxx(149) : error C3861: 'gethostname': identifier not found Also, as already discussed here, #include simgear/math/SGMath.hxx is needed before #include simgear/props/props.hxx in perfomancedb.cxx, FGDeviceConfiguration.cxx, and simgear/scene/material/matmodel.cxx and simgear/scene/model/model.cxx -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] New Sound system committed
I had no sound yesterday evening - but this was an aircraft that I am working on (JSBSim) and didn't investigate why this should be suddenly so. As with Dave Perry I have an Athlon 32 bit machine. _ From: Scott Hamilton [mailto:scott.hamil...@popplanet.biz] Sent: 27 October 2009 11:14 To: FlightGear developers discussions Subject: Re: [Flightgear-devel] New Sound system committed On Tue, 2009-10-27 at 09:03 +0100, Erik Hofman wrote: dave perry wrote: I have been away on a trip for the last 5 days. Today, I did a make clean for both SimGear and fgfs before the compiles. I launched fgfs on the 32bit Athlon and at first, only ATC and no wind or aircraft sounds. It was night, so I used the gui to change the time to afternoon and what do you know, I have all the sounds. If I change back to clock time, only atc sound. This is repeatable. Anyone else who sees this? I tried it locally (with the latest CVS sources for SimGear and FlightGear) and I always get sound. Actually for some aircraft I've lost all sounds, changing time (to one of the presets or clock time) during flight made no difference; dhc8: engine - none flaps transit - none gear transit - none marker morse - none ATC - yes A380: engine - none wind - none tarmac rumble - none flaps transit - yes gear transit - none seat belt chime - yes marker morse - yes ATC - yes c172r engine - none wind - none flaps transit - none marker morse - none ATC - yes The command line args are; bin/fgfs --log-level=warn --enable-hud --enable-sound --airport=YSSY --runway=34L --aircraft=c172r --enable-real-weather-fetch --timeofday=morning --prop:/sim/sound/enabled=true I also noticed that if I change the main volume in the sound dialog, it also reduces the ATC volume, I think the UI assumes they are separate volume controls? Scott. Erik -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] New Sound system committed
With VC++ 2008 Express - no engine sound yesterday Today:- -- Build started: Project: SimGear, Configuration: Release Win32 -- Compiling... sample_group.cxx ..\..\simgear\sound\sample_group.cxx(387) : error C2664: 'isNaN' : cannot convert parameter 1 from 'SGVec3d' to 'float *' No user-defined-conversion operator available that can perform this conversion, or the operator cannot be called ..\..\simgear\sound\sample_group.cxx(388) : error C2664: 'isNaN' : cannot convert parameter 1 from 'SGVec3f' to 'float *' No user-defined-conversion operator available that can perform this conversion, or the operator cannot be called ..\..\simgear\sound\sample_group.cxx(389) : error C2664: 'isNaN' : cannot convert parameter 1 from 'SGVec3f' to 'float *' No user-defined-conversion operator available that can perform this conversion, or the operator cannot be called Build log was saved at file://d:\fg\SimGear\projects\VC90\Win32\Release\BuildLog.htm SimGear - 3 error(s), 0 warning(s) Sorry Alan -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] New Sound system committed
It compiles and sounds are back! That was quick. Well done Alan -Original Message- From: Erik Hofman [mailto:e...@ehofman.com] Sent: 29 October 2009 17:07 To: FlightGear developers discussions Subject: Re: [Flightgear-devel] New Sound system committed Ron Jensen wrote: Hi Erik, Sound seems to work O.K. today for me. Except when I tune atis I get: voice synth: word '(many lines of stuff...)' not found source and listener distance greater than 20km! source and listener distance greater than 20km! And no ATIS sound... I assume its supposed to give sound even if all the samples aren't found? As far as I know it should indeed. Here is the status update of the code: * positioning: needs fixing * orientation and sound direction: should be correct. * velocity vector (and hence Doppler): should be correct. But let me tell you; this evening I'll calibrate that the sound-not-playing bug is finally fixed. Erik -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] boost library version
As as already been pointed out (by Vivian I think) you do not need to compile boost as FG only uses the header files. So just include the headers from the latest version, you do not need the compiled libraries. -- From: Geoff McLane ubu...@geoffair.info Sent: Friday, November 20, 2009 11:51 AM To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] boost library version On Thu, 2009-11-19 at 10:09 -0700, dave perry wrote: [snip] I Googled boost 1.40 source, downloaded boost_1_40_0.tar.bz2 [snip] Hi Dave P., Thanks for the info. I guess that would be the same as their online documentation, which I had read :- http://www.boost.org/doc/libs/1_41_0/more/getting_started/unix-variants.html And yes, this LOOKS EASY, and simple... but this requires - (a) unpacking the WHOLE package, and (b) compiling it as indicated... Generally, I like to 'install' packages like this through the update manager, and not fiddle with them myself... And, as you can read in section 3, in our case we presently only need the 'headers'... so yes, you probably compiled a lot more than required, but all worked. as it should ;=)) Maybe if I too updated to Ubuntu 9.10 (the latest), it _MAY_ have a later version of boost available, but I chose 8.04 LTS, specifically because of its 'Long Term Support, and I hope the distro packages will be 'soon' updated... I have put a message on the Ubuntu forum, Installation Upgrades, asking if and when it is likely that they will update 'boost' in my 8.04 LTS package manager... But thanks again... Regards, Geoff. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Debug Assertion Failed in Sample_opneal.hxx
First the good news, with the current CVS on XP, VC++2008 Flightgear runs well.
The bad news is that on my Vista laptop it stops with a Debug Assertion
Failure before the splash screen is replaced by the runtime display.
VC++2008 debug output is attached.
Both machines have an an identical setup as far as Flightgear is concerned and
I have checked that OpenAL32.dll and wrap_oal.dll are the latest versionfrom
the Creative site. Also the sound device drivers (Realtek High Definition) are
up to date.
The breakpoint is at line 175 in Sample_openal.hxx:-
void free_data() {
if ( _data ) free( _data ); _data = NULL;
The Stack frame points back to line 476 of soundmgr_openal.cxx:-
if ( !testForALError(buffer add data) ) {
'fgfs.exe': Loaded 'D:\FlightGear\source\projects\VC90\Win32\Debug\fgfs.exe',
Symbols loaded.
'fgfs.exe': Loaded 'C:\Windows\System32\ntdll.dll'
'fgfs.exe': Loaded 'C:\Windows\System32\kernel32.dll'
'fgfs.exe': Loaded 'C:\Windows\System32\opengl32.dll'
'fgfs.exe': Loaded 'C:\Windows\System32\msvcrt.dll'
'fgfs.exe': Loaded 'C:\Windows\System32\advapi32.dll'
'fgfs.exe': Loaded 'C:\Windows\System32\rpcrt4.dll'
'fgfs.exe': Loaded 'C:\Windows\System32\gdi32.dll'
'fgfs.exe': Loaded 'C:\Windows\System32\user32.dll'
'fgfs.exe': Loaded 'C:\Windows\System32\glu32.dll'
'fgfs.exe': Loaded 'C:\Windows\System32\ddraw.dll'
'fgfs.exe': Loaded 'C:\Windows\System32\dciman32.dll'
'fgfs.exe': Loaded 'C:\Windows\System32\setupapi.dll'
'fgfs.exe': Loaded 'C:\Windows\System32\oleaut32.dll'
'fgfs.exe': Loaded 'C:\Windows\System32\ole32.dll'
'fgfs.exe': Loaded 'C:\Windows\System32\dwmapi.dll'
'fgfs.exe': Loaded 'C:\Windows\System32\winmm.dll'
'fgfs.exe': Loaded 'C:\Windows\System32\oleacc.dll'
'fgfs.exe': Loaded 'C:\Windows\System32\wsock32.dll'
'fgfs.exe': Loaded 'C:\Windows\System32\ws2_32.dll'
'fgfs.exe': Loaded 'C:\Windows\System32\nsi.dll'
'fgfs.exe': Loaded
'D:\FlightGear\install\msvc90\OpenSceneGraph\bin\osg60-osgd.dll'
'fgfs.exe': Loaded
'D:\FlightGear\install\msvc90\OpenSceneGraph\bin\ot11-OpenThreadsd.dll'
'fgfs.exe': Loaded
'C:\Windows\winsxs\x86_microsoft.vc90.debugcrt_1fc8b3b9a1e18e3b_9.0.30729.1_none_bb1f6aa1308c35eb\msvcr90d.dll'
'fgfs.exe': Loaded
'C:\Windows\winsxs\x86_microsoft.vc90.debugcrt_1fc8b3b9a1e18e3b_9.0.30729.1_none_bb1f6aa1308c35eb\msvcp90d.dll'
'fgfs.exe': Loaded
'D:\FlightGear\install\msvc90\OpenSceneGraph\bin\osg60-osgDBd.dll'
'fgfs.exe': Loaded
'D:\FlightGear\install\msvc90\OpenSceneGraph\bin\osg60-osgUtild.dll'
'fgfs.exe': Loaded
'D:\FlightGear\install\msvc90\OpenSceneGraph\bin\osg60-osgViewerd.dll'
'fgfs.exe': Loaded
'D:\FlightGear\install\msvc90\OpenSceneGraph\bin\osg60-osgGAd.dll'
'fgfs.exe': Loaded
'D:\FlightGear\install\msvc90\OpenSceneGraph\bin\osg60-osgTextd.dll'
'fgfs.exe': Loaded 'C:\Windows\System32\comdlg32.dll'
'fgfs.exe': Loaded 'C:\Windows\System32\shlwapi.dll'
'fgfs.exe': Loaded
'C:\Windows\winsxs\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.6001.18000_none_886786f450a74a05\comctl32.dll'
'fgfs.exe': Loaded 'C:\Windows\System32\shell32.dll'
'fgfs.exe': Loaded 'C:\Windows\System32\OpenAL32.dll'
'fgfs.exe': Loaded 'D:\FlightGear\3rdParty\bin\alut.dll', Binary was not built
with debug information.
'fgfs.exe': Loaded
'D:\FlightGear\install\msvc90\OpenSceneGraph\bin\osg60-osgParticled.dll'
'fgfs.exe': Loaded 'C:\Windows\System32\shimeng.dll'
'fgfs.exe': Loaded 'C:\Windows\System32\apphelp.dll'
'fgfs.exe': Loaded 'C:\Windows\AppPatch\AcLayers.dll'
'fgfs.exe': Loaded 'C:\Windows\System32\userenv.dll'
'fgfs.exe': Loaded 'C:\Windows\System32\secur32.dll'
'fgfs.exe': Loaded 'C:\Windows\System32\winspool.drv'
'fgfs.exe': Loaded 'C:\Windows\System32\mpr.dll'
'fgfs.exe': Loaded 'C:\Windows\System32\imm32.dll'
'fgfs.exe': Loaded 'C:\Windows\System32\msctf.dll'
'fgfs.exe': Loaded 'C:\Windows\System32\lpk.dll'
'fgfs.exe': Loaded 'C:\Windows\System32\usp10.dll'
'fgfs.exe': Loaded 'C:\Program Files\Sophos\Sophos
Anti-Virus\sophos_detoured.dll'
'fgfs.exe': Loaded 'C:\Windows\System32\psapi.dll'
'fgfs.exe': Loaded
'C:\Windows\winsxs\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.6002.18005_none_5cb72f96088b0de0\comctl32.dll'
First-chance exception at 0x75c3fbae in fgfs.exe: Microsoft C++ exception:
sg_io_exception at memory location 0x0012cc54..
'fgfs.exe': Loaded 'C:\Windows\System32\uxtheme.dll'
'fgfs.exe': Loaded 'C:\Windows\System32\ig4icd32.dll', Binary was not built
with debug information.
'fgfs.exe': Loaded 'C:\Windows\System32\ig4dev32.dll', Binary was not built
with debug information.
'fgfs.exe': Loaded 'C:\Acer\Empowering Technology\ePower\SysHook.dll', Binary
was not built with debug information.
'fgfs.exe': Loaded
'D:\FlightGear\install\msvc90\OpenSceneGraph\bin\osgPlugins-2.9.5\osgdb_pngd.dll'
'fgfs.exe': Loaded
'D:\FlightGear\install\msvc90\OpenSceneGraph\bin\osgPlugins-2.9.5\osgdb_txfd.dll'
'fgfs.exe': Loaded
'D:\FlightGear\install\msvc90\OpenSceneGraph\bin\osgPlugins-2.9.5\osgdb_acd.dll'
Re: [Flightgear-devel] Debug Assertion Failed in Sample_opneal.hxx
Erik Thanks for the reply. Unfortunately it is the Vista machine that is having this problem - the XP one is fine. Flightgear 1.9.1 is OK, and until recently all was well with the CVS. It looks as if I will have to back out the CVS versions until I can isolate the change which first exhibits this problem. Alan -- From: Erik Hofman e...@ehofman.com Sent: Sunday, December 06, 2009 9:31 AM To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] Debug Assertion Failed in Sample_opneal.hxx Alan Teeder wrote: First the good news, with the current CVS on XP, VC++2008 Flightgear runs well. The bad news is that on my Vista laptop it stops with a Debug Assertion Failure before the splash screen is replaced by the runtime display. Both machines have an an identical setup as far as Flightgear is concerned and I have checked that OpenAL32.dll and wrap_oal.dll are the latest versionfrom the Creative site. Also the sound device drivers (Realtek High Definition) are up to date. Maybe this message will help? http://opensource.creative.com/pipermail/openal/2008-May/011176.html Erik -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ 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 I have investigated when this bug started on my Vista laptop. CVS of Simgear +Flightgear from 4 October runs on the Vista Machine )but without sound - I probably need to CVS the data as well. CVS from 6 October fails in Sample_openal.hxx as per my note at he start of this thread. It is narrowing down. Alan -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ 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 An aircraft that I am developing caused Flightgear to crash on the Vista box, but not on the XP one. This I traced to some bad coding in my JSBsim aero file:- table !-- Ch-delta elevator -- independentVar lookup=row fcs/elevator-pos-deg/independentVar tableData !-- ** No surface deflections specified in input file ** -- /tableData /table It was an empty table generated by Datcom+ which I had not got around to filling in. The XP machine, which I use most of the time does not hiccup at this. Flightgear on the Vista laptop also crashes with something that appears to be related to the sound patches, AND also every time that I exit. The XP box sees none of these problems. From this I now believe that the problem is that the Vista laptop is less tolerant of run-time errors than the XP box. As far as Sample_openal.hxx is concerned all I can guess from my debug sessions at is that there is some kind of a problem at the time that Rumble.wav is used and it is even possible that the problem is at the XML code level. Alan -- From: Erik Hofman e...@ehofman.com Sent: Sunday, December 06, 2009 9:31 AM To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] Debug Assertion Failed in Sample_opneal.hxx Alan Teeder wrote: First the good news, with the current CVS on XP, VC++2008 Flightgear runs well. The bad news is that on my Vista laptop it stops with a Debug Assertion Failure before the splash screen is replaced by the runtime display. Both machines have an an identical setup as far as Flightgear is concerned and I have checked that OpenAL32.dll and wrap_oal.dll are the latest versionfrom the Creative site. Also the sound device drivers (Realtek High Definition) are up to date. Maybe this message will help? http://opensource.creative.com/pipermail/openal/2008-May/011176.html Erik -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Adjusting the Adjust View Distance
seconded Alan From: UltraZexe Zexeonyo Sent: Tuesday, December 08, 2009 11:31 AM To: flightgear-devel@lists.sourceforge.net Subject: [Flightgear-devel] Adjusting the Adjust View Distance Hi all, I'm very new to this and so forgive me for my abrupt and mailing. I was referred to this devel-list by Gijs as it may interest some of you. Adjusting the 'Adjust View Distance' I have a little different taste than others especially when it comes to the Point of View (POV) of the cockpit. Where most pilots like to fly with a POV of 70- 80, I like to use 120. However, there is one problem with this, using a POV @ 120 causes the cockpit to look very very far away, making it almost impossible to see the instruments, unless of course you zoom it back up to a POV of 80. But you can fly using a POV @ 120 with no problem by adjusting the 'Adjust View Distance' from the 'View' menu. Simply click the dial on the 'Forward/backward' and stop where you like. For some planes, this works very well, for others, it's a disaster. The issue: The Adjust View Distance dial is over-sensitive, if I want a view distance of '0', i would click on '0' but because it's so sensitive, I always over-shoot the '0' mark and always hit '1.0m' or '-0.9m'. The difference in view is dramatic and can be a major flying issue. The solution: The problem is that the dial has a minimum of (-100) to a maximum of (100). The range of it is too large. We need to change the range to a smaller workable range, a good minimum and maximum is (-5m) to (5m). You could change it to (-1m) to (1m) if you wanted to. Where to change these variables? Go to Flightgear/data/GUI/dialog/pilot_offset. In the minimum and maximum field type in the new numbers, (-5m) and (5m) for Left and right, Up and Down, and Forward and Backwards. Save and quit. If you want the Adjust View Distance even more specific, decrease the range, so a good range would be (-1m) to (1m). So, if the cockpit is too close or too far, but you don't want to change the POV, using the adjust view distance is a good way to solve the problem. Just make sure that the Adjust View Distance range is calibrated to your likings. I use (-1m) to (1m) to get the distance just right. If you have any questions feel free to contact me via email. -Zexe Windows LiveT Hotmail is faster and more secure than ever. Learn more. -- 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
With the current CVS on my XP machine (the one that runs) I have been trying
to debug this problem. Here is the progress to date.
I have edited free_data as so to allow facilitate breakpoint setting
void free_data()
{
if ( _data )
free( _data );
_data = NULL;
}
and then set a breakpoint at the if statement.
If I single step (F11) at the first occurrence of the breakpoint it fails as
it enters free( _data)
My guess is that space is not allocated for the rumble.wav data.
Sadly I am retired now and it is several years since I last debugged a
program. Even then as a Fortran man my C++ skills were somewhat lacking an
things like pointers to pointers got my poor brain confused.
I suppose the good news is that I am able to duplicate the fault on the XP
machine (which normally runs without fault) simply by using debug runtime..
Hope this is some help.
Alan
--
From: Erik Hofman e...@ehofman.com
Sent: Monday, December 07, 2009 1:37 PM
To: FlightGear developers discussions
flightgear-devel@lists.sourceforge.net
Subject: Re: [Flightgear-devel] Debug Assertion Failed in Sample_opneal.hxx
Alan Teeder wrote:
Eric
An aircraft that I am developing caused Flightgear to crash on the Vista
box, but not on the XP one.
This I traced to some bad coding in my JSBsim aero file:-
table!-- Ch-delta
elevator --
independentVar lookup=row
fcs/elevator-pos-deg/independentVar
tableData
!-- **
No surface deflections specified in input file
** --
/tableData
/table
It was an empty table generated by Datcom+ which I had not got around to
filling in.
The XP machine, which I use most of the time does not hiccup at this.
Flightgear on the Vista laptop also crashes with something that appears
to
be related to the sound patches, AND also every time that I exit.
The XP box sees none of these problems.
From this I now believe that the problem is that the Vista laptop is less
tolerant of run-time errors than the XP box.
As far as Sample_openal.hxx is concerned all I can guess from my debug
sessions at is that there is some kind of a problem at the time that
Rumble.wav is used and it is even possible that the problem is at the
XML
code level.
It's not getting easier to track down. Although maybe it indicates an
uninitialized variable or something like that.
It might even be allocated memory that is reserved at an unrelated piece
of code but that overwrites the section that gets freed by the
soundmanager.
Erik
--
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
___
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 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. By good news I mean that in Debug mode it is not a fault that exists only on my Vista laptop and therefore should be possible to replicate on any other XP/Vista box. Debugging is slow at the moment as there are currently over 5 lines of First-chance exception at 0x7c812afb in fgfs.exe: Microsoft C++ exception: FP_Inactive at memory location 0x0012f682.. to process before this routine is called. Alan -- From: Erik Hofman e...@ehofman.com Sent: Tuesday, December 08, 2009 1:12 PM To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] Debug Assertion Failed in Sample_opneal.hxx Alan Teeder wrote: I suppose the good news is that I am able to duplicate the fault on the XP machine (which normally runs without fault) simply by using debug runtime.. I'm not sure that's good news.. Are both systems the same (64-bit or 32-bit)? 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] Debug Assertion Failed in Sample_opneal.hxx
Eric This may be of some use. I am getting the debug message:- HEAP[fgfs.exe]: Invalid Address specified to RtlValidateHeap( 02F4, 2EEE0028 ) Windows has triggered a breakpoint in fgfs.exe. _data which free_data is working on is 2EEE0048.~yslcYOF:74457BJSetc (rumble.wav data) Alan -- From: Erik Hofman e...@ehofman.com Sent: Tuesday, December 08, 2009 1:12 PM To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] Debug Assertion Failed in Sample_opneal.hxx Alan Teeder wrote: I suppose the good news is that I am able to duplicate the fault on the XP machine (which normally runs without fault) simply by using debug runtime.. I'm not sure that's good news.. Are both systems the same (64-bit or 32-bit)? 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] 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] Flight Gear on Windows
I am no longer seeing the first two bugs which seem to have been sorted out this week, but do have a similar problem with sound. See my thread with Eric. From: Vivian Meazza Sent: Friday, December 11, 2009 9:13 PM To: 'FlightGear developers discussions' Subject: Re: [Flightgear-devel] Flight Gear on Windows Geoff, I agree with all you have said, but would add the following: The reset bug has been sorted. The crash-on-exit bug has probably been sorted, but I haven't had time to test it yet. I don't see the red/orange effect you report. There is a binary here - a few days old, and using osg rev. 10753 - ftp://ftp.abbeytheatre2.org.uk/fgfs/executable/ It might be helpful if you could test it to see if it solves any of your bugs. Vivian -Original Message- From: Geoff McLane [mailto:ubu...@geoffair.info] Sent: 11 December 2009 12:37 To: FlightGear developers discussions Cc: joshua.c.stonestr...@ivv.nasa.gov Subject: Re: [Flightgear-devel] Flight Gear on Windows On Thu, 2009-12-10 at 11:29 -0500, Joshua C. Stonestreet wrote: RE: Building SG/FG in native MS Windows using MSVC You do not specifically state which MSVC build files you started with, but assume you used those in the respective SG/FG cvs or tar.gz sources? Nearly ALWAYS the MSVC build files are OUT-OF-DATE! This is a FAST changing project, and it is nearly IMPOSSIBLE to keep MSVC build files fully up-to-date! But that said, it is usually a simple matter to start with the current build files, and (a) delete files that no longer exist in the respective source, and (b) when you come to the link, if new files have been added to either SG or FG they will show up as unresolved externals, and you just search for where the particular functions is defined in the source, and ADD those new files to the respective projects. And while you do not particularly need to re-create exactly the same folder structure, not doing so will always mean making more adjustments in the MSVC IDE Property Pages - Configuration Properties - C/C++ - General - Additional Include Directories, and Linker - General - Additional Library Directories, and/or Linker - Input - Additional Dependencies. I have dedicated a section of my site to building flightgear, but it too will always be out-of-date, sometimes just hours after putting it there ;=)), and I now use a 'complete' - that is _ALL_ dependent sources - approach _NOT_ suited to all ;=(), especially since it depends on re-creating the EXACT folder structure for SOURCE and then copies everything to a WORK folder, using the SETUPFG.BAT file... but it works well for me ;=)) See :- http://geoffair.net/fg , specifically http://geoffair.net/fg/fgfs-047.htm , but many other pages with hopefully helpful hints... I too have NOT done an update for a while, due to some new systems (sound, shaders, etc) being modified/added recently, such that I have not yet been able to build a fully stable WIN32 version using MSVC9. Two important things hold me back at the moment, and they are :- (i) a red/orange (and sometimes dark) pall, overlay, over the scene in certain, very repeatable, circumstances, see - http://www.av8n.com/fly/fgfs/htm/bug-list.htm#bug-orange-pall , and http://geoffair.net/tmp/fg/ , and (ii) using the reset causes a crash! The only other MSVC build file set I know about is here :- ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/ - and the sub-directory - ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/MSVC/ Maybe others could remind us of other MS WIN native, MSVC build help locations... and I read here and there some have good success with CygWin... But 'old' MSVC build files in native windows is a way of life in fast changing projects ;=)) Hope this helps. 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 -- 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] Flight Gear on Windows
It is strange that I am the only one reporting this fault, but it is still there. On both my Vista laptop and the XP box it fails if run from Visual C++ 2008 with Debug - Start Debugging. On the Vista laptop it also fails if I run the release build from fgrun , but only if sound is enabled. This case is OK on the XP box. The only compilation flag that I have added to the CVS VC90 configuration is NOMINMAX. VC90 build is very out of date and quite few new files and libraries have to be added. As of today version.h is not found. I have hand built one from version.h.in, with the line #define SIMGEAR_VERSION 1.99.4. Alan -- From: Erik Hofman e...@ehofman.com Sent: Monday, December 14, 2009 9:09 AM To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] Flight Gear on Windows Alan Teeder wrote: I am no longer seeing the first two bugs which seem to have been sorted out this week, but do have a similar problem with sound. See my thread with Eric. Is this something I need to look after or is it a matter of finding the proper compile options? 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] Flight Gear on Windows
On the other hand probably most newcomers to Flightgear CVS are using Windows. The present setup has rather a steep learning curve to achieve first build and may cause many to think that Flightgear is broke and not worth the effort. I am using the 3rd party from ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/MSVC/ to which I have added the latest OpenAL and alut from the Creative site . Boost (headers only) is also required. The DLLs should be in the PATH environment. The VC90 setup already has the library and include file search paths set correctly. At the moment Simgear needs sample_group.cxx/hxx added to the project and NOMINMAX set. Flightgear needs 4 pairs of .cxx, .hxx files ( Sample_queue, FGGyro, FGMagnetometer, AIGroundVehice) to be added to the project and NOMINMAX set. Simgear.h is not generated automatically, so I make my own. OSGText.lib need to be added to the fgviewer project. My build tree is simple with Data, Source, Simgear, 3rd Party Boost.1.39.0 and Install directories all at the same level. This fits in with the Flightgear project that is in the CVS. I may have missed something out, but hopefully most of the changes are above. Finally the data needs to be updated via CVS as the latest gui and other files are needed. Unfortunately the documented build procedures in the FlightGear Wiki http://wiki.flightgear.org/index.php/Building_Flightgear_-_Windows and on Geoff Lane´s excellent FlightGear Build Centre http://www.geoffmclane.com/fg/ do not use this simple structure and require extensive downloading (after setting up CVS, SVN and Git) and then building of the prerequisites as well as the prerequisites of the prerequisites. They may even waste a day building Boost, when only the headers are needed. Alan P.s. I note that the following are not in my build, but do not cause any link errors. Simgear/scene/model :- animation, BoundingVolumeBuildVisitor, CheckSceneryVisitor,shadanim and shadowvisitor. -- From: Olaf Flebbe f...@oflebbe.de Sent: Tuesday, December 15, 2009 9:59 PM To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] Flight Gear on Windows I was asked to remove them! Who asked, and why? I did not read this on the list, or maybe missed it, otherwise I would have offered an 'opinion' then ;=)) I was one of the guys who asked him. If I remember correctly I had it CC'ed on the list. The DSP Files where unchanged for years and didn't work out of the box for years. The am2dsp scripts had to be updated but no one seemed to care for years. I agree that it is rather futile to get vcproj files up-to-date. IMHO converting autoconf isn't optimal, too. Olaf -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Flight Gear on Windows
Correction;: I do have shadanim and CheckScenary visitor in my build. (Red face again) -- From: Alan Teeder ajtee...@v-twin.org.uk Sent: Wednesday, December 16, 2009 11:37 AM To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] Flight Gear on Windows On the other hand probably most newcomers to Flightgear CVS are using Windows. The present setup has rather a steep learning curve to achieve first build and may cause many to think that Flightgear is broke and not worth the effort. I am using the 3rd party from ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/MSVC/ to which I have added the latest OpenAL and alut from the Creative site . Boost (headers only) is also required. The DLLs should be in the PATH environment. The VC90 setup already has the library and include file search paths set correctly. At the moment Simgear needs sample_group.cxx/hxx added to the project and NOMINMAX set. Flightgear needs 4 pairs of .cxx, .hxx files ( Sample_queue, FGGyro, FGMagnetometer, AIGroundVehice) to be added to the project and NOMINMAX set. Simgear.h is not generated automatically, so I make my own. OSGText.lib need to be added to the fgviewer project. My build tree is simple with Data, Source, Simgear, 3rd Party Boost.1.39.0 and Install directories all at the same level. This fits in with the Flightgear project that is in the CVS. I may have missed something out, but hopefully most of the changes are above. Finally the data needs to be updated via CVS as the latest gui and other files are needed. Unfortunately the documented build procedures in the FlightGear Wiki http://wiki.flightgear.org/index.php/Building_Flightgear_-_Windows and on Geoff Lane´s excellent FlightGear Build Centre http://www.geoffmclane.com/fg/ do not use this simple structure and require extensive downloading (after setting up CVS, SVN and Git) and then building of the prerequisites as well as the prerequisites of the prerequisites. They may even waste a day building Boost, when only the headers are needed. Alan P.s. I note that the following are not in my build, but do not cause any link errors. Simgear/scene/model :- animation, BoundingVolumeBuildVisitor, CheckSceneryVisitor,shadanim and shadowvisitor. -- From: Olaf Flebbe f...@oflebbe.de Sent: Tuesday, December 15, 2009 9:59 PM To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] Flight Gear on Windows I was asked to remove them! Who asked, and why? I did not read this on the list, or maybe missed it, otherwise I would have offered an 'opinion' then ;=)) I was one of the guys who asked him. If I remember correctly I had it CC'ed on the list. The DSP Files where unchanged for years and didn't work out of the box for years. The am2dsp scripts had to be updated but no one seemed to care for years. I agree that it is rather futile to get vcproj files up-to-date. IMHO converting autoconf isn't optimal, too. Olaf -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] auto-coordination broken
Moving the joystick or throttle should override the autopilot/autothrotle and cause it to disconnect. Yaw dampers, stick pushers and other stability augmentation demands are added to the pilots´s joystick/rudder input, they would not normally override it. In a training mode there is a case for letting the autopilot automatically re-engage when the pilot has stopped playing around so that the aircraft returns to stable flight. The Ercoupe and certain other aircraft (e.g. TSR2) may have an aileron-rudder interconnect, but this is very aircraft specific and should be part of the aircraft FCS model. Surely the deadspace function of the joystick configuration is meant to cope with noise problems.. Alan -- From: Stuart Buchanan stuart_d_bucha...@yahoo.co.uk Sent: Tuesday, December 22, 2009 9:35 AM To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] auto-coordination broken Ron Jensen wrote: Are you sure you don't have some noisy input device like a joystick or pedals connected that might affect the rudder axis? If two input axes are bound to the same control the last write wins. Thanks for the hint. That helps. It makes sense from a developers' point of view. However ... we still have a bug from the users' point of view. The documentation explicitly mentions the case where the user has a rudder input device but lacks the skill to handle the proper ratio ... and recommends --enable-auto-coordination in this case. If users are required to have zero-noise ailerons and zero-noise rudders, this is quite a serious restriction. This should be prominently mentioned in the documentation. Users will not be pleased. O.K. I guess the documentation should say to remove your rudder pedals when auto-coordinating, or perhaps joysticks configs could pick up on it and not try to drive the rudder. I think all that is required is that we make clear that auto-coordination is designed to help people without any rudder control axis, and that a proper rudder axis (or even a twist axis on a joystick) is preferable. I'll do that in the documentation. However, to hijack the thread further ... ;) There was some previous discussion about the fact that we have manual controls and some autopilots all mapping to a single set of control properties (/controls/flight/[aileron|elevator|rudder]). This is realistic, but because of the limitations of the simulator environment, this can cause them to fight for control - the classic example being someone moving their joystick while the autopilot is switched on. I think if we every fix that, we should consider auto-coordination as another channel into that control mixer. -Stuart -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] auto-coordination broken
-- From: leee l...@spatial.plus.com Sent: Tuesday, December 22, 2009 10:05 PM To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] auto-coordination broken On Tuesday 22 Dec 2009, Alan Teeder wrote: [snip...] The Ercoupe and certain other aircraft (e.g. TSR2) may have an aileron-rudder interconnect, but this is very aircraft specific and should be part of the aircraft FCS model. The YASim BAC-TSR2 doesn't/didn't/shouldn't have an aileron-rudder interconnect. Sorry, I should have been clearer. I was referring to the real aircraft, not your YASim model. It was needed to counteract the yaw due to the tailerons. Alan -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Windows CVS update warnings
I am not getting this so it seems that your CVS is confused, as Eric suggests. My CVS gets screwed up from time to time and I find the quickest and safest solution is to delete everything and start again. Don´t forget to keep your modified files before the delete. In this instance you only need delete the affected aircraft. e.g A380, Long-EZ etc. I have come to the conclusion that CVS is not a very robust system as these corruptions have occurred here several times. Alan -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Windows CVS update warnings
Geoff I am using TortoiseCVS From here I see the same as you with both A380.rgb and a380.rgb at http://cvs.flightgear.org/viewvc/data/Aircraft/A380/Models/ I deleted the A380 directory and re-ran CVS, but no conflicts and A380.rgb and not a380.rgb appeared in A380/models. In the past I have seen upper-lower case CVS conflicts. These were reported by others on the forum and quickly fixed. However Tortoise reports no problems at the movement. Perhaps I should give winCVS or CVSNT a whirl to see what happens. Sorry if this is adding to the confusion. Alan -- From: Geoff McLane ubu...@geoffair.info Sent: Saturday, January 02, 2010 12:47 PM To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] Windows CVS update warnings On Sat, 2010-01-02 at 10:45 +0100, Erik Hofman wrote: Ubuntu Air wrote: Hi FG data cvs maintainers, When updating FG data in Windows, I continually, for quite some time now, get the following CVS warnings :- cvs update: move away Aircraft/A380/Models/a380.rgb; it is in the way It looks like you have local updates that have never been in CVS. If that's unintentional you could run cvs up -PdC (in the a380 directory) to replace the conflicting files. Erik Hi Eric, Alan, Thanks for the replies. But what you are suggesting is that ViewVC also 'lies'. Try say :- http://cvs.flightgear.org/viewvc/data/Aircraft/A380/Models/ and you will clearly 'see' there are TWO(2) files listed :- A380.rgb, _AND_ a380.rgb! As stated, this is the SAME for the others checked, but have NOT checked all... And then checking my Ubuntu linux fgfs/data - ~/fg/fg7/fgfs$ find data/Aircraft/A380/Models -name a380.rgb -type f data/Aircraft/A380/Models/a380.rgb ~/fg/fg7/fgfs$ find data/Aircraft/A380/Models -name A380.rgb -type f data/Aircraft/A380/Models/A380.rgb showing in my linux cvs 1.12.13, both files get downloaded... And just for the record, although I have never really seen my CVS 1.11.17 GNU WIN32 port 'confused', except on one file in SG, simgear\magvar\coremag.cxx, which I have written about before, I did try (a) deleting ALL, which these days takes 'forever' to do a full fresh FG data checkout, approx. 45K files, 2.7GB, and (b) deleting the specific directories... But the warnings persists... as they should in Windows, when there are two files of the same name, but just different case ;=)) What cvs client are you using in Windows Alan? And perhaps more importantly, what is it doing about 2 files of the SAME name, different case? I have read there are ways to perhaps configure NTFS to be case sensitive, but have never tried this, preferring windows 'native' ;=() Regards, Geoff. Windows CVS warnings: cvs update: move away Aircraft/A380/Models/a380.rgb; it is in the way cvs update: move away Aircraft/A380/Textures/Livery/House/COWLING.rgb; it is in the way cvs update: move away Aircraft/A380/Textures/Livery/House/ENDPLATE.rgb; it is in the way cvs update: move away Aircraft/Long-EZ/Nasal/electrical.nas; it is in the way cvs update: move away Aircraft/Noratlas/Readme-First; it is in the way cvs update: move away Aircraft/Zlin-50lx/Models/Lights/Whitelight.xml; it is in the way cvs update: move away Aircraft/dhc2/Models/Instruments/kn53.png; it is in the way cvs update: move away Aircraft/eurofighter/Models/typhoon.xml; it is in the way cvs update: move away Aircraft/fokker50/Models/instruments/general/nav.rgb; it is in the way PS: I normally use cvs up -dPA, and never need -C, since that particular directory _NEVER_ contains any 'locally modified files'. If I do make mods, I copy _all_ to a new directory first, to play, keeping 'C:\FGCVS\FlightGear\data' ONLY for cvs updates... And although I do get the cvs log emails, this gives me a second chance to 'review' what has changed ;=)) -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list
Re: [Flightgear-devel] Native WIN32 MSVC9 build error
Not a lot of help to you, but I´m not seeing this problem here. When was your last successful build? Alan -- From: Geoff McLane ubu...@geoffair.info Sent: Friday, January 08, 2010 6:53 PM To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: [Flightgear-devel] Native WIN32 MSVC9 build error Hi, 1. Did a SG/FG/data CVS update earlier today, but ran into this ERROR when compiling FG, repeated for other files which include 'flight.hxx'... Gear.cpp c:\FG\32\FlightGear\src\FDM/flight.hxx(110) : error C2678: binary '==' : no operator found which takes a left-hand operand of type 'const SGGeod' (or there is no acceptable conversion) C:\Program Files\Microsoft SDKs\Windows\v6.1\include \guiddef.h(192): could be 'int operator ==(const GUID ,const GUID )' c:\FG\32\SimGear\simgear/timing/timestamp.hxx(207): or 'bool operator ==(const SGTimeStamp ,const SGTimeStamp )' while trying to match the argument list '(const SGGeod, const SGGeod)' I remember reading something about this operator ==, comparing two SGGeod's in the CVS logs, so maybe I have missed something, or the cvs update failed. Have not had a chance yet to attempt the same in Ubuntu... But meantime, any help appreciated... 2. Also, when compiling SG, I get a repeated warning, for files including 'EffectBuilder.hxx', like TextureBuilder.cxx c:\fg\32\simgear\simgear\scene\material\EffectBuilder.hxx(280) : warning C4099: 'simgear::InstallAttributeBuilder' : type name first seen using 'class' now seen using 'struct' c:\fg\32\simgear\simgear\scene\material\EffectBuilder.hxx(269) : see declaration of 'simgear::InstallAttributeBuilder' It does seem to be declared a 'class' in one place, then a structure in another... so seems an avoidable warning... These happened on both my all-in-one build system, and the 3rd Party type build using the projects/VC90 build files... Regards, Geoff. PS: The cvs status on this flight.hxx is C:\FGCVS\FlightGear\source\src\FDMcvs status flight.hxx === File: flight.hxxStatus: Up-to-date Working revision:1.23 Repository revision: 1.23/var/cvs/FlightGear-0.9/source/src/FDM/flight.hxx,v Sticky Tag: (none) Sticky Date: (none) Sticky Options: (none) Is this wrong? -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Ubuntu fatal error - rumble.wav?
Eric Could you let us know which version of Alut and OpenAl you are using for your sound development work. It would help if we were all playing from the same sheet of music.. I still see the stack related problem. Alan -- From: Erik Hofman e...@ehofman.com Sent: Monday, January 11, 2010 7:45 PM To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] Ubuntu fatal error - rumble.wav? Geoff McLane wrote: Thank you for the reply, but now I am even more confused ;=() Ah wait, I looked at the code for a different ALUT version.. I must have looked at the wrong code because of it ran great a few days ago, when I reported all seemed well... but now... and the code I looked at was changed just a few days ago. I'm starting to wonder what has changed in the mean time.. need to look at that this week (I'm quite busy so i can't promise any time frame). I looks odd since this line 'int error = alutGetError();' should clear any error for the next call. Erik -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [Simgear-cvslogs] CVS: SimGear/projects/VC90 SimGear.vcproj, 1.8, 1.9
Frederic Thanks for that. Simgear now builds out of the box from the Flightgear VC90 project file, using Fred´s directory structure. I think that a version of simgear.h for VC90 Flightgear itself is still needed. Alan -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: source configure.ac, 1.162, 1.163
Frederic Thanks for today's updates to the Windows build. Flightgear now builds out of the box - well almost. The start point was your 3rd party zip file at ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/MSVC/ I had to make an SVN build of Openscenegraph to get rid of CLEAR_MASK not a member of osg.CullSettings errors in CameraGroup.cxx During this build I overwrote the 3rd party file that they supply over yours, and installed the new Openscenegraph in your install directory. My OpenAl and alut have been updated from the Creative site. Because of differences in OpenAl and Simgear calling conventions all of the alut and Openal includes are repeated in 3rdParty/include and 3rdParty/incude.h Also I built my own plib, but this was just to eliminate all the missing pdb file warnings at Flightgear link time. It was not really necessary. This is a summary of the changes that I can remember that made to your 3rd party distribution. Hopefully these notes cover all of the important steps. Finally I made up my own file simgear/version.h The good news is at last we have up-to-date build files in the CVS. It will be interesting to hear how others get on. Good to have you back. Alan -- From: Heiko Schulz aeitsch...@yahoo.de Sent: Sunday, January 17, 2010 3:15 PM To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: [Flightgear-devel] [Flightgear-cvslogs] CVS: source configure.ac,1.162, 1.163 Welcome back, Frederic! Where have you been so long? :-) still in work: http://www.hoerbird.net/galerie.html But already done: http://www.hoerbird.net/reisen.html __ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Nominations for Aircraft Selection intheFlightGear 2.0 Release
Well if you build from CVS you will find that CVS.data has also to be updated as the version has changed to 2. I have failed to spot any warning about this. -- From: Heiko Schulz aeitsch...@yahoo.de Sent: Tuesday, January 19, 2010 10:32 PM To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] Nominations for Aircraft Selection intheFlightGear 2.0 Release Hi Durk, Please note that there is currently a second release candidate available for windows. (Based on a build by Fred). RC1 for window was skipped to stay synchronized with the mac release candidates: http://www.xs4all.nl/~dtalsma/fgsetup-2.0.0-RC2.exe.torrent Also note that Tat has already made two mac release candidates available at: http://macflightgear.sourceforge.net/home/ Finally, please note that since the final release will be based on source code from the gitorious git repository, the final release will be pretty much identical to RC2, save for bugfixes and cosmetics. So, with that approach, I think we're pretty safe. Cheers, Durk Is there anywhere a official announcement? flightgear.org? Forum? Flightsim forums? Newsletter? Without this, it would be pretty much senseless! Cheers HHs __ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] error C5108 unknown semantics and C7011implicit cast
Tim Moore wrote: glLinkProgram FAILED Program infolog: Fragment info - (25) : error C5108: unknown semantics FACE specified for gl_FrontFacing Has anybody else seen this? Stewart What hardware? Linux 2.6.24, libc 2.7, gcc-4.2.3, windowmaker 0.92.0, glib 2.18.4 AMD Sempron 3000, Nvidia FX5200, driver 173.14.18 Stewart I also see the FACE error with Windows XP, Nvidia FX5200 driver 6.14.11.7519 Alan-- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] VC90 compile fail in WaypointList.cxx
From this morning´s CVS I now get this with VC++ 2008 :- -- Build started: Project: FlightGear, Configuration: Release Win32 -- Compiling... WaypointList.cxx ..\..\..\src\GUI\WaypointList.cxx(112) : error C2057: expected constant expression ..\..\..\src\GUI\WaypointList.cxx(112) : error C2466: cannot allocate an array of constant size 0 ..\..\..\src\GUI\WaypointList.cxx(112) : error C2133: 'buf' : unknown size lines 111,112 are :- int len = strlen(s); char buf[len]; Alan -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Duplicate files in base package
-- From: Stefan Seifert n...@detonation.org Sent: Friday, February 26, 2010 5:26 PM To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] Duplicate files in base package This repeatedly strikes me as problems that Linux packages managers have solved completely, elegantly and simply a long time ago. They support dependencies, so commonly used parts only have to be installed once. They support versioning, making upgrades simple and safe by for example not allowing binaries to be installed alongside incompatible data. With systems like the openSUSE build service, users can even create their own repositories and link to others. Those systems even support mirrors to spread downloads. Maybe it's time to use what's already there? One problem which springs to mind is that there must be many same name files (e.g. HSI.xml and its related HSI.ac) which are specific to one aircraft and are in fact entirely different. These will need to be renamed per aircraft (e.g SpitfireMKX.HSI) or per instrument manufacturer (e.g. FD108HSI). However if a common library could be set up a great saving would be made, not only in unused duplicates, but in the ability of designers to find already completed instruments. -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Duplicate files in base package
-- From: Gene Buckle ge...@deltasoft.com Sent: Friday, February 26, 2010 8:29 PM To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] Duplicate files in base package On Fri, 26 Feb 2010, Alan Teeder wrote: Maybe it's time to use what's already there? One problem which springs to mind is that there must be many same name files (e.g. HSI.xml and its related HSI.ac) which are specific to one aircraft and are in fact entirely different. These will need to be renamed per aircraft (e.g SpitfireMKX.HSI) or per instrument manufacturer (e.g. FD108HSI). It's my understanding that the duplicate checker operates on checksums not filenames. Apologies. The upper-lower case duplicate name problem was in my stupid head. I still support the idea common shared directories idea for such things as instruments Alan -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] New GUI Font
LCD is essentially a memory mapped array. Each element is addressed by row and column, so in effect it can also be visualised as a raster display. To draw a vector on such a display you have to calculate which row/column elements need to be illuminated. With a vector display the hardware had a start and end X-Y positions defined for each vector. The spot was turned on by changing the potential at the CRT control grid and then X and Y were ramped to the end point before turning the spot off. It worked much like an analogue X-Y plotter. This was very efficient for simple cartoon like graphics , and also gave a display with considerably higher contrast and brightness than the alternative raster displays of the time. -- From: leee l...@spatial.plus.com Sent: Wednesday, March 03, 2010 1:56 PM To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] New GUI Font On Tuesday 02 Mar 2010, HB-GRAL wrote: Melchior FRANZ schrieb: * HB-GRAL -- Tuesday 02 March 2010: Melchior FRANZ schrieb: Helvetica is the default font used in HUDs (e.g. in the F16). While not perfect for that (there are MIL standards for this), Do you mean in real HUDs? Real HUDs use a MIL standard font. Ours use Helvetica. I even tuned that for the use in HUDs, as the prior version didn't look good in tapes. I don't say that yours is worse, just that it can't be swapped without checking. And a MIL spec compliant font should be the ultimate goal, anyway. Yes, I see that I misunderstood your comment about f-16. As I started to work for a 'all-in-one FG-Font' I had the HUD in mind and also signage because the original and OFL-Allerta is exactly for this purpose (there are some equal requirements for fonts in a display and for signage I think). Now the real standard numbers like yours(?) in the sign textures are miles better then anywhere and this standard is also used in some real HUDs. I think now it is better to separate all this things and not to work for a 'all-in-one'. Thanks- Yves Does anyone know if raster displays are used in modern HUDs? The early first generation huds were all vector displays, of course, but Wikipedia says that second generation HUDs use an LCD screen to modulate the light from an LED. However, it's still not clear to me whether this counts as a raster display (although it does suggest a raster mask). That all the HUD images I've ever seen, including modern ones, are still monochrome suggests that they're still essentially vector displays, for if the imagery is produced using an LCD then I'd expect to see different colours on the HUD, instead of the ubiquitous green (although red/orange has been used on some automobiles). If anyone can find some high-res pictures of _real_ HUD displays (and not ones from flight sims, as they're obviously going to be produced via a raster display) it should be possible to see the LCD 'dots' (unless they LCD screen uses a ridiculously high resolution, which doesn't really chime with the requirements for size and ruggedisation). Anyway, a vector type font should be used on older first generation HUDs for authenticity. LeeE -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] jsclient.cxx - windows compilation
From current CVS jsclient.cxx compilation with windows fails at line 108 int32_t *msg = (int32_t *)buf; Solution seems easy - just add typedef int int32_t; Alan -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] jsclient.cxx - windows compilation
-- From: Torsten Dreyer tors...@t3r.de Sent: Friday, March 12, 2010 2:15 PM To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] jsclient.cxx - windows compilation Am 12.03.10 15:06, schrieb Alan Teeder: From current CVS jsclient.cxx compilation with windows fails at line 108 int32_t *msg = (int32_t *)buf; Solution seems easy - just add typedef int int32_t; Probably not on 64bit. Maybe something like (untested) #ifdef MSVC typedef __int32 int32_t; #endif if it doesn't exist in some #include. I have no Windows to test, sorry Same excuse here - this time no 64bit machine. That is why I wrote seems and you wrote probably ;-) Alan -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] jsclient.cxx - windows compilation
Torsten Yes, this compiles fine. I haven't checked the operation as I do not have a UDP joystick setup. Thanks Alan -- From: Torsten Dreyer tors...@t3r.de Sent: Friday, March 12, 2010 3:35 PM Alan, could you check if this patch solves your issue? Index: jsclient.cxx === RCS file: /var/cvs/FlightGear-0.9/source/src/Network/jsclient.cxx,v retrieving revision 1.6 diff -u -p -r1.6 jsclient.cxx --- jsclient.cxx10 Mar 2010 08:33:10 - 1.6 +++ jsclient.cxx12 Mar 2010 15:35:09 - @@ -27,6 +27,7 @@ #include simgear/debug/logstream.hxx #include simgear/io/iochannel.hxx +#include simgear/misc/stdint.hxx #include Aircraft/aircraft.hxx #include Main/fg_props.hxx -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] News from FlightProSim!
Clickbank is an interesting site. See http://www.clickbank.com/help/vendor-help/vendor-basics/selling-basics/what-products-are-allowed/ Perhaps they should be advised that he is selling GPL software which includes material with copyright by many contributors. On the other hand they may encourage this kind of thing. -- From: Pete Morgan ac...@daffodil.uk.com Sent: Monday, March 15, 2010 4:11 PM To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] News from FlightProSim! One idea which I've used before, would be to create the flightprosim.flightgear.org subdomain. then link sites (eg wiki, 3rd party) to the subdomain. This gets it well up in the rankings and is easy to implement. When end up on that domain is a nice notice explaining what flightprosim. Also the payments portal maybe worth a shot https://ssl.clickbank.net/order/orderform.html?time=1268669378=666c6967687473696ditem=1detail=Flight%2BPro%2BSimvvar=detail%3DFlight+Pro+Sim%26dlgp%3D1 just some thoughts pete Heiko Schulz wrote: Heiko Schulz wrote: Hey folks, you won't belive that- but Flight Pro Sim releases a new version! Isn't it surprising? Did you know that many of the technologies used in FlightGear are the same within FlightProSim? And that this has many improved graphics as well as 3D clouds and cool water? And did you know that we all are paid? That FlightProSim is a paid Flight Simulator so more work and time goes into it than a volunteer one? This guy is getting annoying. Erik Hopefully you didn't mean me! ;-) Indeed, we should react a bit harder now I think Making advertisement in our own forum shows that it is getting serious now __ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] News from FlightProSim!
From: Frederic Bouvier Sent: Tuesday, March 16, 2010 3:21 PM To: FlightGear developers discussions Subject: Re: [Flightgear-devel] News from FlightProSim! Users of FlightProSim have been scammed and they should not endure our anger. But I am not happy to do the FPS support for free, so we should either tell them, always with courtesy, to ask the FPS support desk, or use the real flightgear. On the http://www.clickbank.com/product_requirements.html website it says You will provide appropriate technical support pages for all Products that You register for sale via the ClickBank Services in English and all of the other languages in which the Products are offered at Your own web site. Your technical support must be consistent with best industry practices and standards. Is he capable of meeting that requirement, especially if his customers can expect no help from here? Alan-- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Bounce at startup.
I am (trying) to develop a model with JSBSim. At the moment the aircraft jumps violently into the air at startup and then bounces around on the runway until it sorts itself out. Is there a way of setting the initial height so that it is more or less in balance or is there something else that I need to look at? Alan -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Bounce at startup.
-- From: Erik Hofman e...@ehofman.com Sent: Saturday, March 20, 2010 10:04 AM To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] Bounce at startup. Alan Teeder wrote: I am (trying) to develop a model with JSBSim. At the moment the aircraft jumps violently into the air at startup and then bounces around on the runway until it sorts itself out. Is there a way of setting the initial height so that it is more or less in balance or is there something else that I need to look at? This normally happens when the gear spring coefficients are not set properly. Try looking at a configuration for a similar aircraft that sits steady at the runway and adjust spring_coeff and damping_coeff accordingly to see if it solves the problem. Erik Thanks Eric, but the U/C (numbers from aeromatic) seems stable. It looks like an initialisation problem. If I start and switch immediately to rear view, the gear extends, and when it reaches down the plane is thrown upwards! Most times it lands back on the wheels and settles down, other times the airframe is first to touch down and then .. Is there a recommended way of initialising all the systems which copes with both on ground and in-air start-ups. ? Alan -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Bounce at startup.
-- From: Ron Jensen w...@jentronics.com Sent: Saturday, March 20, 2010 5:28 PM By design a gear doesn't support weight until it reaches 0.99 of extension. This was done so the gear would collapse rapidly if it was retracted on the ground. In FGLGear code the gear is initialized to down In Aircraft/controls.cxx gear is initialized to down In preferences.xml gear is initialized to down As near as I can tell the gear is always down on the c182rg model during initialization. I verified this by adding a line to source/src/FDM/JSBSim/models/FGLGear.cpp FGLGear::GetBodyForces if (t30.) cout Gear is down : GearDown endl; Cheers, Ron Ron I added your test line to FGLGear.cpp, and with my model GearDown is 0 for 3 frames and then 1 for 4 frames. This is not so for aircraft that do not exhibit the bounce fault, so it looks as if I have go through the spaghetti code that is my FDM and model. Thanks for the help. Alan -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Bounce at startup.
-- From: Alan Teeder ajtee...@v-twin.org.uk Sent: Saturday, March 20, 2010 6:55 PM To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] Bounce at startup. -- From: Ron Jensen w...@jentronics.com Sent: Saturday, March 20, 2010 5:28 PM By design a gear doesn't support weight until it reaches 0.99 of extension. This was done so the gear would collapse rapidly if it was retracted on the ground. In FGLGear code the gear is initialized to down In Aircraft/controls.cxx gear is initialized to down In preferences.xml gear is initialized to down As near as I can tell the gear is always down on the c182rg model during initialization. I verified this by adding a line to source/src/FDM/JSBSim/models/FGLGear.cpp FGLGear::GetBodyForces if (t30.) cout Gear is down : GearDown endl; Cheers, Ron Ron I added your test line to FGLGear.cpp, and with my model GearDown is 0 for 3 frames and then 1 for 4 frames. This is not so for aircraft that do not exhibit the bounce fault, so it looks as if I have go through the spaghetti code that is my FDM and model. Thanks for the help. Alan Thanks Ron , your patch pointed me to the problem, which is now fixed. I had bits of code stolen/borrowed from various aircraft and they were fighting each other. On to the next problem Alan -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Elevator control loading
Back in the 60´s and 70´s we found that bungee rubber gave better feel than steel springs when we made simple (i.e. non-hydraulic) feel units from time to time for our research simulator. I also built a few hydraulic systems, but these need lots of safety devices to protect the pilot from run-aways. I was contemplating building a unit based upon direct drive from large dc torque motors driven by power amplifiers, but never got past the preliminary design. We did however use direct electric motors for throttle servos and trim wheels. They cut out if the motor current went too high due to pilot override. Alan -- From: Harry Campigli harryc...@gmail.com Sent: Tuesday, March 23, 2010 5:33 AM To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] Elevator control loading John, I cant help with your software question, but I also am working on control loadings for rudders, and yokes in a dual pilot jet setup. Currently I have completed the rudder setup and working on the yokes. Ailerons for now, elevators next. i will interface them to FG but using a pic as the controller. I have made a device similar to a Boeng feel unit but no hydraulics, ie, a vee made of 2 arcs with a bearing running along it as a cam. one spring is set up for minimal centering pressure, a motor positioned second spring is added over the first spring under computer control to increase the control loading. Then the entire unit is rotated bt a second motor to move the centre point, and or, force the sim pilot to apply a certain amount of force on the control to maintain the desired attitude. I was planning load cells in the control linkage but think i will get by with measuring the force at different angles and putting in a software lookup table This same motor will also position the controls in autopilot mode (pilot hands off) I am using a linear actuator made from a wiper motor on the spring and an 18 inch satellite positioning actuator to move the unit. Possibly its better and easier with a big servo motor setup but while i have seen many posts in sim builder forums about testing different types of motor, I have not seen an example of a motor that really fits the bill. Possibly we can compare notes on a separate email as this hardware rather than FG code? Harry On Tue, Mar 23, 2010 at 1:03 AM, cas...@mminternet.com wrote: Hi, Can anyone shed some light on the following question? Does JSBSim calculate elevator position and control hinge moments based on the general equation of motion, including inertial coupling, is described by Etkin( 1982 ), or do the FDMs simple accept the value provided via FG or a network interface and position the elevator at that value analogous to an irreversible control system. Working on a control loading system and before digging into the JSBSim code, thought I might ask the question of save some time. Thanks John -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Regards Harry 19b Jln Danau Poso Sanur, Bali 80228 H +62 361 285629 M +62 812 7016328 -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] English Electric Lightning no longer runs
Using latest CVS on windows . The EE Lightning aircraft starts OK, all controls and views seem normal, but when the engines reach about 60% rpm Flightgear crashes. This fault is quite new and was not here about one month ago. For many month now I have been unable to run Flightgear in debug mode as it crashes in soundmgr_openall.cxx at line 486 :- if ( sample-is_file() ) free(sample_data); Erik is aware of this, but nobody else has reported this particular problem. This crash occurs before the cockpit view appears. Unfortunately this means that I can't find much about the cause of the crash. So far I have had a good go at the Lightning nasal files. The electrical system had no var statements, and one or two were missing in the others. All this to no avail. According to the lightning-electrical.nas file, the electrical generators should cut in at 58%, and this is my only clue. Does anyone have any clues? Alan -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] English Electric Lightning no longer runs
-- From: James Turner zakal...@mac.com Sent: Wednesday, March 24, 2010 10:20 PM To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] English Electric Lightning no longer runs On 24 Mar 2010, at 22:09, Vivian Meazza wrote: Bad news - works perfectly here on XP with cvs as of a few minutes ago! Checking to see if I can break it still though. I was using the Lightning to test my mach-calculations code earlier today (Mac, latest CVS code) and it seemed fine. James James, Vivian Thanks for the feedback. I will roll back the CVS to see if I can find when this bug first started. When the splash screen is replaced by the cockpit view I see this error, repeated 5 times: glLinkProgram Failed Program infolog: Fragment shader uses varying gl_FrontFacing but vertex shader does not write to it. To get past the already mentioned debug probelm at the start of this thread I have tried debugging by attaching the Visual Studio debugger to an already running Flightgear . I now get this: Unhandled exception at 0x3e814f0 in fgfs.exe: 0xC05: Access violation reading location 0x000. When I hit the Break button the debug pointer is at line 60 in osg\PrimitiveSet.cpp: else glDrawArrays(_mode,_first,_count); I have updated Osg to the latest SVN and the error remains. The same behaviour is on both my XP desktop and my Vista laptop. Finally, Vivian (or anyone else) , do you have any problems running Flightgear under Debug from the Visual Studio IDE? Alan -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] English Electric Lightning no longer runs
In my last post, I forgot to say that the Fgfs crash and debug message come when the engine reaches aprox 50% rpm. Alan -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] English Electric Lightning no longer runs
-- From: Vivian Meazza vivian.mea...@lineone.net Sent: Thursday, March 25, 2010 10:18 AM To: 'FlightGear developers discussions' flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] English Electric Lightning no longer runs Frederic Bouvier - Vivian Meazza a écrit : I have seen something like this if I add the generate tag to a model shader. generate works fine in a terrain shader. However as default you should not be using any model shader with generate. What ? What What? I haven't mentioned this before because I'm still investigating.. Lauri Peltonen also had a look and came up with an odd error which neither of us understood properly, but there is some indication that it depends on the order of the tags. Or it might be that my shaders are simply crap. Or are you querying the default shaders? Vivian At the moment I can´t roll back the CVS very far as the old version of SGClipGroup.hxx fails to compile with my SVN version of Osg . - RegisterRenderBinProxy is not a member of osgUtil I´m not very keen to roll back Osg as it takes so long to re-build. Alan -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] English Electric Lightning no longer runs
I have rolled CVS back to 1 Feb, except for SGClipGroup.cxx and .hxx. These are the current ones to match with the SVN Osg. I have not rolled back Flightgear data as this takes for ever. Unfortunately Flightgear still crashes when I open up the Lightning´s engines. Perhaps the fault is within Osg. Alan -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] English Electric Lightning no longer runs
Tim I am seeing this on 2 machines. The desktop runs XP and has an NVIDEA FX 5200 card. The laptop runs Vista and is an Acer 5920 has Intel 965 video, with latest the drivers from Intel. (The Acer supplied driver had problems giving a few screen fulls of OpenGL errors on FG startup). Alan From: Tim Moore Sent: Thursday, March 25, 2010 5:21 PM To: FlightGear developers discussions Subject: Re: [Flightgear-devel] English Electric Lightning no longer runs Alan, What graphics hardware are you running on? Turning off shaders should get you going for the moment. Then we'll figure out how to conditionalize the shader code for drivers that don't support gl_FrontFacing. Tim -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] English Electric Lightning no longer runs
Tim I should have been a bit clearer in my last post I was talking about FG crashing when I open up the Lightning Engines. I have tried turning off shades from the FG menu bar, but this does not come up until after the glFrontFacing errors so I have seen no change. This error seems to be present in many aircraft, not just the Lightning. Alan From: Tim Moore Sent: Thursday, March 25, 2010 5:21 PM To: FlightGear developers discussions Subject: Re: [Flightgear-devel] English Electric Lightning no longer runs Alan, What graphics hardware are you running on? Turning off shaders should get you going for the moment. Then we'll figure out how to conditionalize the shader code for drivers that don't support gl_FrontFacing. Tim -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] English Electric Lightning no longer runs
Thanks for all the responses. I have done a lot more playing around this evening. It seems to be to do with generator/battery/external power switching. I can remove the problem by artificially setting a constant voltage on the master bus and inhibiting bus switching. Finding out whether this is due to the electrical switching logic or to some related effect in one of the aircraft systems is my next step. With the switching inhibited the afterburners seem OK. Are any other aircraft similarly affected? I am using the Lightning as a template for a model that I am developing, so I had problems when this fault suddenly appeared in my own development. Back checking to the original aircraft showed that for once it wasn't my stupid fault!. AFAIK the Lightning has been stable and unchanged for some time now. Alan -- From: Victhor victhor.fos...@gmail.com Sent: Thursday, March 25, 2010 9:51 PM To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] English Electric Lightning no longer runs Yup, tested and I only get a crash if I use the afterburners, engines can be started just fine. Alan Teeder Tim I should have been a bit clearer in my last post I was talking about FG crashing when I open up the Lightning Engines. I have tried turning off shades from the FG menu bar, but this does not come up until after the glFrontFacing errors so I have seen no change. This error seems to be present in many aircraft, not just the Lightning. Alan From: Tim Moore Sent: Thursday, March 25, 2010 5:21 PM To: FlightGear developers discussions Subject: Re: [Flightgear-devel] English Electric Lightning no longer runs Alan, What graphics hardware are you running on? Turning off shaders should get you going for the moment. Then we'll figure out how to conditionalize the shader code for drivers that don't support gl_FrontFacing. Unlikely, I know, but is this crash related to the afterburners? Vivian -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] English Electric Lightning no longer runs
Hmm - some kind of Nasal issue then? Any kind of error message? Vivian No error messages , it just stops with an Windows crash report. The dos window is, as usual, filled with the usual stream of annoying messages from traffic manager and navaids. At the moment I am looking at the electrical nasal code, but it could turn out to be the result of applying power to some system or instrument. -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] English Electric Lightning no longer runs
Problem now solved !!
In Lighning-electrical.nas, line 378
if(bus_volts 114){setprop(instrumentation/radar/switch,on );}
Setting this to on crashes Flightgear on both my computers here.
I can do the same by setting the property from the Browse Internal
Properties menu.
During my checking I have modified most of the Lightning's nasal files,
especially the electrical file. These modifications were aimed at inserting
missing nasal var statements.
Also I have changed the battery charge integrator time constant as it was
using milliseconds instead of seconds, and the battery was even worse at
holding charge than my old laptop running down 1000 times faster than
it should do!
Who should I post these changes to for testing and CVS commit ?
Thanks for the help.
Alan
--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] VC9 compile fails in groundnetwork.cxx
Compile report from latest CVS:- groundnetwork.cxx c:\flightgear\source\src\atc\trafficcontrol.hxx(132) : error C4716: 'FGTrafficRecord::setState' : must return a value Alan -- ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] can't launch flghtgear when openscenegraph iscompiled in release
From: Ingels David Sent: Tuesday, April 27, 2010 12:18 AM To: flightgear-devel@lists.sourceforge.net Subject: [Flightgear-devel] can't launch flghtgear when openscenegraph iscompiled in release I can't launch flghtgear when openscenegraph is compiled in release there is a bug with the linking to zlib.dll I dont understand why Error is 'Ordinal 55 not found on zlib.dll' it seems to be a linking problem with zlib.dll Its only when i compil openscenegraph on other version than debug (release ect...) Help ! David ingels I also had zlib.dll problems. These went away when I re-ordered my PATH environment to ensure that the version of zlib.dll that I wanted was nearer the top. Many programs install their own version of zlib. Depends.exe is the tool you need to find out which dll´´s fgfs (or any other progarm) will actually load at run-time. http://www.dependencywalker.com/ (it is free and recommended by Microsoft at http://technet.microsoft.com/en-us/library/cc738370%28WS.10%29.aspx) -- ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] can't launch flghtgear when openscenegraph iscompiled in release
From: Frederic Bouvier Sent: Tuesday, April 27, 2010 10:09 AM To: FlightGear developers discussions Subject: Re: [Flightgear-devel] can't launch flghtgear when openscenegraph iscompiled in release - Alan Teeder a écrit : From: Ingels David Sent: Tuesday, April 27, 2010 12:18 AM To: flightgear-devel@lists.sourceforge.net Subject: [Flightgear-devel] can't launch flghtgear when openscenegraph iscompiled in release I can't launch flghtgear when openscenegraph is compiled in release there is a bug with the linking to zlib.dll I dont understand why Error is ‘Ordinal 55 not found on zlib.dll’ it seems to be a linking problem with zlib.dll Its only when i compil openscenegraph on other version than debug (release ect...) Help ! David ingels I also had zlib.dll problems. These went away when I re-ordered my PATH environment to ensure that the version of zlib.dll that I wanted was nearer the top. Many programs install their own version of zlib. Depends.exe is the tool you need to find out which dll´´s fgfs (or any other progarm) will actually load at run-time. http://www.dependencywalker.com/ (it is free and recommended by Microsoft at http://technet.microsoft.com/en-us/library/cc738370%28WS.10%29.aspx) It only happens in release mode because the debug build link to zlibd.lib/dll and it is most likely that the only one in the system is the one located in the 3rdparty directory. zlib.dll and other Open Source libraries are often used even by commercial products and there should be one with a different version elsewhere, possibly in c:\windows\system32 -Fred OpenSceneGraph (source or SVN version) has its own set of third party files. In the OpenSceneGraph/3rdpart/bin directory there is both zlib1.dll and zlib1d.dll, and in the 3rdparty/lib directory are the equivalent .lib files. On my system I have used the OPenSceneGraph 3rdparty files as the basis for my FlightGear build. Also be aware that zlib.lib is probably not the one you need, for dll builds you should use zlib1. I have copied zlib.lib into my 3rd party directory as both zlib1.lib and zlib.lib for this reason. (see http://www.zlib.net/DLL_FAQ.txt). Alan-- ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] should src/Include/config.h-msvcXX be in.gitignore?
-- From: Torsten Dreyer tors...@t3r.de Sent: Saturday, May 22, 2010 7:20 PM To: flightgear-devel@lists.sourceforge.net Subject: [Flightgear-devel] should src/Include/config.h-msvcXX be in.gitignore? Hi, after cloneing the flightgear sources and running make, git status says # modified: config.h-msvc71 # modified: config.h-msvc8 # modified: config.h-msvc90 I didn't touch them for sure. Torsten Not sure about that, but simgear/simgear/version.h is still missing /(or not generated automatically) for Msvc users. This was reported ages ago. My first attempt at a build from the git-maint branch failed in SGClipGroup.hxx, with the message RegisterRenderBinProxy is not a member of osgUtil This was reported and very quickly fixed back in March. I do not see this problem using the git-next branch. TortoiseGit is rather flaky. It does not run out of the box and the suggestions on the various forums are quite varied. In my case I fixed it by using the tip in http://groups.google.com/group/tortoisegit-users/browse_thread/thread/ff1d81f59cd5fe90. Apart from these foibles the git distribution builds in the same XP/Vista/VC++ Express 2008 environment that I have been using for some time. Alan -- ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Windows config.h-mscxx
The files config.h-msvc8 and config.h-msvc90 are necessary for a windows build but are now in .gitignore making them inaccessible. Natively windows has no method to generate these files from the .in files, although this is probably possible by installing Perl, and GNU versions of autoconf and automake. - and then learning how to use them ! Could they be put back into the normal distribution path? Thanks Alan -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Windows config.h-mscxx
-- From: Frederic Bouvier fredfgf...@free.fr Sent: Saturday, June 26, 2010 5:57 PM To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] Windows config.h-mscxx The files config.h-msvc8 and config.h-msvc90 are necessary for a windows build but are now in .gitignore making them inaccessible. Natively windows has no method to generate these files from the .in files, although this is probably possible by installing Perl, and GNU versions of autoconf and automake. - and then learning how to use them ! Could they be put back into the normal distribution path? It was me, who put them into gitignore because these files are created from the respective *.in files during the build. Maybe I am wrong, but if these files are created from some other sources, they don't belong under source control but the source files do. If I understand the current setup correctly, a run of autogen.sh and configure is required to create the config.h-msvcxx files from the .in files before a windows build can run. I think it is very unfortunate that some *nix system has to run a configure script to generate the files needed for a windows build, put them into the source control system to be accessible for windows users. Maybe Frederic can chime in here with a better idea of how to solve this? I originally included config.h-msvcxx in the autoconf system because there was a long track record of releases made with the wrong version in these files. autoconf is only used to substitute @VERSION@ by the right one. No need of perl or something else, just copy the .in file and replace @VERSION@ by a string, ideally the right version number ;-) If someone is able to alter the project file to autogen this file with the good version number, under Windows, without requiring additional tools, go ahead... Regards, -Fred Fred Thanks for that. I had just this minute run a diff check on config.h-msc90 (from my CVS archive) and config.h-msc90.in As you say the only difference is that each occurrence of @VERSION@ is replaced by 2.0.0. This is exactly the change that has to be made in simgear/simgear.h.in before it is copied to simgear.h. Is there any need for this to be done by all new cloners before compilation? It seems to be an unnecessary complication. All GIT users should be currently working with the same version (2.0.0) in both simgear and flightgear. As and when a new version comes about both these files can be updated and committed by whoever is responsible for raising the issue number. As an aside I tried to generate config.h-msc90 with cygwin autoconf - but it failed with an error at line 799 in file configure.ac. Alan -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Heads up: new autopilot subsystem implementation
--
From: Torsten Dreyer tors...@t3r.de
Sent: Thursday, June 24, 2010 4:24 PM
To: flightgear-devel@lists.sourceforge.net
Subject: [Flightgear-devel] Heads up: new autopilot subsystem implementation
Hi all,
I have just commited a pretty large commit for a new implementation of the
autopilot subsystem(group). The reason for that was that the old way of
having
everything stuffed into one single source file of 1360 lines and a header
file
of 514 lines made working on this piece of code allways a little
challenging.
While at it, I replaced some design patterns to look a little more OO-ish
and
added some doxygen compatible comments to the class definition.
snip
Because I touched at least 90% of all code lines, it is very likely that I
introduced a new bug. Especially the build process was tested on linux
only. I
have no chance to test the build on Windows on OS/X.
snip
Torsten
Now that the config.h file is sorted (many thanks for the commit) I have
again been able to make an MSCV09 from the next branch.
However it was not without problems ;-)
In the autopilot logic.cx was failing due to NOMINMAX not being set. There
were also several problems due to SGvec3 and SGvec4 not being defined.
These I have sorted by re-arranging the order of include file calls. There
may be a better solution, and perhaps my solution will not work on other
platforms.
The changes are all at the beginning of files:-
in analogcomponenet.hxx...
#ifndef __ANALOGCOMPONENT_HXX
#define __ANALOGCOMPONENT_HXX 1
#include component.hxx
#include inputvalue.hxx
namespace FGXMLAutopilot {
in inputvalue.cxx
// Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
02110-1301, USA.
//
#include Main/fg_props.hxx
#include inputvalue.hxx
using namespace FGXMLAutopilot;
in logic.hxx...
#ifndef __LOGICCOMPONENT_HXX
#define __LOGICCOMPONENT_HXX 1
#include analogcomponent.hxx
#include digitalcomponent.hxx
namespace FGXMLAutopilot {
Once it all compiled there were some undefined variables.
To solve these fdm_shell.cxx/.hxx and flightProperties.cxx/.hxx needed to be
added to Lib_Flight.
This produced another compilation error:-
The correction in flightProperties.cxx is
#include Main/globals.hxx
#include FDM/flightProperties.hxx
#include simgear/props/props.hxx
#include simgear/math/SGMath.hxx
#include Main/globals.hxx
FlightProperties::FlightProperties(SGPropertyNode* root) :
Also note that fdm_shell.cxx/.hxx and flightProperties.cxx/.hxx do not have
the usual copyright header.
All compiles and links now. I have not tested to see if it runs OK.
Thanks for all the continuing work by all concerned.
Alan
--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Heads up: new autopilot subsystemimplementation
Thanks for the update. One include file is still required in logic.hxx:- // Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. // #ifndef __LOGICCOMPONENT_HXX #define __LOGICCOMPONENT_HXX 1 #include inputvalue.hxx #include digitalcomponent.hxx #ifdef HAVE_CONFIG_H In my previous post I suggested adding #include analogcomponent.hxx, but inputvalue.hxx is sufficient. Apart from this FG builds out of the box (as long as simgear/simgear/version.h is edited as per step 10 in mini-docs/README.MSVC) Alan -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Solved: gitorious hickup?
-- From: Torsten Dreyer tors...@t3r.de Sent: Monday, June 28, 2010 12:52 PM To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] Solved: gitorious hickup? Hi today, gitorious doesn't like my public key anymore. All attempts to pull filghtgear, simgear or fgdata via the ssh tunnel fail with Permission denied (publickey). fatal: The remote end hung up unexpectedly My config hasn't changed since yesterday. Anybody else having trouble logging in? Uploading my public key a second time solved the issue. Torsten Torsten Sorry, but this does not work. e.g. logic.cxx c:\FlightGear\SimGear\simgear/props/props.hxx(667) : error C2079: 'SGRawValueContainerT::_obj' uses undefined class 'SGVec3T' with [ T=SGVec3d ] and [ T=double ] . (snip more errors) . Generating Code... Build log was saved at file://c:\FlightGear\flightgear\projects\VC90\FlightGear\Win32\Release\BuildLog.htm FlightGear - 6 error(s), 6 warning(s) Could you look at a patch similar to the one that I proposed? Sorry to be the messenger (don´t mention the football !) Alan -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] logic.cxx windows build, was: Solved: gitorious hickup?
Alan,
I don't like the idea to include inputvalue.hxx, the logic class has
nothing
to do with the analog input value class. I try to understand why VC spits
out
the error message here.
Could you send the build log offline, so I can have a look? Sorry, I don't
have a windows machine capable to build FlightGear, but we have a 1:4
chance
to find the bug ;-)
Best, Torsten
All it is complaining about is the lack of the SGVec3 and SGVec4 classes
when the compiler sees Simgear/props.h.
My hack was to look at similar code in your autopilot code and see what was
included in other routines (which compiled successfully) before the
props.h include. That is why I hit upon including inputvalue.hxx.
I have just looked to see what inputvalue.hxx includes ahead of props.h, and
found that adding
#include simgear/structure/SGExpression.hxx
to logic.hxx works:-
i.e.
// Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
02110-1301, USA.
//
#ifndef __LOGICCOMPONENT_HXX
#define __LOGICCOMPONENT_HXX 1
#ifdef HAVE_CONFIG_H
# include config.h
#endif
#include simgear/structure/SGExpression.hxx
#include digitalcomponent.hxx
namespace FGXMLAutopilot {
That looks a lot more elegant !
Alan
PS
I have already sent this reply with a build log attached but it bounced
because the email was too large. The error message quote in my previous
reply should be enough to show the problem.
--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] logic.cxx windows build, was: Solved: gitorious hickup?
-- From: Torsten Dreyer tors...@t3r.de Sent: Tuesday, June 29, 2010 4:49 PM To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] logic.cxx windows build,was: Solved: gitorious hickup? That looks a lot more elegant ! OK - I just managed to get a Windows machine with VS2008 and, thanks to the work of Frederic, I am now able to compile in this environment. I just commited a patch, to make logic.cxx compile. Could you please check, if it works for you, too? Torsten Torsten All compiles OK now. Many thanks. Do you have a suitable aircraft to test the autopilot with ? Alan -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] EGPWS issues (mk-viii module)
-- From: Ivan Ngeow ivanng...@gmail.com Sent: Thursday, July 15, 2010 4:14 AM To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] EGPWS issues (mk-viii module) The radio alt antennas point vertically downward. Just as pitch angle affects the displayed RA, so does bank angle. This effect increases with bank/pitch angle --- you can work out the trigonometry easily. Except that the beam width (45-50 degrees) removes this effect for normal flight attitudes. Alan -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] aircraft search
The current git build does not run on either of my Vista or Xp systems. The release build just has a windows box saying that fgfs.exe has stopped working. The DOS window gets as far as loading scenario nimitz demo and loading scenario aircraft demo. Attempts at debugging fail as FG shuts down with :- 'fgfs.exe': Loaded 'C:\WINDOWS\system32\msacm32.dll' 'fgfs.exe': Loaded 'C:\WINDOWS\system32\midimap.dll' 'fgfs.exe': Loaded 'C:\WINDOWS\system32\setupapi.dll' 'fgfs.exe': Unloaded 'C:\WINDOWS\system32\setupapi.dll' 'fgfs.exe': Loaded 'C:\WINDOWS\system32\setupapi.dll' 'fgfs.exe': Unloaded 'C:\WINDOWS\system32\setupapi.dll' 'fgfs.exe': Loaded 'C:\WINDOWS\system32\setupapi.dll' 'fgfs.exe': Unloaded 'C:\WINDOWS\system32\setupapi.dll' 'fgfs.exe': Loaded 'C:\WINDOWS\system32\setupapi.dll' 'fgfs.exe': Unloaded 'C:\WINDOWS\system32\setupapi.dll' 'fgfs.exe': Loaded 'C:\WINDOWS\system32\setupapi.dll' 'fgfs.exe': Unloaded 'C:\WINDOWS\system32\setupapi.dll' The thread 'Win32 Thread' (0x14b8) has exited with code -1 (0x). The program '[5360] fgfs.exe: Native' has exited with code -1 (0x).a error code -1. and I have no idea where to put breakpoint(s) to track this down. This is consistent on all aircraft that I have tested. Alan :-( -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] aircraft search
Debugging on my windows boxes fg_init.cxx line 21 is reached.
if (_foundPath.str().empty()) {
SG_LOG(SG_GENERAL, SG_ALERT, Cannot find specified aircraft:
aircraft );
return false;
aircaftDir is {path=C:/Flightgear/fgdata/Aircraft}
aircraft isc172p
Directory C:\FlightGear\fgdata\Aircraft\c172p exists on my system.
Alan
--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] aircraft search
--
From: James Turner zakal...@mac.com
Sent: Wednesday, July 21, 2010 9:51 AM
To: FlightGear developers discussions
flightgear-devel@lists.sourceforge.net
Subject: Re: [Flightgear-devel] aircraft search
On 21 Jul 2010, at 09:24, Alan Teeder wrote:
Debugging on my windows boxes fg_init.cxx line 21 is reached.
if (_foundPath.str().empty()) {
SG_LOG(SG_GENERAL, SG_ALERT, Cannot find specified aircraft:
aircraft );
return false;
aircaftDir is {path=C:/Flightgear/fgdata/Aircraft}
aircraft isc172p
Directory C:\FlightGear\fgdata\Aircraft\c172p exists on my system.
Can you add some logging in the search functions, to see which directories
it is / isn't walking into? I tested on my MSVC box and it all seemed to
work as expected, but I will test again this evening.
Note at this point in the startup, SG_LOG has not yet processed
the --log-level argument, so using std::cout to debug may be easier - this
confused me before I understood the order thing are happening in, here.
James
I edited line 507 of fg_init.cxx as log level ALERT works at this point
void fgFindAircraftInDir(const SGPath dirPath, T* obj, bool
(T::*pred)(const SGPath p))
{
if (!dirPath.exists()) {
SG_LOG(SG_GENERAL, SG_ALERT, fgFindAircraftInDir: no such path:
dirPath.str());
return;
}
and the result was:
fgFindAircraftInDir: no such path:C:/Flightgear/fgdata/Aircraft
Single stepping the debugger showed that fopen in simgear SGPath::exists()
failed.
Alan
--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Plib sockets
Windows compiler does not like this:- -- Build started: Project: SimGear, Configuration: Debug Win32 -- Compiling... raw_socket.cxx c:\flightgear\simgear\simgear\io\raw_socket.cxx(334) : error C2065: 'UL_WARNING' : undeclared identifier c:\flightgear\simgear\simgear\io\raw_socket.cxx(334) : error C3861: 'ulSetError': identifier not found c:\flightgear\simgear\simgear\io\raw_socket.cxx(477) : error C2065: 'UL_WARNING' : undeclared identifier c:\flightgear\simgear\simgear\io\raw_socket.cxx(477) : error C3861: 'ulSetError': identifier not found Creating browse information file... Microsoft Browse Information Maintenance Utility Version 9.00.30729 ;-( Alan -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] aircraft search
James Many thanks All seems well with aircraft search and and the plib change here. Alan -- From: James Turner zakal...@mac.com Sent: Friday, July 23, 2010 8:02 AM To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] aircraft search I've committed various tweaks to the path/directory code - if you were having difficulties, please update SimGear and try again. In particular, the Win32 broken-ness should be gone - I've tested various aircraft, and --show-aircraft, on Windows and Unix, and things seem fine to me. Alex and Lance, I'm still confused as to the failures you are seeing. Assuming you're still seeing same issues after updating (and anyone else who is seeing something similar), I will make up a debug patch to see what's going on. Thanks, James -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] GIT and FGDATA
Here Git works well for Simgear and Flightgear, but a sync/pull of Fgdata kills either of my windows boxes. It has been getting slower and slll and today has ground to a complete halt. Now that the aircraft directory can be defined separate from FGROOT (and hence the rest of the data) are their any moves afoot to split Fgdata into more manageable chunks? Alan -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] GIT and FGDATA
-- From: Vivian Meazza vivian.mea...@lineone.net I had reached the same conclusion: it does conform to the observed fact that the slow-down has been faster than the increase in data. The splitting of the repo might not overcome the problem if this is indeed the case. Meanwhile, Git-bash works here. No fancy graphics, but I can push/pull. I'm not always sure what I'm pushing, but hey ho, it's still hanging on in there. Vivian Could something similar to Flightgear´s terasync option be implemented? By this I mean that a complete list of aircraft is always available and kept locally for use by both flightgear and fgrun. If an up-to -date copy of the selected aircraft is not available locally, then it is downloaded (unfortunately together with dependencies) as required. Just a suggestion. The Git symptoms I experience are a 100% cpu load and memory usage increasing above 100M. This goes on for several HOURS. It has got to this state over the last week, before then it was slow. Now it is dead. The only practical way to get a complete set of Fgdata is to start again and make a fresh git clone. Although this takes several hours on my connection it is much quicker than a git pull. Alan -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] GIT and FGDATA
-- From: dave perry skida...@mindspring.com Sent: Friday, August 06, 2010 2:59 PM To: vivian.mea...@lineone.net; FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] GIT and FGDATA I am not seeing the slowdown. I just ran a simple script that updates simgear, flightgear source, and fgdata. I would estimate that the git pull origin run in fgdata took about 3 minutes. This performance has been typical for me. I ran System Monitor (F12) during the fgdata pull and the data rate was between 96 and 100 KB/s and the memory usage was constant. I connect via Earthlink dsl. Dave P. Dave From earlier posts I surmise that you have a 64bit Linux box. I have an old single processor XP box (limited to 1 GB memory by the motherboard) and a newer dual-core laptop. These run Xp and Vista respectively. Not in the same league as yours :-( My searching on the net suggests that the Windows version of Git is not as fast as the Linux original. The net result is that Git on Windows needs a higher spec processor than flightgear does when used with a large and frequently changing set of data such as fgdata. During pull origin Git´s CPU usage goes to 100% (or 50% on the dual core box) and Gits´s memory increases to over 100M, but there is negligible net usage. I have let it run for 3 hours with no sign of any completion. My guess is that Windows Git is having trouble sorting out all the changes and updating its internal databases. Alan -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] GIT and FGDATA
-- From: Alasdair ali...@btinternet.com Sent: Saturday, August 07, 2010 10:47 AM To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Cc: vivian.mea...@lineone.net Subject: Re: [Flightgear-devel] GIT and FGDATA On Fri, 2010-08-06 at 07:59 -0600, dave perry wrote: I am not seeing the slowdown. I just ran a simple script that updates simgear, flightgear source, and fgdata. I would estimate that the git pull origin run in fgdata took about 3 minutes. This performance has been typical for me. I ran System Monitor (F12) during the fgdata pull and the data rate was between 96 and 100 KB/s and the memory usage was constant. I connect via Earthlink dsl. Dave P. I experience much the same as Dave. A git pull in fgdata is no big deal.Here is the output from a little test i just ran : pull started Sat Aug 7 10:32:03 BST 2010 === New directory is /opt/FlightGear/fgdata From git://gitorious.org/fg/fgdata 33b8fe6..74ec1cd master - origin/master Updating 33b8fe6..74ec1cd Fast-forward Aircraft/737-300/Models/contrail.xml | 216 +- Aircraft/C130/Models/main.xml | 33 + Aircraft/Concorde/Concorde-set.xml |8 +- Aircraft/Concorde/Models/Concorde_ba.xml | 21 + Aircraft/Concorde/Models/Effects/contrail-new.xml | 142 + Aircraft/Concorde/Models/Effects/contrail1.eff | 156 + Aircraft/Concorde/Models/Effects/contrail2.eff | 151 + .../Concorde/Models/Effects/contrail_dummy.xml | 11 + .../Concorde/Models/Effects/contrail_shader1.xml | 35 + .../Concorde/Models/Effects/contrail_shader2.xml | 35 + Aircraft/Concorde/Models/Effects/smoke.png | Bin 0 - 6482 bytes Aircraft/Concorde/concorde-submodels.xml | 28 + Aircraft/Concorde/concorde-subsubmodels.xml| 66 + Aircraft/Concorde/concorde-subsubsubmodels.xml | 67 + Aircraft/Concorde/concorde-subsubsubsubmodels.xml | 64 + Aircraft/Short_Empire/Models/Interior/interior.ac | 8138 +--- Aircraft/Short_Empire/Models/Interior/interior.xml | 312 +- .../Short_Empire/Models/Interior/spar_panel.xml| 10 +- Aircraft/Short_Empire/Short_Empire-set.xml | 25 +- Aircraft/Short_Empire/Short_S23.xml| 59 +- Aircraft/Short_Empire/Systems/fuel-system.xml | 20 +- Aircraft/Short_Empire/Systems/short-empire.nas | 11 +- 22 files changed, 8171 insertions(+), 1437 deletions(-) create mode 100644 Aircraft/Concorde/Models/Effects/contrail-new.xml create mode 100644 Aircraft/Concorde/Models/Effects/contrail1.eff create mode 100644 Aircraft/Concorde/Models/Effects/contrail2.eff create mode 100644 Aircraft/Concorde/Models/Effects/contrail_dummy.xml create mode 100644 Aircraft/Concorde/Models/Effects/contrail_shader1.xml create mode 100644 Aircraft/Concorde/Models/Effects/contrail_shader2.xml create mode 100644 Aircraft/Concorde/Models/Effects/smoke.png create mode 100644 Aircraft/Concorde/concorde-submodels.xml create mode 100644 Aircraft/Concorde/concorde-subsubmodels.xml create mode 100644 Aircraft/Concorde/concorde-subsubsubmodels.xml create mode 100644 Aircraft/Concorde/concorde-subsubsubsubmodels.xml === pull ended Sat Aug 7 10:32:40 BST 2010 fgdata git pull took 0 mins 37 seconds === My connection is BT Broadband, nominally 12 Mbps, but actually 7,616 Kbps. My machine is based on a 2x AMD Athlon(tm) 7450 Dual-Core Processor with 2 GB mem. Kind regards, Aasdair I have just done a very quick and successful fgdata git pull using Cygwin. The results were similar to Alistair´s above. Cygwin git also threw up some errors in my Simgear directory that Totoise git (even using the Diff and Check for Modifications options had not found.) From now on I will keep away from Tortoise git. Alan -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Aircraft dirs (and noisy output atlog-level=info)
-- From: James Turner zakal...@mac.com Sent: Monday, August 02, 2010 11:46 PM To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: [Flightgear-devel] Aircraft dirs (and noisy output atlog-level=info) I committed some code a few days ago, to change how aircraft data files are loaded - if you're running the latest code, you may have noticed the paths used for each data file are now logged. This is a transitional feature - it will help if someone reports problems with particular data files not being loaded; once the code has had sufficient testing, I'll remove or downgrade the message. The good news is, FG now supports --fg-aircraft=some/path/;another/path syntax for loading aircraft data; you should be able to place development aircraft or similar outside data/Aircraft and have everything work as expected (right now you still need to have an 'Aircraft' dir, so I do: --fg-aircraft=/foo/my-aircraft, and then have /foo/my-aircraft/Aircraft/MD-81/MD-81-set.xml, and so on). data/Aircraft is still checked as a location, too, of course - this keeps generic Aircraft resources (such as the standard AP) and shared instruments working, though these could also be located in a separate dir - the code check the current aircraft's direction, then the --fg-aircraft paths in order, and finally data/Aircraft. This will hopefully simplify life for aircraft developers, packagers and release maintainers in the near future, but in the short term it would be great if people could try the feature out, and report any issues or problems. BTW, the more verbose logging of file paths does reveal some latent places where a file was missing / not-found (including in the C172 effects files, due to a confused path), but this fact was not previous reported. James I am using the new Aircraft dirs for my current development. It certainly is very useful. However now that I have my cockpit layout nearly sorted out I have come across a problem, which can be duplicated using the existing Lightning (I am using the Lighning as a template for my own model) as follows: Copy the Lightning aircraft into the directory defined by --fg-aircaft, and rename or delete the original in FGROOT. Set --aircraft=lightning in system.fgfsrc and run fgfs. All runs until I attempt Auto Engine Start from the Lightning Configuration menu, when fgfs crashes. If I restore the original Lightning aircraft directory in FGROOT, even after starting up fgfs, but before attempting the engine start, everything runs OK. Hope this give you enough to go on. Regards Alan -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
