Re: [Flightgear-devel] enable-auto-coordination

2008-01-30 Thread Tiago Gusmão
Bohnert Paul wrote:
 Hi All,
 
 I found  --enable-auto-coordination  does not work with CH Pro Pedals.  
 The rudder jumps back and forth between center and aileron position.  It 
 works as expected with the pedals disconnected.
 
 I have my joy stick twist axis commented out.
 
 With  --enable-auto-coordination  I expect the rudder to follow the 
 aileron and ignore all other inputs.
 
 Would someone please take a look at this.
 
 OS Fedora 8.  FlightGear CVS.

Hi

The likely problem is that the pedals are still generating some little 
input (noise) and when several devices control the same axis, the last 
input provided is used (cat /dev/input/js(?) to watch input, ctrl-c to 
exit). Either disable them, edit the configuration file and remove the 
axis or change the name or best of all, disable auto-coord and use the 
pedals all the time :)

Cheers,
Tiago

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] enable-auto-coordination

2008-01-30 Thread Melchior FRANZ
* Bohnert Paul -- Wednesday 30 January 2008:
 It works as expected with the pedals disconnected. 

You can avoid that by setting  --prop:input/joysticks/js[1]=0
(This isn't an Easter Egg. The 0 is only an invalid joystick
configuration, but fgfs refuses to overwrite it nevertheless,
so joystick #1 will be ignored.)

Apart from that I agree with Tiago's analysis.

m.

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


[Flightgear-devel] Inconsistent FGNetFDM size?

2008-01-30 Thread wsacul
I tried the option to write out the native_fdm to a file from the Windows
1.0 release of flightgear, and loaded the result into matlab.   Initially I
thought there was a structure with a regular size of 408 bytes, and I was
able to extract altitude correctly from the first few dozen instances, but
that seemed to change as the simulation progressed and it all got out of
sync.  Is there a byte or two being sent in addition to the FGNetFDM
structure that is not sent every update?

Thanks,

Luke
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Inconsistent FGNetFDM size?

2008-01-30 Thread Curtis Olson
You may want to double check that you are reading and writing the file in
binary mode on windows.  This doesn't make a difference on linux where the
feature was developed, but dos's carriage return/new-line translation might
be biting you?

Curt.


On Wed, Jan 30, 2008 at 4:03 PM, wsacul [EMAIL PROTECTED] wrote:

 I tried the option to write out the native_fdm to a file from the Windows
 1.0 release of flightgear, and loaded the result into matlab.   Initially
 I thought there was a structure with a regular size of 408 bytes, and I was
 able to extract altitude correctly from the first few dozen instances, but
 that seemed to change as the simulation progressed and it all got out of
 sync.  Is there a byte or two being sent in addition to the FGNetFDM
 structure that is not sent every update?

 Thanks,

 Luke

 -
 This SF.net email is sponsored by: Microsoft
 Defy all challenges. Microsoft(R) Visual Studio 2008.
 http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
 ___
 Flightgear-devel mailing list
 Flightgear-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/flightgear-devel




-- 
Curtis Olson: http://baron.flightgear.org/~curt/
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] trees

2008-01-30 Thread till busch
hi stuart,

i have missed you on irc today. and i wanted to tell you that indeed the 
second patch is much better in terms of memory usage. it saves 80 megs of 
allocations compared to your first patch :-)

and considering it looks even prettier than the first one... congratulations!

-till

On Monday 28 January 2008, Stuart Buchanan wrote:
 The current patch is a bit better for memory usage IIRC, but it is still
 quite hefty - a side-effect of generating all the trees at once for the
 tile.

 -Stuart

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Inconsistent FGNetFDM size?

2008-01-30 Thread wsacul
Files generated with flightgear in Linux don't give me any problems, it's
just the official windows build.

On an unrelated note, the sim behaves strangely when the initial position is
set above 64,000 feet.  The plane will drop as I would expect but then stops
(I think right about 64,000 feet, but I haven't checked that)- is there an
altitude limit to jsbsim?

Thanks,

Luke





 You may want to double check that you are reading and writing the file in
 binary mode on windows.  This doesn't make a difference on linux where the
 feature was developed, but dos's carriage return/new-line translation
 might
 be biting you?

 Curt.


 On Wed, Jan 30, 2008 at 4:03 PM, wsacul [EMAIL PROTECTED] wrote:

  I tried the option to write out the native_fdm to a file from the
 Windows
  1.0 release of flightgear, and loaded the result into matlab.
 Initially
  I thought there was a structure with a regular size of 408 bytes, and I
 was
  able to extract altitude correctly from the first few dozen instances,
 but
  that seemed to change as the simulation progressed and it all got out of
  sync.  Is there a byte or two being sent in addition to the FGNetFDM
  structure that is not sent every update?
 
  Thanks,
 
  Luke

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel