> -----Original Message-----
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of 
> Melchior FRANZ
> Sent: Wednesday, January 19, 2005 7:59 PM
> To: [email protected]
> Subject: [Flightgear-users] Re: Loading Problems
> 
> 
> * 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.

Thank you Franz,

I have created a file called "gravis.xml" which contains only the axes/buttons 
Which the Joystick has and placed a name line in the file similar to other files
But with the name that "js_demo" reported.

What I don't understand is how do I tell FlightGear where to find "gravis.xml"

I guess this needs to be in "joysticks.xml"

Please clarify

I tried running "fgfs with the params you gave but it reports the following:-

Base package check failed ... Found version [None] at: \FlightGear
Please upgrade to version 0.9.6

I will followup the fgfs error and try that again

Grayham.............


_______________________________________________
Flightgear-users mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-users
2f585eeea02e2c79d7b1d8c4963bae2d

Reply via email to