Bizarre Thrustmaster Control Issues

[Vol4Ever]

I've browsed boards but haven't found my exact issue discussed. Been away for a while, but got second monitor and also a new rudder set to go with existing HOTAS Warthog. Renewed interest! Took some doing in other threads, but I finally got second monitor setup exactly like I wanted without much effort. It amazes me how programmers had the foresight to allow so much (relatively easy) customization via user editable LUA files. Doesn't take high level IT specialist to do all kinds of cool things.

 

Anyway, then I went to actually fly my trusty F18 and problems started. I don't know if it was the rudder addition or DCS version updates, but my custom controls layouts were completely garbled. When I tried to manually load LUA backup, stuff didn't populate in correct columns (setup screen now has extra pedals column). Kind of a pain, but I just deleted entire user/Saved Games/DCS/ subdirectory & let software rebuild everything from scratch. Not a big deal as I have a hard copy graphical printout of bindings to use as a quick reference & there was really nothing else of interest saved.

 

Still had major problems, so I took it one step further. With F18 loaded, I went to controls adjustment screen and manually cleared every single column for all three devices, including axis settings. Other than keyboard and mouse default bindings, there was *nothing* else assigned. First step was simply re-assigning basic pitch / roll / rudder / left & right thrust / left & right brakes on Axis Settings screen. Programmed those & little "action" bars underneath settings moved exactly in coordination with proper external input, but here's where it gets bizarre. Even though control axis assignments have been double and triple checked, the aircraft DOES NOT respond accordingly. It's not a calibration issue as some controls don't even move the correct surface. For example, wheel brakes operate the elevator/pitch. Left throttle moves rudder. Right throttle does nothing.

 

I haven't the foggiest clue what could be wrong. I even reinstalled all the Thrustmaster drivers & its control panel app correctly "sees" all 3 controllers and their movements operate correctly on test screens. The strangest part is they show to operate correctly in the DCS SOFTWARE screen, but the aircraft doesn't respond accordingly.

 

Sorry for the long note, but short of reinstalling entire software package, which I don't want to do @ 100 plus GB, what else could be gummed up to cause such weird behavior? Feel free to ask questions if I can describe anything more clearly. Can also do screenshots, but there's nothing to see other than a whole bunch of controller blanks with only axis commands defined.

 

~Vol

[Vol4Ever]

EDIT: I just figured at least part of it out. I have every setting I can think of set to "Simulation", including the dropdown on the Adjust Controls menu. However, some of the controls are still responding to the "Game" dropdown settings. Is that a glitch? "Game", for example, doesn't have wheel brakes nor dual throttle on the axis page. I would think these 2 dropdowns are supposed to be a one-or-the-other. Basically, if I have Sim in the dropdown, why would I have to worry about whatever is in the Game menu?

 

Probably missing something obvious where I'll feel dumb . . .

[Flappie]

Hi. Can you please attach a zip containing your "Saved Games\DCS\Config\Input\FA-18C_hornet\joystick\" as well as your dcs.log file?

[Vol4Ever]

Hi. Can you please attach a zip containing your "Saved Games\DCS\Config\Input\FA-18C_hornet\joystick\" as well as your dcs.log file?

 

joystick.zip dcs.log WRF-FA18C-Thrustmaster.diff.lua

 

See if those work. Is there a toggle I'm missing to tell software to use "F/A-18C Sim" configuration dropdown instead of "F/A-18C Game"? I'm pretty sure those 2 groups are somehow conflicting. Only related setting I can find is "Game Flight Mode" in the Gameplay settings menu, and it's UNchecked. Just for grins, I'm also uploading a copy of LUA backup made before adding rudder pedals and updating to latest software revs. FYI, the file is dated March 2020 so it hasn't been THAT long ago. Thanks!

[Flappie]

I confirm "Game" unchecked = Sim. But some mission can force the "Game" setting for you (it's rare though).

 

I'll take a look at your files in a couple of hours.

[Flappie]

Your log and your .diff.lua share the same peripheral IDs, so it should be OK.

Check if the mission you're playing is set to "Game".

[Vol4Ever]

I don't see anywhere in Mission Briefing that it specifies, but you may be onto something. I have Caucasus and Persian Gulf modules, and have been grabbing either Dark Start or Start On Ramp simply to test controls and buttons. *IF* those missions do force the Game settings regardless of checkbox, do they have their own LUA files that I can force to use Sim setup instead? I never really played the game super heavy, but I'm planning to start going through some of the tutorials now that I'm getting deeper into it with the second monitor & rudder pedals! :)

[Flappie]

To change this setting in missions, you need to open it in the editor, and uncheck "Game avionics" and "Game flight" in the mission options ("Check" icon).

 

Here's a very simple CAP mission with "Game" forced off. Play it and see if your controls are all working.

Simple_Sim_Hornet_mission.miz

[Vol4Ever]

uncheck "Game avionics"

 

Well son of a gun. You just figured it out and didn't realize you did!!! Unticked that one more option, and kaboom. Control functionality jumped over to the sim settings. THANK YOU! I was just short of uninstalling and re-installing the whole blooming thing and probably would've ticked that same Avionics box again. Wasn't 100% sure what it did other than label surrounding aircraft, but evidently also completely screws up the controls. LOL

 

I had already manually re-programmed all my buttons back and that one check box fixed it. For what it's worth, I *tried* going to GAME control settings and loading revised LUA file to use as a starting point, but that was a total disaster. It did some of the stuff from my OP like putting stick button number assignment text into the rudder category (which doesn't even have buttons??). I guess the software can't properly decode and sort the LUA between GAME versus SIM since they have completely different list of settings, but that's OK. Not planning to use game mode anyway.

 

You ARE the man. Have a great night, kind sir!

 

~Vol

[Flappie]

Thank you.:)

You're welcome.