Ms Sidewinder Force Feedback 2

Really ? It has it’s own AC supply input – I had always 'assumed" that also supplied most of its Power requirements, and it therefore drew very little power over the USB buss. ?

I’m still rocking the non force feedback version, it’s 22 year’s young. For the tiller and rudders, I use a combination of a g920 and universal mapper to make the gas and clutch pedal act as one axis, the wheel being the tiller. I’m limited on space so this works great for me.

Well you would think so but my experience over the years has been a powered USB hub reduces issues with the FFB2. That said, there are also people who have always just used a motherboard port without problems. May depend what other high draw devices (such as trackIR) you have, no idea.

If it is working fine plugged into the motherboard I would leave well enough alone. On the other hand if you are having issues a Powered USB Hub is probably worth a try.

I am using a powered Hub. Everything seems fine but not sure if random coincidence - I had some terrible frame rate problems last night when flying low to ground. Dev Mode said I was heavily GPU limited, which is never normally the case for me.

I flew in a less heavy area (and different plane) and things were back to normal (48fps locked by Nvidia CP) but in the UK it was dropping to as low as 8 in areas I usually get easily 30+! Needs more investigating tonight. Hope it was just something badly loaded and PC reboot will have fixed it hahah.

So, nobody has a tweaked XPF profile file to share then? :slight_smile:

Heavily addicted Sidewinder FFB2 user here. Mine is also always automatically reported correctly in Windows. I’m also positive I’ve not ever installed any driver for it in any os since Windows XP probably.

Have you tried to use another USB port, and do you have the same issue with both joysticks, that you have bought?

Good decision, I’ve bought a spare Red Edition one once, and had to replace the handle :upside_down_face:

XPF should not have any influence here, me thinks. Also, there is not much tweaking, just set the effects
to ones liking and forget about it (well I do…)

I’ve also never had any issue with any of my FFB2’s in this regard.
This joystick is one sturdy beast, and probably my only piece of hardware, thats still going strong after like 18 years, despite me having piled up 3 (yes, three :crazy_face:) replacement FFB2s…

Neither have I .. I measured the 5v Current that mine took from the USB 2.0 port last night, and it was only 40ma – almost insignificant loading on the USB Voltage Bus.

Thanks for the reply. I didn’t try the other stick yet - still in factory sealed box so I’m resisting the temptation to open it until the used one dies, or I decide to sell it :smiley:

I will try a different USB port tonight and see what happens.

There are a lot of different sliders and settings - not really sure what they all do and as I said earlier, I whacked them all up high and couldn’t really feel any difference but I need to have a deeper play with it and see.

Same here. I’ve had mine for ages. Indestructable, and would not want to fly without. I even even have a spare one (New in box!!!) on stand-by.

No very happy with XPforce though.

Is it still the “best” option? I seen two others mentioned back in 2020 but sounds like they are not developed/supported or just didn’t happen at all.

Try usbdeview.exe.
Disconnect all of your non-essential usb devices. Select all the non connected devices listed. Right click. Select uninstall and delete drivers.
Reboot.

I’m using airforce player. It’s free and works better that xpforce.

1 Like

Thanks for the tip. I’m not brave enough to do that I think! I’m sure something will go wrong.

Is there any harm in it not picking up the correct name? I mean, it works … “if it ain’t broke, don’t fix it”! :smiley:

As for AirForce, gonna try it now. Hope I can get a refund on XPF if I prefer this! Thanks again

Oh never heard of that before. Thanks! Will check it.

OK my friend, you’ve really got yourself into something here :slight_smile:

It’s not working for me. I have uninstalled XPF and installed this. Followed the step for SimConnect.xml (actually I already had that exact block in my file so didn’t touch anything there). That is all the documentation they have on the site - the rest is for Unreal Engine?

So I start the Sim, start AFP and it says Connected. Then what? If I click the START button it says “Stopped” at the bottom of the window. Click the STOP button (that Start changes into) and it then says “Connected” at the bottom. That seems like it’s the wrong way around!

Check the Log and it says “effects started successfully” but I have nothing going on on the stick. Tried changing the Gain slider. “Enable Device” is ticked.

If I select View > Simulate Effects (which I assume is a preview of what it can do)… nothing.

Any ideas? Thanks in advance (hope you can spare me some time for a reply - much appreciated!)

Doesnt work for me, either

I was using xpforce.

But, now I just use my MS Sidewinder FFB 2 was nothing.

What a pity. This topic about FFB2 makes me really sad. A fine piece of hardware as this one, with almost 20 years, working like the first day without support in the sim.

Time ago I tried airforce player and it was a little disappointing. And I don’t want blame on the developer. They do the best they can having no support in the SDK.

Although the first weeks after the release he received a lot praises, I didn’t want buy xforce as I had a bad experience with the developer and the absence support on his tools.

Anyhow, I don’t want lose my faith that in the future Asobo will finally give love and attention to FFB and our joysticks, as they deserve.

I hear you! Definitely wish it was more refined and integrated to the sim.

But with my limited experience (just maybe 5 hours so far flying with FFB) I still prefer it for the types of planes I’ve used it with so far (bush planes). I definitely need to spend some time tuning the effects but it gives me a more interesting experience I think.

I don’t believe in some of the feelings as being how it would be in a real plane (or anywhere close to that, really) but I’m gonna tone it down and see if I can get it to be more gentle. Seems there are some situations especially when elevator trim is far out that it’s pushing way too much against me. Also in faster planes it seems to lose the plot more (Pilatus PC-21, Hawk T1/A). Overall the tightening with increased air speed is good though and definitely a step in the right direction.

All good fun! :slight_smile:

I also have asked the developer for support once, but never gotten any reply. Still XPForce at least works, and it’s being offered at around EUR 15,- so kudos to the dev.
It’s a great little tool, and I can recommend it.

Airforce player, I played around with (haha…), but also did not to get it to work properly. @JCSLOVE do maybe have any tips on how you got it to work? I’d love to compare it to XPForce

There also is FS Force, which unfortunately does not support the new MS Flight Simulator, but worked
flawlessly in FS9 and FSX

I believe we might be out of luck with official support from Asobo, as long as there is no consumer hardware featuring FFB.(Yes, there is Brunner, but these are not exactly consumer targeted)
Then unlike race simulations like Assetto Corsa Competitione, rFactor2, or iracing, where FFB is mandatory, flight sims do just fine without FFB.
I would not fly without it, but being honest, it’s like a niche in a niche

It would seem the FSForce developer has “moved on” and is no longer active with any development for MSFS 2020.

I purchased FsForce back in the FSX days, and it worked well – disappointing that it was not carried over into MSFS 2020.

GITHUB ?

Maybe, if the Developer no longer is willing / able to develop FsForce for MSFS, he might consider putting it up on GitHub, so others can take a look at it and maybe solve the remaining technical issues

If there are functions missing in MSFS to support the Force Feedback software (as the Dev suggests), then maybe Asobo will be responsive to adding them .. but that is difficult if nobody is asking the right questions and making the appropriate SDK support requests.

.

“The Difficult We Do Immediately. The Impossible Takes a Little Longer”

Charles Alexandre de Calonne, 1794