![]() |
|
#16
|
|||
|
|||
|
Hi the miss spelled words are poss to do with the firmware you have, it is a very old version of the stick, latter ones have this fixed, it was to do with windows 7.
Just wondered if it is the old version firmware , if it is there is nothing to fix it.
__________________
Best regards Mike Cannaby Customer support |
|
#17
|
|||
|
|||
|
To be honest Mike, I don't really mind the misspelled words...
The lockups of the software are the only annoying issue. It's just that I suspect the misspelled characters might cause SST lockups even when using shorter names. Especially the pinkie switch seems to cause very long names on the MFD. Or do you mean that the old firmware might not be compatible with W7 in itself?? Some pics for you to check out... Normal http://img849.imageshack.us/img849/8579/photo3ki.jpg http://img98.imageshack.us/img98/3626/photo2qqn.jpg Error http://img839.imageshack.us/img839/4104/photo1xy.jpg Pinkie switch error http://img195.imageshack.us/img195/2809/photo4gn.jpg Regards, Sylvain |
|
#18
|
|||
|
|||
|
Hi, have you tried it yet, one more thing you can try.
Put the Saitek DirectOutput on Automatic – Delayed start. 1. Start menu, Run, “services.msc”, enter. 2. Scroll down to find “Saitek DirectOutput” or “SaiDOutput” (you should have one or the other). 3. Right-click it and go to Properties. 4. Click the Start button so it will activate now. 5. Set Startup Type to “Automatic (Delayed Start)” (for Windows Vista/7/2008). Reboot your computer
__________________
Best regards Mike Cannaby Customer support |
|
#19
|
|||
|
|||
|
Quote:
I have no such service mentioned in the services list Any idea how this can be? Cheers, Sylvain |
|
#20
|
|||
|
|||
|
Hi Mike,
Any news from your programmer? Even if it does not fix the MFD display I would be a very happy camper if it would help me getting rid of the freezes... Regards, Sylvain |
|
#21
|
|||
|
|||
|
After waiting for a solution/work-around during the last 3 months frustration ultimately settled in.
Solved all my issues described above... by buying myself a brand new Thrustmaster Warthog HOTAS. Excellent build quality & most importantly no software compatibility problems with Windows 7 64bits. I can finally enjoy flying Falcon 4 and DCS A-10 without freezing Joystick button presses! Kind of a stupid solution to be honest as there was still NOTHING wrong with the hardware side of of my old X-52... My problems were purely SST software related. Expensive solution too but I didn't mind replacing my thrustworhty X-52 as I have been using it extensively since 2005. My next joystick COULD have been a Saitek product for this matter... but you guys need to cover the software side of things too!! When I realized that a lot of users have been complaining for a long time about issues with their Saitek gear used in conjunction with windows 7 I didn't want to take the plunge. Thank you Mike for trying to offer a solution... Unfortunately your efforts are in vain if other people in your company do not care to really fix the SST software. They should take example to the good work you are trying to do here. As far as I'm concerned... Saitek >>>> GREAT hardware, really POOR software... It's a shame, really... Regards, Sylvain Last edited by Sylle : 3rd June 2012 at 22:01. Reason: Spelling + extra paragraph |
|
#22
|
|||
|
|||
|
Hi, thanks for the post, it was not the ST software, It is down to the firmware in the stick, yours was a very old version when Win7 came out it upset every thing, but ST has kept up with it. we fixed the firmware a few months back, but it is only in the newer sticks. the X52 is still a great stick,
__________________
Best regards Mike Cannaby Customer support |
|
#23
|
|||
|
|||
|
Hi Mike,
No hard feelings! I agree with you the X-52 is still a great buy. I certainly don't regret buying it at all as it provided me with countless hours of very enjoyable gaming. I do understand old firmware can result in faulty characters on the MFD but I fail to see why an old firmware would cause full lock-ups of the SST software, never getting past the SST splash-screen anymore (as you could see in the youtube movie I sent you by mail). While configuring my new joystick this issue even caused problems with the Thrustmaster TARGET software. As soon as I unplugged the X-52 everything returned to normal??? I'm no expert in this stuff so I will not argue if this issue is caused by firmware or SST software... I do regret however that you seem to be the only one around here to offer support. My questions of the old firmware compatibility with windows 7 or the missing Saitek services in the services.msc for example (see post above) remained unanswered for several weeks... This apparent lack of support is mainly what put me off and drove me towards a different brand, NOT the fact that a joystick bought in 2005 is no longer working in W7. H*ck, I'm surprised it lasted THAT long considering the heavy duty useage over the years to be honest! Madcatz should realize I could have bought the X65f iso the Warthog if they would provide support in a swift manner. Only one person offering forum support (that would be you) is simply not enough in my opinion to take the risk to spend the amount of money for hardware like the X65f. Thanks again for your open attitude about this. Regards, Sylvain |
|
#24
|
|||
|
|||
|
I just downloaded the most current SST software and drivers for my Windows 7 64bit in light of the exciting new Mechwarrior Online game and guess what... my Joystick hangs even without loading a profile at: "Mouse Wheel Down" (because it has more than 15 characters, which is more than the display of the X52 can display)
This bug is still not fixed? I reported that bug 3 years ago! Please support. We gave you all the info you need to fix this... You just need to trunicate the text string for the name of the Button at 15 characters, before you send the profile to the joystick. Can you please add that ONE LINE OF CODE to your SST software? Please respond! Thank you! |
|
#25
|
|||
|
|||
|
Quote:
|
![]() |
| Thread Tools | |
| Display Modes | |
|
|