Re: [Flightgear-users] FlightGear 0.9.9 Crashing on startup
On Sunday 20 November 2005 13:49, Gerard ROBIN wrote: Working perfectly, as usual. Only a little visual defect inside Hangar near to Elevator 1 (face not triangulated). Here:http://ghours.club.fr/AC-carrierHangar.jpg Actually I think that that defect is the result of two faces ocupying the same real estate. There are a few more places on the Nimitz where more than one face is fighting for the exact same plane in space. -- Roy Vegard Ovesen ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Re: Whats a good web-site for uploading
On Thursday 17 November 2005 12:19, Melchior FRANZ wrote: If there is a more friendly way of viewing the discussions and replying please let me know. This is the first anyone has said to me about it. No, this message was perfect. And it was the first correct reply from you, after lots of separate threads under the subject Whats a good web-site for uploading. :-) Hmmm I disagree! Dene's message appears as a new thread in my mail reader (KMail 1.8.2). When I look at the source for the message I see that it has no In-Reply-To field, consequently it has to start a new thread. -- Roy Vegard Ovesen ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-users] Re: Whats a good web-site for uploading
This reply sent by clicking the reply link in list archives. Apologies for using the list as a test vehicle. -- Roy Vegard Ovesen ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] autopilot
On Sunday 30 October 2005 08:32, Innis Cunningham wrote: Hi All Could someone with more understanding than me,of autopilot, tell me where the property is that is restricting the autopilot to a climb rate of 8.33 FPS and a decent rate of 16.67 FPS.Look as I might I can't see where this is set. I'll assume that you are talking about the 737 autopilot. The Altitude Hold Stage 1 controller, starting at line 224, restricts the rate-of-climb setpoint to -2000 to 2000 fps. I guess that makes sense?! Further down, beginning at line 400, you'll see that the Speed hold (vary pitch) Stage #1 controller restricts the _pitch_ to -8.0 to 15.0 degrees. Are you sure that it's the climb rate that is restricted to 8.33/16.67, and not the pitch when in speed hold mode? -- Roy Vegard Ovesen ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] autopilot
On Sunday 30 October 2005 14:33, Innis Cunningham wrote: I'll assume that you are talking about the 737 autopilot. Yes it is for the 737. I also assumed that the 737 uses the $FG_RROT/Aircraft/737/Systems/737-autopilot.xml, but it doesn't, it uses the generic autopilot. Of course it should use it's own custom autopilot.xml file, because no one autopilot can be generic enough to work on all aircraft. The Altitude Hold Stage 1 controller, starting at line 224, restricts the rate-of-climb setpoint to -2000 to 2000 fps. I guess that makes sense?! Sorry, that's a typo it should of course be fpm. No changing that value does not change the rate of climb/decent. Is I already said, the 737 doesn't even use the 737-autopilot.xml file. Further down, beginning at line 400, you'll see that the Speed hold (vary pitch) Stage #1 controller restricts the _pitch_ to -8.0 to 15.0 degrees. Are you sure that it's the climb rate that is restricted to 8.33/16.67, and not the pitch when in speed hold mode? The property involved is /autopilot/internal/target-climb-rate-fps when using the altitude hold selection of the autopilot.It only shows about 1deg +/- on the AH/ADI which is 480 FPM climb and 1000 FPM decend which I would think is about right for the light aircraft but not for commercial aircraft.Somewhere else this restriction is in place.I would guess it is the same place that the restriction for roll rate is set at 20 deg.I have looked in the preferences file in the set file for the 737 the generic autopilot file and the 737 autopilot file but I can't see anywhere were this restriction is set. They are of course all in the $FG_ROOT/Aircraft/Generic/generic-autopilot.xml file. The 8.33/16.67 fps climb/descend rates too (line 381). Also the heading select mode does not seem to operate using the mode control panel. It seems to work a little better if the autopilot settings drop down menu is used.but the laterial control seems to work ok when using the nav modes.As I think that the 737 is probably the only aircraft that uses hotspots to select and adjust the autopilot/autothrottle system it would be nice to get it to work correctly to add to the realism of the aircraft. The first thing one should do then is to make the 737 use it's own custom autopilot.xml configuration file. I tried the Beech 1900d and it seems to clip to the same target climb rate. Makes perfect sense if the Beech 1900d also uses the generic autopilot. -- Roy Vegard Ovesen ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] setting GPS waypoints and flying with autopilot
On Tuesday 16 August 2005 15:21, Mike Rawlins wrote: Hi, In the past I've used the autopilot to fly between 5-letter GPS waypoints. IIRC, I would enter waypoints using menu or waypoint file and engage/disengage using ctrl-H. Lately when I enter a 5-letter GPS waypoint a message is issued in my shell window which reads: Failed to find STELR in basic.dat.gz Failed to find MAILS in basic.dat.gz Failed to find YARNN in basic.dat.gz IIRC basic.dat.gz used to hold the airport data. Now airport data is in apt.dat.gz. GPS fixes are (and AFAIK have always been) in fix.dat.gz. So those messages don't make much sense. as examples. However, a lat/lon pair do appear alongside waypoint name in the pop-down waypoint menu, so it could be that the right coordinates are being accessed. I guess that they are naturally not found in basic.dat.gz but found in fix.dat.gz. Maybe I just need to engage the waypoint tracker in the autopilot? I don't believe the KAP-140 is used to do this (?) The KAP140 in the C172 is connected to the navradio and the directional gyro. By altering the autopilot config file you should be able to connect it to the GPS instead, and input GPS fixes through the GPS GUI. -- Roy Vegard Ovesen ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] a few questions about the f16
On Sunday 26 June 2005 15:14, Erik Hofman wrote: Given 190 m/s = 623 ft/s http://www.grc.nasa.gov/WWW/K-12/Missions/Jim/Project1ans.htm So 190 m/s must be pretty close. According to this http://www.grc.nasa.gov/WWW/K-12/airplane/mach.html Mach calculator, the speed of sound at 40 000 feet is 660 mph. And acording to http://www.onlineconversion.com/speed_common.htm 660 mph is about 295 m/s. -- Roy Vegard Ovesen ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Re: the nimitz_demo HOW??
On Saturday 25 June 2005 17:32, Vivian Meazza wrote: If someone could give me a steer (pun intended) on TACAN that would be good. In real life an aircraft controller would give an aircraft a course to recover back to the carrier. That would be nice to implement too. I'd even settle for a Melchior balloon (if pressed). Take a look at the ADF instrument module (adf.*xx). It could be used as a template to create a TACAN instrument module. According to this site: http://www.radarpages.co.uk/mob/navaids/tacan/tacan1.htm TACAN gives the pilot range and bearing to the beacon. That's readily available in the ADF code. You can then add an entry in the navlist (Navaids/navlist*xx), and figure out how to change the position of that entry according to the carriers position. I guess that adding some sort of beacon property to the AIShip class could do the trick. -- Roy Vegard Ovesen ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-users] World Wind as moving map display
Hi all! I've whipped together a python script that reads position from FlightGear and instructs World Wind to goto that position. A couple of screenshots show just how accurately the FlightGear scenery and the World Wind images correspond. http://82.164.122.241/~royvegard/ I stripped down the playback.xml generic protocol into a new one called ww.xml. The new one only outputs position and orientation. FlightGear ran on a linux box sending the data to a winXP box with World Wind and my simple python socket reader running. Now... where is that aeronautical chart overlay plugin for World Wind?! -- Roy Vegard Ovesen ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Re: version 0.9.8
On Thursday 07 April 2005 11:11, Kees Lemmens wrote: Hi, In our Math department we are rapidly replacing Matlab (commercial and VERY expensive !) with Octave (GNU Open Source). I wonder: wouldn't it be a better to make a connection to an Open Source project like Octave instead ? Incidently I tried this the other day. Actually I tried to connect to SciLab's Simulink clone Scicos. Of course my first effort failed, but I will try again. I wanted to make an automatic control system in Scicos. I've done this with Matlab, back in university, with a physical helicopterish model. I think that Flightgear has all the functionality to connect to other programs, see README.IO. It is at the other end that work needs to be done. -- Roy Vegard Ovesen ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Nimitz
On Tuesday 22 March 2005 05:20, Arnt Karlsen wrote: On Mon, 21 Mar 2005 21:05:28 -0500, MCVAY wrote in message [EMAIL PROTECTED]: Thanks Mathias: I think I'm getting there. Could you just talk me through how to comment out the nimitz_demo scenerio. I found nimitz_demo, tried a few things with it, but it won't let me proceed any further. Thanks for your patience! Doug I think that Mathias meant to _un_ comment out the nimitz_demo scenario. It's already commented out, and you need to remove the comment tags in $FG_ROOT/preferences.xml ..anything behind a # is a comment. To comment it out, do Comments in xml start with a !-- and end with a -- , _not_ #. -- Roy Vegard Ovesen ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Dated Docs
On Saturday 26 February 2005 08:01, Paul Surgeon wrote: Now what you don't have is the original source of the getting started guide which means you can either copy the text and images out of it and reformat it in your favourite editor before exporting it again or we can try get hold of the author. The latex sources for the Installation and Getting Started manual is located here: http://cvs.flightgear.org/cgi-bin/viewcvs/viewcvs.cgi/docs/getstart/source/?cvsroot=FlightGear-0.9 If we look in the CVS logs we find that it was created by someone called j4strngs j4strngs is the username of the user that committed the file to the CVS repository, and not necessarily name of the author of the file. BTW the primary authors are Michael Basler and Martin Spott. -- Roy Vegard Ovesen ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] setting a new starting airfield
On Tuesday 08 February 2005 00:47, Richard Keech wrote: How do I determine (short of first principles or using TerraGear) which scenery set I need for particular airports? I find that using terrasync is a great way to get the scenery for a particular airport. It downloads scenery on the fly (pun intended). Execute this alongside FlightGear: nice terrasync -p 5500 -s scenery.flightgear.org::Scenery -d Scenery The -d option tells what directory the scenery should be downloaded to. I'd recommend to set this to some directory in your homedir. This directory has to be added to FG_SCENERY, and FlightGear has to output it's position on port 5500 with this option: --atlas=socket,out,1,localhost,5500,udp When you start at an airport that you haven't got any scenery for yet you _will_ end up in the middle of the ocean the first time. Terragear should start to download the new scenery, wait for it to finish, quit FlightGear, and restart at the same airport. The scenery should now be there. There is a readme in source/utils/TerraSync/README.txt Why do I have to specify a runway when I specify a new airport; don't airports have a default runway? In preferences.xml the default runway is 28R on KSFO. When you specify a different airport you override the default airport with the --airport option. If you don't also override the default runway with the --runway option, runway 28R (from preferences.xml) will be used, but of course the new airport that you chose may or may not have a runway 28R. -- Roy Vegard Ovesen ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Airplanes
On Tuesday 04 January 2005 10:43, Frank Olaf wrote: Is there somewhere from where one may download aircrafts? It seems from the changelogs that aircrafts that I can't find have been updated. I'm using 0.9.6 in WinXP and I can't find f.ex the concorde which apparently should be there. I think I'm missing several other aircrafts to :( Anyone got any ideas? See this recent thread in the Devel list: http://baron.flightgear.org/pipermail/flightgear-devel/2005-January/033276.html I don't think you can download any of the aircraft on the list yet. I guess they will become downloadable after the release of version 0.9.8. It is possible to download tarballs of aircraft from CVS. Go to: http://cvs.flightgear.org/cgi-bin/viewcvs/viewcvs.cgi/data/Aircraft/?cvsroot=FlightGear-0.9 Browse to the aircraft you want to download, at the bottom there is a Download tarball link. Warning: If you are using 0.9.6 then probably all of these aircraft won't work properly because of changes (radios and radio gauges) in the source. I suggest that you wait until 0.9.8 is released, it should be right around the corner. -- Roy Vegard Ovesen ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Scenery concerns
On Tuesday 28 December 2004 14:35, Frank Olaf wrote: To where should I direct concerns about the scenery? There is quite a large portion of scenery near my home which is terribly incorrect. From N60.50 to N61.00, E11 there is a large strip running east and west with apparently no elevation data. This is true for the entire globe. The reason for this is that FlightGear gets terrain elevation data from the SRTM: http://www2.jpl.nasa.gov/srtm/ They only mapped between N60 and S60. That leaves out most of Norway flat. :-( -- Roy Vegard Ovesen ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Mouse sensitivity
On Friday 24 December 2004 04:58, [EMAIL PROTECTED] wrote: Is there some way to set the mouse sensitivity in flightgear? I have to fly by mouse and the thing is so sensitive that moving one dot across the screen sends it one way and a dot the other way of course, sends it the other way. is there no happy medium? Open the mouse config file (data/mice.xml), starting at line 90 you will see the mouse binding to the aileron control. You will see that it has a factor tag, probably set to 4.0. Set this to a lower value if you feel that your mouse is too sensitive. Further down the file you will find bindings for the other control surfaces where you can set their sensivities with the factor tag. -- Roy Vegard Ovesen ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Still haven't found what I need, more on readios :)
On Thursday 23 December 2004 10:47, Thomas Förster wrote: The format is relatively easy. Every line contains an airway segment. The first 3 values per line are the data for the starting fix (name, lat, lon). The next 3 the same for the endpoint fix. I'm not completely sure about the last 4 columns in the file. The last one is most probably the name of the airway. The seventh seems to be some kind of classification with values 1 or 2 (High/Low Enroute?). The other two being heading(?) and flight level(?) Can anyone confirm this? I guess Robin Peel can confirm ;-) http://x-plane.org/home/robinp/AptNavFAQ.htm#awy.dat -- Roy Vegard Ovesen ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Still haven't found what I need, more on readios :)
On Wednesday 22 December 2004 22:00, Chris Metzler wrote: On Wed, 22 Dec 2004 22:22:58 +0200 Paul Surgeon wrote: I really feel that FG should have a built in flight planner of some sort. All the basic navaid data is already in FG we just need some way of displaying it. Well, Atlas can be used for displaying it, as Melchior noted. But as for a real planning tool . . .various well-meaning folks have commented on this before, and even declared that they were going to build such a tool; but it's never happened. I agree that it'd be a cool thing to have. Actually there exists a flight planning tool for FlightGear: http://sourceforge.net/projects/fgflightplanner/ It's written in Java, so I guess it should be platform independent. I have only tried it on Suse 9.1. -- Roy Vegard Ovesen ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Still haven't found what I need, more on readios :)
On Wednesday 22 December 2004 22:43, David Megginson wrote: On Wed, 22 Dec 2004 22:22:58 +0200, Paul Surgeon [EMAIL PROTECTED] wrote: I really feel that FG should have a built in flight planner of some sort. All the basic navaid data is already in FG we just need some way of displaying What's not in FlightGear, like the actual airways, is in the DAFIF (as long as it lasts). There is the data/Navaids/awy.dat.gz file that I guess contains the airways. AFAIK it's not used by FlightGear, but it could of course be used by Atlas. -- Roy Vegard Ovesen ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Instrument Panel development tools?
On Tuesday 21 December 2004 01:47, Curtis L. Olson wrote: For visualization while you work try hitting F3 (or is it shift-F3?) One of those reloads the panel, and the other takes a screen shot, I always forget which is which. But that let's you work on your panel and see the results immediately in a live running copy of FG. This only works for 2d panels. And it does not work for a 2d panel included in the 3d model, like the default C172. -- Roy Vegard Ovesen ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] C172P panel now hacked
On Sunday 19 December 2004 02:12, Dave Martin wrote: Just another thought on that; I've been reworking the 172P model so that the polygon count stays low at all distances (its the default model so high quality / polys may = bad thing for users with low-end systems). However, I do like the idea of making a very high quality C172 for use by people who do have the hardware to deal with it. This could be a totally seperate model with 'all the trimmings' :) There are some beautiful instruments that you might want to use for this high quality version, they are named *172S*.xml. Interestingly, I may have stumbled over a 'hack' for 3d cockpit illumination at night but I haven't tested out the idea yet. Take a look at the compass in the Instruments-3d directory. It's completely 3d and it's illuminated at night. This is done by using emissive (white) color. You could of course use any color you like -- Roy Vegard Ovesen ___ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] [from AVSIM] Config file parseerror: C:/ProgramFiles/FlightGear/data/system.fgfsrc '--prop: encountered in XP
On Sunday 12 December 2004 14:55, Paul Surgeon wrote: I'll bet tho that it would increase the incidence of people moaning that the aircraft is 'broken' and 'always pulling to the left'. I'm not sure I understand what you mean. Are you suggesting we should prevent people from using single engine aircraft all together? Why not just remove the 172, PA-28, etc from FG and be done with it? I think he means that if FlightGear was easier to get started, then more noobs would be able to, and consequently more noobs would complain about always pulling to the left. If I'm right, then I think he is generalizing a bit: It looks like if a person is a noob, then he/she doesn't know what a command line is _and_ he/she doesn't know how an aircraft is supposed to behave, and in addition he/she is probably ignorant to a lot of other things. One might say that he/she is noob all over. On the other hand we have persons that do know what a command line is. Obviously he/she who knows what a command line is also knows how an aircraft behaves, right. ;-) M$FS has realism sliders that affect aircraft handling and they are set to noob by default. It works just fine and I don't see why we can't do the same. I guess that we don't do the same because we don't want to do that. -- Roy Vegard Ovesen ___ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] NASA Worldwind
On Wednesday 08 December 2004 21:02, Paul Surgeon wrote: Just out of interest has anyone ever done a poll to find out who uses what OS for FG? It would be interesting and possibly useful info to see what OS's are the most popular for FG especially amongst the developer community. I use Suse Linux 9.1. I used Cygwin earlier. -- Roy Vegard Ovesen ___ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] NASA Worldwind
On Thursday 09 December 2004 20:19, Lee Elliott wrote: BTW, is everyone who posts to this list still getting spammed by [EMAIL PROTECTED] I am and it's a real pita. Yes, me too! -- Roy Vegard Ovesen ___ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] NASA Worldwind
On Thursday 14 October 2004 08:19, Chris Ridley wrote: Found a very interesting program at http://learn.arc.nasa.gov/worldwind I've been playing around with World Wind, and I think that it would be possible to use it as a moving map display for FlightGear (just like Atlas). I tried to averlay a few NDB symbols onto the globe, and it worked great. I guess I should make some kind of script to parse the files in navaid and convert to World Wind's xml format. -- Roy Vegard Ovesen ___ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Re: glide
On Friday 19 November 2004 01:14, Nick Coleman wrote: I don't have the scenery for there, but if I tune in 110.3 I get a working glide slope and localizer indication. This is using v0.9.6. I just tried this airport, and I also got what seemed to be a working glide slope and localizer indication. But when I tried to hold a backcourse (REV mode on the KAP140) I noticed that the CDI needle was deflecting in the wrong direction. I turned the autopilot to HDG mode to manually intercept the localizer. Still the needle was deflecting in the wrong direction. As I approached the runway the glide slope needle showed that I was below the glide slope, but the glide slope lights beside the runway clearly showed that I was above (4 white lights). Obviously the glide slope needle was wrong too. I immediately suspected that this has something to do with the fact that the airport SBKP is located below the equator. Has anyone else experienced this problem with other airports in the southern hemisphere? -- Roy Vegard Ovesen ___ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Re: glide
On Friday 19 November 2004 11:34, Roy Vegard Ovesen wrote: On Friday 19 November 2004 01:14, Nick Coleman wrote: I don't have the scenery for there, but if I tune in 110.3 I get a working glide slope and localizer indication. This is using v0.9.6. I just tried this airport, and I also got what seemed to be a working glide slope and localizer indication. But when I tried to hold a backcourse (REV mode on the KAP140) I noticed that the CDI needle was deflecting in the wrong direction. Oops! I was approaching runway 33. It seems that the ILS on 110.30 is for runway 15, cause when I approached that one it all worked perfectly. ;-) So, please disregard the rest of my foul analysis! :-( I turned the autopilot to HDG mode to manually intercept the localizer. Still the needle was deflecting in the wrong direction. As I approached the runway the glide slope needle showed that I was below the glide slope, but the glide slope lights beside the runway clearly showed that I was above (4 white lights). Obviously the glide slope needle was wrong too. I immediately suspected that this has something to do with the fact that the airport SBKP is located below the equator. Has anyone else experienced this problem with other airports in the southern hemisphere? -- Roy Vegard Ovesen ___ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Re: Error in CVS build (adf.cxx)
On Thursday 11 November 2004 15:41, Mr Michael Rawlins wrote: Now about the autopilot. I'm sticking with the c172r for now. ctrl-C highlights the active selections on the panel, and all work except for the AP: Nasal runtime error: undefined symbol at command, line 2 Failed to execute command nasal When you are using the latest CVS version, you generally also have to have the latest CVS version of the base package (the data directory). To checkout the CVS version of the base package do: cvs -d :pserver:[EMAIL PROTECTED]:/var/cvs/FlightGear-0.9 login CVS passwd: guest cvs -d :pserver:[EMAIL PROTECTED]:/var/cvs/FlightGear-0.9 co data You also have to make sure that you point to this new directory when you run fgfs. The autopilot in the c172 should then work. If you are not familiar with the KAP140 autopilot I advise you to read the pilot's guide available from the Bendix/King website. A link to it was posted on the user list not too long ago. -- Roy Vegard Ovesen ___ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Re: Error in CVS build (adf.cxx)
On Thursday 11 November 2004 18:14, Mr Michael Rawlins wrote: Thanks Roy. I've updated the data directory, and had grabbed the KAP140 manual last week. But am still unable to turn on autopilot with left mouse click on AP. All other functions on the panel work with left mouse click. You said you get something about not finding a nasal function at line 2, so the the autopilot xml instrument configuration is working, it just cant find the nasal function that it is tied to. This nasal function is in data/Aircraft/c172p/kap140.nas, this file gets included by data/Aircraft/c172p/c172p-set.xml. Can you verify that kap140.nas is in the c172p directory. It used to be in data/Nasal, but it's not supposed to be there! Did you say you used the c172r?! I'm pretty sure you have to use the c172p for the kap140.nas file to be included and the autopilot to work. If you start FlightGear without specifying any aircraft you get the default c172p, and the autopilot should definetly work there. This is in my .fgfsrc --fg-root=/usr/local/FlightGear-0.9/data/ Are you absolutely, 100%, positively sure that this is the directory that you just updated to latest CVS? It looks like a typical place where make install would place the data files. I don't do make install, because I update from CVS all the time, I keep it all in my home directory. For the past few months I've used the autopilot menu at top of FG screen, which I've read is not the way to go. Well for aircraft that don't have a custom/explicit autopilot configuration, the menu _is_ the way to go. Unfortunately the majority of aircraft don't have a custom configuration, so they fall back to the generic. -- Roy Vegard Ovesen ___ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] KAP-140 Autopilot
On Monday 08 November 2004 02:18, Nick Coleman wrote: Congrats to the developer, it seems to be very accurately modelled and behaves just like the manual says it should. Well, almost. The REV mode behaves slightly different from what the manual says. In REV mode you have to set the but to the inbound heading, not the outbound heading. Or was it the other way around? I forget. At least it is the opposite of what the manual says! Have you got the latest version from CVS? It includes the altitude preselect feature. I'm always happy to receive feedback if anything is not working as it should. -- Roy Vegard Ovesen ___ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Error on ./configure (FDM/SP/Maikefile.in)
On Saturday 06 November 2004 11:49, Adam Cripps wrote: Been a while since I last compiled from CVS on my debian unstable system. Getting this error on ./configure: config.status: error: cannot find input file: src/FDM/SP/Makefile.in Any ideas of how to get round this? It looks like you forgot to do ./autogen.sh first. -- Roy Vegard Ovesen ___ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Data visualization tool
On Saturday 02 October 2004 05:04 pm, Arnt Karlsen wrote: ..gnuplot? Oughtta be available with Cygwin too. I threw together a bash script some time ago that used gnuplot to plot the tail of a FlightGear log file. It worked in real-time, but the main problem was that it was so CPU intensive that FlightGear suffered. Now I wanted to make something in Python, and I found an extremely simple module called tkplot.py. I made a simple Python program that reads FlightGear properties through telnet. It works quite well. I've only plotted one property (/velocities/airspeed-kt) so far, but I guess it would be quite easy to plot more in the same window. Here is a screen-shot: http://home.tiscali.no/rvovesen/plot.png tkplot.py can be downloaded from here: http://bonsai.ims.u-tokyo.ac.jp/~mdehoon/software/python Got to the bottom of the page! -- Roy Vegard Ovesen ___ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] How to reload 3d panel
On Wednesday 29 September 2004 08:41 pm, Horst J. Wobig wrote: Anyway... panel reload does not work for me - what am I doing wrong? AFAIK the panel reload only reloads the 2d panel. The 3d panel I believe is part of the 3d aircraft model. The 3d panel of the defaut Cessna is actually a 2d panel that is pasted into the 3d aircraft model. I think that reloading of the 3d aircraft model, and thus the 3d cockpit, would be a useful feature for aircraft creators. -- Roy Vegard Ovesen ___ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] KAP140 two-axis in NAV mode
On Saturday 25 September 2004 12:14 pm, Horst J. Wobig wrote: Hello, I very much appreciate the work that has been done for the KAP140 (by Roy I think). I also downloaded the pilot's guide but I still wonder how it should work in NAV mode when flying *over* the station beeing tracked. I'm *not* talking about *intercepting* when close to a station. I'm talking about beeing on track for some time until coming close to the station and ultimately flying over it. As currently simulated, the AP tries tracking - but of course can't when that close. How does the real thing handle this? I would like to know that too! So that I can simulate it propertly. I'm not a pilot and have never seen a real KAP140. Maybe that's obvious for everybody but me... I do have a suggestion about how it could be done: When the aircraft is within a certain range to the VOR, switch to heading hold mode, or even wings level mode. Fly straight over, and switch back to NAV mode when outside the same certain range. That was easy ;-) Only problem is that the KAP140 doesn't know the range to the VOR station. So this will not work after all. Maybe it could detect that it can't track the VOR, but how would we distinguish a loss of track caused by wind or turbulence from loss of track due to close range? I guess I really don't know how to fix this, if it indeed needs to be fixed. Maybe the real KAP140 only has a better controller and is thus able to track over the VOR station. BTW I'm currently working on the with altitude preselect part of the KAP140, and would like to submit it to CVS when complete. If you are interested I could put up a link to the current work in progress. -- Roy Vegard Ovesen ___ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
