Issues with X52 Pro Throttle

[SubEclipse]

Hello all,

 

For the last week or two I have been experiencing an issue with my X52 Pro throttle.

 

From a fresh reboot, everything will work perfectly... and actually, just unplugging and plugging back in the USB cable resets the problem for me...

 

So, with that said, the problem I'm experiencing is that after a few minutes, when I push the throttle all the way forward, the z axis will only register being pushed up to about 90%.

 

I *think* this problem started after updating to the latest drivers / programming software (version 7.0.27.13), however, I hadn't played DCS for a while before upgrading my drivers, so it's possible that this is irrelevant to the issue.

 

Things I've tried:

-- I've opened up a ticket with Saitek support, and they've offered to RMA it for me, however, I'm not completely convinced that this is a hardware related issue, and want to do a little more exploring before sending it in.

 

-- Uninstalled the device drivers and programming drivers... deleted calibration data from the registry, rebooted and then reinstalled drivers / programming software.

 

-- Tried using a different USB port.

 

Currently, I've bypassed the issue by setting the min/max sliders on the Deadzones tab to be within in the working range of the throttle, but this is less than ideal, and I'd like to fix the issue rather than work around it.

 

If anyone has any ideas, I'd really appreciate the assistance.

 

Working properly (after reboot or usb disconnect/reconnect):

 

The issue - Throttle all the way forward, input reads about 90%:

 

 

Thank you!

[Darkwolf187]

You're sure you're pushing it past the afterburner detent? The LEDs on the throttle scale are going red?

 

If so, you may need to force a recalibration of your X52. Do a search (I can't find the link right now and don't know what O/S you're using) for the registry keys you delete in order to force recalibration on restart. Basically, you unplug the unit, delete those keys, reboot, plug it in, and then move it through all its axes four times to recalibrate.

 

I had the recalibration for my X52 go wonky, and I did the above and it was fine. Mine went wonky after the drivers got updated in Windows Update.

[SubEclipse]

Thanks for the reply, comments below:

 

You're sure you're pushing it past the afterburner detent? The LEDs on the throttle scale are going red?

 

Yes, it's definitely all the way forward, past the detent and the scale is turning red.

 

If so, you may need to force a recalibration of your X52. Do a search (I can't find the link right now and don't know what O/S you're using) for the registry keys you delete in order to force recalibration on restart. Basically, you unplug the unit, delete those keys, reboot, plug it in, and then move it through all its axes four times to recalibrate.

 

I had the recalibration for my X52 go wonky, and I did the above and it was fine. Mine went wonky after the drivers got updated in Windows Update.

 

This is actually one of the things I've already tried... The process I followed was found here: X52 Calibration Fix

 

When your calibration data was giving you problems, was it always an issue, or would it work properly sometimes?

[Darkwolf187]

It was random. What would happen to me is that the mouse stick would sometimes start up in a slight down position, other times it was fine. Then the stick started in a left cant some of the time (severe enough that I couldn't trim it out in-game). Recalibrated, and the problem went away for me.

 

If you've done the recalibrate and it's still doing it, dunno what to say. Sorry :(

Edited May 24, 2013 by Darkwolf187
read the original post more carefully

[SubEclipse]

When you move the throttle up the slide, does the physical throttle stop moving at the same time that the readout hits 90% ? Or does it hit 90%, and the throttle keeps moving a bit?

 

The former. The control panel registers forward movement on the z axis until I hit the fully forward position of the throttle.

 

If it's the former, you can take that out by recalibrating in-game or messing with the deadzones in the control panel. If it's the latter, I'm inclined to think something mechanical if you've done the recalibrate.

 

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.

 

As another test, when I push my throttle forwards so that the 50 text on the throttle dust shield is halfway visible (ie, the line next to it has just become visible), my throttle reads 50% in the control panel. Does yours read 45% or 50%?

 

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.

Edited May 24, 2013 by SubEclipse

[Darkwolf187]

That result is pretty peculiar. If the reading is 60% when the physical throttle is at 50%, then that's very strange indeed, and quite unexpected. That would mean that the throttle's measurement is no longer linear.

 

What I mean is this... If your throttle reads from 0-90 across its entire travel, then at half travel it should read 45. If it reads 60 at half travel, 90 at full travel, and 0 at no travel, then its response must be non-linear (reading goes from 60-90 in the same travel distance it takes to go from 0-60).

 

It's possible that the potentiometer or other electronics that drive the throttle may be malfunctioning and giving you a non-linear response. Of course, it could also be software issues, but I haven't had any issues like that.

 

Is the throttle still under warranty? If not, I'd suggest you just mess with the X saturation in-game to get around the problem, you can also mess with the curves to get the response linear again.

[SubEclipse]

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.

[Flegma]

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.

 

Hello, searching on net for my problems related for this version of drivers I've found your post.

I think your problem is definitely in this version of drivers.

I use X52 Pro too and I noticed that X and Y axes don't move to full range with 7.0.27.13

and I have problems with regulating MFD with rotary dials (with FSX plugin)

 

I've revert back to 6.2.2.4 and SST 7.0.2.7 and all problems are gone

Also, I sugest you to replug joystick with throthle to 0 (zero) because joystick have autocalibration

 

sorry for bad english

 

[edit]

Do you try to see what's going on with JoyTester2.exe (goole it)

Normal range is from -65536 to 0

Edited May 29, 2013 by Flegma

[SubEclipse]

Hello, searching on net for my problems related for this version of drivers I've found your post.

I think your problem is definitely in this version of drivers.

I use X52 Pro too and I noticed that X and Y axes don't move to full range with 7.0.27.13

and I have problems with regulating MFD with rotary dials (with FSX plugin)

 

I've revert back to 6.2.2.4 and SST 7.0.2.7 and all problems are gone

Also, I sugest you to replug joystick with throthle to 0 (zero) because joystick have autocalibration

 

sorry for bad english

 

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!

[SubEclipse]

[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]

[Flegma]

[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]

 

You can find older driver at ftp://ftp.saitek.com/pub/software/full/ (scroll down)

And you must perform more deep(ly) uninstall of old drivers. That's mean erasing all Saitek folders (remember to backup profiles in C:\Users\Public\Documents) and erasing Saitek registry entries

 

Here is "normal" procedure for uninstalling (copied from support e-mail)

 

First, kindly unplug all Saitek peripherals from your machine.

 

Go to Control Panel and run the Programs and Features icon. Remove all Saitek and ST Programming Software entries in the list of programs and then go to the C:\Program Files (and/or x86) directory and delete the Saitek folder.

 

Restart your computer and the files will all be uninstalled.

 

Now browse to your C:\Windows\Inf folder (If you can't see an Inf folder then click Organize > Folder and search options near the top-left corner of the window, go to the View tab and in there check the Show hidden files, folders and drives option, then click OK - you should now be able to open the Inf folder in the Windows directory).

 

Look for the OEM0.inf file. Find the highest numbered OEMXX.inf file and double click on it - a Wordpad screen will open up with information in it. You're looking for any lines that refer to Saitek (usually at the top of the window). If you don't see any such info close that window and open the next OEMXX.inf file - so if you started on, say, OEM30.inf then you'd now open OEM29.inf.

 

If you find any that refer to Saitek then close the window and delete that OEMXX.inf file along with its accompanying OEMXX.pnf file. Go through all of them until you have deleted any files that mention Saitek.

 

Now, please do a ‘search’ for files in Windows using the following search string: sai*.*

 

Once it's finished finding any files delete them - files only though, don't delete any folders, and only Saitek files. All Saitek files have sai at the start and are usually followed by a capitalised word (like SaiMini.sys for example).

 

Go to the Program Files directory on your PC and delete the InstallShield Installation Information folder (if it exists).

 

Go to the C:\Windows\Temp folder, as well as the C:\Users\<your_user>\AppData\Local\Temp folder and delete everything in there.

 

Click Start>Run and type regedit and click Ok. Alternatively, Windows key + R will open the Run dialog.

 

Go to HKEY_CURRENT_USER and remove any of the following entries if present:

 

- Software\Microsoft\Windows\CurrentVersion\Uninstall\Saitek Gaming Extensions

- Software\Microsoft\Windows\CurrentVersion\Uninstall\{167E4A06-F407-11D3-95F5-0080AD910D79}

- Software\Microsoft\Windows\CurrentVersion\Uninstall\{1bfde623-95c2-40b4-ad14-224afc590dec}

- Software\Microsoft\Windows\CurrentVersion\Uninstall\{1d639238-eddf-4a28-8ad7-82744af5bc34}

- Software\Microsoft\Windows\CurrentVersion\Uninstall\{76da7051-7a5d-4bd7-9e05-7a4014d3e905}

- Software\Microsoft\Windows\CurrentVersion\Uninstall\{3a9e0e2f-b0d1-452b-b833-7a7300ea1231}

- Software\Microsoft\Windows\CurrentVersion\Uninstall\{90126b79-c0d2-41a5-86b2-2f6666c446b9}

- Software\Microsoft\Windows\CurrentVersion\Uninstall\{40B3A7BB-0D2C-4BC4-B7AA-C326A5793C21}

- Software\Microsoft\Windows\CurrentVersion\Uninstall\{03adca1c-bcf0-4b12-afcf-8ebf2cb3ab07}

- Software\Microsoft\Windows\CurrentVersion\Uninstall\{655ee3b7-0113-4c5e-b147-b82ba325643f}

- Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{655ee3b7-0113-4c5e-b147-b82ba325643f}

- Software\Microsoft\Windows\CurrentVersion\Uninstall\{DC431222-E2D0-4C4A-9438-52D4626202B3}

- Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{DC431222-E2D0-4C4A-9438-52D4626202B3}

- Software\Microsoft\Windows\CurrentVersion\Uninstall\{967FB80D-56BD-42EF-A942-9E8C78F984A4}

- Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{967FB80D-56BD-42EF-A942-9E8C78F984A4}

 

Then, please use the link below to download the 3.5 version of the .NET framework

 

http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=21

 

If you have already installed version 4.0, the two of them will not conflict with each other, but the ST software needs the 3.5 version to function properly.

 

After installing it, please use the links below to download the driver and the necessary version of the ST software.

 

Please save the files onto your hard drive and then run them from your Downloads directory, as running them directly from the site might cause some issues.

 

ftp://ftp.saitek.com/pub/software/full/Saitek_X52Pro_Flight_Controller_SD6_64.exe - driver

 

ftp://ftp.saitek.com/pub/software/full/ST_SD7_0_24_8_64Bit_Software.exe - ST software

 

Begin the driver installation first, with the product unplugged (in this case, the USB dongle), as the installation guide will instruct you to plug in the product at the necessary moment.

 

After the driver installation was finished, please install the ST software, following the procedure below:

 

Go to the Downloads Directory > Right click on the saved file > Run as.... > Administrator, then follow the instructions guide.

 

Regrding the 2nd enquiry, what exactly do you need to move in order to obtain calibration? What exactly happens with the joystick? What do you mean by not calibrated completely?

 

Should you require further assistance from our team, do not hesitate to contact us again and we will follow up accordingly.

 

Best regards,

Cristina Toma

[SubEclipse]

You can find older driver at ftp://ftp.saitek.com/pub/software/full/ (scroll down)

And you must perform more deep(ly) uninstall of old drivers. That's mean erasing all Saitek folders (remember to backup profiles in C:\Users\Public\Documents) and erasing Saitek registry entries

 

Here is "normal" procedure for uninstalling (copied from support e-mail)

 

First, kindly unplug all Saitek peripherals from your machine.

 

Go to Control Panel and run the Programs and Features icon. Remove all Saitek and ST Programming Software entries in the list of programs and then go to the C:\Program Files (and/or x86) directory and delete the Saitek folder.

 

Restart your computer and the files will all be uninstalled.

 

Now browse to your C:\Windows\Inf folder (If you can't see an Inf folder then click Organize > Folder and search options near the top-left corner of the window, go to the View tab and in there check the Show hidden files, folders and drives option, then click OK - you should now be able to open the Inf folder in the Windows directory).

 

Look for the OEM0.inf file. Find the highest numbered OEMXX.inf file and double click on it - a Wordpad screen will open up with information in it. You're looking for any lines that refer to Saitek (usually at the top of the window). If you don't see any such info close that window and open the next OEMXX.inf file - so if you started on, say, OEM30.inf then you'd now open OEM29.inf.

 

If you find any that refer to Saitek then close the window and delete that OEMXX.inf file along with its accompanying OEMXX.pnf file. Go through all of them until you have deleted any files that mention Saitek.

 

Now, please do a ‘search’ for files in Windows using the following search string: sai*.*

 

Once it's finished finding any files delete them - files only though, don't delete any folders, and only Saitek files. All Saitek files have sai at the start and are usually followed by a capitalised word (like SaiMini.sys for example).

 

Go to the Program Files directory on your PC and delete the InstallShield Installation Information folder (if it exists).

 

Go to the C:\Windows\Temp folder, as well as the C:\Users\<your_user>\AppData\Local\Temp folder and delete everything in there.

 

Click Start>Run and type regedit and click Ok. Alternatively, Windows key + R will open the Run dialog.

 

Go to HKEY_CURRENT_USER and remove any of the following entries if present:

 

- Software\Microsoft\Windows\CurrentVersion\Uninstall\Saitek Gaming Extensions

- Software\Microsoft\Windows\CurrentVersion\Uninstall\{167E4A06-F407-11D3-95F5-0080AD910D79}

- Software\Microsoft\Windows\CurrentVersion\Uninstall\{1bfde623-95c2-40b4-ad14-224afc590dec}

- Software\Microsoft\Windows\CurrentVersion\Uninstall\{1d639238-eddf-4a28-8ad7-82744af5bc34}

- Software\Microsoft\Windows\CurrentVersion\Uninstall\{76da7051-7a5d-4bd7-9e05-7a4014d3e905}

- Software\Microsoft\Windows\CurrentVersion\Uninstall\{3a9e0e2f-b0d1-452b-b833-7a7300ea1231}

- Software\Microsoft\Windows\CurrentVersion\Uninstall\{90126b79-c0d2-41a5-86b2-2f6666c446b9}

- Software\Microsoft\Windows\CurrentVersion\Uninstall\{40B3A7BB-0D2C-4BC4-B7AA-C326A5793C21}

- Software\Microsoft\Windows\CurrentVersion\Uninstall\{03adca1c-bcf0-4b12-afcf-8ebf2cb3ab07}

- Software\Microsoft\Windows\CurrentVersion\Uninstall\{655ee3b7-0113-4c5e-b147-b82ba325643f}

- Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{655ee3b7-0113-4c5e-b147-b82ba325643f}

- Software\Microsoft\Windows\CurrentVersion\Uninstall\{DC431222-E2D0-4C4A-9438-52D4626202B3}

- Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{DC431222-E2D0-4C4A-9438-52D4626202B3}

- Software\Microsoft\Windows\CurrentVersion\Uninstall\{967FB80D-56BD-42EF-A942-9E8C78F984A4}

- Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{967FB80D-56BD-42EF-A942-9E8C78F984A4}

 

Then, please use the link below to download the 3.5 version of the .NET framework

 

http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=21

 

If you have already installed version 4.0, the two of them will not conflict with each other, but the ST software needs the 3.5 version to function properly.

 

After installing it, please use the links below to download the driver and the necessary version of the ST software.

 

Please save the files onto your hard drive and then run them from your Downloads directory, as running them directly from the site might cause some issues.

 

ftp://ftp.saitek.com/pub/software/full/Saitek_X52Pro_Flight_Controller_SD6_64.exe - driver

 

ftp://ftp.saitek.com/pub/software/full/ST_SD7_0_24_8_64Bit_Software.exe - ST software

 

Begin the driver installation first, with the product unplugged (in this case, the USB dongle), as the installation guide will instruct you to plug in the product at the necessary moment.

 

After the driver installation was finished, please install the ST software, following the procedure below:

 

Go to the Downloads Directory > Right click on the saved file > Run as.... > Administrator, then follow the instructions guide.

 

Regrding the 2nd enquiry, what exactly do you need to move in order to obtain calibration? What exactly happens with the joystick? What do you mean by not calibrated completely?

 

Should you require further assistance from our team, do not hesitate to contact us again and we will follow up accordingly.

 

Best regards,

Cristina Toma

 

 

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?

 

[Flegma]

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?

 

 

 

 

Older drivers are Saitek_X52Pro_Flight_Controller_SD6_64.exe (or download 32-bi if you are on 32-bit OS) and ST_SD7_0_24_8_64Bit_Software.exe

[SubEclipse]

Older drivers are Saitek_X52Pro_Flight_Controller_SD6_64.exe (or download 32-bi if you are on 32-bit OS) and ST_SD7_0_24_8_64Bit_Software.exe

 

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

[Flegma]

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

 

Remeber "two" things:

 

1. When you first plug be sure that throthle is in 0 pozition

2. Rotaries are in full + or - (not in neutral)

3. Stick itself is on flat surface

 

Becaus, as I say, this HOTAS has autocalibration ability.

 

Unlike joystick, throthle uses potentiometers and there is no chance potentiometer in Z axis to travel only 90%

I don't play DCS (I plan to bay A-10) but I think there is some issue with this game. I sugest you to delete file that holds calibration and axis assignment in DCS and recalibrate again.

[SubEclipse]

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.

[SubEclipse]

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.

[Flegma]

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.

 

Do you use other sims like FSX or P3D?

[SubEclipse]

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.

[Flegma]

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.

 

I agree

As you can see problem is drivers not hardware because joy. works just fine on laptop

[SubEclipse]

I agree

As you can see problem is drivers not hardware because joy. works just fine on laptop

 

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.

[Flegma]

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.

 

If problem is solved with these version please report this to Saitek because latest drivers is "extra" buggy

In my case 7.0.27.13 makes my MFD nonfunctional and "cuts" axis ranges to 32703 instead of 32768 at central position (obviously the have aded null zone)

And I think that every driver isn't suitable for every version of firmware. Some series of joystick seems to be made to work only with one or max. two versions of drivers

[SubEclipse]

If problem is solved with these version please report this to Saitek because latest drivers is "extra" buggy

In my case 7.0.27.13 makes my MFD nonfunctional and "cuts" axis ranges to 32703 instead of 32768 at central position (obviously the have aded null zone)

And I think that every driver isn't suitable for every version of firmware. Some series of joystick seems to be made to work only with one or max. two versions of drivers

 

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.

[SubEclipse]

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.

[Flegma]

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.

 

Depends on with whom you chatting , Saitek Live Chat sometimes gives good results (:

(Yes, they have Live Chat)

Here is a small part of my talk with Saitek employee . He / She admitted that the problem is in drivers

 

08:26 Your Question: I have problems with latest drivers for X52 Pro

08:26 Please wait, an operator will be with you shortly.

08:27 You are now chatting with Mad Catz

08:27 Me: hello

08:27 Mad Catz: Hello where did you download the drivers from?

08:27 Me: From official Saitek page

08:28 Me: 7.0.27.13 and SST with same version

08:28 Mad Catz: What operating system are you using?

08:28 Me: Windows 7 64-bit SP1

08:29 Mad Catz: What is going on after you download the drivers?

08:30 Me: With 7.0.27.13_x64_ I've lost ability to control items on MFD when FSX is loaded.

When I change something from within cockpit (for example frequency) changes are reflected on MFD but, as I say, I can't change values with rotary dials.

Also I've lost ability to control illumination with right dial.

08:32 Me: With 6.2.2.4 and SST 7.0.27 (I think) everything was fine except inability to load and unload profiles with joystick via clutch button

08:33 Me: Now, that problem seems to be solved but MFD is half functional

08:33 Me: I've folow procedures for uninstalling/install but no sucess

08:34 Mad Catz: I apologize we are currently working on updating the drivers and that is going to be the issue. They should be back up in about 2 weeks. I apologize for the inconvenience .

**********

08:36 Mad Catz: Thank you and I apologize for any inconvenience. have a nice day

________________________________________

 

That's all. I'm glad if I helped you