Flegma

Great If you already didn't remove old drivers and software maybe you will have difficulties because new joystick has different PID and ID's in registry. So, when you have time perform clean install. Assigning buttons 9, 10 and 11 in both game and SST are cause of phantom keystrokes

Great I'll be waiting for info

Do you make a successful RMA?

I'm using X52 Pro This is from altitude.lua require("saitek"); require("gd"); I suppose requre("gd"); is not needed for X52 Pro and I must change for example saitek.SetLed("SFIP", 1, 1, 7, false); to saitek.SetLed("X52P", 1, 1, 7, false); And I must replace saitek.SetImage to saitek.AddPage(model, index, page, activate) and to add this from example -- Callback function to update air speed function setValues(offset, value) if (offset == 0X3324) then altimeter = value; elseif (offset == 0x0330 and value ~= 0) then kollsman = math.ceil(value / 16 * 0.000295299830714 * 10) / 10; kollsman = math.max(kollsman, 28.1); kollsman = math.min(kollsman, 31.9); print(value); end redrawAll(); end redrawAll(); -- Register to receive updates event.offset(0X3324, "UW", "setValues"); event.offset(0X0330, "UW", "setValues") Did this way will work?

Where I can find examples for FSX?

Can you please tell me what are the procedures for RMA? From where you buy yours? I barely remember but I think somewhere on Saitek site I read that I (in case of failure) can send direct to Saitek instead to retailer. Do you check cable between units?

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

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 agree As you can see problem is drivers not hardware because joy. works just fine on laptop

Do you use other sims like FSX or P3D?

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.

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

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

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