Re: [Flightgear-devel] fg_sqawk Version 0.2beta
Jon, first of all: thanks for testing! There were some problems with the conference system and I fixed them yesterday (thanks Martin!). On Sat, Feb 17, 2007 at 10:22:56PM +, Jon Stockill wrote: [...] > I've just been trying to get this running, but have run into a few > problems. iaxcli seems to be linked against a shared libgsm, I've > tracked down libgsm and the currently distributed source only builds > static libraries, not shared. Do you have a definitive list of the > dependencies? It looks like an extremely useful piece of software, and > I'd love to help test it. I am not sure if I made a static or a dynamic binary of iaxcli... I will fix this soon. Until the fix is on the web you can try to compile iaxcli by yourself. It should be easy if you have libiaxclient, libspeex and libgsm installed. On Debian you only need to do $ apt-get install perl libexpect-perl libcompress-zlib-perl libiaxclient-dev libspeex-dev libgsm1-dev flightgear (Perhaps you have already some of the packages... feel free to install what you like :-) ) Or go to the folowings sites to get the sources for the library: - http://ftp.digium.com/pub/libiax/ - http://www.speex.org/downloads/ - libgsm... hm, sorry I cannot find any sites for this lib :-( Regards, Holger -- # ## ## Holger Wirtz Phone : (+49 30) 884299-40 ## ## ## ### ## DFN-Verein Fax : (+49 30) 884299-70 ## ## ## Stresemannstr. 78E-Mail: [EMAIL PROTECTED] ## ## ## ## ### 10963 Berlin # ## ## ## GERMANY WWW : http://www.dfn.de GPG-Fingerprint: ABFA 1F51 DD8D 503C 85DC 0C51 E961 79E2 6685 9BCF - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] altimetry method ... alpha version
On Sun, 2007-02-18 at 12:22 -0500, John Denker wrote: > On 02/12/2007 08:43 PM, Dave Perry wrote: > > > What I am proposing is to create a C++ function (say height_ft) that has > > two arguments, P0 and P1 that does the interpolation in John's new patch > > using his constants. > > > > Then the kap140.nas could use that function, the encoder could use that > > function to compute PA and the altimeter > > Those who are interested may try out the alpha version of > the FGaltimeter::reading_ft(,) feature in: > >http://www.av8n.com/fly/fgfs/atmo.diff > > The interface to this feature is about as simple as it could > possibly be. In Instrumentation/altimeter.cxx we find only > the following three lines: > > 1) Grab the definitions > #include > 2) Instantiate the object (once, at startup time): > FGaltimeter _altimeter; > 3) Ask for the altimeter reading: > _altimeter.reading_ft(pressure, setting) > > This is implemented as a class rather than as a plain-old > function, so that it can build and use an interpolation > table. > > This altimetry method is valid to above 100,000 feet, and > correctly handles Kollsman settings (unlike the altimeter > instrument in the current and previous cvs versions). > > > Notes: > > 1) I did say this an _alpha_ feature, right? That means > a) Now is a particularly timely time to make suggestions. > b) There is even less warranty than the usual "no warranty" >and there are no promises of stability. I can't presently >think of any reason to change the FGaltimeter::reading_ft(,) >interface, but no promises are being made. Thanks John, Just made the changes in your new patch to a copy of cvs source and all compiled and ran OK. I was running a version of your prior patch that was also good to 100K ft. I am not sure the new patch is giving the same results, but I have not done any controlled comparisons; just one flight from 2V2 (now KLMO) to KBJC with real metar weather. The QNH was 29.71 and later 29.70 as I approached KBJC. The field elevation with the altimeter kollsman setting correct was about 60 ft low. I will double check and compare some examples with the previous patch. > 2) You may notice the files contain quite a bit of additional > functionality beyond the FGaltimeter::reading_ft(,) feature, > but it is pre-alpha. That means >a) Play if you dare. >b) Comments are welcome. >c) I /know/ some of it is going to change. > > If you want to play with member functions in the FGatmobase > class, it suffices to call them using an anonymous temporary > instance, as in: > FGatmobase().qnh(elev, Pfield); > Looking at FGaltimeter, the following calls allow separating PA and C. If I want just the PA as in the encoder, the assign would be pressureAltitude_ft = _altimeter.reading_ft(pressure, 29.92); and if I want just the kollsman offset as in kap140.nas kollsman_shift_ft = _altimeter.reading_ft(setting, 29.92); Again, tomorrow, I will do some more comparisons and feed the results back. Thanks for staying with this. -- Dave Perry - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] cool flight sim....
Thought this might interest someone... in my own town too, and i didn't even know it ! http://www.docscomputers.com/ Cheers, Syd - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] fg_sqawk Version 0.2beta
Holger Wirtz wrote: > > My current VoIP-Implementation (=Asterisk) hast all north american radio > frequencies as a conference room so there _are_ may ATIS frequencies and > not just 118.85 :-) 118.85 is the frequency by default if I press the > change button on COM1... so if I find a way to supress ATIS in FG I can > play my "own" ATIS when conecting to 118.85. > > >> Certainly we need a better ATIS function, but moving to /no/ >> ATIS function would be a step in the wrong direction. >> > > No, I think you have misunderstand (perhaps my english is not good > enough - sorry). ATIS in FG is ok - but not in multiplayer mode with realtime > radio. > It's no problem to allow ATIS to be turned off. I haven't had a working self-compiled build since the OSG switch so can't look at the moment, but does fgfs --disable-atc exist, and if so does it disable the ATIS? If not, it could be made to, or an extra --disable-atis option could be added. What I originally assumed, was that when a real-time voice server became available, only some channels would be manned be real people (due to logistics) and that the server would communicate in some manner to each FG instance that connected to it which stations would be handled by the server and which would be handled by FG. Does that still sound reasonable, or am I misunderstanding what you've done? Cheers - Dave - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Which OSG?
Hi, Martin Spott wrote: Ron Jensen wrote: As of last Tuesday CVS OSG is required: If you don't want to use CVS then this tarball is supposed to do it for you: ftp://ftp.ihg.uni-duisburg.de/FlightGear/Misc_maf/OpenSceneGraph-20070122/OSG_OP_OT-CVS20070122.tar.bz2 Thanks a bunch. This did it for me, even though I had a link time failure with OSG because it was trying to link some tool against /usr/local/lib instead of against the ones it had just built. I solved it by doing a make install, then make again (clean this time), and another make install. Martin. Cheers Lou - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FG IVAO client
Pep Ribal wrote: > The problem is that I want to start developing the GUI, but honestly I'm > a bit lost and overwhelmed. I don't know which toolkit I should use. > I've been looking at FLTK and GTK+, but I'm not sure they are the right > tools to use. While they would be nice for the standard forms > (flightplan and so on), I'm not sure I can use them for the main > "window" (the picture I'm attaching). > > As I'm in a learning process, I prefer to start learning the right tool, > so this is my question: what's your advice? How should I start with the > interface? FLTK? GTK+? SDL? OSG? etc.? > > Bear in mind that whatever you use wants to be as cross platform as possible. Both FLTK and wxWidgets have been successfully used in cross platform FG related applications (FGSD and TaxiDraw respectively), and would both probably do what you want. I would however second Martin's advice about getting the core to work without GUI being the best way to start. Cheers - Dave - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] New Instruments-3d/kap140 for CVS
Hi all, I've finished (I hope) a 3D Kap-140 head. Its at http://www.jentronics.com/fgfs/kap140.tgz If someone could commit it to CVS? Thanks, Ron The head uses the traditional left/right click squares on the setting knob. It also uses a much cooler mouse-wheel click: - Point to the inner knob, scroll the wheel up and down for small steps - Point to the outer knob, scroll the wheel up and down for large steps - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] altimetry method ... alpha version
On 02/12/2007 08:43 PM, Dave Perry wrote: > What I am proposing is to create a C++ function (say height_ft) that has > two arguments, P0 and P1 that does the interpolation in John's new patch > using his constants. > > Then the kap140.nas could use that function, the encoder could use that > function to compute PA and the altimeter Those who are interested may try out the alpha version of the FGaltimeter::reading_ft(,) feature in: http://www.av8n.com/fly/fgfs/atmo.diff The interface to this feature is about as simple as it could possibly be. In Instrumentation/altimeter.cxx we find only the following three lines: 1) Grab the definitions #include 2) Instantiate the object (once, at startup time): FGaltimeter _altimeter; 3) Ask for the altimeter reading: _altimeter.reading_ft(pressure, setting) This is implemented as a class rather than as a plain-old function, so that it can build and use an interpolation table. This altimetry method is valid to above 100,000 feet, and correctly handles Kollsman settings (unlike the altimeter instrument in the current and previous cvs versions). Notes: 1) I did say this an _alpha_ feature, right? That means a) Now is a particularly timely time to make suggestions. b) There is even less warranty than the usual "no warranty" and there are no promises of stability. I can't presently think of any reason to change the FGaltimeter::reading_ft(,) interface, but no promises are being made. 2) You may notice the files contain quite a bit of additional functionality beyond the FGaltimeter::reading_ft(,) feature, but it is pre-alpha. That means a) Play if you dare. b) Comments are welcome. c) I /know/ some of it is going to change. If you want to play with member functions in the FGatmobase class, it suffices to call them using an anonymous temporary instance, as in: FGatmobase().qnh(elev, Pfield); - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel