Re: [Flightgear-devel] Get nearest Airport : Not Working

2005-07-26 Thread Gerard Robin
Le lundi 25 juillet 2005 à 23:55 +0200, Gerard Robin a écrit :
 Le lundi 25 juillet 2005 à 23:02 +0200, Roy Vegard Ovesen a écrit :
 
  AFAICT there hasn't been any significant changes to 
  Instrumentation/gps..*xx or 
  Airports/simple.*xx. There has been alot of improvements to the gui system 
  lately, so maybe my dialog has become broken. Could you try to trigger the 
  Get Nearest Airport from the property browser? Go to 
  /instrumentation/gps/wp/wp[1] and set get-nearest-airport to true. I'm 
  not able to run FG right now because of some freeglut issue (I believe) so 
  I 
  can't test this myself :-(
  
 sorry
 It has not any effect. We get nothing :=(
 Looking at the guy dialog it is the old usual nasal command. it should
 work.

I am not fully sure, 
but it is probably coming from an old update, because every July CVS
releases does not work (i keep it).
BTW: Isn't it any relationship with electrics modifications ? (turn
indicator not working, gps may be)

-- 
Gerard


___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] Get nearest Airport : Not Working

2005-07-26 Thread Gerard Robin
Le mardi 26 juillet 2005 à 17:04 +0200, Roy Vegard Ovesen a écrit :
 On Tuesday 26 July 2005 15:16, Gerard Robin wrote:
  I am not fully sure,
  but it is probably coming from an old update, because every July CVS
  releases does not work (i keep it).
 
 ??? Do you keep every July CVS release for the past couple of years?
 Have none of your CVS updates this July worked for you?

Ouaf Ouaf 
I am not enough crazy to keep only every old times July from every
years :=

 
  BTW: Isn't it any relationship with electrics modifications ? (turn
  indicator not working, gps may be)
 
 That could be the cause. If you again use the property browser to look at 
 /instrumentation/gps/***. Here you should see longitude and latitude values 
 changing as you move. If not then the gps might not be getting power.
 

We get nothing but Zero in /instrumentation/gps/***
Who is able to tell what must be done to solve it ?


-- 
Gerard


___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] Get nearest Airport : Not Working

2005-07-26 Thread Gerard Robin
Le mardi 26 juillet 2005 à 18:05 +0200, Gerard Robin a écrit :
 Le mardi 26 juillet 2005 à 17:04 +0200, Roy Vegard Ovesen a écrit :
  On Tuesday 26 July 2005 15:16, Gerard Robin wrote:
   I am not fully sure,
   but it is probably coming from an old update, because every July CVS
   releases does not work (i keep it).
  
  ??? Do you keep every July CVS release for the past couple of years?
  Have none of your CVS updates this July worked for you?
 
 Ouaf Ouaf 
 I am not enough crazy to keep only every old times July from every
 years :=
 
  
   BTW: Isn't it any relationship with electrics modifications ? (turn
   indicator not working, gps may be)
  
  That could be the cause. If you again use the property browser to look at 
  /instrumentation/gps/***. Here you should see longitude and latitude 
  values 
  changing as you move. If not then the gps might not be getting power.
  
 
 We get nothing but Zero in /instrumentation/gps/***
 Who is able to tell what must be done to solve it ?
 
Hi Roy
I have got the answer the electrical nasal file must include the short
term patch 28 = 60 ideal volts with rpm_source : /engines/engine
[0]/rpm

you suggested it before  about turn indicator 

 
-- 
Gerard


___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] Get nearest Airport : Not Working

2005-07-26 Thread Roy Vegard Ovesen
On Tuesday 26 July 2005 18:25, Gerard Robin wrote:
 Hi Roy
 I have got the answer the electrical nasal file must include the short
 term patch 28 = 60 ideal volts with rpm_source : /engines/engine
 [0]/rpm

In theory this hould not make any dfference because the gps is not as 
demanding as the turn indicator. The gps should work with any electrical 
input larger than 0. So it should work just as well on 28 as on 60. But hey, 
if you say it's working now, then who am I to dispute that? ;-)

-- 
Roy Vegard Ovesen

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] Get nearest Airport : Not Working

2005-07-26 Thread Gerard Robin
Le mardi 26 juillet 2005 à 18:45 +0200, Roy Vegard Ovesen a écrit :
 On Tuesday 26 July 2005 18:25, Gerard Robin wrote:
  Hi Roy
  I have got the answer the electrical nasal file must include the short
  term patch 28 = 60 ideal volts with rpm_source : /engines/engine
  [0]/rpm
 
 In theory this hould not make any dfference because the gps is not as 
 demanding as the turn indicator. The gps should work with any electrical 
 input larger than 0. So it should work just as well on 28 as on 60. But hey, 
 if you say it's working now, then who am I to dispute that? ;-)
 

You should be right. On my side i don't understand as well.
The fact is 28 - not working   60 - working.
When your FG will be on, you will probably give a good explaination.

-- 
Gerard


___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] Get nearest Airport : Not Working

2005-07-26 Thread Gerard Robin

  In theory this hould not make any dfference because the gps is not as 
  demanding as the turn indicator. The gps should work with any electrical 
  input larger than 0. So it should work just as well on 28 as on 60. But 
  hey, 
  if you say it's working now, then who am I to dispute that? ;-)
  
 
 You should be right. On my side i don't understand as well.
 The fact is 28 - not working   60 - working.
 When your FG will be on, you will probably give a good explaination.

If we look at /systems/electrical/outputs/
we get gps to null when volt=28
we get gps to 60 when volt=60

in gps.cxx we find Line 102
 _electrical_node = fgGetNode(/systems/electrical/outputs/gps, true);

I am far be expert, it seems that gps needs a good electrical  value, is
it right ?
 
-- 
Gerard


___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] Get nearest Airport : Not Working

2005-07-26 Thread Roy Vegard Ovesen
On Tuesday 26 July 2005 19:20, Gerard Robin wrote:
 If we look at /systems/electrical/outputs/
 we get gps to null when volt=28
 we get gps to 60 when volt=60

 in gps.cxx we find Line 102
  _electrical_node = fgGetNode(/systems/electrical/outputs/gps, true);

That's the initialization of the property. This is where it gets created.

 I am far be expert, it seems that gps needs a good electrical  value, is
 it right ?

That's right. At line 215 that property needs to be true (that is not 
zero/null) for the gps to update.

-- 
Roy Vegard Ovesen

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] Get nearest Airport : Not Working

2005-07-25 Thread Gerard Robin
Get Nearest Airport (From Menu Equipment GPS) seems not working.
It was working with olders CVS. 
Is it any new modifications which deleted that function ?

Thanks
-- 
Gerard


___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] Get nearest Airport : Not Working

2005-07-25 Thread Roy Vegard Ovesen
On Monday 25 July 2005 20:49, Gerard Robin wrote:
 Get Nearest Airport (From Menu Equipment GPS) seems not working.
 It was working with olders CVS.
 Is it any new modifications which deleted that function ?

AFAICT there hasn't been any significant changes to Instrumentation/gps.*xx or 
Airports/simple.*xx. There has been alot of improvements to the gui system 
lately, so maybe my dialog has become broken. Could you try to trigger the 
Get Nearest Airport from the property browser? Go to 
/instrumentation/gps/wp/wp[1] and set get-nearest-airport to true. I'm 
not able to run FG right now because of some freeglut issue (I believe) so I 
can't test this myself :-(

-- 
Roy Vegard Ovesen

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] Get nearest Airport : Not Working

2005-07-25 Thread Gerard Robin
Le lundi 25 juillet 2005 à 23:02 +0200, Roy Vegard Ovesen a écrit :

 AFAICT there hasn't been any significant changes to Instrumentation/gps.*xx 
 or 
 Airports/simple.*xx. There has been alot of improvements to the gui system 
 lately, so maybe my dialog has become broken. Could you try to trigger the 
 Get Nearest Airport from the property browser? Go to 
 /instrumentation/gps/wp/wp[1] and set get-nearest-airport to true. I'm 
 not able to run FG right now because of some freeglut issue (I believe) so I 
 can't test this myself :-(
 
sorry
It has not any effect. We get nothing :=(
Looking at the guy dialog it is the old usual nasal command. it should
work.
-- 
Gerard


___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] Get nearest Airport : Not Working

2005-07-24 Thread Gerard Robin
Get Nearest Airport (From Menu Equipment GPS) seems not working.
It was working with olders CVS. 
Is it any new modifications which deleted that function ?

Thanks
-- 
Gerard


___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d