SubEclipse

Yeah... what ended up fixing the issue for me was removing the drivers through the device manager and reinstalling... I didn't have to do a deeper removal process than that, (luckily). Also, I had nothing bound to anything other than the axis og the joystick in game... had that same thought, though. Anyway, still so far so good here... seems like the replacement has taken care of my throttle issues I was originally dealing with.

Received my replacement yesterday... after dealing with a heck of a lot of new issues from the SST software where it was sending keystrokes as rapid press / releases rather than pressing and holding the commands, I got to play a few hours of A-10C last night. So far, no throttle issues.

Thanks for the replies guys... I *think* I fixed the problem last night by deleting the driver data from the device manager, and reinstalling the 6.2.2.4 drivers along with SST 7.0.24.8 My problem wasn't with the commands being latched, but rather like the OP's where a command would be sent as if it was being rapidly pressed and depressed, not pressed and held like it should be. This is interesting... one issue that came up for me last night was that a few times some of the people in my TS channel would claim they could no longer hear me. I would alt-tab from DCS to find that my PTT was no longer being recognized by TS (non-hotas PTT button on mouse). The only cure seemed to be closing / reopening TS. I wonder if this could be related to that... either way, I've changed it to direct input, so we'll see. Thanks again guys.

Hello, I realize this thread is very old, but I wondered if you were ever able to come up with a solution. I'm having this very issue, and for the life of me cannot find a solution that works.

Saitek marked my ticket as complete today, stating that a replacement would be on its way to me within 2 days. Pretty quick turnaround time all in all. Now I just have to hope there are no problems with the replacement.

Looks like they have yet to process it at their RMA facility. Being patient is tough with this as my backup stick:

My stick made it's way to them early last week, but they haven't updated the ticket yet. I may contact them this afternoon to see if I can get a status update.

The warranty is good through Saitek for 2 years from the original purchase date. In my case, I sent them a copy of my invoice and they authorized the RMA. I got mine from Amazon, who only offers replacement for 30 days, so I couldn't just exchange it through them. I did check that the PS2 cable between the units wasn't loose, but I do not have a spare that I could use to rule that possibility out completely.

I may have spoken too soon... I've had the issue happen twice since posting that I thought it was fixed... mind you, before going back to 6.2.2.4 it was happening every 5 minutes... I seem to be able to go for a lot longer now, but the timing may be unrelated... :/ I'll give it through the weekend before committing to a course of action, but I think I'll most likely be sending it in after all... [EDIT] Yeah, seems to be back in full force now... sometimes it goes longer than others before happening, but the problem is definitely not gone. I'll get it boxed up on Monday and shipped out to Saitek [/EDIT]

After 1 hour of issue-free gameplay, I've updated my support ticket with Saitek not only asking them to be aware of multiple users experiencing issues on the latest drivers, but also sharing my frustration that the technician assigned to my case blew off my request to roll back my drivers, stating that they do not keep archived software available, when clearly you found a technician willing to share more accurate information with you. Thanks again for taking the time to help me out with this... If you ever pick up any DCS mods, let me know if you'd like to join up in a server.

I definitely will... I intend to put enough time into DCS today that I can be certain the problem is gone. I'll update my ticket (and this thread) later today with my findings.

Yep, exactly. I've formatted my PC, reinstalled using the 6.2.2.4 drivers / SST 7.0.24.8 and so far so good with the throttle bug.

Went ahead and formatted the PC... problem solved.

The only other Sim I have is Falcon BMS (which I barely know). It is unaffected by the new stick X / Y issue, but the throttle issue is still a problem there. Interestingly enough, last night I installed DCS on my laptop along with the latest Saitek drivers and SST, flew the SU-25T for abot 15 minutes and the throttle issue never happened. Due to my new issue with the stick, I'm leaning toward formatting my PC, and starting from scratch. Not the most fun thing to do, but it's not going to kill me. When doing so, I'll be sure to start with a fresh install of the older Saitek drivers, just in case my issue is linked to them.

@Sarge55 Yes, I have everything programmed using SST... I'd hate to have to rebind in DCS, but I went ahead and uninstalled SST anyways and this did not fix the problem. @JG14_Smil I use SIM in the P-51D, (but my P-51D doesn't seem to be affected by the issue), but also, half of my FC3 jets (F-15C, SU-27, etc) are having the issue. SU-25T is unaffected (which I assume is in Sim mode, and a couple of the Migs don't seem to have the problem). --------------------------------------------------------------------------------------------------------- I've just about talked myself into formatting. Never fun, but it could be worse.

Hello all, In an attempt to fix another issue I've had going on with my X52 pro, I seem to have created a new problem for myself. In single player, everything works properly, in all jets, all mods, etc. In multiplayer, the X & Y axis movements of my joystick do not register at all in any of the jets I normally fly, however, I jumped into an SU that I had never flown before and it works properly. Twist rudder and throttle are unaffected. This all started after rolling back the drivers for my X52 in an attempt to fix an issue with the throttle that I'm experiencing, discussion here. I have tried everything I can think of to correct this issue, including the following: -- Removed C:\Users\<user>\Saved Games\DCS folder (started new game and recreated) -- Removed C:\Program Files\Eagle Dynamics\DCS World\Config\Input as well as C:\Program Files\Eagle Dynamics\DCS World\Mods\aircrafts and used repair to rebuild them -- Uninstalled & Reinstalled DCS World and all modules -- Reinstalled previous X52 drivers that I had been using -- Tried in another Windows user profile (same behavior... wasted an activation :/) I have to imagine there is another folder somewhere, which isn't removed by the uninstallation of DCS which holds some sort of joystick data that I'm missing, but I have no idea where this would be. Any ideas you guys might have would be greatly appreciated.

Uh oh... reinstalled DCS and all modules, and the new joystick issue remains in multiplayer. I'm going to open a new thread in hopes that I can get that resolved.

Well... it doesn't look like this has corrected the problems I'm experiencing, and unfortunately, I've developed a new bizarre issue as well. For some reason now, in multiplayer, no movement by the stick is recognized... In singleplayer, however, it works properly. I flew around in a quick mission just now, and the throttle problem returned. One last thing I think I'll do, just to rule it out, is a full reinstall of DCS, though I should mention that since my original post, I have been able to duplicate my throttle issues many times without DCS loading at all, so I don't think it's the culprit. At this point, it seems likely to me that the potentiometer used by the throttle could be faulty after all. Oh well... I'll get DCS reinstalled and will report back this evening.

Got it... thanks again. The process continues.

Excellent info... I'm trying this now, however, I don't see older drivers at the location you provided (see screenshot below). Have they possibly been pulled since you obtained them?

[uPDATE]It looks like I had these same drivers available to me using "Roll Back Driver" from the device manager. I'll report back later this evening whether or not this corrects my problems.[/uPDATE]

Hi Flegma, Thanks for this information... When I was working with Saitek Support, I actually asked them if they had a drivers archive so I could try this, but they told me they did not. Were the 6.2.2.4 drivers the ones that were provided with the X52 on the cd? I haven't actually mailed my X52 back to them yet, so I'd really like to try this before doing so. Thanks again!

Yeah, I think it's time to go ahead and start the RMA process with it. I'll update this thread when I get the replacement... if it was a software related, I suspect the issue will continue. Thanks again for the help.

The former. The control panel registers forward movement on the z axis until I hit the fully forward position of the throttle. Are there calibration settings within DCS its self? Maybe you're suggesting that I decrease the X saturation on the throttle in-game? I'm sure that would work, but would essentially do the same thing as setting the deadzones in the control panel. Yeah, as a temp workaround, I have been bandaiding the problem by setting the deadzones like so (image below), however, this puts me at 0% on the first detent and 100% all the way forward, which is kind of annoying. With my throttle in this position, it shows just under 60% (image below) What's really weird about this problem is that I can disconnect/reconnect the USB cable and the problem goes away (every time). I can then leave it plugged in all day and check it, and usually it will still be working properly at this point... I should note that I have, on one occasion, found the problem occurring out of game. Without fail, 5-10 minutes of DCS multiplayer and the problem arises, which really makes it seem as though DCS is creating the issue... It's just as likely though that the problem does not occur until the throttle has been used quite a bit. I have tried disconnecting/reconnecting, and moving the throttle back and forth a few dozen times. This doesn't seem to kick off the problem by its self. I really appreciate you taking the time to help me troubleshoot.

Yes, FC3. Bummer... I'll keep wishing.