Re: [Flightgear-devel] C172p strange behaviour with --flight-plan

2007-02-10 Thread Roy Vegard Ovesen
On Saturday 10 February 2007 01:08, gh.robin wrote:
 Hello Roy,
 I do not  notice any differences regarding /autopilot/new-config dir
 between first load values (after FG loaded)  and after reload  autopilot.

 i get two  pi-simple-controllers and sixteen pid-controllers.

OK, you said that the heading hold in the dc3 was crazy. The dc3 uses the 
generic autopilot, then all aircraft using the generic autopilot should 
experience the same crazieness in heading hold mode.

Could you try activating the debug option of the two pid-controllers that are 
used in heading hold mode? Open data/Aircraft/Generic/generic-autopilot.xml 
and set the debug flag to true for the controllers named Heading Bug Hold 
(DG based) Stage 1, and Heading Bug Hold (DG based) Stage 2.

When you activate the heading hold mode you should get debug messages from 
those two controllers on the console. This is what I get when I'm in a left 
turn chasing the heading bug in the dc3 (# My comments):


Updating Heading Bug Hold (DG based) Stage 1 Ts 0.0416667
  input = -50.076 ref = 0 # We are -50.076 degrees from our desired heading.
  ep_n = 50.076  ep_n_1 = 50.1743 e_n = 50.076 ed_n = 50.076 Tf = 1e-06 edf_n 
= 50.076 delta_u_n = -0.110384
P:0.0982607 I:-0.20865 D:5.29441e-06
 min saturation 
  output = -20 # The controller has commanded a 20 degree left bank.

Updating Heading Bug Hold (DG based) Stage 2 Ts 0.0416667
  input = -16.6732 ref = -20 # We are currently at 16.6732 degrees left bank.
  ep_n = -3.32684  ep_n_1 = -3.34097 e_n = -3.32684 ed_n = 16.6732 Tf = 1e-06 
edf_n = 16.6732 delta_u_n = 2.75638e-05
P:0.00141368 I:-0.00138618 D:6.68812e-08
  output = -0.00296141 # This is the commanded aileron, a tiny bit of left 
aileron makes sense.

# 0.03 seconds later:
Updating Heading Bug Hold (DG based) Stage 1 Ts 0.033
  input = -49.9996 ref = 0
  ep_n = 49.9996  ep_n_1 = 50.076 e_n = 49.9996 ed_n = 49.9996 Tf = 1e-06 
edf_n = 49.9996 delta_u_n = -0.09026
P:0.0764119 I:-0.15 D:-6.55459e-06
 min saturation 
  output = -20

Updating Heading Bug Hold (DG based) Stage 2 Ts 0.033
  input = -16.6844 ref = -20
  ep_n = -3.31557  ep_n_1 = -3.32684 e_n = -3.31557 ed_n = 16.6844 Tf = 1e-06 
edf_n = 16.6844 delta_u_n = 2.10212e-05
P:0.0011263 I:-0.00110519 D:-8.62141e-08
  output = -0.00294038


As you can see the inputs and outputs to/from these controllers look 
reasonable. Are you getting crazy inputs and outputs when you try the same? 
And are you getting sane inputs and outputs after a autopilot reload?

If you are getting crazy inputs and outputs, you should run fgfs in a debugger 
like ddd and step through the FGPIDController::update() method in 
source/src/Autopilot/xmlauto.cxx to see what is going on.


-- 
Roy Vegard Ovesen

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] DME for pa28-161

2007-02-10 Thread Dave Perry
On Fri, 2007-02-09 at 13:44 +, Martin Spott wrote:
 Hi Ron,
 
 Ron Jensen wrote:
 
  Truly bizarre, I fired up this aircraft and saw the radiostack,
complete
  with DME and though, what is Thiago talking about, its right
there...
  Then I looked at my CVS repository and realized my Cherokee is
modified.
  Don't remember doing that, but then I'm old.   My model is a bit
  different but this patch should work.  Note you need the pa24-250
  installed.
 
 Would you consider working together with Dave in order to 'generalize'
 the radio-stack so we can put it into the Instruments-3d directory ?

Hi Ron  Martin,

On my system, I have the following running:
1.  Moved the pa24 radio stack to Aircraft/Instruments-3d/, along with
the required changes to the pa24-250.
2.  Made similar changes to the pa28-161 to use the now public radio
stack.
3.  Modified the alt, hi, the two vor heads to use pick so all the
knobs now work on the pa28-161 panel.
4.  Commented out the corresponding actions in the pa24-panel.xml file.
5.  Made the required changes to pa28-161-set.xml to use the kap140
autopilot that comes with the radio stack.

A year ago, when I first submitted the pa24-250, David Megginson told me
to go ahead and bring the pa28-161 up to the same functionality as the
pa24-250.  This is now done on my system.  

Is there interest in a patch to do the same in osg cvs?  These changes
make both AC dependent on osg (i.e. the pick is not supported in the
plib only branch).

Regards, 

-- 
Dave Perry [EMAIL PROTECTED]


-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] C172p strange behaviour with --flight-plan

2007-02-10 Thread Ron Jensen
On Sat, 2007-02-10 at 10:53 +0100, Roy Vegard Ovesen wrote:
 On Saturday 10 February 2007 01:08, gh.robin wrote:
  Hello Roy,
  I do not  notice any differences regarding /autopilot/new-config dir
  between first load values (after FG loaded)  and after reload  autopilot.
 
  i get two  pi-simple-controllers and sixteen pid-controllers.
 
 OK, you said that the heading hold in the dc3 was crazy. The dc3 uses the 
 generic autopilot, then all aircraft using the generic autopilot should 
 experience the same crazieness in heading hold mode.

Just a random thought: the autopilot does not lock the controls out (and
it shouldn't) so rudder inputs will make the  heading hold wander.  I
fly with pedals, so I can really pull the nose off course when the
autopilot is flying.

Are the people experiencing problems with the autopilots using
--auto-coordinate?

Ron



-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] DME for pa28-161

2007-02-10 Thread Ron Jensen
On Sat, 2007-02-10 at 07:48 -0700, Dave Perry wrote:
 On Fri, 2007-02-09 at 13:44 +, Martin Spott wrote:
  Hi Ron,
  
  Ron Jensen wrote:
  
   Truly bizarre, I fired up this aircraft and saw the radiostack,
 complete
   with DME and though, what is Thiago talking about, its right
 there...
   Then I looked at my CVS repository and realized my Cherokee is
 modified.
   Don't remember doing that, but then I'm old.   My model is a bit
   different but this patch should work.  Note you need the pa24-250
   installed.
  
  Would you consider working together with Dave in order to 'generalize'
  the radio-stack so we can put it into the Instruments-3d directory ?
 
 Hi Ron  Martin,
 
 On my system, I have the following running:
 1.  Moved the pa24 radio stack to Aircraft/Instruments-3d/, along with
 the required changes to the pa24-250.
 2.  Made similar changes to the pa28-161 to use the now public radio
 stack.
 3.  Modified the alt, hi, the two vor heads to use pick so all the
 knobs now work on the pa28-161 panel.
 4.  Commented out the corresponding actions in the pa24-panel.xml file.
 5.  Made the required changes to pa28-161-set.xml to use the kap140
 autopilot that comes with the radio stack.
 
 A year ago, when I first submitted the pa24-250, David Megginson told me
 to go ahead and bring the pa28-161 up to the same functionality as the
 pa24-250.  This is now done on my system.  
 
 Is there interest in a patch to do the same in osg cvs?  These changes
 make both AC dependent on osg (i.e. the pick is not supported in the
 plib only branch).
 
 Regards, 
 

Hi Dave,

I'm good with osg only.  I think one of the reasons 3d cockpits are rare
is its very hard to do hot-spots with the plib method.  (I am in awe of
the work on panel hot-spots that went into the SenecaII!)

As I understand it plib happily ignores pick animations, so keeping the
plib branch in-sync maybe as simple as not committing the hotspot
changes in the pa24-panel.xml file to the plib branch.  Since the radio
panel is a 2.5d panel its hotspots should still work in the plib branch.

Thanks,

Ron





-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


[Flightgear-devel] ILS service volume issues

2007-02-10 Thread John Denker
In some parts of the world, (including the southwest
US), a goodly fraction of the localizers have an expanded
service volume (ESV), often quite a bit larger than the
standard service volume you see in the AIM.

The code in navradio.cxx has been ignoring the service volume
information in the database and wrongly assuming the default
values applied everywhere.  A patch to fix the range-related
part of the problem can be found at:
   http://www.av8n.com/fly/fgfs/service-volume.diff

... but alas there are other service volume issues.

The code has no understanding of how azimuth affects the
localizer.  There is more to the story than reception *range*.
It is perfectly possible to be outside the LOC service volume
for reasons having to do with azimuth, not range.

Good ident will be heard, but false localizer courses will
cause serious trouble for the unwary pilot.

Similar remarks apply to false glide slopes.

The patch does not address these non-range issue.  The code
would need to be significantly restructured to deal with this.


-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


[Flightgear-devel] building the library of 3D instruments (was: DME for pa28)

2007-02-10 Thread John Denker
On 02/10/2007 09:48 AM, Dave Perry wrote:

 On my system, I have the following running:
 1.  Moved the pa24 radio stack to Aircraft/Instruments-3d/, along with
 the required changes to the pa24-250.
[etc.]

Yes, that's a good move.

While were on the subject ... could you please similarly
export the mag switch + key object?  It's a whole lot more
attractive than the corresponding 2D object, and I suspect
a great many of the 3D singles will want to use it.


-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


[Flightgear-devel] Joystick setup for Saitek P880

2007-02-10 Thread Ed Sirett
This file works for a Saitek P880.

I would welcome its inclusion into ...data/Input/Joysticks/Saitek

Thanks.

-- 
Ed Sirett  T: 020 8883 1448 M: 07860 432401 P: 72 Wilton Road, N10 1LT



P880.xml
Description: application/xml
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Joystick setup for Saitek P880

2007-02-10 Thread Melchior FRANZ
* Ed Sirett -- Sunday 11 February 2007:
 This file works for a Saitek P880.

This looks rather archaic. It doesn't support several aircraft,
because it doesn't use the controls wrappers. Also it lacks
indentation. Who's going to fix it all?  :-)

m.

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] C172p strange behaviour with --flight-plan

2007-02-10 Thread gh.robin
On Sat 10 February 2007 10:53, Roy Vegard Ovesen wrote:
 On Saturday 10 February 2007 01:08, gh.robin wrote:
  Hello Roy,
  I do not  notice any differences regarding /autopilot/new-config dir
  between first load values (after FG loaded)  and after reload  autopilot.
 
  i get two  pi-simple-controllers and sixteen pid-controllers.

 OK, you said that the heading hold in the dc3 was crazy. The dc3 uses the
 generic autopilot, then all aircraft using the generic autopilot should
 experience the same crazieness in heading hold mode.

 Could you try activating the debug option of the two pid-controllers that
 are used in heading hold mode? Open
 data/Aircraft/Generic/generic-autopilot.xml and set the debug flag to true
 for the controllers named Heading Bug Hold (DG based) Stage 1, and
 Heading Bug Hold (DG based) Stage 2.

 When you activate the heading hold mode you should get debug messages from
 those two controllers on the console. This is what I get when I'm in a left
 turn chasing the heading bug in the dc3 (# My comments):


 Updating Heading Bug Hold (DG based) Stage 1 Ts 0.0416667
   input = -50.076 ref = 0 # We are -50.076 degrees from our desired
 heading. ep_n = 50.076  ep_n_1 = 50.1743 e_n = 50.076 ed_n = 50.076 Tf =
 1e-06 edf_n = 50.076 delta_u_n = -0.110384
 P:0.0982607 I:-0.20865 D:5.29441e-06
  min saturation
   output = -20 # The controller has commanded a 20 degree left bank.

 Updating Heading Bug Hold (DG based) Stage 2 Ts 0.0416667
   input = -16.6732 ref = -20 # We are currently at 16.6732 degrees left
 bank. ep_n = -3.32684  ep_n_1 = -3.34097 e_n = -3.32684 ed_n = 16.6732 Tf =
 1e-06 edf_n = 16.6732 delta_u_n = 2.75638e-05
 P:0.00141368 I:-0.00138618 D:6.68812e-08
   output = -0.00296141 # This is the commanded aileron, a tiny bit of left
 aileron makes sense.

I have settled Heading Bug =180
autopilot does not work (crazy)

I get  messages
here an extract

..
Updating Heading Bug Hold (DG based) Stage 2 Ts 0.025
  input = -0.129679 ref = 0
  ep_n = 0.129679  ep_n_1 = 0.130254 e_n = 0.129679 ed_n = 0.129679 Tf = 1e-06 
edf_n = 0.129679 delta_u_n = -2.51044e-05
P:-5.75163e-05 I:3.24197e-05 D:-7.7432e-09
  output = 0.000684861
Updating Heading Bug Hold (DG based) Stage 2 Ts 0.017
  input = -0.129309 ref = 0
  ep_n = 0.129309  ep_n_1 = 0.129679 e_n = 0.129309 ed_n = 0.129309 Tf = 1e-06 
edf_n = 0.129309 delta_u_n = -1.53979e-05
P:-3.69617e-05 I:2.15515e-05 D:1.23327e-08
  output = 0.000669463
Updating Heading Bug Hold (DG based) Stage 2 Ts 0.017
  input = -0.128936 ref = 0
  ep_n = 0.128936  ep_n_1 = 0.129309 e_n = 0.128936 ed_n = 0.128936 Tf = 1e-06 
edf_n = 0.128936 delta_u_n = -1.58609e-05
P:-3.73499e-05 I:2.14893e-05 D:-2.32856e-10
  output = 0.000653603
Updating Heading Bug Hold (DG based) Stage 2 Ts 0.017
  input = -0.12854 ref = 0
  ep_n = 0.12854  ep_n_1 = 0.128936 e_n = 0.12854 ed_n = 0.12854 Tf = 1e-06 
edf_n = 0.12854 delta_u_n = -1.81036e-05
P:-3.95257e-05 I:2.14234e-05 D:-1.30541e-09
  output = 0.000635499
..



 # 0.03 seconds later:
 Updating Heading Bug Hold (DG based) Stage 1 Ts 0.033
   input = -49.9996 ref = 0
   ep_n = 49.9996  ep_n_1 = 50.076 e_n = 49.9996 ed_n = 49.9996 Tf = 1e-06
 edf_n = 49.9996 delta_u_n = -0.09026
 P:0.0764119 I:-0.15 D:-6.55459e-06
  min saturation
   output = -20

 Updating Heading Bug Hold (DG based) Stage 2 Ts 0.033
   input = -16.6844 ref = -20
   ep_n = -3.31557  ep_n_1 = -3.32684 e_n = -3.31557 ed_n = 16.6844 Tf =
 1e-06 edf_n = 16.6844 delta_u_n = 2.10212e-05
 P:0.0011263 I:-0.00110519 D:-8.62141e-08
   output = -0.00294038



 As you can see the inputs and outputs to/from these controllers look
 reasonable. Are you getting crazy inputs and outputs when you try the same?
 And are you getting sane inputs and outputs after a autopilot reload?

And after reloading autopilot
autopilot works

I get messages
Here an extract
..

Updating Heading Bug Hold (DG based) Stage 1 Ts 0.017
  input = -86.2699 ref = 0
  ep_n = 86.2699  ep_n_1 = 86.3099 e_n = 86.2699 ed_n = 86.2699 Tf = 1e-06 
edf_n = 86.2699 delta_u_n = -0.103803
P:0.0399801 I:-0.143783 D:1.29082e-08
 min saturation
  output = -20
Updating Heading Bug Hold (DG based) Stage 2 Ts 0.017
  input = -17.7823 ref = -20
  ep_n = -2.21771  ep_n_1 = -2.22147 e_n = -2.21771 ed_n = 17.7823 Tf = 1e-06 
edf_n = 17.7823 delta_u_n = 6.21317e-06
P:0.000375831 I:-0.000369619 D:9.22063e-10
  output = -0.00492783
Updating Heading Bug Hold (DG based) Stage 1 Ts 0.017
  input = -86.2299 ref = 0
  ep_n = 86.2299  ep_n_1 = 86.2699 e_n = 86.2299 ed_n = 86.2299 Tf = 1e-06 
edf_n = 86.2299 delta_u_n = -0.103755
P:0.039962 I:-0.143717 D:-1.08567e-08
 min saturation
  output = -20
Updating Heading Bug Hold (DG based) Stage 2 Ts 0.017
  input = -17.7861 ref = -20
  ep_n = -2.21394  ep_n_1 = -2.21771 e_n = -2.21394 ed_n = 17.7861 Tf = 1e-06 
edf_n = 17.7861 delta_u_n = 

Re: [Flightgear-devel] C172p strange behaviour with --flight-plan

2007-02-10 Thread Roy Vegard Ovesen
On Sunday 11 February 2007 00:29, gh.robin wrote:
 I have settled Heading Bug =180
 autopilot does not work (crazy)

 I get  messages
 here an extract

 ..
 Updating Heading Bug Hold (DG based) Stage 2 Ts 0.017
   input = -0.128936 ref = 0
   ep_n = 0.128936  ep_n_1 = 0.129309 e_n = 0.128936 ed_n = 0.128936 Tf =
 1e-06 edf_n = 0.128936 delta_u_n = -1.58609e-05
 P:-3.73499e-05 I:2.14893e-05 D:-2.32856e-10
   output = 0.000653603
 Updating Heading Bug Hold (DG based) Stage 2 Ts 0.017
   input = -0.12854 ref = 0
   ep_n = 0.12854  ep_n_1 = 0.128936 e_n = 0.12854 ed_n = 0.12854 Tf = 1e-06
 edf_n = 0.12854 delta_u_n = -1.81036e-05
 P:-3.95257e-05 I:2.14234e-05 D:-1.30541e-09
   output = 0.000635499
 ..

The autopilot is holding the wings level, right. I think characterizing this 
as crazy is very misleading. One might think that it was turning left and 
right.

 And after reloading autopilot
 autopilot works

 I get messages
 Here an extract
 ..

 Updating Heading Bug Hold (DG based) Stage 1 Ts 0.017
   input = -86.2699 ref = 0
   ep_n = 86.2699  ep_n_1 = 86.3099 e_n = 86.2699 ed_n = 86.2699 Tf = 1e-06
 edf_n = 86.2699 delta_u_n = -0.103803
 P:0.0399801 I:-0.143783 D:1.29082e-08
  min saturation
   output = -20
 Updating Heading Bug Hold (DG based) Stage 2 Ts 0.017
   input = -17.7823 ref = -20
   ep_n = -2.21771  ep_n_1 = -2.22147 e_n = -2.21771 ed_n = 17.7823 Tf =
 1e-06 edf_n = 17.7823 delta_u_n = 6.21317e-06
 P:0.000375831 I:-0.000369619 D:9.22063e-10
   output = -0.00492783
  ...


 I can notice  with the first example (before reload) only stage2 gives
 messages

 With second example (after reload) with autopilot working i do have both
 stage1 and stage2

It looks like the stage 1 controller fails to initialize at startup. Is this 
consistent, or are you, like Lee was, seeing some randomness in what 
controllers aren't working before autopilot reload?

  If you are getting crazy inputs and outputs, you should run fgfs in a
  debugger like ddd and step through the FGPIDController::update() method
  in source/src/Autopilot/xmlauto.cxx to see what is going on.

 Because i am not developer ,  i will not be able to do it

Sure you can! ;-)


-- 
Roy Vegard Ovesen

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] C172p strange behaviour with --flight-plan

2007-02-10 Thread gh.robin
On Sun 11 February 2007 01:01, Roy Vegard Ovesen wrote:
 On Sunday 11 February 2007 00:29, gh.robin wrote:


 The autopilot is holding the wings level, right. I think characterizing
 this as crazy is very misleading. One might think that it was turning
 left and right.


Yes , in that case crazy is not good, but randomly i can get some 
uncontrolled movements, like start to turn keeping that turn permanently  or 
turn left then turn right, then lost stability and crash on the ground.

 It looks like the stage 1 controller fails to initialize at startup. Is
 this consistent, or are you, like Lee was, seeing some randomness in what
 controllers aren't working before autopilot reload?


To me it is consistent, i get only stage 2 , i did not noticed some 
randomness.


   If you are getting crazy inputs and outputs, you should run fgfs in a
   debugger like ddd and step through the FGPIDController::update() method
   in source/src/Autopilot/xmlauto.cxx to see what is going on.
 
  Because i am not developer ,  i will not be able to do it

 Sure you can! ;-)

I confirm i can't

Regards



-- 
Gérard

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] C172p strange behaviour with --flight-plan

2007-02-10 Thread leee
I couldn't see a parameter to enable dynamic view in the command line but it 
seemed ok if I enabled it via the menu.  The view pitched a small amount when 
I enabled it and pitched back when I disabled it.

LeeE

On Friday 09 February 2007 20:51, Maik Justus wrote:
 Hi LeeE,

 can you start flightgear with the bo105 and dynamic-view enabled? If the
 view direction is ok during the first second or is it spinning around?

 Maybe this bug has a similar cause.

 Maik

 leee schrieb am 09.02.2007 20:22:
  On Friday 09 February 2007 19:04, Roy Vegard Ovesen wrote:
  I just tried the dc3. Heading hold is working perfectly.
 
  Could there be something on your and Lee's system that is causing this?
  I tried the first time you reported this issue, and was unable to
  reproduce what you saw then too.
 
  Are anyone else on this list seeing the problems that Lee and Gérard are
  seeing?
 
  It's difficult to imagine a system problem that might cause this
  behaviour, in view of the fact that resetting appears to fix the problem.
 
  However, I know that there are a few problems that I've seen here that no
  one else appears to have experienced on their systems, one long running
  example being problems with the wind and visibility settings not being
  honoured.

 -
 Using Tomcat but need to do more? Need to support web services, security?
 Get stuff done quickly with pre-integrated technology to make your job
 easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache
 Geronimo
 http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
 ___
 Flightgear-devel mailing list
 Flightgear-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/flightgear-devel


-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Joystick setup for Saitek P880

2007-02-10 Thread Ron Jensen
On Sun, 2007-02-11 at 00:12 +0100, Melchior FRANZ wrote:
 * Ed Sirett -- Sunday 11 February 2007:
  This file works for a Saitek P880.
 
 This looks rather archaic. It doesn't support several aircraft,
 because it doesn't use the controls wrappers. Also it lacks
 indentation. Who's going to fix it all?  :-)
 
 m.

xmllint did the indents, I changed the function wrappers.

Ed,

Can you try this file and confirm it still works?  I don't have a Saitek
P880.

Thanks,

Ron



P880b.xml
Description: application/xml
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Joystick setup for Saitek P880

2007-02-10 Thread Melchior FRANZ
* Ron Jensen -- Sunday 11 February 2007:
 I changed the function wrappers.

But not all. pa24 and b29 flaps won't work correctly that way.
Their mod-up bindings need to call controls.flapsDown(0), so
that the flap movement is stopped on button-release. But I can
do that, too. Or whoever commits.

Personally, I like the view axis done via wrappers, too.
Not that I could give a single convincing reason for it ...  ;-)

m.

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] autopilot, Was: C172p stra nge behaviour with --flight-plan

2007-02-10 Thread leee
On Friday 09 February 2007 21:36, Roy Vegard Ovesen wrote:
 On Friday 09 February 2007 21:13, leee wrote:
  Just tried another quick test.
 
  Opened five property browsers - autopilot/locks, autopilot/settings,
  autopilot/internal, autopilot/FCS/locks  autopilot/FCS/controls - all
  seemed ok but then I pre-set most of the nodes during aircraft
  initialisation.

 The one I asked Gérard to look at was /autopilot/new-config.

 When you have pinpointed that a certain controller is not outputting what
 it should, look in /autopilot/new-config to see if the controller is
 actually there. If it is there, try enabling the debug option for that
 controller.

  On this test the altitude hold failed to work.  The altitude hold
  controller reads the filtered target alt and outputs to
  autopilot/settings/target-climb-rate-fps.  When the altitude hold
  controller was engaged it failed to update the target climb rate.  Agl
  hold, which also outputs to the same target climb rate node in
  autopilot/settings, was ok and I could see the node being updated.
 
  I switched back to altitude hold and forced a climb by over-typing a +ve
  climb rate into the non-updating node.  Once I got to around 10k ft I
  reset the A/P and the climb rate started updating.

 It looks like the controllers are not getting built correctly at FG
 startup. When you do a autopilot-reset, the controllers in
 /autopilot/new-config are cleared and the autopilot config xml file is
 re-read and the controllers re-built.

Quick test - this time on take-off the pitch hold didn't kick in.  This is the 
very first controller in the config and it appeared to be there in 
new-config, with the correct config.  It just didn't seem to be sending 
anything to the output.

All the other controllers seemed to be accounted for too - I didn't check each 
one but the numbers tallied.

Yup - just tried again and got the same pitch-hold problem.  I checked 
everything for this controller in new-config, making sure that all the nodes 
were ok, and it all looked fine.

LeeE


-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] C172p strange behaviour with --flight-plan

2007-02-10 Thread leee
On Saturday 10 February 2007 16:04, Ron Jensen wrote:
 On Sat, 2007-02-10 at 10:53 +0100, Roy Vegard Ovesen wrote:
  On Saturday 10 February 2007 01:08, gh.robin wrote:
   Hello Roy,
   I do not  notice any differences regarding /autopilot/new-config dir
   between first load values (after FG loaded)  and after reload 
   autopilot.
  
   i get two  pi-simple-controllers and sixteen pid-controllers.
 
  OK, you said that the heading hold in the dc3 was crazy. The dc3 uses
  the generic autopilot, then all aircraft using the generic autopilot
  should experience the same crazieness in heading hold mode.

 Just a random thought: the autopilot does not lock the controls out (and
 it shouldn't) so rudder inputs will make the  heading hold wander.  I
 fly with pedals, so I can really pull the nose off course when the
 autopilot is flying.

 Are the people experiencing problems with the autopilots using
 --auto-coordinate?

 Ron

Not here.

LeeE


-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] C172p strange behaviour with --flight-plan

2007-02-10 Thread Ron Jensen
On Sun, 2007-02-11 at 00:16 +, leee wrote:
 I couldn't see a parameter to enable dynamic view in the command line but it 
 seemed ok if I enabled it via the menu.  The view pitched a small amount when 
 I enabled it and pitched back when I disabled it.
 
 LeeE
 

Dynamic view from the command line:
--prop:/sim/view/dynamic/enabled=1


-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] autopilot, Was: C172p stra nge behaviour with --flight-plan

2007-02-10 Thread leee
On Sunday 11 February 2007 00:37, leee wrote:
 On Friday 09 February 2007 21:36, Roy Vegard Ovesen wrote:
  On Friday 09 February 2007 21:13, leee wrote:
   Just tried another quick test.
  
   Opened five property browsers - autopilot/locks, autopilot/settings,
   autopilot/internal, autopilot/FCS/locks  autopilot/FCS/controls - all
   seemed ok but then I pre-set most of the nodes during aircraft
   initialisation.
 
  The one I asked Gérard to look at was /autopilot/new-config.
 
  When you have pinpointed that a certain controller is not outputting what
  it should, look in /autopilot/new-config to see if the controller is
  actually there. If it is there, try enabling the debug option for that
  controller.
 
   On this test the altitude hold failed to work.  The altitude hold
   controller reads the filtered target alt and outputs to
   autopilot/settings/target-climb-rate-fps.  When the altitude hold
   controller was engaged it failed to update the target climb rate.  Agl
   hold, which also outputs to the same target climb rate node in
   autopilot/settings, was ok and I could see the node being updated.
  
   I switched back to altitude hold and forced a climb by over-typing a
   +ve climb rate into the non-updating node.  Once I got to around 10k ft
   I reset the A/P and the climb rate started updating.
 
  It looks like the controllers are not getting built correctly at FG
  startup. When you do a autopilot-reset, the controllers in
  /autopilot/new-config are cleared and the autopilot config xml file is
  re-read and the controllers re-built.

 Quick test - this time on take-off the pitch hold didn't kick in.  This is
 the very first controller in the config and it appeared to be there in
 new-config, with the correct config.  It just didn't seem to be sending
 anything to the output.

 All the other controllers seemed to be accounted for too - I didn't check
 each one but the numbers tallied.

 Yup - just tried again and got the same pitch-hold problem.  I checked
 everything for this controller in new-config, making sure that all the
 nodes were ok, and it all looked fine.

 LeeE

I thought I'd give it another go, with debug on the pitch-hold controller and 
waddya know - this time the pitch hold worked and the alt hold failed.

Ok - so I set debugging on all three of the pitch related controllers and on 
the next test it was back to the pitch hold problem again but with no heading 
hold either.  Anyway, there was no output from the pitch hold controller 
although I could see the climb rate and altitude controllers come in as they 
were engaged.

I paused the sim once I was above the target altitude, inserted some blank 
lines into the debug o/p, so I could find the point again, and reset the a/p.  
After doing this I could then see debug o/p from the pitch controller.

Do you want to see the debug o/p?

LeeE


-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


[Flightgear-devel] altimeter.xml

2007-02-10 Thread John Denker
The standard altimeter (used by the default c172p aircraft and many others)
had been using an unhappy hodgepodge of layers. The analog Kollsman window
was unusable, because it was unlabeled, and the digital altimeter setting
was unusable, especially at altitudes near 2500 feet, partly from being
behind the needle. On a real altimeter, things are positioned so that
cannot happen.

Fixing this requires using a more suitable font, moving the digits over,
and getting rid of conflicting extraneous markings.

A patch to implement this fix can be found at
   http://www.av8n.com/fly/fgfs/altimeter.diff

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


[Flightgear-devel] incorrect altimetry

2007-02-10 Thread John Denker
There is evidently at least one serious misconception in
the code that calculates atmospheric pressure, altimeter
settings, et cetera. This can be easily demonstrated:

Park at or near the threshold of runway 33 at Aspen
(KASE). Under standard conditions, observe that the
altimeter reads 7820 feet MSL, as it should.

Use the Weather : Weather Conditions dialog popup to look at
the ground-level altimeter setting (QNH).  This is bottom row
in the Alt (inHg) column of the popup.  Verify that it is
29.92.

Now use the dialog box to change this property. Change it to
30.92, a one-inch difference.

Go to your altimeter instrument and enter the new altimeter
setting in the Kollsman window. Ideally, this should cause
the instrument to read the correct altitude once again,
namely 7820 feet MSL.

However, due to bugs, it is likely that you will observe
something closer to 8120. This means the airplane is 300
feet lower than the altimeter says it is.

In case it wasn't obvious, when flying around near Aspen,
being 300 feet lower than you think you are can be very bad
for your health.

The absolutely correct formula for computing the altimeter
setting can be found in the jsd barometry page -- look where
it mentions Field Pressure.
  http://www.av8n.com/physics/barometry.html




While we're in the vicinity:

Both the Weather Conditions popup and the atis.cxx code rely
on the pressure-sea-level-inhg property and use it in ways
that the altimeter setting should be used.

This is at least a misnomer, and probably a misconception.
The altimeter setting is not the same thing as the sea-level
pressure. The altimeter setting is something else; it is
properly called the altimeter setting. It is also properly
called the QNH, although private pilots who fly only in
the US may be unfamiliar with the QNH terminology.

This property needs to be expunged and replaced with
something else, something with a correct name and with
correct semantics.


-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


[Flightgear-devel] Weekly CVS Changelog Summary: SimGear

2007-02-10 Thread Curtis L. Olson
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-02-05_15:41:33 (mfranz)
/var/cvs/SimGear-0.3/source/simgear/io/sg_binobj.cxx

fix error message


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-02-05_15:41:40 (mfranz)
/var/cvs/SimGear-0.3/source/simgear/io/sg_binobj.cxx

fix error message


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-02-07_13:21:24 (andy)
/var/cvs/SimGear-0.3/source/simgear/scene/model/animation.cxx

bias argument to texture animations by Ron Jensen


2f585eeea02e2c79d7b1d8c4963bae2d

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


[Flightgear-devel] Weekly CVS Changelog Summary: FlightGear source

2007-02-10 Thread Curtis L. Olson
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-02-05_14:29:26 (mfranz)
/var/cvs/FlightGear-0.9/source/src/Input/input.cxx

export mouse coords of main mouse


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-02-05_14:29:29 (mfranz)
/var/cvs/FlightGear-0.9/source/src/Input/input.cxx

export mouse coords of main mouse


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-02-05_23:32:24 (frohlich)
/var/cvs/FlightGear-0.9/source/src/Main/renderer.cxx

Modified Files:
src/Main/renderer.cxx: Avoid an additional camera.
Guard the plain OpenGL drawables better.
This change now requires the new osg tarball or osg cvs.


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-02-08_23:34:34 (frohlich)
/var/cvs/FlightGear-0.9/source/src/Airports/runways.cxx

Modified Files:
Airports/runways.cxx: Correct termination condition.


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-02-08_23:35:10 (frohlich)
/var/cvs/FlightGear-0.9/source/src/Navaids/navdb.cxx

Modified Files:
Navaids/navdb.cxx: Olaf Flebbe: plug memory leak.


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-02-08_23:41:42 (frohlich)
/var/cvs/FlightGear-0.9/source/src/Instrumentation/navradio.cxx

Modified Files:
navradio.cxx: Olaf Flebbe: Use bool for booleans.


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-02-09_05:01:57 (mfranz)
/var/cvs/FlightGear-0.9/source/src/Instrumentation/navradio.cxx

Olaf Flebbe: Use bool for booleans

mf: merged from HEAD


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-02-09_05:02:50 (mfranz)
/var/cvs/FlightGear-0.9/source/src/Airports/runways.cxx

Mathias FROEHLICH: Correct termination condition

mf: merged from HEAD


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-02-09_05:03:25 (mfranz)
/var/cvs/FlightGear-0.9/source/src/Navaids/navdb.cxx

Olaf FLEBBE: plug memory leak

mf: merged from HEAD


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-02-10_10:32:21 (fredb)
/var/cvs/FlightGear-0.9/source/src/Main/renderer.cxx
/var/cvs/FlightGear-0.9/source/src/Network/jpg-httpd.cxx

Fix the jpg http server


2f585eeea02e2c79d7b1d8c4963bae2d

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


[Flightgear-devel] Weekly CVS Changelog Summary: FlightGear data

2007-02-10 Thread Curtis L. Olson
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-02-04_04:26:44 (sydadams)
/var/cvs/FlightGear-0.9/data/Aircraft/dhc2/dhc2-sound.xml
/var/cvs/FlightGear-0.9/data/Aircraft/dhc2/dhc2F.xml
/var/cvs/FlightGear-0.9/data/Aircraft/dhc2/Instruments/asi.xml
/var/cvs/FlightGear-0.9/data/Aircraft/dhc2/Instruments/fuel-gauge.xml
/var/cvs/FlightGear-0.9/data/Aircraft/dhc2/Instruments/oiltemp-gauge.xml
/var/cvs/FlightGear-0.9/data/Aircraft/dhc2/Instruments/vacuum.xml
/var/cvs/FlightGear-0.9/data/Aircraft/dhc2/Instruments/vsi-gauge.xml
/var/cvs/FlightGear-0.9/data/Aircraft/dhc2/Models/dhc2W.ac

more float adjustments...
updated sounds and wake animation...


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-02-04_04:26:45 (sydadams)
/var/cvs/FlightGear-0.9/data/Aircraft/dhc2/Models/submodels.xml
/var/cvs/FlightGear-0.9/data/Aircraft/dhc2/Models/wake.ac
/var/cvs/FlightGear-0.9/data/Aircraft/dhc2/Models/wake.xml
/var/cvs/FlightGear-0.9/data/Aircraft/dhc2/Nasal/dhc2.nas

more float adjustments...
updated sounds and wake animation...


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-02-04_06:55:28 (mfranz)
/var/cvs/FlightGear-0.9/data/Aircraft/Instruments/KAP140TwoAxis.xml

Dave Perry  Roy Vegard Ovesen:

This patch allows all the AC using the kap140 to use one kap140.nas
which includes Roy's move to bool values as well as the check for
power used by the pa24-250. (dp)


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-02-04_06:55:29 (mfranz)
/var/cvs/FlightGear-0.9/data/Aircraft/Generic/kap140.nas
/var/cvs/FlightGear-0.9/data/Aircraft/Generic/limits.nas
/var/cvs/FlightGear-0.9/data/Aircraft/Instruments/KAP140TwoAxisAlt.xml
/var/cvs/FlightGear-0.9/data/Aircraft/Instruments/fuel-c172s.xml
/var/cvs/FlightGear-0.9/data/Aircraft/c172/c172-electrical.nas
/var/cvs/FlightGear-0.9/data/Aircraft/c172p/c172p-set.xml
/var/cvs/FlightGear-0.9/data/Aircraft/c172p/Attic/kap140.nas
/var/cvs/FlightGear-0.9/data/Aircraft/c182/c182-set.xml
/var/cvs/FlightGear-0.9/data/Aircraft/c182/Attic/kap140.nas
/var/cvs/FlightGear-0.9/data/Aircraft/c182/Systems/KAP140.xml
/var/cvs/FlightGear-0.9/data/Aircraft/c182rg/c182rg-set.xml
/var/cvs/FlightGear-0.9/data/Aircraft/pa24-250/Attic/kap140.nas
/var/cvs/FlightGear-0.9/data/Aircraft/pa24-250/pa24-250-set.xml
/var/cvs/FlightGear-0.9/data/Aircraft/pa24-250/pa24-electrical.nas

Dave Perry  Roy Vegard Ovesen:

This patch allows all the AC using the kap140 to use one kap140.nas
which includes Roy's move to bool values as well as the check for
power used by the pa24-250. (dp)


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-02-04_06:55:30 (mfranz)
/var/cvs/FlightGear-0.9/data/Aircraft/c172p/Systems/KAP140.xml

Dave Perry  Roy Vegard Ovesen:

This patch allows all the AC using the kap140 to use one kap140.nas
which includes Roy's move to bool values as well as the check for
power used by the pa24-250. (dp)


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-02-04_07:30:10 (martin)
/var/cvs/FlightGear-0.9/data/Aircraft/Instruments-3d/kt70/kt70.xml


Ron Jensen:

Add panel lighting effects to transponder.


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-02-04_07:32:17 (martin)
/var/cvs/FlightGear-0.9/data/Aircraft/c182/c182-set.xml
/var/cvs/FlightGear-0.9/data/Aircraft/c182rg/c182rg-set.xml


Ron Jensen:

Make the night lighting wrap at 1.0 instead of 0.75.


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-02-04_12:06:02 (sydadams)
/var/cvs/FlightGear-0.9/data/Aircraft/dhc2/Nasal/dhc2.nas

fixed some nasal bugs...


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-02-04_14:18:31 (mfranz)
/var/cvs/FlightGear-0.9/data/Aircraft/a4/Models/a4.nas

use function object in setlistener(), not a function call


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-02-04_14:20:45 (mfranz)
/var/cvs/FlightGear-0.9/data/Aircraft/Generic/aar.nas

- reset engines' consumed fuel
- change variable name


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-02-04_16:09:43 (mfranz)
/var/cvs/FlightGear-0.9/data/Aircraft/Generic/aar.nas

- work around broken props.Node.getBoolValue()
- simplification  cleanup


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-02-04_23:51:48 (sydadams)
/var/cvs/FlightGear-0.9/data/Aircraft/dhc2/dhc2-sound.xml
/var/cvs/FlightGear-0.9/data/Aircraft/dhc2/dhc2F.xml
/var/cvs/FlightGear-0.9/data/Aircraft/dhc2/Models/submodels.xml
/var/cvs/FlightGear-0.9/data/Aircraft/dhc2/Models/wake.xml
/var/cvs/FlightGear-0.9/data/Aircraft/dhc2/Nasal/dhc2.nas

Updated float water - handling , more realistic now but haven't solved the 
sideways drift yet
Updated sounds but click sound is gone in OSG version...
Added Melchoir's crash handler to test beaching crash ...


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-02-05_05:27:57 (mfranz)
/var/cvs/FlightGear-0.9/data/Aircraft/bo105/bo105.xml