Martinlest Posted January 31, 2016 Report Share Posted January 31, 2016 Hi, I have searched and searched through the pdf files and not been able to get this to work. I'd really appreciate some help. I would like my Saitek X52 to control flaps and spoilers in the TinMouse 737-200, the way it does with all other aircraft and have tried using FSUIPC (v.3.999z2)... to achieve this. I don't get very far I'm afraid - from what I have read and been told, I go to the Buttons + Switches tab, check the box 'Profile Specific?' and carry on from there. But from that tab, clicking on most buttons and switches on the X52 does nothing at all in the FSUIPC UI; only a couple of hat switches bring up any numbers in the boxes, some cause a 'ping' error warning sound (like the one made in Windows when for instance, you try to close a programme window when there is a dialogue box created by that window still open): the rest do nothing at all (the X52 works fine in the sim though). Why might FSUIPC not be 'seeing' most of the X52's buttons and switches? Has anyone else set this up for the TM 732? I wonder whether I could just copy the entries directly into the ini file, as I don't seem to be able to access the UI properly. Thanks for any help! Martin Link to comment Share on other sites More sharing options...
Pete Dowson Posted February 7, 2016 Report Share Posted February 7, 2016 Why might FSUIPC not be 'seeing' most of the X52's buttons and switches? FSUIPC only recognises the first 32 buttons on any joystick device, numbered 0-31 in FSUIPC, 1-32 in FS. Pete Link to comment Share on other sites More sharing options...
Martinlest Posted February 7, 2016 Author Report Share Posted February 7, 2016 Hi. It is not seeing any, just a couple of hat switches. If it saw 31, I'd be fine! :smile: All the buttons work fine in FS and in the device control panel. Link to comment Share on other sites More sharing options...
Pete Dowson Posted February 7, 2016 Report Share Posted February 7, 2016 Hi. It is not seeing any, just a couple of hat switches. If it saw 31, I'd be fine! :smile: All the buttons work fine in FS and in the device control panel. Sounds like the device doesn't have an assigned Windows ID. That seems to happen a lot in Win8 and Win10. I've managed to program around it in FSUIPC4 for FSX etc, but it isn't possible for FSUIPC 3 (and not just because development for that is discontinued after 12 years). See the FAQ subforum thread entitled Fixing joystick connections not seen by FSUIPC Pete Link to comment Share on other sites More sharing options...
Martinlest Posted February 7, 2016 Author Report Share Posted February 7, 2016 OK, I'll check that in the FAQ. (I run Windows 7 x64 though, not Win8 or Win10). Many thanks. Link to comment Share on other sites More sharing options...
Martinlest Posted February 8, 2016 Author Report Share Posted February 8, 2016 Installed the programme and made the X52 No.1 in the list. No change, so I tried a few other positions (I only have the X52 and a Nostromo N52 keypad there). Still FSUIPC sees only a couple of hat switches. :???: I guess I could try reinstalling FSUIPC?? Link to comment Share on other sites More sharing options...
Pete Dowson Posted February 8, 2016 Report Share Posted February 8, 2016 Installed the programme and made the X52 No.1 in the list. No change, so I tried a few other positions (I only have the X52 and a Nostromo N52 keypad there). Still FSUIPC sees only a couple of hat switches. :???: I guess I could try reinstalling FSUIPC?? These hat switches, are they on the same device as the buttons and axes you are trying to access? Because if FSUIPC sees the device it will be reading the entire set -- 8 axes. 4 hats and up to 32 buttons. All of them are read together, they can't be separated. if they are not detected then they don't appear to be changing. Are you sure you haven't got some other driver or software reading these devices? That's the only cause i know of for this sort of thing. Pete Link to comment Share on other sites More sharing options...
Martinlest Posted February 8, 2016 Author Report Share Posted February 8, 2016 Are you sure you haven't got some other driver or software reading these devices? That's the only cause i know of for this sort of thing. OK, yes, you are right, I have been trying to have FSUIPC read the device buttons with the profile active (in other words, FS9 is reading the device). Now I have switched off the FS9 profile, all the buttons now create numbers in the FSUIPC boxes. Many thanks Pete, Martin Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now