I have installed FG 0.9.3 and also run the fgfs.exe joystick config and copied fgfsrc.js to the Flightgear-0.9.3 folder.I cannot control the view, which swings around out of control. Nor can I use the joystick controls insofar as I can tell by adjusting the throttle the engine note does not change.The view is initially ahead with the panel and runway showing. But immediately it swings up and left and I can only perceive moving gray patches from then on.This occured when I first started FG and does not change whether I select joystick or keyboard as the input.Nigel

Nigel,What type of connection does your joystick use? USB or Serial (the 9 pin 'D' shape connector)?Also, Are you running Windows XP or some other system, and what are your video card driver and memory (DRAM and Video memory) amounts?Tom C.

I have an old style 'gameport' joystick.I have Win XP Pro with all latest drivers and patchesThe video card has 64mb (I don't have the DRAM figure).Did I explain the situation clearly? I would imagine it was affected by software or drivers.It looks like the view (pan/tilt) control is offset so giving and immediate change of view. (tho' strangely the cockpit view doesn't come into view again!)Also as I have been thru' the joystick config why doesn't at least the throttle affect the engine?Nigel

Hi thereI believe I had the same problem. The hat on joystick is an axis and it seems it's not defined correctly.I've followed the procedure jcomm described and it works fine now. No more "rotating out of control view".Quoted from his post :"1) Run FlightGearbinWin32js_demo.exeFirst Column refers to Joystick ButtonsSecond Column is Joy Axis 0Third is Joy Axis 1,etc..."Doing that I noticed my hat axis were 6 and 7 and not 5 and 6 as described in the xml file corresponding to my Thrustmaster joysticMore of jcomm's post: "3.1) Open the xml file of the joystick that better suites my joystick, under FlightGeardataInputJoysticks.Mine is under the Logitech directory - "Extreme-3d-win.xml".3.2) Copy your modified ".xml" file over dataInputJoysticksjoystick.xml and you're ready to go."I use xml Notepad to edit those .xml filesAll I did was rename the Hat axis numbers for my own Thrustmaster joystick to cure the constantly rotating view. Axis 5 becane 6 and axis 6 became 7. T'was that simple.You might want to refer to Joystick issues topic up here if you need more reading.Q!

Thanks Q I will give that a try. I was about to give up on it and be very annoyed. The trial copy worked fine so I bought it and the bought version seemed permanently flawed in this way.Nigel

> The trial copy worked fine so I bought it>and the bought version seemed permanently flawed in this way.Just wondering where you bought flightgear from / how much you paid. I've always found it to be a free download (unless you paid for the media)?Cheers,Alex

Please excuse my forgetfulness. I was getting confused between this and Xplane which I bought a few weeks before.Indeed FG was a free download!But also I did have the view problem on FG!Nigel

Q,I finally got around to trying your solution for my problem, but it doesn't seem to make any difference.I found that I didn't have a joystick.xml set-up, so maybe I missed some of the installation instructions.I copied the appropriate one for my stick into the Flightgear folder (not the dataInputJoysticks you suggested). The hat axes are correct in that XML for my stick.However the view still swings up and left as soon as the cockpit appears on the screen. Nothing seems to stop it.Watching it for somewhile no cockpit details pass thru' the view again. So I assume that it is swinging upto the roof and then just rotating round a point on the cabin roof.Any other help would be gratefully received.Nigel

Bonjour NigelI'm sorry to hear you're still having problems. I'm enjoying FligtGear big time since I got my stick working. It's really worth the extra effort, hang in there. Keep in mind I am running FG 0.94 (-: FlightGear uses the data in this file "joystick.xml" found in C:Program FilesFlightGeardataInputJoysticksDefault (on my system) to get the joystick going.Any joystick file you find or edit (like I did for my Thrustmaster) needs to be copied to that folder and must be renamed to "joystick.xml" for the joystick to work.If that is what you did and it still isn't working... I'm in the blue. I can only recommend starting over with a fresh cup of coffee.When editing those .xml file, you need to be extra carefull to not type in any unwanted characters or the data in that section won't be recognised.Remember, you must use the info given by "js_demo.exe" : (C:Program FilesFlightGearbinWin32) and enter it in the Saitek joystick file you are using as a starter.First column gives up joytick button numbers,the 2nd column is AXIS 0, :-doh (carefull, can be a catch)the 3rd one is AXIS 1,and so on...When I edited mine I only replaced the hat axis numbers (6 and 7) by the ones "js_demo.exe" came up with (5 and 6) and that's what cured the constantly rotating view.As you see it's a -1 correction, so that AXIS 0 might have caught other people :-hahAs I mentionned in another post, I use XML Notepad to edit xml files, the way it displays the data makes it very easy to edit. It's free and is very easily found with Google.In case my instructions seem unclear, I refer you to jcomm's post with clearly labeled steps. They worked fine for me :)http://forums.avsim.net/dcboard.php?az=sho...esg_id=85&page=I really hope this helps, but post again if it doesn't. OK?Best of luck :-smile12Q!

Thanks for your reassurance on the proper location for the XML file.Fortunately there is a file for my exact stick, so I will move it to the new location and give it another whirl.I wonder tho' whether this is going to do anything for the problem I see (tho' you said you had something similar). If I am not moving the joystick there shouldn't be anything to cause the eyepoint movement!Nigel

>I wonder tho' whether this is going to do anything for the>problem I see (tho' you said you had something similar). If I>am not moving the joystick there shouldn't be anything to>cause the eyepoint movement!If the axis isn't well defined, FlightGear will look for something to do with it anyhow. Since this is considered an axis, it will rotate.Have you printed keyboard commands? v/V will cycle views, try going external and see if all the control surfaces work OK.If you need to Zoom. it's z and Z = zoom in/out.From what I read at http://www.flightgear.org/version.html Version 0.94 update history says : Add support for Logitech Extreme 3D Pro, thrustmaster top gun afterburner USB, Logitech WingMan Force 3D, Logitech Extreme 3D Pro USB, and Microsoft SideWinder 3D Pro joysticks"I don't know if the various joysticks .xml files where already there in 0.93 but the "support" wasn't. I'm clueless. Perhaps worth a download or it's only a typo and you're on 0.94?Hope this helps a bit more. All I am really sure about is that doing what JC said worked fine for me, but I'll admit it sounds easier than it really is for most Windows users. I had to give it a few shots to clear everything out, but it's really worth it. I ended up with 3 functions on Hat, thamks to 2 already programmed modifier buttons,view, trim, mixture control and 18 button commands. Neatest set up ever :)Q!PS. Once you get it going, it will be worth printing out joystick button commands config ;)

Q,Thanks again for your encouragement.I am sure that I have 0.93 and I downloaded it around Apr5.My joystick, whilst included in the choices of XML it is the old gameport version. Hopefully that isn't where I am going wrong. But I do remember, checking right at the start, that the throttle on the stick did change the engine note. Also using the joystick set-up prog that responds to the buttons. Tho' on the pan view left and pan view right, if I move the hat switch, it shows 'skipped'.With the weekend around the corner I have no excuse for not nailing this.Nigel

Q,Still no joy. I moved the joystick.xml to the correct folder (overwriting the default file there). But still the eyepoint rotates.Changing the view as you suggested shows the a/c taxiing in a small circle on the threshold and the eyepoint rotating looking straight down. With the joystick still selected I found the brake (fire trigger) stopped the plane (but I got a stall warning sound!). But the top down view was still spinning. If I altered the rudder (turning the joystick handle) the engine speeded up!I reran the joystick config program. But afterwards the controls still worked, the wrong way!In the config that opens before FG runs I selected keyboard instead of joystick, and it still rotates!I will try d/l 0.94 later and see if that cures anything. Not much left to try after that.Nigel

Hi thereYes, I think it's a very good idea to get 0.94, it carries many upgrades/improvements. However I still get the impression you're missing something.The joystick config program you refer to (js_demo.exe) does not configure anything at all. It only tells you what axis and button labels (numbers) are.You are the one configuring the joystick when you enter the correct numbers in the xml file (saitek in your case) you use as a starter, copy and then rename it to joystick.xml and then move it to the correct folder.When you look at js_demo.exe running, the 1st column is button ID's (numbers) When you press buttons, you'll see wich ID they each have.The 2nd column is axis 0 so when you move your stick around you will see what axis (usually ailerons but not always) is "Axis 0", the next column "Axis 1" should then be elevator, the next 2 are either rudder or throttle, wich are obviously mixed up according to what you tell me.If you aren't much comfortable with editing xml files, you could read up your joystick data with js_demo.exe, post it in a message here. I then could edit the xml file you need and e-mail it your way afterwards.Q!

Q,Thanks for your last and your kind offer.I should have been specific that I was using the program fgjs which brings up a DOS window and prompts for each control to be assigned a jostick button.Even tho' I chose the matching XML for my joystick, the controls were wrong. So I ran fgjs to attempt to right that.I will go for the latest version later today.Nigel