[Flightgear-devel] further enhanced active-runway selection
I just pushed one more commit to http://gitorious.org/~jsd/fg/sport-model/commits/navaid-repairs This provides IMHO a pleasing combination of simplicity, versatility, consistency, and verisimilitude. The main new feature is to allow the active runway to be chosen to have a crosswind or tailwind. From the README file: This describes the effect of /environment/runway-wind-skew. Setting this variable affects the choice of runway. This is relevant in three ways: -- It affects the selection of the runway for placement of the aircraft during initialization, assuming an airport has been specified but no specific runway has been specified. (This affects the code in two places, in fg_init.cxx and main.cxx.) -- It affects what ATIS says is the runway-in-use. -- It affects which end of a reversible ILS will be active. The specific effect works like this: Suppose the wind at the airport is coming from the direction WWW, and suppose the value of runway-wind-skew is RWS. Then we /pretend/ the wind is coming from WWW+RWS and choose the runway accordingly. A value of RWS that is positive (but less than 180) mean the runway will be to the right of the actual wind WWW, which increases the chance that you will have a crosswind from your left when using the chosen runway. Assuming there is some nonzero wind, and the wind doesn't shift: ++ Setting RWS=90 guarantees a crosswind component from the left. ++ Setting RWS=-90 guarantees a crosswind component from the right. ++ Setting RWS=180 guarantees a tailwind component. Some examples: Suppose the airport provides runways 4/22 and 16/34, all of which are similar in length and width. Suppose the actual wind is coming straight out of the north. *) RWS greater than -80 and less than 10 Runway 34, crosswind from the right *) RWS greater than 10 and less than 100 Runway 4, crosswind from the left *) RWS greater than 100 and less than 190 Runway 16, crosswind from the left *) RWS greater than -170 and less than -80 Runway 22, crosswind from the right -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] ATIS upgrades
-Original Message- From: John Denker [mailto:j...@av8n.com] Sent: 03 January 2011 02:03 To: FlightGear developers discussions Subject: Re: [Flightgear-devel] ATIS upgrades Hi -- On 01/02/2011 06:37 PM, you wrote: Can I just clarify whether you are happy to have your scripts committed to flightgear/utils in addition to being available from your website? Yes, happy. Public domain, not GPL. If so, I'll add them ASAP. Er ... not GPL. That would be a show-stopper then? Vivian -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] ATIS upgrades
Hi Vivian, public domain is less restrictive than the GPL so it's GPL compatible. Where we run into trouble is with licenses that are more restrictive than the GPL and explicitly disallow something the GPL allows. Regards, Curt. On Mon, Jan 3, 2011 at 8:09 AM, Vivian Meazza wrote: -Original Message- From: John Denker [mailto:j...@av8n.com] Sent: 03 January 2011 02:03 To: FlightGear developers discussions Subject: Re: [Flightgear-devel] ATIS upgrades Hi -- On 01/02/2011 06:37 PM, you wrote: Can I just clarify whether you are happy to have your scripts committed to flightgear/utils in addition to being available from your website? Yes, happy. Public domain, not GPL. If so, I'll add them ASAP. Er ... not GPL. That would be a show-stopper then? Vivian -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Curtis Olson: http://www.atiak.com - http://aem.umn.edu/~uav/ http://www.flightgear.org - http://www.flightgear.org/blogs/category/curt/http://www.flightgear.org/blogs/category/personal/curt/ -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] [PATCH] Add ILS data to GUI/MapWidget
Hello.
Unfortunately, I have no permission to put patches directly to git. So
please review attached for small patch to display ILS data on the map
widget.
Thank you.
---
Regards,
Alexey.
From c1cd3fe22764ad24a1e654d69e4b91d15048cfca Mon Sep 17 00:00:00 2001
From: Aliaksei Ivaniuk aliaksei_ivan...@epam.com
Date: Mon, 3 Jan 2011 17:06:37 +0200
Subject: [PATCH] Add ILS data to GUI/MapWidget
Added code for displaying ILS data (ILS category, channel, frequency) in to
the Map widget.
---
src/GUI/MapWidget.cxx | 16
1 files changed, 16 insertions(+), 0 deletions(-)
diff --git a/src/GUI/MapWidget.cxx b/src/GUI/MapWidget.cxx
index bdd73a1..4b4ef93 100644
--- a/src/GUI/MapWidget.cxx
+++ b/src/GUI/MapWidget.cxx
@@ -1285,6 +1285,22 @@ void MapWidget::drawILS(bool tuned, FGRunway* rwy)
glVertex2dv(endCentre.data());
glVertex2dv(endR.data());
glEnd();
+
+ if (validDataForKey(loc)) {
+setAnchorForKey(loc, endR);
+return;
+ }
+
+ char buffer[1024];
+ ::snprintf(buffer, 1024, %s\n%s\n%3.2fKhz,
+ loc-name().c_str(), loc-ident().c_str(),loc-get_freq()/100.0);
+
+ MapData* d = createDataForKey(loc);
+ d-setPriority(40);
+ d-setLabel(loc-ident());
+ d-setText(buffer);
+ d-setOffset(MapData::HALIGN_CENTER | MapData::VALIGN_BOTTOM, 10);
+ d-setAnchor(endR);
}
void MapWidget::drawTraffic()
--
1.6.6.1
signature.asc
Description: PGP signature
--
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [PATCH] Add ILS data to GUI/MapWidget
On 3 Jan 2011, at 15:21, Alexey Varjat wrote: Unfortunately, I have no permission to put patches directly to git. So please review attached for small patch to display ILS data on the map widget. Looks fine, I'll apply/test/commit later today, time permitting. Regards, James -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Disabling menu items (was Re: map question)
On Sun, Jan 2, 2011 at 5:14 PM, Stuart Buchanan wrote: On Sun, Jan 2, 2011 at 3:44 PM, James Turner wrote: On 2 Jan 2011, at 14:56, Stuart Buchanan wrote: gui.menuEnable(fuel-and-payload, false); We can add new names for any other menus that we might want to disable on a per-aircraft basis, but from a quick skim through the menus I couldn't see any other candidates. Proving one again that FlightGear already supports everything, if only it were documented ;) WHich aircraft need to be updated to use this feature, prior to the release? As always, once we have a decent corpus of aircraft following the 'correct' style, it's easier to tell aircraft developers to 'do what the f14 already does' when updating aircraft. I've done a grep of the Aircraft tree and eyeballed the results. ... and missed a couple in the process by not looking carefully enough. Whoops. The following aircraft override the radio dialog, which has moved since v2.0.0. 777-200ER b1900d Citation-Bravo I've just pushed an enhancement to gui.nas that allows the aircraft developer to change the binding for a symbolically named dialog, in the same way that they can enable/disable dialogs and menus using the existing gui.menuEnable() function. So, you can now put the following code in your aircraft-specific Nasal files: gui.menuBind(radio, dialogs.Radio.open()); This replaces the binding for the radio menu item with a command to open the dialogs.Radio dialog box (that you've defined elsewhere). Note that this searches the menu for the symbolic names (name tag) defined in menubar.xml, (e.g. radio, autopilot-settings, gps, map) rather than the label tag, which may change over time, so should be a robust long-term solution. Syd - I think all these aircraft are yours. Could you update them to use the new function? Hint: - the code you want for the 777-200ER is to add the following to the bottom of 777-200ER/Nasal/dialogs.nas: gui.menuBind(radio, dialogs.Radio.open()); gui.menuBind(autopilot-settings, dialogs.ap_settings.open()); I expect the code for the other aircraft is similar :) I've still to work out a better way to handle adding new items to the existing menus, e.g. pushback. Part of me feels that this should be located in the aircraft-specific menu rather than Equipment, but it would be straightforward to add a new gui.menuAdd() function along similar lines to menuBind(). Anyone got any preferences? -Stuart -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Fwd: Generic Autopilot works by location?
Hey all, I am finding the Generic Autopilot either works as expected, or loads with unchangeable data, depending on spawn location. I seem to recall some discussion about a location dependent bug, but I thought it was related to weather. (?) FlightGear v2.0 8/21/2010 snapshot from Tat's site. Any aircraft without a purpose built AP seems to be affected, based on the number I've tested, but for these locations listed I was using the popular MD-81 from Gary Neely's website. Airports to the north and to the south are working, where the middle area is not. Working locations tested: To the south - Kathmandu, Nepal, San Antonio, TX; Orlando, FL, and Key West, FL To the north - Rost, Norway; Montreal, QC Non-working locations seem to be anything across the middle third - Burlington, VT (just across the border from Montreal) Atlanta, GA Charles De Gaulle, Paris, France EHAM KSFO What I don't know yet is if this related to latitude/longitude, the airport itself, or something outside of that. But the data at the moment presents itself as a lat/lon issue. In a non-working location bad data consists of a default speed in the 13,000 range, alt hold in the 33,000 range, and headings from 130 - 550 degrees. These values can not be changed by the user. Often the headings and speed values are constantly climbing. A valid working location typically loads with 0 for heading and speed, and a single digit value for altitude hold. These are then changeable. Can anyone enlighten me on it? Thank you, Peter Brown Does no one have information on the Generic Autopilot only working above or below certain latitudes? -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Fwd: Generic Autopilot works by location?
Hi Peter, I can't think of any reason the basic autopilot functionality would be tied to a particular location. Could you provide a specific aircraft and airport (i.e. command line options) that tickle this bug? Perhaps it's something with your local build? Perhaps it's something really obscure that no one else has noticed? Thanks, Curt. On Mon, Jan 3, 2011 at 1:28 PM, Peter Brown wrote: Hey all, I am finding the Generic Autopilot either works as expected, or loads with unchangeable data, depending on spawn location. I seem to recall some discussion about a location dependent bug, but I thought it was related to weather. (?) FlightGear v2.0 8/21/2010 snapshot from Tat's site. Any aircraft without a purpose built AP seems to be affected, based on the number I've tested, but for these locations listed I was using the popular MD-81 from Gary Neely's website. Airports to the north and to the south are working, where the middle area is not. Working locations tested: To the south - Kathmandu, Nepal, San Antonio, TX; Orlando, FL, and Key West, FL To the north - Rost, Norway; Montreal, QC Non-working locations seem to be anything across the middle third - Burlington, VT (just across the border from Montreal) Atlanta, GA Charles De Gaulle, Paris, France EHAM KSFO What I don't know yet is if this related to latitude/longitude, the airport itself, or something outside of that. But the data at the moment presents itself as a lat/lon issue. In a non-working location bad data consists of a default speed in the 13,000 range, alt hold in the 33,000 range, and headings from 130 - 550 degrees. These values can not be changed by the user. Often the headings and speed values are constantly climbing. A valid working location typically loads with 0 for heading and speed, and a single digit value for altitude hold. These are then changeable. Can anyone enlighten me on it? Thank you, Peter Brown Does no one have information on the Generic Autopilot only working above or below certain latitudes? -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Curtis Olson: http://www.atiak.com - http://aem.umn.edu/~uav/ http://www.flightgear.org - http://www.flightgear.org/blogs/category/curt/http://www.flightgear.org/blogs/category/personal/curt/ -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Fwd: Generic Autopilot works by location?
On Jan 3, 2011, at 2:37 PM, Curtis Olson wrote: Hi Peter, I can't think of any reason the basic autopilot functionality would be tied to a particular location. Could you provide a specific aircraft and airport (i.e. command line options) that tickle this bug? Perhaps it's something with your local build? Perhaps it's something really obscure that no one else has noticed? Thanks, Curt. On Mon, Jan 3, 2011 at 1:28 PM, Peter Brown wrote: Hey all, I am finding the Generic Autopilot either works as expected, or loads with unchangeable data, depending on spawn location. I seem to recall some discussion about a location dependent bug, but I thought it was related to weather. (?) FlightGear v2.0 8/21/2010 snapshot from Tat's site. Any aircraft without a purpose built AP seems to be affected, based on the number I've tested, but for these locations listed I was using the popular MD-81 from Gary Neely's website. Airports to the north and to the south are working, where the middle area is not. Working locations tested: To the south - Kathmandu, Nepal, San Antonio, TX; Orlando, FL, and Key West, FL To the north - Rost, Norway; Montreal, QC Non-working locations seem to be anything across the middle third - Burlington, VT (just across the border from Montreal) Atlanta, GA Charles De Gaulle, Paris, France EHAM KSFO What I don't know yet is if this related to latitude/longitude, the airport itself, or something outside of that. But the data at the moment presents itself as a lat/lon issue. In a non-working location bad data consists of a default speed in the 13,000 range, alt hold in the 33,000 range, and headings from 130 - 550 degrees. These values can not be changed by the user. Often the headings and speed values are constantly climbing. A valid working location typically loads with 0 for heading and speed, and a single digit value for altitude hold. These are then changeable. Can anyone enlighten me on it? Thank you, Peter Brown Does no one have information on the Generic Autopilot only working above or below certain latitudes? -- Curtis Olson: http://www.atiak.com - http://aem.umn.edu/~uav/ http://www.flightgear.org - http://www.flightgear.org/blogs/category/curt/ I will put together more information. Thank you, Peter-- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] AH-1 Merge Request
Hi, It is time again for my AH-1 to be merged into GIT. If somebody could do this for me that would be great. You can download the AH-1 package here: http://jacksfilestorage.yolasite.com/resources/AH-1_1-3-11.zip Thanks! - Jack -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] ATIS upgrades
I just now pushed a couple more ATIS upgrades to http://gitorious.org/~jsd/fg/sport-model/commits/atis One of them will, alas, require rebuilding the voice snippet data. http://www.av8n.com/festival/ Mostly this is to improve the internationalization. -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] A380 Merge Request
Greetings and New Year merriment to all, After a flurry of activity over the Christmas holiday, could someone please commit the latest changes to the A380 in fgdata from; http://gitorious.org/airbus-aircraft/a380/archive-tarball/master simply replace all the files and git add the following; Systems/Electrical/A380-electrical.xml Textures/Instruments/buttons4.png Textures/Instruments/buttons5.png Textures/Instruments/buttons6.png Many thanks Scott. -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Disabling menu items (was Re: map question)
The following aircraft override the radio dialog, which has moved since v2.0.0. 777-200ER b1900d Citation-Bravo I've just pushed an enhancement to gui.nas that allows the aircraft developer to change the binding for a symbolically named dialog, in the same way that they can enable/disable dialogs and menus using the existing gui.menuEnable() function. So, you can now put the following code in your aircraft-specific Nasal files: gui.menuBind(radio, dialogs.Radio.open()); This replaces the binding for the radio menu item with a command to open the dialogs.Radio dialog box (that you've defined elsewhere). Syd - I think all these aircraft are yours. Could you update them to use the new function? Hint: - the code you want for the 777-200ER is to add the following to the bottom of 777-200ER/Nasal/dialogs.nas: gui.menuBind(radio, dialogs.Radio.open()); gui.menuBind(autopilot-settings, dialogs.ap_settings.open()); -Stuart Sounds like a much easier solution , thanks . I can fix all these tomorrow ... still not sure how to go about commiting them though maybe I'll reread git for dummies ;) Syd -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] terragear roadmap
Hi Pete, Currently, TerraGear is mostly being redeveloped in order to handle more detailed scenery - recent advances in FlightGear scenery data technology have made this necessary. I think this is a lot of GIS C++ work - I am primarily a data contributor. So please note anything you do should be compatible with this roadmap - other than that, I think there's just a TerraGear wish list, but those actually programming can correct me if I'm wrong. I would say feel free to work on uv-mapping and brainstorm on the idea of transition polygons. However, I am working on some quite detailed scenery at the moment and can say when scenery data is at about 30m precision transition polygons become difficult to manage. The problem with vector-only data is it doesn't allow for the fuzzy pixels you see in remotely sensed imagery, which allow - somewhat - for realistic transitions - everything is hard-edged. Some sort of automated seam blending would be really cool, but I think this is hard to do... As far as updating apt.dat goes, we've done a fork of 8.10 and have quite a number of updated airports sitting on the mapserver somewhere. Curved taxiways would be brilliant but because of both distribution and performance limitations the problem is inserting curved polygons as cheaply as possible when it comes to polygon counts. A somewhat dated but interesting primer can be found here: http://custom-scenery.org/Research-Deve.274.0.html (make sure to click on the sub-links on the left). Have fun and welcome Cheers John -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
