* Grayham Smith -- Wednesday 19 January 2005 03:38:
> I have recently purchased FlightGear V0.9.6 (win32) on CD and installed it
> some 5 days ago.
[...]
> All went well for 3 days using an old late-80's Gravis joystick.
[...]
> I purchased a new Logitech Attack 3 joystick, uninstalled the old one and
> installed the new one.
> From that time onwards FlightGear has refused to load.
> [...]
> "js_demo" reports both joysticks accurately and I have tried out "fgjs" with
> success.
This version had still a bug that crashed fgfs if the joystick config file
defined
more axes/buttons than the js actually has. Ideally, as Erik already said, you
would
write a configuration file for this joystick. It's not really difficult. Just
copy
the closest of the existing congfigs, change the name in the <name> tag to what
js_demo.exe reports and add the path to $FG_ROOT/joysticks.xml. A text editor
is all
you need.
Alternatively, you can find out which js fgfs tries to use, and remove all axes
and buttons that your js doesn't have. Running C:\> fgfs.exe
"--log-level=info"|more
should tell you the used joystick. You get something like this:
Looking for bindings for joystick "SAITEK CYBORG 3D USB"
Trying "Analog 4-axis 4-button joystick"
Trying "SAITEK CYBORG 3D USB"
Found bindings
I don't claim that this *is* your problem, but it's a good chance.
m.
_______________________________________________
Flightgear-users mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-users
2f585eeea02e2c79d7b1d8c4963bae2d
