Re: [Flightgear-users] Can't Configure Joystick

2004-12-23 Thread Sid Boyce
Dave Martin wrote:
On Wednesday 22 Dec 2004 11:37, Sid Boyce wrote:
With a XP2200+, it was normal, but with
this XP3000+, it was a nightmare ride.

Is that a Gameport joystick? - Would have thought there was an upper limit on 
polling at least for a gameport (baud rate) but for USB I'm not so sure.

Do they behave nicely in jscal / jstest?
The CH Products yoke and pedals are USB. jstest works, jscal goes as far 
as detecting the aeileron control, then does nothing when you press any 
other button.
Regards
Sid.
--
Sid Boyce  Hamradio G3VBV and Keen Flyer
=ALMOST ALL LINUX USED HERE, Solaris 10 SPARC is just for play=

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


Re: [Flightgear-users] Can't Configure Joystick

2004-12-23 Thread Sid Boyce
Sid Boyce wrote:
Dave Martin wrote:
On Wednesday 22 Dec 2004 11:37, Sid Boyce wrote:
With a XP2200+, it was normal, but with
this XP3000+, it was a nightmare ride.

Is that a Gameport joystick? - Would have thought there was an upper 
limit on polling at least for a gameport (baud rate) but for USB I'm 
not so sure.

Do they behave nicely in jscal / jstest?
The CH Products yoke and pedals are USB. jstest works, jscal goes as far 
as detecting the aeileron control, then does nothing when you press any 
other button.
Regards
Sid.
aeileron should read elevator.
Regards
Sid.
--
Sid Boyce  Hamradio G3VBV and Keen Flyer
=ALMOST ALL LINUX USED HERE, Solaris 10 SPARC is just for play=
___
Flightgear-users mailing list
Flightgear-users@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-users
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-users] Can't Configure Joystick

2004-12-22 Thread Sid Boyce
Jeremy Johnson wrote:
On Tuesday 21 December 2004 10:31 pm, Mr. Nigel Chuckletrousers wrote:
I'm trying to get a Logitech Attack 3 to work with FlightGear, but
things aren't going as FlightGear.org's documentation suggests.
Whenever I run js_demo and jstest, the joystick is recognized, so at
least that works correctly.
I'm running this on my dad's SuSE 9.1 Linux box, and SuSE seems to
treat FlightGear differently than other distros, as it has a
custom-made SuSE package for FlightGear (not the standard-issue rpm or
compiled-from-source), and many paths are different. For example, the
instructions say to run cd /usr/local/FlightGear/Input/Joysticks,
but in SuSE, one must run cd
/usr/lib/FlightGear/data/Input/Joysticks. This may have some effect
on why things aren't acting correctly:
Whenever I run fgjs, everything works fine to configure the joystick
to work. However, it's supposed to create the file fgfsrc.js, which
cannot be located anywhere on the hard drive. Has anyone else had a
problem with it not producing a configuration file? And could somebody
please assist me? Thank you.
I have no knowledge of SuSE.
I installed from source.
For me fgjs creates fgfsrc.js in the current directory. Since I ran it from
my home directory that's where my file was created. If I tried to run it
from a directory for which I didn't have write permissions -- who knows?
I ended up manually creating  an xml file for my joystick:
I added an entry for my_joystick.xml to /usr/share/FlightGear/joysticks.xml
and then created my_joystick.xml and added it 
to /usr/share/FlightGear/Input/Joysticks/my_joystick's_manufacturer/

I based my_joystick.xml on that for a simple CH-compatable stick
with 4 axis and 4 buttons in /usr/share/FlightGear/Input/Joysticks/ which had 
a similar number of buttons, sliders, axis, triggers, etc.

When the SuSE package gets installed, I never used it. I grab all the 
sources and build it myself. Calibration of the CH yoke and pedals 
assigns the elevator, then does not respond to any other buttons. I've 
had to cut and try values in the xml file to get the sensitivity of 
controls to react properly, e.g with the default file, a slight input of 
rudder on the take-off run would cause it to veer off the runway 
rapidly, turns and climbs were way out of true. It would seem they 
depend on the processor speed. With a XP2200+, it was normal, but with 
this XP3000+, it was a nightmare ride. I wonder if there could be a way 
for fgfs to take a cue from the data in /proc/cpuinfo.
# fgjs
Found 2 joystick(s)
Joystick 0 has 7 axes
Joystick 1 has 3 axes
Move the control you wish to use for elevator

Assigned axis 1 on joystick 0 to control elevator
Press any button for next control
Regards
Sid.
--
Sid Boyce  Hamradio G3VBV and keen Flyer
=LINUX ONLY USED HERE=
___
Flightgear-users mailing list
Flightgear-users@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-users
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-users] Can't Configure Joystick

2004-12-22 Thread Dave Martin
On Wednesday 22 Dec 2004 11:37, Sid Boyce wrote:
 With a XP2200+, it was normal, but with
 this XP3000+, it was a nightmare ride.

Is that a Gameport joystick? - Would have thought there was an upper limit on 
polling at least for a gameport (baud rate) but for USB I'm not so sure.

Do they behave nicely in jscal / jstest?

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


[Flightgear-users] Can't Configure Joystick

2004-12-21 Thread Mr. Nigel Chuckletrousers
I'm trying to get a Logitech Attack 3 to work with FlightGear, but
things aren't going as FlightGear.org's documentation suggests.
Whenever I run js_demo and jstest, the joystick is recognized, so at
least that works correctly.

I'm running this on my dad's SuSE 9.1 Linux box, and SuSE seems to
treat FlightGear differently than other distros, as it has a
custom-made SuSE package for FlightGear (not the standard-issue rpm or
compiled-from-source), and many paths are different. For example, the
instructions say to run cd /usr/local/FlightGear/Input/Joysticks,
but in SuSE, one must run cd
/usr/lib/FlightGear/data/Input/Joysticks. This may have some effect
on why things aren't acting correctly:

Whenever I run fgjs, everything works fine to configure the joystick
to work. However, it's supposed to create the file fgfsrc.js, which
cannot be located anywhere on the hard drive. Has anyone else had a
problem with it not producing a configuration file? And could somebody
please assist me? Thank you.

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


Re: [Flightgear-users] Can't Configure Joystick

2004-12-21 Thread Jeremy Johnson
On Tuesday 21 December 2004 10:31 pm, Mr. Nigel Chuckletrousers wrote:
 I'm trying to get a Logitech Attack 3 to work with FlightGear, but
 things aren't going as FlightGear.org's documentation suggests.
 Whenever I run js_demo and jstest, the joystick is recognized, so at
 least that works correctly.

 I'm running this on my dad's SuSE 9.1 Linux box, and SuSE seems to
 treat FlightGear differently than other distros, as it has a
 custom-made SuSE package for FlightGear (not the standard-issue rpm or
 compiled-from-source), and many paths are different. For example, the
 instructions say to run cd /usr/local/FlightGear/Input/Joysticks,
 but in SuSE, one must run cd
 /usr/lib/FlightGear/data/Input/Joysticks. This may have some effect
 on why things aren't acting correctly:

 Whenever I run fgjs, everything works fine to configure the joystick
 to work. However, it's supposed to create the file fgfsrc.js, which
 cannot be located anywhere on the hard drive. Has anyone else had a
 problem with it not producing a configuration file? And could somebody
 please assist me? Thank you.

I have no knowledge of SuSE.
I installed from source.
For me fgjs creates fgfsrc.js in the current directory. Since I ran it from
my home directory that's where my file was created. If I tried to run it
from a directory for which I didn't have write permissions -- who knows?

I ended up manually creating  an xml file for my joystick:
I added an entry for my_joystick.xml to /usr/share/FlightGear/joysticks.xml
and then created my_joystick.xml and added it 
to /usr/share/FlightGear/Input/Joysticks/my_joystick's_manufacturer/

I based my_joystick.xml on that for a simple CH-compatable stick
with 4 axis and 4 buttons in /usr/share/FlightGear/Input/Joysticks/ which had 
a similar number of buttons, sliders, axis, triggers, etc.

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