Re: [Flightgear-devel] FlightGear terrain engine
Ralf Gerlich schrieb: Hi! Georg Vollnhals wrote: Hi Ralf, you know yourself how much I appreciate your work and like the output - ... The problems you mentioned are applicable to _all_ such activities and I would call it unfair to attribute this specifically to a single project. If it was unfair what I wrote or I used bad word then I will excuse here formally as it not my intention to be unfair or hurt anybody. Especially not you as a productive part of the FlightGear development and shouldering a heavy workload. I will now get back to more productive activities so that my schedule won't get any more worse, pushing back any activities for FlightGear further. I hope that I was successful in clarifying that the application of automatic classification is nothing that we will only see in the far future, as you implied, but it _is_ working and is near a stage were users will actually be able to help improving the database, instead of just looking at the results the project people produced. The only limiting factor right now is the free time of the people doing the work. Cheers, Ralf Yes, thank you a lot. I understood. Regards Georg - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear terrain engine
Hi! Georg Vollnhals wrote: Hi Ralf, you know yourself how much I appreciate your work and like the output - just remember my words about the Berlin terrain in the GFF. The aim of this project is to enhance the local scenery worldwide automatically by scanning the LS7 stuff. This worldwide automatically = press the button I'll do the rest is really far from working as you describe yourself. Actually there is a lot of knowledge necessary to do the work and even if Martin will finish his part you have to go through the training process for every LS7 picture as far as I understood all. Well, if you raise the bar that high, _all_ efforts of improving world scenery are far from working, including e.g. OpenStreetMap - and will be forever. Our job is to enable users to use the methods or synthesis of methods we developed. We will use these ourselves to improve scenery in some areas, but we can't do everything and it is clearly not the intention of our project to get all the data automatically, because this is comprehensibly not possible. submit that to the service again and retrieve automatically classified vector data I doubt that this will help most of the scenery-developers/users as long as you cannot process these data due to that cannot compile, cannot use TerraGear problem. Well, this is something to tackle, but it is not and never was a goal of the Automatic Landcover Classification Project to make a new TerraGear or to improve its handling. It _is_ part of the mission of the Custom Scenery Project, but that clearly doesn't add anything to your claim that the classification concept would be far! from working. I have brought the fgfs-builder to attention multiple times and I have mentioned that it downloads and compiles the problematic dependencies of TerraGear as well. I created the fgfs-builder because I had problems with compiling TerraGear and the required stuff at the beginning myself, and I am using it regularly without many problems. Up to now I haven't received any feedback on that part, so either nobody has tried it, nobody has had any problems compiling TerraGear or nobody bothered to report their problems. I know that it probably won't work out of the box on Cygwin or similar, but I can't do everything at once, similar to everybody else here. BTW: the fgfs-builder SVN repository has moved to http://svn.community.therosconsulting.com/fgfsbuilder/. Many Thanks to Douglas Campos for hosting it! I also prepared a new tarball of the current version at ftp://ftp.uni-duisburg.de/FlightGear/Misc_rag/fgfs-builder Some weeks ago I nearly had a full new tutorial for building scenery with TerraGear done, including current datasources, current preparation tools (e.g. the shape-decoder) etc. An unfortunate slip ruined that work and up to now I didn't have the time to re-establish that part and it will stay that way for at least one further week. The intention of the scenery database is similar to that of the scenery object database: We want to collect customised landcover and linear feature data at a central point, were we can integrate multiple sources (e.g. OSM, TIGER, Canada Road Map) and from which we can automatically, regularly and much more often than currently generate scenery. When you submit a change in the data - e.g. by using Landsat imagery of your region, providing training data, checking the classification results returned to you and submitting them after correction - the change will be visible shortly in the next scenery build. For that we already got TerraGear running on the OSGeo machine that currently hosts the FlightGear mapserver (which makes it possible to get the data out of the database without having to go via possibly errorprone network connections). The problems you mentioned are applicable to _all_ such activities and I would call it unfair to attribute this specifically to a single project. I will now get back to more productive activities so that my schedule won't get any more worse, pushing back any activities for FlightGear further. I hope that I was successful in clarifying that the application of automatic classification is nothing that we will only see in the far future, as you implied, but it _is_ working and is near a stage were users will actually be able to help improving the database, instead of just looking at the results the project people produced. The only limiting factor right now is the free time of the people doing the work. Cheers, Ralf - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] S-51 Dragonfly and H-21C Shawnee
* gerard robin -- Friday 02 November 2007: Sikorsky S-51 Dragonfly and the Piasecki flying banana H-21C Shawnee, are now available on CVS. Wonderful! Many thanks for this enhancement of our helicopter fleet. :-) m. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] [PATCH] IVSI problem
Hi! I have been investigating the Concorde IVSI problem. I came to the conclusion that the trouble is that the environment altitude and thus the pressure (which is calculated from that) is lagging by 1 frame. Normally that wouldn't be a problem, but the IVSI calculates rate of change and it will use the new dt with the old value difference, thereby arriving at bad results if dt changes (and it does). My proposed fix would be to move the environment subsystem earlier in the initialization and thus the update sequence, as per the attached patches. Alternatively it should be possible to achieve a similar result by delaying the dt value by one frame in the IVSI itself. Any objections or comments? PS: Many thanks to Aerotro who kept nagging everyone that Concorde is broken ;) -- Csaba/Jester Index: src/Main/fg_init.cxx === RCS file: /var/cvs/FlightGear-0.9/source/src/Main/fg_init.cxx,v retrieving revision 1.189 diff -u -r1.189 fg_init.cxx --- src/Main/fg_init.cxx7 Oct 2007 19:27:05 - 1.189 +++ src/Main/fg_init.cxx2 Nov 2007 17:29:07 - @@ -1642,6 +1642,15 @@ // model or control parameters are set fgAircraftInit(); // In the future this might not be the case. + + +// Initialize the weather subsystem. + + +// Initialize the weather modeling subsystem +globals-add_subsystem(environment, new FGEnvironmentMgr); + + // Initialize the aircraft systems and instrumentation (before the // autopilot.) @@ -1688,14 +1697,6 @@ -// Initialize the weather subsystem. - - -// Initialize the weather modeling subsystem -globals-add_subsystem(environment, new FGEnvironmentMgr); - - - // Initialize the lighting subsystem. Index: src/Main/fg_init.cxx === RCS file: /var/cvs/FlightGear-0.9/source/src/Main/fg_init.cxx,v retrieving revision 1.172.2.14 diff -u -r1.172.2.14 fg_init.cxx --- src/Main/fg_init.cxx7 Oct 2007 19:27:06 - 1.172.2.14 +++ src/Main/fg_init.cxx2 Nov 2007 17:30:56 - @@ -1666,6 +1666,15 @@ // model or control parameters are set fgAircraftInit(); // In the future this might not be the case. + + +// Initialize the weather subsystem. + + +// Initialize the weather modeling subsystem +globals-add_subsystem(environment, new FGEnvironmentMgr); + + // Initialize the aircraft systems and instrumentation (before the // autopilot.) @@ -1712,14 +1721,6 @@ -// Initialize the weather subsystem. - - -// Initialize the weather modeling subsystem -globals-add_subsystem(environment, new FGEnvironmentMgr); - - - // Initialize the lighting subsystem. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] S-51 Dragonfly and H-21C Shawnee
Hello, In order to please to the old time helicopter lover Sikorsky S-51 Dragonfly and the Piasecki flying banana H-21C Shawnee, are now available on CVS. http://pagesperso-orange.fr/GRTux/S-51-Dragonfly.jpg http://pagesperso-orange.fr/GRTux/S-51-img1.jpg AND http://pagesperso-orange.fr/GRTux/H-21-Img1.jpg Could you notice that the start process is not the usual FG helicopter process. It is the usual Aircraft process , magneto first, and start (s key) These Helicopter had piston engines (no turbine yet). An other old time Piasecki helicopter is coming, the HUP Piasecki. It was the Piasecki's response to a US Navy Bureau of Aeronautics requirement issued in 1945 for a helicopter designed specifically for operations at sea, the HUP was designed to be both compact enough to fit aboard a variety of ships, yet capable of performing vertical replenishment, casevac, rescue and plane-guard duties. here the shape http://pagesperso-orange.fr/GRTux/Piasecki-HUP.jpg Regards -- Gérard http://pagesperso-orange.fr/GRTux/ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Problem compiling Atlas
On Thursday 01 November 2007 08:22, K. Hoercher wrote: On 10/31/07, Durk Talsma [EMAIL PROTECTED] wrote: As I was typing this reply, I got your other mail. Yes, you're pretty much right that Atlas no longer compiles against Simgear CVS. But, most fixes are pretty straightforward. Provided one already has that optind=0; stuff, the attached patch should take care of the linking flags and some simgear type changes I encountered. (Minus some local hackery I removed; it does compile and seemingly run as of last week's cvs HEAD of simgear , qualified by that evil for me) HTH K. Hoercher Thanks for that but no luck _here_ I'm afraid:( ...that's assuming I applied the diff correctly. Actually, when I tried to apply it using patch it just sat there doing nothing so I had to apply the changes manually but they seemed clear enough. Not to worry though - I'm sure it'll get sorted out in cvs eventually. Thanks for your help. LeeE - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Fixing head lag
I think it's great that FlightGear added head lag to the sim -- it's a good alternative when the pilot can't feel forces -- but I think we'd do better to model it based on perceived forces, not on roll/yaw/pitch damping. For example, simply entering a coordinated bank gently shouldn't cause any head movement at all, but flying straight in a forward slip should, because there's a yaw force pulling the head slightly sideways. Likewise, while the pilot is perceiving 1G the head should move up a bit, and while the pilot is perceiving 1G, the head should move down a bit. Would anyone object to my checking in some changes over the next week or two to change this? We can always roll them back if they don't work. All the best, David - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
