Re: [Flightgear-devel] contacting tower
Ampere K. Hardraade wrote: On October 18, 2005 05:51 am, Frank Olaf wrote: > >>Another point is that I am not always able to contact the tower when > >>pressing the ' key, even though I am on the correct radiofrequency. > > Er... try flying out of the ATC's control area before you attempt to contact the tower. Ampere It's not the tower that is the problem, it is that the key-press is not recognised more than once, several keys and key combinations are recognised only once in CVS versions I compile. -- Frank Olaf Sem-Jacobsen ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] contacting tower
On October 18, 2005 05:51 am, Frank Olaf wrote: > > >>Another point is that I am not always able to contact the tower when > > >>pressing the ' key, even though I am on the correct radiofrequency. > > > Er... try flying out of the ATC's control area before you attempt to contact the tower. Ampere ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] [PATCH] TU114-set.xml help/spelling in comments
Index: ../data/Aircraft/TU-114/TU-114-set.xml === RCS file: /var/cvs/FlightGear-0.9/data/Aircraft/TU-114/TU-114-set.xml,v retrieving revision 1.1 diff -u -r1.1 TU-114-set.xml --- ../data/Aircraft/TU-114/TU-114-set.xml 5 Oct 2005 15:59:17 - 1.1 +++ ../data/Aircraft/TU-114/TU-114-set.xml 19 Oct 2005 01:11:34 - @@ -9,6 +9,16 @@ + + + K + Toggle trajectory markers + + +L/U +Update Tower/Drop View position + + + @@ -181,7 +191,7 @@ -U +L Update Tower View position nasal ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] fgfs on AMD64 status? Mobo suggestions/warnings?
Hi, I've been out of the fgfs development loop for an annoyingly long time. At first, I had to adjust to a big drop in free time after (thankfully) finally getting employed. Then I had a video card failure that forced me back to an old card I had lying around which had no 3D acceleration. And then, at the end of July, problems with my motherboard started, and worsened through the month until it became basically unusable by September. I'm secure enough now that I'm shopping to build a new machine. I'm looking at AMD64 motherboards and one of the newer nvidia cards. And what I'm wondering is whether any fgfs developers can speak to building and running fgfs, on linux, on an AMD64 box, and/or with the nv 6600's/6800's etc. I've seen some threads that people are running it on AMD64 OK; but I'm wondering if there are any suggestions, recommendations, or warnings that are worth hearing before I start shelling out the big $ (e.g. mobos you're happy with or had nothing but trouble with). I wanna get back to this stuff. Cheers, -c ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] [PATCH] OV10 aircraft help dialog updated
I've just flown the OV10 a bit --- a very nice model, thanks. I've copied the .html docs over in a shorthand form to the XML file, for them to appear in the aircraft help dialog, in the following patch: Index: ../data/Aircraft/OV10/OV10-set.xml === RCS file: /var/cvs/FlightGear-0.9/data/Aircraft/OV10/OV10-set.xml,v retrieving revision 1.10 diff -u -r1.10 OV10-set.xml --- ../data/Aircraft/OV10/OV10-set.xml 14 Jun 2005 18:04:28 - 1.10 +++ ../data/Aircraft/OV10/OV10-set.xml 18 Oct 2005 22:22:39 - @@ -46,8 +46,14 @@ false - + OV-10A + Vr 100 KIAS + Vy 130 KIAS + Procedures_ + Takeoff: no flaps, full throttle + Normal landing: gear down, 100KIAS w/full flaps. + Short-field landing: gear down, 75KIAS w/full flaps. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: [PATCH] [BUG] fix a NASAL error when the W&B dialog is open w/jsbsim
Following Andy's and Melchior's comments, here is a shorter patch
with more user-friendly text displayed.
Please apply,
V.
Index: ../data/Nasal/gui.nas
===
RCS file: /var/cvs/FlightGear-0.9/data/Nasal/gui.nas,v
retrieving revision 1.10
diff -u -r1.10 gui.nas
--- ../data/Nasal/gui.nas 13 Jul 2005 11:30:32 - 1.10
+++ ../data/Nasal/gui.nas 18 Oct 2005 20:02:20 -
@@ -132,6 +132,20 @@
header = dialog[name].addChild("text");
header.set("label", title);
+dialog[name].addChild("hrule").set("pref-height", 2);
+
+if (props.globals.getNode("/yasim") == nil) {
+msg = dialog[name].addChild("text");
+msg.set("label", "Not supported for this aircraft");
+cancel = dialog[name].addChild("button");
+cancel.set("legend", "Cancel");
+cancel.prop().getNode("binding[0]/command",
1).setValue("dialog-close");
+fgcommand("dialog-new", dialog[name].prop());
+showDialog(name);
+return;
+}
+
+
contentArea = dialog[name].addChild("group");
contentArea.set("layout", "hbox");
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Carrier Taking Off & Landing Customization
On Tuesday 18 October 2005 12:26, Dai Qiang wrote: > Hi folks, > > I have chosen FGFS as the tool to finish my master > thesis. I hope to realize a carrier taking off and > landing simulation program. > > Here is my question: > > Is it possible to make my own plane and carrier in > FGFS? If so, what are the specific steps? > > Thanks for your help. > > - Qiang There are already working carrier ops in FlightGear. There is the Nimitz carrier just off the West coast of San Francisco and several aircraft are carrier ops equipped. The carrier moves all the time in a box pattern but can be told to head into the wind for launches and landings. This all works perfectly in the CVS version so if you're interested in developing other aircraft carriers and/or aircraft I suggest you grab a copy of the CVS code and take a look at what we already have. Regards Paul ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] [PATCH] a new doc file to document the realtime wx update
Following the comments from Ralf, > Vassilii Khachaturov schrieb: > >>> $ fgfs --prop":/environment/params/real-world-weather-fetch"=true > >>>--prop":/environment/params/control-fdm-atmosphere"=true > >> > >>Why not "--enable-real-weather-fetch"? > >> > > > > > > Because I didn't know about the shorthand option :-) > > :-) > > > BTW, the second property is not affected by this switch still; > > Hm, this is interesting. As far as I see the switch controls whether > temperature, pressure and air density are passed on to the FDM - which > _I_ didn't know about. > > Regards, > Ralf here's an update mentioning the shorthand. Please apply, an extra doc never hurts, does it? --- /dev/null 2005-01-09 22:40:54.0 +0200 +++ data/Docs/README.Real-WX2005-10-18 21:28:20.847371600 +0200 @@ -0,0 +1,22 @@ +Real-world Weather Update += +Launch fgfs with the following two command-line switches in addition to +whatever else you put there: + + $ fgfs --prop":/environment/params/real-world-weather-fetch"=true --prop":/environment/params/control-fdm-atmosphere"=true + +(Unfortunately, if you try to turn these properties on after the program +has started, it doesn't work.) + +The option --prop":/environment/params/real-world-weather-fetch"=true +can be shortened to --enable-real-weather-fetch, but this doesn't +include the second property setting option. + +Alternatively, you can add the two switches to your $HOME/.fgfsrc, +or change the corresponding properties in $FG_ROOT/preferences.xml + +This will allow you to enjoy real-world weather as reported on +the NOAA site, currently at http://weather.noaa.gov/weather/metar.shtml + +You can also use the metar(1) program, coming with flightgear, +to query the NOAA site from the command line in text format. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: CVS: FlightGear/src/Scenery scenery.cxx, 1.9, 1.10
* Mathias Fröhlich -- Tuesday 18 October 2005 19:44: > On Dienstag 18 Oktober 2005 19:05, Melchior FRANZ wrote: > > This patch (in four commit messages) has caused a serious regression: > > When using submodels, fgfs crashes within seconds. > Fixed by the attached patch. Works. Committed. Thanks. :-) m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: CVS: FlightGear/src/Scenery scenery.cxx, 1.9, 1.10
On Dienstag 18 Oktober 2005 19:05, Melchior FRANZ wrote:
> * Erik Hofman -- Saturday 15 October 2005 16:51:
> > Mathias Froehlich:
> >
> > I had a quick view over the ssgBase::ref() calls in flightgear.
> > I made them all symmetric and used ssgDeRefDelete to dereference them.
>
> This patch (in four commit messages) has caused a serious regression:
> When using submodels, fgfs crashes within seconds. Try, for example,
> this line:
>
> $ fgfs --aircraft=737 --vc=400 --altitude=2
>
> and let the 737 dive. The contrails will now crash fgfs, as do other
> submodels, such as the seafire's smoke.
>
> $ cvs up -D'2005/10/15 16:51:50' ---> works
>
> $ cvs up -D'2005/10/15 16:51:55' ---> broken
Thanks for reporting.
Fixed by the attached patch.
Please apply.
Greetings
Mathias
--
Mathias Fröhlich, email: [EMAIL PROTECTED]
Index: src/AIModel/AIBase.cxx
===
RCS file: /var/cvs/FlightGear-0.9/source/src/AIModel/AIBase.cxx,v
retrieving revision 1.43
diff -u -r1.43 AIBase.cxx
--- src/AIModel/AIBase.cxx 15 Oct 2005 14:55:51 - 1.43
+++ src/AIModel/AIBase.cxx 18 Oct 2005 17:42:41 -
@@ -160,7 +160,6 @@
prop_root,
sim_time_sec);
manager->setModel(path, model);
- model->ref();
}
//else
// {
@@ -169,6 +168,10 @@
//aip.setVisible(false);
//globals->get_scenery()->get_scene_graph()->addKid(aip.getSceneGraph());
// do some setModel stuff.
+
+ if (model)
+model->ref();
+
return model;
}
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: CVS: FlightGear/src/Scenery scenery.cxx, 1.9, 1.10
* Erik Hofman -- Saturday 15 October 2005 16:51: > Mathias Froehlich: > > I had a quick view over the ssgBase::ref() calls in flightgear. > I made them all symmetric and used ssgDeRefDelete to dereference them. This patch (in four commit messages) has caused a serious regression: When using submodels, fgfs crashes within seconds. Try, for example, this line: $ fgfs --aircraft=737 --vc=400 --altitude=2 and let the 737 dive. The contrails will now crash fgfs, as do other submodels, such as the seafire's smoke. $ cvs up -D'2005/10/15 16:51:50' ---> works $ cvs up -D'2005/10/15 16:51:55' ---> broken m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] [PATCH] Select another airport for the tower location
This patch is thanks to Melchior and Andy for their pointing me
to the right places to learn about fg/nasal and for their advice
while implementing it.
You will see (in the commented part of the dialog xml) that
a second part is coming in the future, with a shorthand
to import the airport from the COM frequencies.
Enjoy.
Index: src/Main/fg_init.cxx
===
RCS file: /var/cvs/FlightGear-0.9/source/src/Main/fg_init.cxx,v
retrieving revision 1.132
diff -u -p -r1.132 fg_init.cxx
--- src/Main/fg_init.cxx12 Oct 2005 08:55:58 - 1.132
+++ src/Main/fg_init.cxx18 Oct 2005 16:45:38 -
@@ -695,29 +695,42 @@ static bool fgSetPosFromAirportID( const
}
#endif
+static void fgInitTowerLocationListener() {
+struct TowerLocationListener : SGPropertyChangeListener {
+ void valueChanged(SGPropertyNode* node) {
+ const double hdg = fgGetDouble( "/orientation/heading-deg", 0);
+ const string id(node->getStringValue());
+ fgSetTowerPosFromAirportID(id, hdg);
+ }
-// Set current tower position lon/lat given an airport id
-static bool fgSetTowerPosFromAirportID( const string& id, double hdg ) {
-FGAirport a;
-// tower height hard coded for now...
-float towerheight=50.0f;
-
-// make a little off the heading for 1 runway airports...
-float fudge_lon = fabs(sin(hdg)) * .003f;
-float fudge_lat = .003f - fudge_lon;
-
-if ( fgFindAirportID( id, &a ) ) {
-fgSetDouble("/sim/tower/longitude-deg", a.getLongitude() + fudge_lon);
-fgSetDouble("/sim/tower/latitude-deg", a.getLatitude() + fudge_lat);
-fgSetDouble("/sim/tower/altitude-ft", a.getElevation() + towerheight);
-return true;
-} else {
-return false;
-}
+ // Set current tower position lon/lat given an airport id
+ static bool fgSetTowerPosFromAirportID( const string& id, double hdg ) {
+ FGAirport a;
+ // tower height hard coded for now...
+ float towerheight=50.0f;
+
+ // make a little off the heading for 1 runway airports...
+ float fudge_lon = fabs(sin(hdg)) * .003f;
+ float fudge_lat = .003f - fudge_lon;
+
+ if ( fgFindAirportID( id, &a ) ) {
+ fgSetDouble("/sim/tower/longitude-deg", a.getLongitude() +
fudge_lon);
+ fgSetDouble("/sim/tower/latitude-deg", a.getLatitude() +
fudge_lat);
+ fgSetDouble("/sim/tower/altitude-ft", a.getElevation() +
towerheight);
+ return true;
+ } else {
+ return false;
+ }
+ }
+};
+fgGetNode("/sim/tower/airport-id", true)
+ ->addChangeListener( new TowerLocationListener() );
}
+
+
// Set current_options lon/lat given an airport id and heading (degrees)
static bool fgSetPosFromAirportIDandHdg( const string& id, double tgt_hdg ) {
FGRunway r;
@@ -1178,12 +1191,15 @@ bool fgInitPosition() {
string parkpos = fgGetString("/sim/presets/parkpos");
string fix = fgGetString("/sim/presets/fix");
+fgSetDouble( "/orientation/heading-deg", hdg );
+fgInitTowerLocationListener();
+
if ( !set_pos && !apt.empty() && !rwy_no.empty() ) {
// An airport + runway is requested
if ( fgSetPosFromAirportIDandRwy( apt, rwy_no ) ) {
// set tower position (a little off the heading for single
// runway airports)
-fgSetTowerPosFromAirportID( apt, hdg );
+ fgSetString("/sim/tower/airport-id", apt.c_str());
set_pos = true;
}
}
@@ -1193,7 +1209,7 @@ bool fgInitPosition() {
if ( fgSetPosFromAirportIDandHdg( apt, hdg ) ) {
// set tower position (a little off the heading for single
// runway airports)
-fgSetTowerPosFromAirportID( apt, hdg );
+ fgSetString("/sim/tower/airport-id", apt.c_str());
set_pos = true;
}
}
@@ -1237,8 +1253,6 @@ bool fgInitPosition() {
fgGetDouble("/sim/presets/longitude-deg") );
fgSetDouble( "/position/latitude-deg",
fgGetDouble("/sim/presets/latitude-deg") );
-fgSetDouble( "/orientation/heading-deg",
- fgGetDouble("/sim/presets/heading-deg") );
// determine if this should be an on-ground or in-air start
if ((fabs(gs) > 0.01 || fabs(od) > 0.1 || alt > 0.1) && carrier.empty()) {
Index: data/gui/menubar.xml
===
RCS file: /var/cvs/FlightGear-0.9/data/gui/menubar.xml,v
retrieving revision 1.38
diff -u -p -r1.38 menubar.xml
--- data/gui/menubar.xml5 Jul 2005 08:51:18 - 1.38
+++ data/gui/menubar.xml18 Oct 2005 16:47:26 -
@@ -196,6 +196,14 @@
+
+ Tower position
+
+dialog-show
+ location-of-tower
+
+
+
--- /dev/null 2005-01-09 22:40:54.0 +0200
+
Re: [Flightgear-devel] contacting tower
Buchanan, Stuart wrote: >>Has anyone had the time to look at this problem yet? >>it is a bit >>annoying when flying having a large number of key >>presses available only >>once. Since I don't have any insight into the >>source code I think I >>will do more harm than good if I should try to >>correct it myself (and it >>would take a very long time ;) ) > > >Hi Frank, > >Like you, I don't have enough experience of the code >to be able to delve in and pinpoint your problem, but >I do have a suggestion or two. Suggestions are always welcome :) >- Firstly, do you see this on a 0.9.8 FG install ? If >so, it would suggest that something has changed on >your box, rather than a straightforward FG bug. The problems I described are only present in the CVS version of flightgear. The 0.9.8 release works normally, i.e. I may press every key multiple times and have flightgear respond every time. >- Secondly, could you have triggered anything in the >Accessibility Options on XP like StickyKeys, >ToggleKeys or FilterKeys. They hay be named something >different on XP (I'm looking at a 2k box right now). I >don't really know much about them, but they get >triggered somewhat easily (pressing shift 5 times for >example) and might mess up some key codes. I have checked my settings in control panel and found that sticky keys is turned off. Additionally, the problems with the CVS version are present on both my Windows XP PCs. >- Thirdly, and very speculatively, is there some way >within the properties tree to detect what keys are >currently pressed? Poissibly under the input branch? You might want to see if the key-presses are reaching >FG. I've checked the property browser, but I can't seem to find any property that displays raw keypresses :( >Sorry I can't be of more help. > >-Stuart > -- Frank Olaf Sem-Jacobsen ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Carrier Taking Off & Landing Customization
Hi folks, I have chosen FGFS as the tool to finish my master thesis. I hope to realize a carrier taking off and landing simulation program. Here is my question: Is it possible to make my own plane and carrier in FGFS? If so, what are the specific steps? Thanks for your help. - Qiang ___ 雅虎免费G邮箱－No.1的防毒防垃圾超大邮箱 http://cn.mail.yahoo.com ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] contacting tower
> Has anyone had the time to look at this problem yet? > it is a bit > annoying when flying having a large number of key > presses available only > once. Since I don't have any insight into the > source code I think I > will do more harm than good if I should try to > correct it myself (and it > would take a very long time ;) ) Hi Frank, Like you, I don't have enough experience of the code to be able to delve in and pinpoint your problem, but I do have a suggestion or two. - Firstly, do you see this on a 0.9.8 FG install ? If so, it would suggest that something has changed on your box, rather than a straightforward FG bug. - Secondly, could you have triggered anything in the Accessibility Options on XP like StickyKeys, ToggleKeys or FilterKeys. They hay be named something different on XP (I'm looking at a 2k box right now). I don't really know much about them, but they get triggered somewhat easily (pressing shift 5 times for example) and might mess up some key codes. - Thirdly, and very speculatively, is there some way within the properties tree to detect what keys are currently pressed? Poissibly under the input branch? You might want to see if the key-presses are reaching FG. Sorry I can't be of more help. -Stuart ___ How much free photo storage do you get? Store your holiday snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: [Terragear-devel] uav update
"Curtis L. Olson" wrote: > Well now how did I get the terragear address on that email ... Never mind, this was an interesting reading :-) Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] contacting tower
Hi, Has anyone had the time to look at this problem yet? it is a bit annoying when flying having a large number of key presses available only once. Since I don't have any insight into the source code I think I will do more harm than good if I should try to correct it myself (and it would take a very long time ;) ) > >>Another point is that I am not always able to contact the tower when > >>pressing the ' key, even though I am on the correct radiofrequency. > > > Since this appears to be a bug I'll continue this discussion on the > developer list.(I assume I shouldn't post this message on both lists?) > Further investigation into the tower communication problem shows that > several of my key presses are available only once. I may lower the > flaps to one notch once, and raise them again once. v cycles the view > multiple times, but shift+v only cycles the view backwards once. I may > only contact the tower once with the ' key, h cycles the HUD, but shift > + h only works once. > This is present both in a two weeks old CVS checkout, and in one from > yesterday. The problem only seems to affect keyboard commands, this is > the commands that are mapped to the joystick like flaps and view cycling > work well multiple times in both directions. > My system is a Windows XP box with service Pack 2, compiled using MSYS. > Please let me know if additional information is required. -- Frank Olaf Sem-Jacobsen ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] uninitialized variables used
2005/10/16, Erik Hofman <[EMAIL PROTECTED]>: > Thanks for the patch Ladislav, I've committed a slightly modified > version to CVS now. > > Erik Not at all. Just I am not sure about computing of geoc in src/Scenery/hitlist.cxx . Regards Ladislav. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: A question regarding accurate taxiways
"Ampere K. Hardraade" wrote: > On October 17, 2005 02:28 am, Martin Spott wrote: >> I' pretty sure it easier to convert the PDF's into some common vector >> drawing format than adding editing capabilities to [X,K,G]PDF. Once you >> have a nice vector format you can easily load that into your favourite >> editor, and group the necessary lines together. > No -- no editing. Just an interface for the user to select what is > appropiate > for export. I understood your wish very well but I suspect that this is not feasible. Some of the logic behind such an airport layout is not explicitly printed in the diagram and needs some guessswork and/or experience to make it over into a functional airport description. This is why I think we will always need an editing stage, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
