X52 Problems & Solutions | Windows 7 |
-
This is not for Hackers,
hackers can solve everything xΔOk, so I took my time and here I present you a little tiny bit of information about some problems that I encountered while using x52 Joystick
and now that I’m pretty much done with them, I’ll take my time to give instructions to anyone facing any of these problems.
This is also a work to let people know what they are about to encounter by purchasing a Saitek x52,
because you might think that you can magically avoid those problems, but you’ll not! So let’s get to it…
(and excuse my bad English).// // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // //
Introduction
A Lot of people complain about x52 and windows 8 and 10.
I don’t know about that, this thread is ONLY for Saitek X52 (non pro) in Windows 7 ONLY.
If you have other windows versions and you have the same problems, give them a try but
I cannot guarantee that you will solve all of them in any version.Disclaimer.
Those tips that I am about to give you have one thing in common. First: they do NOT use the profiler (a little program
that maps keyboard keys to joystick keys) and Second: they keep the “Saitek X52 Saitek control system” open at all times.
The reason for that is that, the profiler program caused me a lot of problems. The most important one was that, my x52 was
constantly losing control after 5 minutes or so, of gameplay for unknown reasons and I was unable to control anything in the game.
That’s why I won’t use the profiler to solve any of the other problems or in other words, I won’t go full retard -.-
If you tried the profiler program and it does work for you, then what can I say? You are lucky and I’m jealous
If you have any help that you can give me on how to fix my profiler problem, they will be gladly acceptableThat being said, these solutions are NOT done by using the profiler, because the profiler for me was obsolete.
So, with all that being said and without further ado, let’s begin with the known problems!
// // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // //
PROBLEMS
- Joystick is losing control or behave weirdly in the game, instantly or after a while playing.
- The “i” button (button #30 on the Throttle) cannot be mapped in game.
- The “mouse button 1”, “mouse button 2”, “mouse wheel” and “mini joystick” (buttons: #31, #32, mouse wheel and mini joystick, on the Throttle) cannot be mapped in game.
- Pinky Trigger (button #6 on the Joystick) cannot be mapped in game.
- Throttle idle and afterburner detents (those bambs) are frustrating and don’t allow smooth movement.
- The Profiler switch cannot be mapped in game.
- Other problems
// // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // //
! Before going any further: Go to http://www.saitek.com/uk/down/drivers.php?HWID=06a3075c&DRVER=7.0.27.13&SWVER=7.0.27.13&OSVER=7601&LANGID=0000&TARGET=i386 !
! and download and install the latest drivers. After that go to your Profiler and disable every profile you might be using. You won’t be using the profiler from now on.!
! And finally go to “Saitek X52 Saitek control system” and keep it open AS LONG AS YOU ARE PLAYING ANY GAME. It works 100% and It’s the main fix for most !
! of the bellow problems. !:/: The “Saitek X52 Saitek control system” should remain open AT ALL TIMES while you play ANY game for AS MANY hours you play. :/:
// // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // //
SOLUTIONS
-
As I said in the beginning, this (for me) could only be solved by never using the profiler program ever again.
Make sure to clear the profiler from any profile you may have made.
This will stop this problem. -
You have to go to the “Saitek X52 Saitek control system” and at the “MFD” tab
at the very end you will see a tick that says, “Clutch settings” you want to tick “Enable clutch mode”.
If that doesn’t solve your problem then also check the “latched clutch mode” separately or enable them both at the same time.
Remember to keep the “Saitek X52 Saitek control system” ALWAYS open.
Try and see what works for you, most of the times just the “Enable clutch mode” will do the trick,
so make sure you check this 1st (and only this maybe). -
Again, keep the “Saitek X52 Saitek control system” enabled and enable the clutch mode at all times while you play, you will be able to map the #31, #32 buttons.
But you won’t be able to use the mouse wheel (not the real mouse wheel but the one on your Throttle -.-) and the mini joystick on your Throttle…
If you want to keep the mini joystick and mouse wheel, working then you will need to disable every clutch mode
Then if you want to map the wheel the mini joystick and the buttons #31 #32 you won’t be able to map them directly, but ONLY by mapping YOUR MOUSE ITSELF to those controls or axis!
Or you might want try and see if you can keep them all enabled (but indirectly mapped) by closing the “Saitek X52 Saitek control system” but then you will lose other things…
by indirectly I mean that you’ll have to map the mouse and not the throttle buttons and axis -
Again! It’s the same solution. Keep the “Saitek X52 Saitek control system” on at all times, and you should be able to use it, BUY NOT as a shift button, and only as a regular one.
(also play with the clutch button modes and see if you get any results). -
Ok, you can do 2 things. 1st is to set the left and right deadzones (not the center one) in the “Saitek X52 Saitek control system” Deadzones Tab at 2 click’s each.
Or, open the throttle and remove the detends if you are manly enough xD Don’t worry, just kidding, don’t do that because after a while you will start to like the detents actually! (I was pissed of at first). -
It will, but only work as a regular button, and NOT as a profiler switcher, (you don’t have any profiles remember?) do that by keeping the “Saitek X52 Saitek control system” on at all times.
(also play with the clutch button modes and see if you get any results). -
Hit me up and let me know if other problems occur. Make sure you have the latest drivers 1st.
// // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // //
The “Saitek X52 Saitek control system” is located at your Control Panel > Hardware and Sound > Devices and Printers > Saitek X52 Saitek control system.
Keep it open and play with the clutch modes and you will solve all these problems.// // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // //
Disclaimer #2: By not using the profiler you (might;) not be able to use the pinky as a shift trigger and the profiler switch as a profiler switch any more…
Again if you know what is causing the Joystick to loose connection or behave crazy in game when using a profiler, hit me up, I would like to know!
What I suggest you to do to solve most of them is to Keep the Saitek control panel always on and enable the clutch mode and disable the latched clutch mode.
But you won’t have wheel and mini joystick control We cannot have everything in life.I know that there are a lot of programs that might or might not help you enable pretty much everything or replace the profiler and still give you profiles functionality,
but this information on this thread is for the people that don’t really feel like hackers so much.That’s all from me, I hope you like it
and thanks for reading! -
For what it’s worth, my saitek profile for bms only contains keystrokes for the mini-stick…everything else (including the clutch button and the function/start/reset buttons on the bottom of the throttle) is programmed as a directx button using the included keyfile editor. The pinky switch is even programmed as a “shift” button allowing my other buttons to have a second function. There is a ton of information available on this forum to help you get your stick programmed the way you want in a more effective and efficient manner that using the profiler.
Cheers!
-
ok i will need to do a better ressearch and post something a bit more up to date, that will include the profiler…
-
Hi, I still have some weird behaviours with my joystik: Saitek X-52 with Win10.
I am not sure if also in 4.32 the situation was the same because I have never done it in MP (abroad for a job).When playing solo, the DMS commands work correctly.
When in MP, in flight, after few minutes, DMS and sometime pinky and NWS/AP DISC stop work and I am not able to manage the MFD’s.
Of course, I am able to switch button with mouse but DMS AFT to change SOI is not possible.
Yes, I can use the keyboard but it is not useful while in combat.I would like to give this a try but I want to be sure about procedures:
PROBLEMS
- Joystick is losing control or behave weirdly in the game, instantly or after a while playing.
SOLUTIONS
- As I said in the beginning, this (for me) could only be solved by never using the profiler program ever again.
Make sure to clear the profiler from any profile you may have made.
This will stop this problem.
Just to be sure… do this mean I have to assign the command with DX assignment directly inside Falcon-SetUp-Controllers?
Thanks for your help.
Regards