FC2 and Saitek SST/X-52:a cruel battle.

[Semtex]

hello gents,

I've encountered a lot of problems-for the first time-using SST software with FC2(with and without the recent patch released),expecially

for launching missiles(but not only).

I've discovered that pushing Ralt+space without any profile active there's no problem,using ANY btn in SST or simply adding a btn in FC2 config panel releasing a missile is only a dream,even because,and it happens only for US planes,Russians jets have only a key to fire both(why?boh..),it looks that the multiple keys(Alt+key,RCTRL+key,etc.)don't have effect during the game(with an active Saitek SST profile).

Example(with a SST profile on):

-taxy lights not working;

-firing "

-rotary buttons for radar use(azimuth,scan,etc.)not working or cause stability problem during the game(I use rotary 2 for radar scan and the wheel scroll for radar RWS/TWS,X-52 mode 2,A/A mode.Results:all throttle off,only trust is still working.The only 2 rotary btns recognized by FC2 are the POV hat 3 used for TDC,the precision slide for zoom and rotary1 for radar range and stop!).:furious:

I'm not a computers expert,but I've used this hotas for FC1.1 without a noise(and for a lot of other sims).I know there's some config problems with the older X-52,but I've encountered more than an problem,for the moment unsolved.

I hope that someone have the magic wand...

Many thanks for every aid.

 

P.S.:of course I've installed the latest drivers and SST software.

My current OS is Win7 64 over Acer 7740G notebook.

Now I'm testing the Cougar hotas and foxy with FC2 without pain..

:helpsmilie:

[EtherealN]

Note that latest drivers and SST version is not always a panacea. Saitek are unfortunately extremely flaky in their drivers (you can crash the mfd driver through entering too long names for commands in the profiler).

 

I have absolutely no problem at all with my x52 in FC2, aside from the mentioned thing with long command names. (Basically, having them so long that they would have to scroll on the MFD causes the driver to hang and take the computer with it, that's a Saitek driver issue that FC2 has nothing to do with though.) However I know another player had issues with mapping modifier keys on a non-english keyboard (I also have non-english and no issue there though), and swapping versions on the driver and profiler package fixed it.

[Semtex]

Hello,thanks for reply.

I'll immediately rename all my btns in SST(even if the wide part of them are very short:WPT,REL MSL,ILS,etc.)and downgrade all drivers and SST softare.

I confirm that only the old X-52,from my experience,gives some issue:I',m using the Cougar for FC2 too and all looks ok.

Edited June 7, 2010 by Semtex