Saitek X52 pro

[DarkStar]

In SST you remove the modes that include the use of the Pinkie for enabling shift-states.

 

Then it acts like any other button again.

 

See the before/after images attached.

 

Awesome, will try it after the weekend. Thanks alot!

[Bucic]

Here's what I got for you:

 

- my rather comprehensive X52 Pro SST profile (WIP but 95% functional)

http://forums.eagle.ru/showthread.php?t=53213

 

- my video tutorial on SST

 

SST works and it gives far more possibilities than in-game assignments. Those who 'prefer doing it in-game' are people who either have damaged X52s or can't figure out SST :P

 

I highly recommend using a windowed mode for Black Shark for the time you will work on your profile. Also, IIRC, there's no need to restart the whole game to test profile modifications just done. Just exit mission and start it again. You can also do an even faster test using built-in SST tester (see the vid I posted).

 

You can find more SST video tutorials on the official Saitek forums.

Edited September 11, 2010 by Bucic

[DarkStar]

the reason I don't primarily use SSD is that I want my joystick to be as close to the real KA-50 set-up as possible, thus, I don't need multiple commands on multiple buttons, only a few, which I manage by using the pinkie as a modifier in-game :) I'd definitively use it for other games though.

[26-J39]

I'd say just map the axes to your X52 Pro ingame and start playing. After a while you'll notice what commands you use often. This combined with the information from the Flight Manual about the real-life cyclic and collective you can create your own profile. I'm sure that if everyone posted and tried each other's profile we'd all be pretty confused and complain about some (if not all) settings.

I configured my X52 Pro as such:

Axis settings were done in Black Shark.

ALL buttons were assigned in my SST profile as the key strokes that perform each function.

 

I really think that ED is a wonderful developer here in that they have given every single in-game function a key bind. This makes for very easy profiling - unlike for example IL-2 where almost no function is bound to any key by default, making profile creation for a game like that almost impossible with out a lot of alt-tabbing and messing around with new binds etc...

 

I'd say just map the axes to your X52 Pro ingame and start playing. After a while you'll notice what commands you use often. This combined with the information from the Flight Manual about the real-life cyclic and collective you can create your own profile. I'm sure that if everyone posted and tried each other's profile we'd all be pretty confused and complain about some (if not all) settings.

I configured my X52 Pro as such:

Axis settings were done in Black Shark.

ALL buttons were assigned in my SST profile as the key strokes that perform each function.

 

I really think that ED is a wonderful developer here in that they have given every single in-game function a key bind. This makes for very easy profiling - unlike for example IL-2 where almost no function is bound to any key by default, making profile creation for a game like that almost impossible with out a lot of alt-tabbing and messing around with new binds etc...

 

You guys think the same.. LOL :P

[Avilator]

In the Game Controller options under windows vista, the clutch mode can be switched off. I actually use it to reset my TIR view to straight ahead. Note, I have the Pro version:

 

 

I stand corrected. It is so on the non-pro version as well. Guess I have to do more :book:

[Ghost17]

Magic Bus Problem

 

A new wrinkle has wormed its way into my simming: I have a particularly odd error regarding the Saibus.sys driver, along with some quirky behavior of my Saitek X-52 Pro Flight Controller system.

 

Firstly, everything was fine until I started getting BSOD's when flying BlackShark and Flight Simulator X. I thought I might have some driver conflicts, and started deleting unwanted and unused drivers. Previously I had purchased a Saitek Eclipse keyboard, installed it and then later decided I wanted to go back to my older MS Wireless Natural. Everything worked normally with my X-52 in game until I made the mistake of deleting some of the Magic Bus drivers. Now I get a little yellow flag on the "Root Enumerator" icon in Device Manager, and some of the X-52 buttons have stopped working in game. This includes BlackShark and FSX. I tried finding the offending driver online, but all I get are a bunch of ads for driver software. A search on the Saitek site brings up nothing on Saibus.sys, Magic Bus, or Root Enumerator. An email to the support guys at Madcatz has gone unanswered.

 

I have uninstalled and reinstalled the controller software and the SSD software but still no joy. Under the Saitek Control Panel, all the buttons work and the MFD is lit with my selected default profile. Profile Editor shows all keys responding as normal, but they are not functional in game.

 

Any ideas on how to get back on the the Magic Bus (with apologies to the Who)?

[Ramstein]

have you tried the support forum for Saitek:

 

http://www.saitekforum.com/

[Sarge55]

Did you clean your registry out after uninstalling the SSD software? Perhaps some of the old data is conflicting with the new install.

 

I beleive the "Magic Bus" is installed when you re-install, IIRC you get a box asking if you want it installed (it was a long time ago so I could be wrong on that)

[Ghost17]

Ramstein: As I said.."An email to the support guys at Madcatz has gone unanswered." Madcatz IS the Saitek support group.

 

Sarge: As noted, I have uninstalled and reinstalled both the controller and SSD software. Magic Bus is still not there.

 

Thanks for the comeback guys. "But I still haven't found what I'm looking for.." (With apologies to U2)

[Bulletstop]

A quick try, uninstall all the software, Shut pc down, move joystick to another usb port re-install device and software and see if it repopulates.

 

 

Bullet

[Ghost17]

Possible Sticky?

 

Bulletman: OK, you get the kewpie doll for your girlfriend. I had no idea that a change in USB ports after reinstall would do the trick. For anyone who has experienced this weirdness, I recommend Bullet's fix. I'd even post it as a Sticky, but I'm not exalted enough to do so. Bravo Zulu, partner.

 

G'Stone