[CANNOT REPRODUCE] TMS fwd not working in game (TM warthog hot as)

[coolts]

Anyone else seen this? Works in dcs controller page but does bugger all in game. I can’t hook on tad, or point track or create spi in tgp. Very odd.

[Mumby]

Working for me as normal.

[Foka]

Working ok.

[Ziptie]

Anyone else seen this? Works in dcs controller page but does bugger all in game. I can’t hook on tad, or point track or create spi in tgp. Very odd.

 

Make sure you aren’t in the “game” key binds section. There have been numerous issues with this lately.

 

As the others have stated - works as it should for me.

 

 

Cheers,

 

Ziptie

[coolts]

I'll try again tonight making special note of what key bind section I'm in.

[LeCuvier]

@coolts: If you own the Garmin NS430 then that could be the cause of your issue. The NS430 should be disabled for the A-10C II (as it is for the version I), but currently it isn't. That's a reported bug. Now if you have bound TMS Fwd to a command for the NS430 then it will not do anything for the Hog II. You can bind it in Options/Controls, but it will not do anything in the game. I haven't tried this myself, but you might see the same issue in other modules where the NS430 is enabled (in Options/Specials/NS430).

Edited October 19, 2020 by LeCuvier

[The_GhostRider]

I had the same issue with the default bindings, it turns out that TMS Fwd was not mapped on my warthog. I set the binding manually and it's been good since.

[coolts]

Can confirm I am in A-10C II real settings

 

"HOTAS TMS Forward" highlighted in red.

 

Cleared and re-added. Made no difference.

Tried key combos and they work fine. I can Point track and set SPI using keys

Checked stick TMS DX functions in control panel --> game controllers and working fine.

DCS lets me remap TMS FWD in settings but does not work in game.

(checked flying A-10c II in mission editor).

 

Will verify other modules tonight.

Edited October 19, 2020 by coolts

[LeCuvier]

"HOTAS TMS Forward" highlighted in red.

Will verify other modules tonight.

This line highlighted in red indicates to me that there is an issue in the file "Joystick - HOTAS Warthog.lua". Have you edited this file?

Either way, I would suggest you run a Repair!

[coolts]

Nope. Never heard of it. Might delete it and run repair? Is that a dcsupdater.exe switch?

 

File might have borked during install.

Edited October 19, 2020 by coolts

[Frederf]

It's either a problem with the baseline .lua that defines the control in the game directory or the user .diff.lua which is the difference file that is the user preference differences from default.

 

I would try first to find the .diff.lua file that corresponds to the problematic controller in \Saved Games\DCS.openbeta\Config\Input\A-10C II\joystick\ and temporarily move it (e.g. to desktop). If that file was the issue then the next run of the program will have no red highlight and all bindings for that controller will be default again.

 

Then you can bind that controller again as new or if you're brave try to find the offending line in the .diff.lua that you moved, erase it, and put it back.

[coolts]

Cheers man. Tried all that but no joy. Uninstalled the lot.

 

Cleaned registry of all DCS fluff so will reinstall once desire to buy a console has subsided :)

[coolts]

Fixed with clean install. I'm sure it was just a rogue .lua file but I'd not done a clean install in years and it was due. Now back to re--re learning the hog :)