Jump to content

Recommended Posts

Posted

I just re-installed my pit and got hit with the bug where ok would not work once I setup my joystick. Looking in the log files I was getting the following error:

 

GUI Error: [string ".\Scripts\Input\Data.lua"]:1270: bad argument #2 to 'format' (number expected, got nil)
GUI debug.traceback: stack traceback:
[C]: ?
[C]: in function 'format'
[string ".\Scripts\Input\Data.lua"]:1270: in function 'writeForceFeedbackSettings_'
[string ".\Scripts\Input\Data.lua"]:1458: in function 'saveDeviceProfile'
[string ".\Scripts\Input\Data.lua"]:1508: in function 'saveChanges'
[string ".\MissionEditor\modules\me_options_controls..."]:93: in function 'save'
[string ".\MissionEditor\modules\me_options.lua"]:380: in function 'func'
[string "./dxgui/bind/Widget.lua"]:203: in function <[string "./dxgui/bind/Widget.lua"]:181>
[C]: in function '?'
[string ".\MissionEditor\MissionEditor.lua"]:908: in main chunk
stack traceback:
[C]: ?
[C]: in function 'format'
[string ".\Scripts\Input\Data.lua"]:1270: in function 'writeForceFeedbackSettings_'
[string ".\Scripts\Input\Data.lua"]:1458: in function 'saveDeviceProfile'
[string ".\Scripts\Input\Data.lua"]:1508: in function 'saveChanges'
[string ".\MissionEditor\modules\me_options_controls..."]:93: in function 'save'
[string ".\MissionEditor\modules\me_options.lua"]:380: in function 'func'
[string "./dxgui/bind/Widget.lua"]:203: in function <[string "./dxgui/bind/Widget.lua"]:181>
[C]: in function '?'
[string ".\MissionEditor\MissionEditor.lua"]:908: in main chunk

 

I traced the problem back to my F16 MFD's. The default profile for them are missing some default configuration for force feedback, which causes the save profile to crash.

 

To fix open "F16 MFD1.lua" and "F16 MFD2.lua" in the "DCS World\Mods\aircrafts\A-10C\Input\A-10C\joystick" folder and replace

forceFeedback = {
},

with

forceFeedback = {
trimmer = 1.000000,
shake = 0.500000,
swapAxes = false,
invertX = false,
invertY = false,
},

 

Now delete the files that begin with "F16 MFD" from your "C:\Users\<Username>\Saved Games\DCS\Config\Input\A-10C\joystick" folder. Restart DCS and you can now configure your joysticks again.

  • Like 1
Posted

Rep inbound

 

+1 for that. Nice.

This was a Boutique Builder iBuypower rig. Until I got the tinker bug again i7 920 @3.6Mhz 12Gig Corsair XMS3 ram 1600 Nvidia 760 SLi w/4Gig DDR5 Ram Intel 310 SSD HDD 160 Gb + Western Digital 4Terabyte HDD Creative SB X-Fi HD Audio Logitech X-530 5.1 Surround Speaker System Dual Acer 32"Monitors. PSU 1200 w Thermaltake Win10 64Bit.

Posted (edited)

Thx you!!!!:megalol: +1 But I'll have to owe ya. Need to spread it around.

Edited by slowhand

[sIGPIC][/sIGPIC] SMOKE'M:smoke: IF YA GOT'M!:gun_rifle:

H2o Cooler I7 9700k GA 390x MB Win 10 pro

Evga RTX 2070 8Gig DD5

32 Gig Corsair Vengence, 2T SSD.

TM.Warthog:joystick: :punk:, CV-1:matrix:,3x23" monitors, Tm MFD's, Saitek pro rudders wrapped up in 2 sheets of plywood:megalol:

  • 2 months later...
Posted

How the f**& did you figure that out??? :huh:

 

Long story short: I configured some basic controls, then played A10C for about 10 min before deciding to get the TM MFD's. I also decided to load DCS World and access the modules through that via Steam. When I got the MFDs, I plugged them in and they were recognized in A10C. But I had a problem launching the game, so had to reinstall. Of course, that wiped my control settings, so I went back in to change them and ran in to this...

 

I found your thread after a few hours of tearing my hair out and wondering why no one else seemed to have this problem.

 

Thanks dude! :thumbup:

Intel i9 9900k | 32 GB RAM | EVGA RTX 2080Ti | 2x 1TB Samsung 970 Evo

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...