I have a registered copy of FSUIPC v4.929 and I am not able to get any response when trying to assign axis to the module. I have looked over the users guide and the advanced users guide and it says to press the rescan button and then move an axis. The axis that moves first is the one that will be picked up and displayed for it to be used. I have tried many times to assign different axes with no luck. I have removed the.dll file and started with a brand new install of FSUIPC and nothing. Replacing a DLL with an identical DLL rarely achieves anything! I might join on this thread as I'm facing quite a similar issue.I've been using FSX within Windows 8 since a good amount of time.

We've put everything you need to get started with your Flight Multi Panel right here. If you still have questions browse the topics on the left. Most Popular. Troubleshooting; Reference; How to; Setup. Most Popular. Saitek device driver installer does not complete. If you're having a.

And was using the X52 Pro until recently which always worked perfectly, and thanks to FSUIPC never lost the controler during flight, wether small or lengthy, while FS would lose them randomly, but usually very quickly. So I've wanted to upgrade my things a little and I've gone to get a X55, because I knew all the things around the saitek software and never had any trouble with their controlers ever since I started with an X45. And also have a rudder pedal set which works nicely. So the problem comes with the Rhino, but only a part of it, which is the stick part. I can get the throttle working just fine and assign it's axes without any problem. But as for the stick it's completely unseen within FSUIPC interface.

I can move the stick all that I want it won't detect anything. While it works perfectly for the throttle part, and still work perfectly for the rudder too. So before making the test above I deleted the FSUIPC.ini file so I would make sure it would be clean, and it did not changed a thing so I did apply the logging option, and have placed the resulting file here: (the ini is included as well) I did try the controller on other sim like Take On Helicopter or DCS A10C and for neither there were an issue.

Also as long as FS did not ditch the controlers, if I get in the FSX command options and try to assign an axis to this stick it works fine. I hope you might have tome pointers to sort the issue:) Cheers. So the problem comes with the Rhino, but only a part of it, which is the stick part. I can get the throttle working just fine and assign it's axes without any problem.

But as for the stick it's completely unseen within FSUIPC interface. I can move the stick all that I want it won't detect anything. While it works perfectly for the throttle part, and still work perfectly for the rudder too.

The log is rather overfull with useless repeats of errors on unconnected devices, so I'm making a little interim FSUIPC update which doesn't repeat those. However, the log does certainly show that FSUIPC is successfully reading all three devices fine. Dowson, Thank you for such a speedy reply.

I have looked through the log from last night and did not see an error in that file. I have added the lines under general to allow the extra logging and there is more in the log file now. However when I try and copy and paste it locks up the web page as the file really long with a bunch on repeating errors. I have tried to push buttons on the buttons+keys page and did not get any feedback there either. I did not stay in the FSUIPC page a long time as there was not any response coming back from the module, done the test and got the log. I am running FSX in compatibility mode to Windows 7 and have it installed directly to the root folder instead of installed in the Program files area.

Not sure if that makes a difference but thought it might be pertinent. Here is the Log file: ********* FSUIPC4, Version 4.929 by Pete Dowson ********* Reading options from 'C: FSX Modules FSUIPC4.ini' Running inside FSX on Windows 7 Module base=66040000 User Name='Jonathan Dowdy' User Addr=' FSUIPC4 Key is provided WIDEFS7 not user registered, or expired 1092 System time = 10: FLT path = 'C: Users pfcdo_000 Documents Flight Simulator X Files ' 1138 Trying to connect to SimConnect Acc/SP2 Oct07. 1170 FS path = 'C: FSX ' 1544 #### Initialising Dlrectinput Axis Scanning. 1544 Trying: 'HKCU SYSTEM CurrentControlSet Control MediaProperties PrivateProperties DirectInput VID_06A3&PID_0BAC Calibration 0' 1544 Found correct joystick Id 0 1544. And a 'GUID' value 1560 DirectInput8Create failed, return = 800 Trying: 'HKCU SYSTEM CurrentControlSet Control MediaProperties PrivateProperties DirectInput VID_06A3&PID_0763 Calibration 0' 1560 Found correct joystick Id 1 1560. And a 'GUID' value 1591 DirectInput8Create failed, return = 800 Trying: 'HKCU SYSTEM CurrentControlSet Control MediaProperties PrivateProperties DirectInput VID_06A3&PID_0C2D Calibration 0' 1591 Found correct joystick Id 2 1591. I have looked through the log from last night and did not see an error in that file.

I have added the lines under general to allow the extra logging and there is more in the log file now. However when I try and copy and paste it locks up the web page as the file really long with a bunch on repeating errors. Yes, I'll be uploading an interim update to stop those repeating unnecessarily. Did you see the other report, above, about a similar (but different) problem, and my reply? Your case is certainly different. Windows DirectInput is returning an error, so that FSUIPC cannot read any of the devices.

You say you have the throttle and rudder working, but there are no assignments in your INI file, so I'm not sure what you mean by that. Can you clarify? You apear to have no button assignments either, and you haven't answered the question about whether your buttons are seen in FSUIPC or not. I've not reassigned things at all for the test as I deleted the FSUIPC ini file to make sure it was clean. What I mean by that is that axis from the rudder and throttle are detected in the axis assignment window in the FSUIPC options. And I've the same issue with the buttons, Throttle buttons push are detected by FSUIPC but those from the stick don't do a thing and are not detected in FSUIPC. On both case the Joy/Axes or Joy/button window stay empty for any stick action and do fill on throttle actions.

Do you have some Saitek software installed? The log definitely shows that FSUIPC sees the device and is reading the values using the standard Windows interface without any problems. It's just that the values are stuck at zero. Yes both drivers and softwares are installed. Just the same way as they are for the rudder and as I had done with my X52 Pro. I'll try your suggesion this evening, I think I had tried that but only then reinstalled drivers and software, so I should remove all the occurences of the hardware in the windows manager, removing the pilot for each, remove the software, unplug everything.

Reboot and then plugin the stick and try to get it working without doing anything or installing anything. Is that correct? DirectInput8Create failed, return = 80040154 So I searched for all Directinput8 files and found only one. Sade Stronger Than Pride Rarlab.

It was found in the main FSX folder so I deleted it. I have no idea how it got there, my guess is it was tagged in with a freeware addon I installed at some point. I deleted it out and I can now get axis assignment information, as well as Button + Switches Assignments. Thanks for your help with this I am going to see if I can get things set up with all FSUIPC controls and get up in the air again. It seems the DirectInput8 file was blocking information from getting to the module. Relieved, Jonathan Dowdy Edited March 22, 2014 by Jonathan Dale Dowdy.

So I searched for all Directinput8 files and found only one. It was found in the main FSX folder so I deleted it. I have no idea how it got there, my guess is it was tagged in with a freeware addon I installed at some point. I deleted it out and I can now get axis assignment information, as well as Button + Switches Assignments.

Thanks for your help with this I am going to see if I can get things set up with all FSUIPC controls and get up in the air again. It seems the DirectInput8 file was blocking information from getting to the module. I've heard of DX video modules in the FS folder messing things up on the graphics front. But this is a first for me with DirectInput. Thanks for letting me know!

I'll bear this one in mind! Ok I did try removing everything but it's still the same. Though I can't be sure it really properly deleted everything. I've tried to find a way to clean properly but did not find any I check the box to remove driver too on deleting items in the windows hardware manager, and so now when I plug they don't appear in the user interface part, and I have two hardwares that have the yellow exclamation mark which are Saitek Bus which I believe ust be the Throttle and the Stick. But that is still the samething as long as FS sees it there is no problem for FS axis assignement, but still invisible for FSUIPC. And as previously the throttle is here and working just fine and nothing from the stick. But that is still the samething as long as FS sees it there is no problem for FS axis assignement, but still invisible for FSUIPC.

And as previously the throttle is here and working just fine and nothing from the stick. I'm pretty sure i must be a Windows problem somewhere -- registry or drivers. FSUIPC uses pretty much the same facilities in Windows as FSX, but probably a different version level - DX8 instead of DX9 I think. But all updates to DX are backwards compatible (else when DX10, DX11 etc came out and got installed FSX etc wouldn't work). With this in mind, I would have advised trying to repair Windows -- maybe update or reinstall the current DirectX package. But one thing which contradicts all this is that some devices are detected, which in turn points away from DirectX problems and straight back at the way the devices are defined to Windows -- i.e.

I don't know how you'd sort that out. Is there no help on the Saitek forum at all? FSUIPC can't really do anything unless it sees the devices, and it evidently doesn't see all of them. I'll try and see things on staitek side, but there is very little activity on their forums.

I've a ticket with support but no real answer yet, so gonna check on that. The DirectX websetup says everythign is up to date so nothing on that side either. I'll keep searching there must be something somewhere as just one is not visible and only in FSX and the Windows calibration. Inside any other sim I've tried they are both detected fine. And while testing I don't know why but I had once an opposite situation where the stick would work and the throttle would not be. Allright I might have made some progress though surprising enough, and that seemed both unrelated to either Saitek or DirectX.

While searching for joystick test application, I did find a small application called JoyIDs which purpose is to change the device ids for the joysticks. In the last trials I had the throttle in #1, the joystick in #2 and the rudder pedal in #3. I have previously reinstalled the official drivers too, which was not fixing anything.

Having only the stick not working I changed it's id to #12, not chose really specifically, just wanted to change, and surprisingly enough windows started to see the axis and button in the calibration menu, as well as FSUIPC within FSX. Not sure at all of what caused this though, but looks fixed, but interesting to keep in my mind. I tried rebooting the PC it worked,as well as unplugging, rebooting and plugging again and it's still there, I believe I might have solved that issue. Having only the stick not working I changed it's id to #12, not chose really specifically, just wanted to change, and surprisingly enough windows started to see the axis and button in the calibration menu, as well as FSUIPC within FSX.

I think that seems to prove a Registry problem, because it is the registry entries for a device which determine that joystick ID. The actual IDs were seen be FSUIPC before (hence the Joy stick identities in the INI file), but then they didn't respond using the associated data.

Yes don't kow what is going on but the stick is actually on the ID 11 both on the joyids program and on the FSUIPC axis assignement. I do wonder if there might not be some 'virtual' device with the X55 as Saitek through it's new control panel allow a lot of alibration, deadband, saturation, curves and all. Maybe the 14 is the raw input that Saitek then takes and passes to Dx through the 11 ID, though it would do it only for the stick which would be strange. I've also fixed the throttle issue through one of your other post with the UseAxisControlsForNRZ=Yes option. Looks like I'm all set now. I hope it'll stay like this:) Thanks a lot for the support!:) Edit: just a little addition when checking on the DX Input page there are also two sticks listed which concurs with FSUIPC detections though th esecond one have 0 id, and I see the workign one with it's 11 id Edit 2: Made a thread on the AVSIM community forum on the hardware section so it might help others facing the issue.

Hiya, and sorry to resurrect an older thread, but I just got a Saitek X55 HOTAS and I've run into the same problem with the stick not being recognised. It works fine in DCS World, but trying to program in FSX using FSUIPC has been impossible. Rpg Maker Xp Postality Knights Edition Enhanced. I've opened a ticket with MadCatz Tech Support, but just found this in their knowledge-base: It would appear that for FSUIPC to hook the inputs from the stick its necessary for Windows to do its jobs and pick up the inputs in the first place, and Saitek have missed something when creating the drivers.

Its obviously an ongoing issue with them, and hopefully they get it sorted soon. Is everyone above everyone reporting trouble with the X55 and FSUIPC running Windows 8.1 as well?

Edited November 19, 2014 by Andy Browne.