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...

Thanks peachmonkey! Latest chipset drivers are in, W10 are the only ones available me thinks (Asus Prima Z370-P) "continuing press/push to retract/release" does it me you press the button and keep it pressed, instead of press-release-press-release? If so, could you try and see if whilst holding the button down the stick movements in the cockpit is fluidly following the joystick itself? As in my case, whilst the button is being held down, the 'delay' occurs as well. ===== So - I am already carefully looking into what a re-install of W10 would mean for me (Though I will first fiddle with the mobo/chipset drivers...)

No software for re-mapping present here. I want to keep it all as simple a possible - will always find a different way of doing things without having to install extra supporting software. TrackIR is running though

So, uninstall I-16, cleanup, Repair, Install I-16. Assigned the basic stuff again, to be able to fly. And it still occurs Okay, @peachmonkey, I need you to try it ... (For me, the next thing to try would probably a re-install of W10... lol)

Well, this is getting interesting. Really. Kinda ... So, with HotPlug disabled, I thought that did it. In Free flight. No issues for some seven minutes. It all felt so nice, that I decided to fly to the airfield, and try and land. So, line up, fly over the field, turn into a left circuit, slow down, drop gear on downwind leg, turn to base ... oh dear - here we go again... Now, the way I drop the gears is to keep one bodnar based button depressed until it's all the way down, as in I am not operating that handle for like 32 cycles ... (Issue also occurred when using a keyboard key to drop the gears.) Disconnected the bodnar controller, used keyboard to lower and raise the gears, had to lower-raise-lower to have the issue occur ... but indeed, it did in the end! To me now it is clear - there is some input buffer overflowing. That's why I never saw it on the ground... there's too little time spent on the ground with lots of inputs - one usually still has the gears down. Oh well. Maybe there is an I-16 related .lua file that has an incorrect value in it? Yes, I am now going to get rid of the I-16 install, remove leftovers of it, Repair the installation, then add the I-16 to it again.

Hotplug is enabled. Will disable it and test again ...

Please take your time, do it your own way - I am not in a hurry!

The I-16 is very nice to fly - difficult take-off and landing, but it's lovely in the air... Try it in Instant action, then you'd only have to assign the basic three axis, throttle and you're fine Motherboard is of 2018, and yes - latest BIOS version is installed. Chipset drivers: only older ones available ...

So... here's more... 1) Swapped out the Bodnar board for a spare one - (slightly different model - by looks/color.) 2) Tried with both home built HAL sensors disconnected. 3) Used different USB port - it was connected to a separately powered USB hub, now on motherboard directly. All to no avail... It's as if every now and then an HID related buffer overflows. And it seems it's down to the Bodnar board. The issue only occurs when that one is connected. Anyone out there using a Bodnar board and is 'flying' the DCS I-16 ??

1) Done. 2) Can't, they are not listed as a category when the devices are unplugged ... 3) Flew the I-16 using keyboard controls, left-right and up-down, Five minutes of Instant Action, Free Flight - issue not seen a) Added the FFB2 stick back into action. Have not reset the assignments. Five minutes of Instant Action, Free Flight - issue not seen b) Hooked the Home Built Bodnar board up again. Five minutes of Instant Action, Free Flight - issue not seen - However, FPS are down to 27 suddenly. c) Un-hooked Bodnar controller, tried again: One minute of Instant Action, Free Flight - Still low FPS. Restart of PC. d) Bodnar connected, One minute of Instant Action, Free Flight, FPS good (144), but issue is back! Restart of PC. e) Bodnar disconnected, One minute of Instant Action, Free Flight , issue not seen. FPS Good. Then, Hooked up Bodnar (hot-plug!), issue is there. UnHoooked Bodnar, issue stays. Restart PC. f) Bodnar disconnected, One minute of Instant Action, Free Flight , issue not seen. FPS Good. g) Bodnar board connected, without its rudder pedals (those are home built as well), One minute of Instant Action, Free Flight, FPS good (144), but issue is back! So, it’s the Bodnar board, and/or the wiring. Really weird though that it only shows up in DCS I-16 … Got a spare Bodnar, so next thing to try is to swap it. Hope it helps, as I do not want to work on that wiring Thanks very much @peachmonkey, for steering me in the right direction!

Thanks for your reply! I do not think I removed all of its .lua files... You gave me plenty of good options to try, thanks very much!