Bailen

Hey Filthyone: It looks like my problem has been solved, I am not experiencing the issue anymore. I am still not sure what I did to correct it because I am a fool and did three things at once, not thinking that I really should try to isolate what the problem was in case it happens again. I unintalled all saitek software and drivers and reinstalled, updated motherboard USB drivers, and switched over to my two USB 3.0 ports on my motherboard that use their own separate controller. That being said switching back to USB 2.0 ports has yet to reproduce the issue either, perhaps it was either a motherboard driver issue or a software or x55 driver issue.

Filthy: I think that did the trick for me. I plugged my throttle into another computer and set it up and it was fine, unplugged it and put it back on my main before I updated anything and it kept glitching out which makes me think it's a driver issue and not the throttle. I then updated my USB drivers for my motherboard (P67 Sabertooth) and it appears to be working now. Now that I think of it I did move the throttle and stick to two USB 3.0 ports. I will move it back to the 2.0 ones for a test to see if the issue comes back. I will report back. P*Funk: thanks for the ideas, are you aware of any way to mix and match keyboard and joy button presses in the same function? For instance can I program the trigger to Shift+joybtn1? If I could do that I could just remap all the buttons to have a modifier that way. From what I gather the programming portion of the x55 is exactly the same as other saitek devices. Looks the same as my mouse at least. I know I could remap everything to keyboard functions but I have been having issues with the software getting it to stay. I can map a command like shift+B and it will work but only for a few tries then gets unrealiable for some reason. I could remap all the keyboard functions in game to make it easier to map too but I'm still fairly new and like having those functions standard in case I have to ask for help. But if all else fails I guess I could build a few switch boxes to suit my needs lol.

Have just updated my USB drivers for my motherboard and that seems to have done the trick with the throttle causing random button press events. On another note: I have only limited experience with saitek programming software. I am curious if it is possible to use the mode dial as a modifier somehow. I would like to have say mode 1 as takeoff and landind, mode 2 as navigation, and mode 3 as combat and customize the hat and toggle switches to suit. The two ways I can think of doing this is to somehow have the button events change somehow (e.g. have the "E" button on the throttle register in DCS as Joy_BTN 1 in mode 1, as JOY_BTN 31, in mode 2, ect.) Looking at the H.U.D. software I do not think this is possible. The other way I can think of is to set a modifier to the modes and use the modifier switch in DCS. (e.g. mode 1 is default no modifier, mode 2 has a permanent shift modifier with all button presses, mode 3 has a permanent ctrl modifier, and set up new presses accordingly in DCS) This looks like it may be possible but I cannot figure it out in the H.U.D. Software. Anyone have any ideas?

I just purchased a new X55 after a very long time away from any kind of flight sim and I must say, for the money I think it seems like a pretty good unit. I had tried the x52 and was not that impressed, mostly I didn't care for the plastic feel and led lights everywhere. While the x55 is pretty much all plastic, the rubber coating adds a lot to comfort and I find the design helps add to the flight sim enjoyment. One issue I am having though is that sometimes when I am using the throttle it triggers random button events from the rest of the throttle, but only when using the two throttle levers. I find in games like DCS I will power up and my landing gear will come down and my MFCD's will start changing. When I go into the saitek software and move the throttle I can see the buttons flickering orange like they are being pressed. This seems to be intermittent as after a fresh install of the software and drivers it does not happen, it takes a few hours to kick in. Has anyone else notices anything similar to this? I have a few days left to exchange my unit, but seeing as its a bit of a trip, if this is a software issue I may hold off. In the mean time I am going to try installing and uninstalling some drivers and testing it on a different computer to see if it changes anything. I have already tried it on my main computer running windows 8.1 and 7, both 64 bit and it has the same issue.