Big Problems

[Mr_Burns]

Just built a new PC, i7-2600K and HD 6870 2GB with 8gb ram.

 

It was a clean system running on Win 7 x86.

 

But its driving me mad, let me explain some of the problems.

 

1. Saitek X52 profile doesnt work (i use SST to create T2 to start engine) go into sthe options and in the keyboard cheats start engine press T2, it creates the keystroke I assigned. Start the game and engine start doesnt work.

 

2. Sometimes, TMS works, other time is doesnt, programmed through SST.

 

3. The game installed in the X86 file and then in the normal programes file.

 

4. If I alt tab out of it and click the A-10 icon in the toolbar thing at the bottom, it starts another session.

 

5. Have send activation key every time I re boot game

 

6. Keyboard stops functioning.

 

7. After a game, keyboar and mouse act strange selecting multiple icons on the desktop.

 

I thought I would be alright with saitek but I think its SST is screwing everything, has anyone any ideas I would really appreciate it!

 

Thanks

[Tek]

have you got the sliders on the x-52 assigned to an action? i had speedbrake assigned to the slider and if i did not centre it properly it would continue pressing keys giving me a situation akin to yours. If you do have the sliders set then make sure that you use bands for the sliders so that the software only responds at the extremes of the slider.

 

on a side note the x86 is the 32bit windows folder whereas the regular programs is the 64 bit. I also hear that the sst software has issues with W7 that drove me insane and caused me to spend a large some of money on a warthog hotas

[WRFirefox]

Take a look at the keysettings in the SST

 

B+LShift makes problems, cause the "B" comes first

LShift+B makes no problems

 

maybe this helps:smilewink:

[WarriorX]

Why did you not go with the 64 bit version of Win 7 for your new build?

[cichlidfan]

While all of the above are valid issues/points. I would definately start with the SST software, when their drivers and software go nuts they seem to really run amok.

 

Have you tested the profile in the SST software. That will tell you right away if you have any "stuck key" issues.

 

Even if you don't I would give it a spin without the SST software. Just try to get up and flying, don't worry about a major config and see what happens.

 

If none of that improves anything then I would start looking at issues with the 32bit version of Win7 (No offense intended but the person that let you buy that should be shot:D).

 

I have no idea what if any might be issues but I also don't know anyone running that varient of Win7.

[Mr_Burns]

It is 64 bit windows - it just has 2 program folders (one is programs x84 which I have found out is for 32 bit programs in win 64).

 

I was wondering if there were issues with using the different folders, the first time I installed DCS it put in the programs x86 and I also loaded some of the other programs in x86 folder (i didnt see the programs folder just the programs x86 folder) but then I re-installed DCS and it put it in the programs folder.

 

So now some programs are loaded to programs and some to programss x86.

 

Does anyone even know what I am talking about cos Im confused!!!

 

I think I will reinstall all programs, helios, SST onto just the same folder but I cant beleive that would matter.

 

Bloody computers...

[Mr_Burns]

Take a look at the keysettings in the SST

 

B+LShift makes problems, cause the "B" comes first

LShift+B makes no problems

 

maybe this helps:smilewink:

 

 

Thanks will remap tonight - wish I had bought a Warthog but Australia is expensive!!

[scheffchen]

Why would you Not try it without the software? Win7 should recognize the different inputs from the x52 by itselft.

Since you don't Need any macros this is the best Option i would suppose...

[Mr_Burns]

Hey I think I sorted it but its not perfect, in fact I dont like it at all!

 

So SST needs to be told that you dont intend on using it by right cliking and assigning it to unprogrammed, otherwise, its sending keystrokes rather than saitek buttons.

 

I wanted to assign POV1 to move the head cos I dont have the IR5 yet, I want POV2 to be the TMS and POV3 to slew the TGP.

 

As DCS doesnt recognise the X52 pinky as a 'modifier' the only way to use the POVs twice (once normal and once shift state) is to program the shift states through SST turning it into a macro'd keypres.

 

Then in SST i only programme the multiplier (pinkie) plus POV to send a keystroke, make sure everything else is set to únnasigned.

 

This reduces the chance of every button press being a keystroke through a macro through SST which I think it increases the chance of failing IMO. Where you do use SST to assign a macro, then like WRFirefox said, Imake sure you put the 'modifier'before the key it is pretending to be.

 

So if you want my advice X52 programmers, where you can, use the X52 buttons in the X52 column of the DCS controllers section first, make sure you delete the keyboard presses in SST and DCS, where you need to use a modifer, programme this in SST and then put that in the keyboard section of DCS Controlls.

 

 

Thanks to warrior and tec.

 

Hope this garbled message makes sense cos Im 8 bottles of beer down.

Edited September 22, 2011 by Mr_Burns

[cichlidfan]

You can tell DCS that the pinky is a modifier. You can tell DCS that any switch on the X-52 is a modifier. In the controls screen there is a modifier button where you can define all the modifiers you want. I ran two modes on my X-52 without using SST at all.

[WRFirefox]

:huh:

Cichlidfan

 

Every button can be define as modifier:unsure:....these are great "news":beer:

so cheeeeeeeeeers!:pilotfly:....ups forgot: "dont drink and fly!":music_whistling:

[Mr_Burns]

Awesome cos I dont like SST and now i dont like HIDMacros.

 

Thanks for that i will check it out tonight

[Mr_Burns]

Hey I had my setup all working OK, logged on this morning and most of my controll options had dissapeared.

 

So I remapped everything, saved the profile and made a back up, now my right MFD buttons 11-15 couger are controlling the gear and stuff and not pressing DMS or TADS even though they are correctly mapped in the controlls options?

 

Does anyone else 'lose'their settings over night and can anyone explain the MFD not doing what its told?

 

I tend to spend more time resetting the controlls than flying the damn jet!

[Cali]

That doesn't sound good, I have been using mine cougar MFD's for about 6 months and haven't had a problem at all. Maybe unplug them for a bit and see if that works.

[Sarge55]

I've had my Cougar MFD's for almost two years and not had that problem. The only time I've had my settings go wonky overnight was when I used Saitek SST programing software. Good HOTAS, very poor software....

 

I have heard that if you save or use the profile "Save As" function in the Options it can be screwy as well. I had that problem when I tried it in LockOn and BS so it maybe the same for A10C.

[Mr_Burns]

Thanks guys, I sussed out the Couger issue, for some reason, when I loaded the profile it had replicated my Left MFD in the keyboard section of the controls as well as in the left MFD column, I deleted all the buttons from the keyboard and it worked fine.

 

So not a problem with the MFD just with the DCS profiles.

 

I will try and stop using save as to see if that works!

 

I like the X52 and have moved away from SST, I find I dont need the Mic so using one hat as POV I can still have 5 others which is enough for my level of immersion. Plus the trick to add the pinky as a toggle was great. One thing I dont use at all is the slider and the wheels, cant find a use for them.

 

Thanks

[avlolga]

Hi Mr_Burns,

 

i have q for you - how did you install / connected your x52???

 

did you first connected it after installing the windows ?

or you have install the x52 updated driver with SST and then connected the x52?

 

Avlolga