Nopileus

So the stick is completely limp, no resistance on it at all? (while in game in a started up huey for example) If you go to your game controller panel in windows, does it correctly show up with all the axis and buttons moving? You could try going to the device manager and letting windows reinstall the driver for it. If that doesn't solve it i'm going with some sort of hardware defect.

It works without any special configuration on Windows 7, 8 and 8.1, drivers are installed automatically. (32 or 64bit does not matter) If FFB doesn't work your settings in DCS are probably wrong or you have a hardware defect. Turn FFB on in the MISC tab and in CONTROLS on each aircraft select the MSFFB2, press 'FF TUNE' and check the 'swap axis' box. You also need to keep your hand on the grip for FFB to be active as it turns off if the sensor does not detect your hand (you can tape one of the holes shut if you like).

If you can control the ambient light it really makes no difference at all, i too use the reflector (ziptied to my headphones). Its advantage is that you can set the sensitivity lower since the Pro outputs a lot more light than the reflectors bounce back, so ambient light doesn't affect it as much. I've also found the Pro to be worse at pitch movements (cuts out sooner) than the regular one, which in turn gives you less yaw range. tl;dr keep using if it works for you, tracking quality is the same.

To clarify, the only thing you need to check in the 'FF Tune' menu is 'swap axis'. Also make sure to not set any curves or deadzones on the stick, leave everything linear otherwise it gets out of sync.

The main reason why the FFB2 is great for helos seems to be the complete lack of static friction, it's completely effortless to make tiny movements. It also has a rather loose center position without harsh transitions. The one big issue for me was the grip being too small and causing my hand to cramp after a while, i ended up modding it with a grip for an old Thrustmaster x-fighter stick. At this point i prefer it to the Warthog unless i really need a lot of buttons.

Make sure you have Mirrors turned off, i'm getting massive stutter depending on what objects are visible in the mirrors. Even though the fps counter still shows 50+ it's unplayable. Turning off mirrors fixed it.

Just make sure you don't update the Warthog firmware while connected to the USB3.0 ports (known to fail), normal use shouldn't be a problem at all.

Because it's a really cheap upgrade on LGA775. (if you don't have a quad already) People have found way to use LGA771 Xeons on LGA775 with a slight modification, those xeons go for pretty cheap prices on ebay because they're being phased out from datacenters.

There will likely be a new WHQL driver next week.

I have this code for Teensy i found somewhere on the Internet a while ago, i can't remember the source though. This won't work on a normal Arduino without changing it, so be warned. Grab it here http://cl.ly/252W1j1K3a35 Edit: the source in post #22 on here

Be aware that DVR only works in 32bit applications for now. It also seems to be the case that all games that are not in raptr just won't work at all. I can for example get it to work with Wing Commander Saga (has a raptr entry), but not with other FS2Open based games/mods.

Same here, massive input delay as soon as the FFB is starting to go to work. The stick itself might "only" have a second of delay, but keyboard inputs only get through once FFB forces stop coming. If it was only the 0.03 second delay c0ff mentioned i'd be perfectly fine with it.

I can confirm this, brings back a noticeable chunk of performance in both 1.2.7 and 1.2.8. Too bad there is so many problems with the MSFFB2 in both versions. (completely unrelated to this)

My R9 290 powers through almost anything i throw at it, there are only two things that cause "issues" (this is with a i5 2500k at 4,2ghz and 8gb RAM) One being DCS, that just hovers around the 35fps mark, that changes with every driver and whichever mission you are playing. While i don't have intimate knowledge i figure it's somehow limited by driver overhead. The other one being Project CARS, which is still in a pretty early phase of development and has not received any form of optimization. PS: Get RadeonPro, it lets you tweak profiles on a per-game basis and has some very good options for vsync or advanced AA methods

I've had a problem with the FFB settings resetting every time i loaded a mission in 1.2.7 beta, you might want to try setting them again after you're in a mission. You also need to check the swap axis checkbox.

That is the CPU limit i am talking about, you might get super high max-fps but at some points it will just tank because of bad optimization. Go for a regular GTX780 or non-reference R9 290 (once those appear) depending on what you prefer, paying more for a 780ti is pretty much pointless.

You have to stop spouting nonsense mate... DCS is completely CPU bound on any system out there, graphics card is almost irrelevant as long as its current midrange or above. @Razorback What is you budget?

I just got an old Thrustmaster FLCS and TQS combo (pre-Cougar) from ebay with the intent of converting at least the throttle to USB. Doubt this works with the old one, but cool none the less.

To put it bluntly, if you are expecting a huge performance boost in DCS you will also need a new CPU. Other than that right now the AMD R9 280x and R9 290 are probably the best bang for your buck and should fit your budget regardless of which currency we're talking about. The Nvidia equivalent being the GTX770 and GTX780, both of which cost noticably more. If you decide for the R9 290 i suggest you wait for variants with a better cooler, the reference design is fairly loud.

And probably ups the VRM temps to over 9000°C

Exactly, the Ka-50 has two rotors that cancel each others torque out, this is also the reason why it does not need an anti torque rotor in the back. The Huey however uses a conventional design and does require the use of pedals to counter the torque. Game Mode does indeed not work in the Mi-8 yet if i remember that correctly.

The Mi-8 has a massive main rotor which creates a lot of torque, it seems that is enough to turn the helicopter even with idle throttle/collective. Combined with the free spinning front wheel that ends in you rotating endlessly. You have to counter the torque using the pedals controls or what ever device you have mapped to them.

"Messer, Gabel, Schere, Licht sind für kleine Kinder nicht" :smilewink: Looking good though, keep it up.

Burried in that old thread, i should've known. Anyway, that is good news.

I have confirmed this in the SU-25A and P-51D. Due to lack of time i have not tried others but i expect it to happen in every ED made plane. It does not occur in the MI-8 and UH-1H (The UH-1 has a trim related issue though). After several minutes in said aircraft the joystick and keyboard controls become delayed, this delay is variable and changes constantly. Sometimes it can take seconds to switch views for example. I am using the MSFFB2 Joystick and have FFB enabled in options, i get 40-60fps during the occurrence of the bug which should insure that its not a performance related issue. When FFB is turned off in options the bug does not appear. If there is any log files or other information needed i'd be happy to post it here. Edit: upon further testing i have confirmed the issue with most SFM and AFM planes from the FC3 library