X65F -- lots of frustrations

[Stretch]

Got the X65F set up, and I must say I am very frustrated. In no way does this compare to the Cougar I think.

 

Black Shark on Win7 x64

 

It doesn't even work. I can map the buttons using DirectX (which I prefer over keyboard mapping), but DirectX doesn't see all the buttons and all the axes. So, the ones that it doesn't see, I figured I'd map them using the SST software, but no matter what the profiles will not load. It says the profile is loaded but when I press buttons no keystrokes are generated, period.

 

Also, I can't map the microstick axes to the Shkval. I can do it using bands but I'd rather that the axes show up in DirectX for finer control.

 

OpenFalcon on WinXP x86

 

At least the SST actually works; I can map keyboard commands using the software, apply the profile, and when I press buttons key-presses are generated. Here's the problem: if I map a button to a key in SST, but then unmap it, it's gone from DirectX forever. And there's no easy way to unmap DirectX controls in OpenFalcon. So now I have some buttons that do two things (they have a keyboard map and a DirectX map in OpenFalcon), and no easy way to make them do just one thing. I will have to edit the OpenFalcon config files to unmap the DirectX map, and just use the keyboard map, because once you go keyboard, there's no going back to DirectX.

 

Also, as in Win7, I can't map the microstick X and Y axes to DirectX axes; I have to use bands.

[Pilotasso]

Thx for warning us, I had similar situation (actually worse with my G940).

 

But try sort it out your problems first before blaming the hardware. Saitek usually provides good support so those issues probably are going to be addressed. Just make sure you visit their forums.

 

Cheers.

[Stretch]

Signed up for an account on the Saitek forums but I've been waiting for admin approval for hours now ... I am understandably pretty eager to get my new purchase working. I hope the forums are filled with answers. :)

[Bearitall]

Signed up for an account on the Saitek forums but I've been waiting for admin approval for hours now ... I am understandably pretty eager to get my new purchase working. I hope the forums are filled with answers. :)

 

 

Admin will answer you by tomorrow go have a beer:music_whistling:

[Total]

I takes the admins a while. It is afterall an international company :)

 

First do a search for "X65" and "X65F"

 

READ through the returned threads. Someone may have very well already addressed the same problem and a fix may have already been posted. MNo sense in making a new thread.

 

Examples:

 

Watch this one: http://www.saitekforum.com/showthread.php?t=18657&highlight=X65F

 

Support replied in this one: http://www.saitekforum.com/showthread.php?t=18606&highlight=X65F

 

:)

[A.S]

if it is frustrating you...watch this x65F introduction ...from minute 1:25

 

[ZaltysZ]

There is a limit on axis per device for DirectX. This is the reason why ministick of X52 is not seen as 2 axis by games. I am almost sure that X65 has the same problem, unless throttle and stick are recognized as separate controllers by Windows, however this is not very likely as there is only single USB cable.

[Stretch]

I thought there was some kind of virtual joystick tool that could solve this problem? Basically turn your X65F into two virtual joysticks?

[ZaltysZ]

I thought there was some kind of virtual joystick tool that could solve this problem? Basically turn your X65F into two virtual joysticks?

 

It will probably use the same DirectX as it is the way to access game controller in universal way (without knowing the internals of controller). So, the limits will be the same.

[Stretch]

Oh, right. That makes sense. Sucks though.

[zakobi]

 

Eww... What happened to the human gene-pool? :fear:

Edited April 14, 2010 by zakobi

[Shaman]

TOO MUCH SOLARIUM! Both girls within 5 years will look like dried-out-grandma.

[zakobi]

What is the difference on the X65 and the X65F?

[Emmer]

I'll stick with me good old Suncom SFS Combo.

Double throttle works perfect........:pilotfly:

The throttle unit:

 

 

The stick unit:

 

 

The set uses a gameport connection.That's a bit of a problem to newer systems.

I use a Soundblaster Audigy 2 with a gameport connection.

I can add the unit at the Gamecontroller section in the configurationscreen as 4 axis 4 buttons controller.

 

In FC2 i can add the left and right engine to the throttle unit.

Edited April 14, 2010 by Emmer

[Feuerfalke]

What is the difference on the X65 and the X65F?

 

X65 has an F missing. Unless you are referring to the Samsung X65.

[Stretch]

An update ... resigned to my fate since the X65F does not come with an axis-remapping tool like the Cougar does, I've decided to figure out why the keypresses aren't happening in Win7. I called up the MadCatz support line, and after being on hold for 5 minutes, got redirected to voicemail. (This is during their business hours.) Tried again, same thing.

 

So I thought maybe I downloaded the wrong drivers -- I need Win7 x64 after all, and I think I just installed whatever was on the CD. So I go to the Saitek driver page, which is taking an excruciatingly long time to load. I am sitting here waiting for it to populate a menu of options so that I can FINALLY choose the correct drivers to download.

 

Still no luck accessing the Saitek forums.

[ZaltysZ]

Stretch, check Device Manger. Are Magic mouse and Magic keyboard installed? They are virtual Saitek devices, used by SST for keyboard and mouse emulation.

[Pilotasso]

Eww... What happened to the human gene-pool? :fear:

 

TOO MUCH SOLARIUM! Both girls within 5 years will look like dried-out-grandma.

 

as if you had anything better! :D

 

what a bunch of picky guys ahaha

[*Rage*]

as if you had anything better! :D

 

what a bunch of picky guys ahaha

 

lol +1

 

 

 

But seriously....I have better;)

[Stretch]

Ah, looks like reinstalling the drivers did the trick. Mayhaps the ones on the CD were not x64 compatible? Anyway, drivers are reinstalled, keypresses work now, and there's only one problem left: Getting the keypress delays to work in F4AF so that my speed brakes open and close incrementally instead of all-or-nothing.

 

Still no Foxy, but I'm happier than before.

[Feuerfalke]

Ah, looks like reinstalling the drivers did the trick. Mayhaps the ones on the CD were not x64 compatible? Anyway, drivers are reinstalled, keypresses work now, and there's only one problem left: Getting the keypress delays to work in F4AF so that my speed brakes open and close incrementally instead of all-or-nothing.

 

Still no Foxy, but I'm happier than before.

 

You can program those things with macros.

 

Normally you just do basic mapping in the STT software. If you chose macro, you can assign key for different actions, like in FOXY: press, release and hold. Of course you need to map the right key combinations: Open/Close brakes instead of toggle brakes ;) - because even if you map incremental keys to buttons, they only work as long as they are depressed.

[M31]

Ummm... unless there is a patch I've missed somewhere? The Saitek X-65F is still missing the dual throttle function, BS too.

 

Why are we still talking about this?