Another x52 bites the dust! pov hats not working

[emenance]

Throttle works great, stick sucks. Months ago perhaps since owned a common problem everyone knew about was that the hat 1 would stop working causeing a replug of the cable. Times goes by and my stick flakes out, drivers suck and so I give up. New computer build was around the corner and so insted of risking my stable os I went through some withdrawal about not being able to fly. So now with new computer built I expect the stick to work....nooooooooo it doesnt.

 

Working with my old profile and the stock LOMAC profile I get the same problem.

 

Here are the crazy symptoms.

 

hat 1 and 2 work in the control panel...matter of fact everything does as usual.

hat 1 does not work on LOMAC input test screen but hat 2 doesand the sticks buttons.!!!!

go into game and start to fly...hat 1 AND 2 are dead.

Stick axis works just fine in game and out....I can manuver, whatever.

Also all the buttons on the stick work on the in game test screen but DO NOT when flying.

What a mess. If someone want this to mod or fix email me Ill sell it cheap.

 

Does not make a bit of sence. It was working fine until I messed with some usb stuff on my old computer build. Everything now is new hardware in the computer and I cant get this stick to work. This is after ripping out a previous saitek driver install and starting over. Im sick of Saiteks crap and want to fly again. Lock on has never looked so good on the new computer!

[therion_prime]

Well if it works in the control panel, I would assume it's not the sticks fault....

[thereminqblank]

 

hat 1 does not work on LOMAC input test screen but hat 2 doesand the sticks buttons.!!!!

 

Also all the buttons on the stick work on the in game test screen but DO NOT when flying.

 

Does this mean that you're setting the button inputs within the Lock On control options?

 

If so, it's best to make a Saitek profile and assign button inputs to key strokes. I think Lock On suffers from craziness when trying to directly set up button inputs within Lock On.

[nemises]

^^ agreed...assign a profile with key strokes instead of using the POV Hat function / buttons IMHO

[RedTiger]

Another thought: disable the feature in windows that will shut off USB ports when not in use.

[bengo]

I know from previous experience that the drivers can cause these problems, especially if you've tried to uninstall or mess with them.

I recommend going to the Saitek site, lookup the proper uninstall procedure, execute, dl-latest drivers, install according to Saitek. Doesn't hurt to try. Hope it works out for ya.

[emenance]

negative on all. I did use the saitek tech uninstall procedure. No change.

 

I have tried several profiles, same thing.

 

Whatever, it used to work I didnt change the profile the only thing that changed were the drivers and then a new computer. I dont deserve this hassle.

 

Still looking thanks for the ideas but I have tried them all.

[emenance]

Does this mean that you're setting the button inputs within the Lock On control options?

 

If so, it's best to make a Saitek profile and assign button inputs to key strokes. I think Lock On suffers from craziness when trying to directly set up button inputs within Lock On.

 

 

no it doesnt

 

crazy aint it.

[bengo]

What OS are you using ?

[emenance]

xp pro Same things for years. I think I might uninstall flaming cliffs , the dl portion and redownload it from the website. Might have a corrupt Flaming cliffs?

[bengo]

Have you tried programming a single keystroke to those buttons/switches, and then load the profile and check in notepad to see if the keystrokes get generated that way ? That's always a good check to see if the Saitek side of things are working or not. I'd try that before uninstalling LockOn.

 

Here's a thread with good info : http://forums.eagle.ru/showthread.php?t=28251

[emenance]

Well after confirming the stick does work at least without using the software etc etc I have decided to rescue myself from the time to time annoyances of this POS and rid my life of it for good!!

 

Looking around on the internet no one seems happy with the software. I believe I saw a chipset conflict on my nforce 3 system. I dont know for sure but there just are too many people unhappy with it. Im going to buy a cougar Thrustmaster and use that Nicolas profile at cougar world. Im not risking a stable build with saitek crap again. No one else should either. Even though I have to learn a whole new setup it will be worth it in the long run!