Thread: [Opengc-devel] nav display?
Status: Pre-Alpha
Brought to you by:
madmartigan
From: Wendell T. <we...@ad...> - 2003-08-29 17:10:54
|
What is the name of the nav display (HSI) shown on the home web page? I get blank screens when I load Boeing737NAV. What files should be in the 'NAV DATABASE PATH'? Should this point to the directory with the apt.dat, etc. files? Or one above it? If there is no nav data to read, or no connection to flightgear, will that result in a blank screen for the nav display? That is, does the nav display need a valid position from the flight sim? Wendell |
From: John W. <ca...@mm...> - 2003-08-29 18:40:46
|
Hi, I've not kept up with the latest CVS version, so I'm not sure which version you are running. If you are running an "older" version perhaps I could help, if you'r running the latest then Damion... Again, I've not looked at the latest CVS source, but I think Damion was creating a generic nav display whereas the earlier version was specific. The earlier version should work (i.e., load and display irrespective of nav data since there were default values for LAX). But data or a connection is NOT required to bring up the display (at least not in the earlier version) If you are running flightgear, I might note there has not been an update to the FG/OpenGC interface in some time Regards JW ----- Original Message ----- From: "Wendell Turner" <we...@ad...> To: <ope...@li...> Sent: Friday, August 29, 2003 10:10 AM Subject: [Opengc-devel] nav display? > What is the name of the nav display (HSI) shown on the home web > page? I get blank screens when I load Boeing737NAV. > > What files should be in the 'NAV DATABASE PATH'? Should this > point to the directory with the apt.dat, etc. files? Or one > above it? > > If there is no nav data to read, or no connection to flightgear, > will that result in a blank screen for the nav display? That > is, does the nav display need a valid position from the flight > sim? > > Wendell > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Opengc-devel mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opengc-devel |
From: Wendell T. <we...@ad...> - 2003-08-29 18:56:24
|
On Fri, Aug 29, 2003 at 11:39:21AM -0700, John Wojnaroski wrote: > I've not kept up with the latest CVS version, so I'm not sure which version > you are running. The cvs version. As I'm on a Linux platform, I only have access to CVS; there don't seem to be older tar files around. > Again, I've not looked at the latest CVS source, but I think Damion was > creating a generic nav display whereas the earlier version was specific. I don't really care which version, just any nav/hsi display would be nice. > The earlier version should work (i.e., load and display irrespective of nav > data since there were default values for LAX). But data or a connection is > NOT required to bring up the display (at least not in the earlier version) Ok, thanks for that piece of information. > If you are running flightgear, I might note there has not been an update to > the FG/OpenGC interface in some time The other displays (pfd) seem to work fine, so I have no reason to doubt that interface. Wendell |
From: John W. <ca...@mm...> - 2003-08-29 20:20:55
|
If you go to the website, you'll see some screenshots. the latest show the generic display, go down (back) a few pages and you'll see some earlier (circa Feb 02) shots of the PFD/ND and PFD/EICAS. Sorry, I don't have the latest CVS (I've been quite busy this year and not kept up with the development) but perhaps that code is still there and you might have to edit the make files to compile. As I recall, an entry in opengc.ini not supported by the code is simply ignored which might account for the blank screen Hope this helps. Regards JW ----- Original Message ----- From: "Wendell Turner" <we...@ad...> To: <ope...@li...> Sent: Friday, August 29, 2003 11:56 AM Subject: Re: [Opengc-devel] nav display? > On Fri, Aug 29, 2003 at 11:39:21AM -0700, John Wojnaroski wrote: > > I've not kept up with the latest CVS version, so I'm not sure which version > > you are running. > > The cvs version. As I'm on a Linux platform, I only have access > to CVS; there don't seem to be older tar files around. > > > Again, I've not looked at the latest CVS source, but I think Damion was > > creating a generic nav display whereas the earlier version was specific. > > I don't really care which version, just any nav/hsi display > would be nice. > > > The earlier version should work (i.e., load and display irrespective of nav > > data since there were default values for LAX). But data or a connection is > > NOT required to bring up the display (at least not in the earlier version) > > Ok, thanks for that piece of information. > > > If you are running flightgear, I might note there has not been an update to > > the FG/OpenGC interface in some time > > The other displays (pfd) seem to work fine, so I have no reason > to doubt that interface. > > Wendell > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Opengc-devel mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opengc-devel |
From: Damion S. <be...@cs...> - 2003-08-29 20:06:03
|
> What is the name of the nav display (HSI) shown on the home web > page? I get blank screens when I load Boeing737NAV. Sorry for the confusion... the name of the gauge is: NavTestGauge (note case sensitivity). The current incarnation of this gauge only loads airports and some classes of VOR's, and is best used in latitudes below 60 degrees n/s because of the Mercator projection. I'm working on a new map projection system but it's not finished yet. Boeing737NAV used a bunch of code that was incomplete (the original developers disappeared) so I should remove any references to it from the .ini file. > What files should be in the 'NAV DATABASE PATH'? Should this > point to the directory with the apt.dat, etc. files? Or one > above it? It should point to the .dat files - I should clarify this in the documentation. > If there is no nav data to read, or no connection to flightgear, > will that result in a blank screen for the nav display? That > is, does the nav display need a valid position from the flight > sim? If there is no nav data to read, I believe this results in OpenGC aborting (I haven't tried that error case in a while). If it does not receive a network comm from flightgear or another sim, the gauge will display but remain static. Hope this helps, any other questions please let me know. Cheers, -Damion- --------- Damion Shelton Carnegie Mellon University, Robotics Institute A408-o Newell Simon Hall 412.268.3866 (office) 412.818.8829 (cell) 412.268.6436 (fax) http://www.cs.cmu.edu/~beowulf --------- We tend to scoff at the beliefs of the ancients. But we can't scoff at them personally, to their faces, and this is what annoys me. |
From: Wendell T. <we...@ad...> - 2003-08-29 20:35:46
|
On Fri, Aug 29, 2003 at 04:05:57PM -0400, Damion Shelton wrote: > > What is the name of the nav display (HSI) shown on the home web > > page? I get blank screens when I load Boeing737NAV. > > Sorry for the confusion... the name of the gauge is: NavTestGauge (note > case sensitivity). Thank you, that one looks nice. > I'm working on a new map projection system but it's not > finished yet. This one is fine. > > What files should be in the 'NAV DATABASE PATH'? Should this > > point to the directory with the apt.dat, etc. files? Or one > > above it? > > It should point to the .dat files - I should clarify this in the > documentation. Oops, the 'NAV DATABASE PATH' must end in a '/'. My mistake. > If there is no nav data to read, I believe this results in OpenGC > aborting (I haven't tried that error case in a while). It just reports 'The navaid list contains 0 items' and continues. > Hope this helps, any other questions please let me know. Yes, and thank you for your hard work. Wendell |