compuway Posted May 27, 2014 Posted May 27, 2014 Hi folks, I have a bit of a strange issue. I have DCS World, A-10C, BS2, P51, FC3 and UH-1H running two different machines, one on a MSI GT60 laptop and on a PC. Both run Win 7 Home Premium. On both systems I have a TM Warthog and Track IR. No mods on either system. On the Warthog I have mapped the F1, F2, F3 and F4 keys to the DMS switch in the DSC Control Panel (not in T.A.R.G.E.T.) All has been working fine until one of the final 1.2.7 updates when the views on the PC stopped working. The laptop still works OK. F1 on the keyboard still brings up the cockpit view but the other view "F" keys don't work, either from the keyboard or from the Warthog DMS switch. Everything works fine in the DCS Control Panel. I have cleared them several times and remapped and all appears good including in the Windows Devices properties. Once you get in game they don't work. The F10 map key works fine as does the Track IR. This is the same for all aircraft in all simulations so it must be a common DCSW issue. I have recently upgraded to 1.2.8 hoping that this would fix the problem, but alas it has not. :cry: It all seems very strange that it would affect one machine and not the other. The only thing that is different with the two is the laptop is running a single screen where as the PC is running multiple screens. (1 x 1920x1080 plus 2 x 800x600 TM Cougar MFD's) I have tried comparing .lua files but cannot see any difference there. I have not tried uninstalling and reinstalling everything.(YET!) Any ideas or solutions would be most welcome before I contemplate a reinstall.:helpsmilie: Thanks...Wayne Self Built Block 52 F-16 Cockpit - Win10 Pro 64Bit; i5-6600K @ 3.40GHz; ASROCK Z170 Extreme 4+; 32GB Corsair Vengence DDR3 1600MHz; AMD Radeon Vega 64 8GB HBM2; TM Warthog HOTAS; TM Cougar MFD x3; Saitek Pro Combat Pedals; TIR-5 w/Pro Clip; Logitech G510; Logitech G13; Gametrix KW908 G-Cueing Jetseat. [sIGPIC][/sIGPIC]
cichlidfan Posted May 27, 2014 Posted May 27, 2014 Try moving/renaming ..\Saved Games\DCS\Config\Input\A-10C and letting the game recreate the default controller settings. Note: Updates, repairs and reinstalls will not fix a problem in the Saved Games folder. ASUS ROG Maximus VIII Hero, i7-6700K, Noctua NH-D14 Cooler, Crucial 32GB DDR4 2133, Samsung 950 Pro NVMe 256GB, Samsung EVO 250GB & 500GB SSD, 2TB Caviar Black, Zotac GTX 1080 AMP! Extreme 8GB, Corsair HX1000i, Phillips BDM4065UC 40" 4k monitor, VX2258 TouchScreen, TIR 5 w/ProClip, TM Warthog, VKB Gladiator Pro, Saitek X56, et. al., MFG Crosswind Pedals #1199, VolairSim Pit, Rift CV1 :thumbup:
compuway Posted June 1, 2014 Author Posted June 1, 2014 Thanks cichlidfan, Gave that a try but no luck, same result. I have also tried without actually mapping the views to the Hotas. The "F" keys all work fine in the control panel set up but again in game only the F1, F5 & F10 keys are the only ones that work. I have had a look at the default, keyboard and joystick.lua files and they seem to have the correct entries for the F keys and associated views. One other thing I noticed today is it doesn't matter which aircraft I load and fly, whenever I come back to the options screen in the control panel it defaults to the UH-1H control set. Even though I may have flown the F-15C and afterwards exited, when I fire it back up it defaults to the UH-1H again. I am wondering if I just reload the whole damned thing and all my modules? Self Built Block 52 F-16 Cockpit - Win10 Pro 64Bit; i5-6600K @ 3.40GHz; ASROCK Z170 Extreme 4+; 32GB Corsair Vengence DDR3 1600MHz; AMD Radeon Vega 64 8GB HBM2; TM Warthog HOTAS; TM Cougar MFD x3; Saitek Pro Combat Pedals; TIR-5 w/Pro Clip; Logitech G510; Logitech G13; Gametrix KW908 G-Cueing Jetseat. [sIGPIC][/sIGPIC]
Recommended Posts