![]() ![]() I then uninstalled FG and did a reinstall but now I'm getting "no disk in harddrive" error. I deleted the amended joystick.xml file and restored the opriginal but the problem still remained. I have spent most of the day trying to resolve the problem but have instead ended up in a worse muddel. If I did that would I need to make any changes to the joystick file or should it "work out of the box". The obvious choice is MS Sidewinder but I'm sure there are other equally good options, just need to trawl through the xml files and see if I can lay my hands on a matching joystick (will be a used one). However, I am now wondering whether I should accept abandoning the XBOX controller and go for a standard joystick, preferably one that has a preformed xml file in FG. Does FG have any diagnostic software which might show what's going wrong.Īs I had decided that the keyboard option was not for me, the XBOX seemed to offer the chance to avoid the expense of buying a joystick until I had decided FG was OK on my system. Have closed all other applications in case there might have been a conflict but no difference. Have tried it several times with the same result. Unfortunately, I now find that the program sits at the loading scenery stage, so it's a case of one step forward and two steps backward. This would suggest that the controller is being recognised by FG which is a step in the right direction (don't know at this stage which buttons are which but that can come later). Your system and FlightGear will not overwrite it. This will then be used for the first joystick on The second example shows how to load a driver directly to (You can also add a defaultĮntry to the driver to make it the default choice.) These drivers have precedence over already existing drivers The joystick hardware (see output of the js_demo application). Such "named"ĭrivers are only picked up if one of their s matches ![]() The joysticks.xml file resides (first example). entries with paths relative to the directory where I have done as you suggested and below you will see the joystick.xml file content and below that the details from the Help/joystick info pull down which I did after several attempts manage to view. Hi again, sorry to keep coming back but at the moment I am feeling very frustrated. I have assumed that although his was written for a wireless xbox 360 controller and mine is wired this shouldn't make any difference. Therefore, under the PropertyList I have the following line as the first entry ![]() In my data/joysticks/Microsoft folder I have an entry xbox-360.xml which is, as I have said, a copy of the entry posted by zexe modified as required to match the info I receive from Help/Joystick Info and Device Manager. I do not have an Input/Joysticks/Local folder (unless it's hidden). I have edited the PropertyList entry in the joystick,xml file, which in my case is found in FlightGear 2.4.0/data folder to add the last line (shown in bold). Note: not all the buttons use the modifier in this code box.Sorry to be dumb but I am obviously not understanding the xml file entries correctly as the joystick is still showing as default when I run FG. m = 0 is first modifier state (button "0" off) m = 1 is second modifier state (button "0" pressed) Here is the sort of thing I mean, this one nominates button "0" as the modifier near the bottom of the page. So start hunting through the joysticks folder to find one to suit!.sim You can adopt one of the single button modifier scripts from another joystick set up. Then all other buttons, axii can perform 2 different functions. Yes Zexe, You need to make button 0 a modifier. How does one speed up the panning rate and how do you code it? One last thing, I am not sure how to set VIEW_PAN_RATE. Up will zoom in, releasing the zoom will set zoom back to default, down will zoom out, releasing the zoom will set it back to default. Is this possible too? I'd like to try to get axis 7 to be zoom. By pressing and holding the button, the map will stay open, but when I release the button the map will close. I'd like to use these buttons to bring the map out and also close it. Although in reality it is an analog up, down, left, right button, it acts like an axis, and is therefore recognized as axis 6 by the js_demo and not buttons. Is this possible?Īnother idea was using axis 6 on the controller. For the starter(ignition) use combination button 0 and button 2. is it possible to combine two buttons to execute a function? For example, I'd like to set magnetos using the controller by pressing simultaneously button 0 and button 1. After configuring my xbox 360 controller for the past 4 hours, I've noticed how much fun it actually is to get things to work.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |