DD_FT

Came across this post at a different forum : Force Feedback Induced Camera Movement Stutter And it fixes the issue with the controls in the I-16 for me. No more intermittent lag when FFB is switched on. I've copied the 64bit dinput8.dll to DCS's bin folder, and had to restart the PC to see / feel the difference.

To add: After installing that Open Beta patch, radio in the I-16 works, even after removing my fix, the dynamic radio.

From latest Open Beta patch notes: "DCS: I-16 by OctopusG Fixed ground crew interaction (intercom)"

Found a 'solution' for this issue. (Now as I basically just tried something, one might call it a work-around instead of solution.) Options, MISC, Dynamic Radio There was no radio selected for the I-16, so I added an extra one, picking the one listed as 'Integrated' for the Spitfire MkIX. So: Select I-16 at the Unit drop down list, and select SCR-522A at the bottom drop down list, and hit 'Add Existing Radio' button. As a double check, I removed the radio again, and for sure Ground Crew would no longer listen to me anymore ... Put it back in, and they do listen and act!

I'm getting the re-arm screen, and can change livery succesfully. But chocks, and load-outs, no way. There's also no audio-response even from the ground crew.. Have even renamed my Saved Games\DCS folder so it would start all new, and use all default settings: No change. (Both stable and beta are affected in my case)

I had SRS installed once, but no longer.

It is strange. It's the same on the stable version - odd. Some config setting maybe?

Thanks for that. Loaded it via 'Mission' ... no dice, no response to wheel chocks nor refuel/re-arm ... Weird stuff!

Could you please share that mission file? (I tried it on Normandy map, but ground crew still does not respond...)

Well, this problem is still here as well.... so Mesha44, you are not alone! (Even when trying the instant action, cold start mission ... )

I do not have any other hotas available to try! But I am pretty sure of it, as it did also show up without the bodnar-based controller connected ... As soon as you get over a certain limit of 'inputs' when FFB is switched on, the stuttering input can and will occur. The fact I saw it only(mainly) on the I-16 is probably because of its features and nature it needs/uses lots of input pulses: Manual gear, no trim ie. more stick movements ... and it is a throw-around-the-corner-type aircraft, (much more than a Spit or P51) especially when a 109 or 190 is trying to get and stay on your tail

And, to add, if I really try hard, I can see the same effect in the Tomcat...

So, finally getting somewhere: Switching OFF the ForceFeedback helps. It's even obvious moving the stick left/right whilst lowering the gears, keeping that button down ... FFB=on, delays are visible, FFB=off instant movements all of the time. Analysis complete. Now for a fix ... (And no, I am not giving up on da SideWinder!)

How does one switch FFB off in DCS? lol Tried it without the power cord in the SideWinder... after gear down/up, down/up, down, landing, take off the slow responses returned. Oh well - found out now my rudder pedals need some attention, its wiring needs checking ... May have to try and live with this one. (Had a DCS Session yesterday, and the intermittent input stutters were not that bad, could maneuver a lot whilst ground-attacking - before I'd be in trouble down low, heavily bankin' left when you cannot level out in time due to stick input not getting through is a recipe for a hole-in-the-ground. Had no such events during the last session... Maybe all the tinkering with the bodnar and all its wiring did help here... ?)

Thanks! You indeed have a bunch of stuff connected. Using the word 'stuff', because, if peripherals connected to your computer were to be called 'junk', then there would be no words available on the scale to use for the peripherals connected to my computer There's one more thing we've kept out of the equation: FFB. I got an MS-FFB2 stick, yours is none-FFB. A squadron mate mentioned that he remembered seeing something similar in DCS with the TomCat, it was fixed though - ages ago ... I will try next with it switched off...