sotosev Posted November 17, 2015 Posted November 17, 2015 Problem using 3 buttons in hotas warthog controller. When I first move flaps switch to middle on controller flaps don’t move, return my switch back and then middle again now works. Same happens with left, right throttle from engine off to idle. First time I use them to start engines does nothing second attempt to start engines controllers work properly. I checked my controllers outside game in windows setting and work fine every time I press flaps switch or idle cut off. This problem doesn’t occur in DCS world 1.1.6 , only in 1.5.1 open beta. Is this a bug or I need to do something in my in game settings? System specs below Case - Antec Three Hundred PSU - Corsair AX750watt Board - MSI Z170A GAMING PRO CPU - Intel i5 6600K 3900MHz Cooler - CoolerMaster Hyper 212 Plus Memory - Kingston HYPERX 16G DDR4 2400Mhz CL15 Graphics - MSI GEFORCE GTX 980 GAMING 4G SSD - Samsung 950 PRO 256GB M.2 NVMe Monitor - Philips 277E 27" 1920x1080 60Hz OS - Windows 10 Home 64bit Flight Controllers - Thrustmaster HOTAS WARTHOG, Saitek COMBAT RUDDER PEDALS, TrackIR 4, Track Clip Pro [sIGPIC][/sIGPIC]
Aeger Posted December 2, 2015 Posted December 2, 2015 Try this: Go to Options -> Misc -> Enable "Synchronize Cockpit Controls with HOTAS at Mission Start" Also make sure you don't have any other throttles/sticks connected other than the ones you use for DCS world. [sIGPIC][/sIGPIC]
some1 Posted December 3, 2015 Posted December 3, 2015 I also noticed that, it looks like the game does not recognize that the joystick button is pressed at the beginning of a mission so it doesn't update the corresponding control when you release it. Hardware: VPForce Rhino, FSSB R3 Ultra, Virpil WarBRD, Hotas Warthog, Winwing F15EX, Slaw Rudder, GVL224 Trio Throttle, Thrustmaster MFDs, Saitek Trim wheel, Trackir 5, Quest Pro
sotosev Posted December 13, 2015 Author Posted December 13, 2015 I pleasantly noticed that the problem solved in version 2.0 Alpha. Althought the problem still exists in ver 1.5.2. I am sure after lot of tests that problem isn't in my stick or other reason but in Open beta ver of the game. System specs below Case - Antec Three Hundred PSU - Corsair AX750watt Board - MSI Z170A GAMING PRO CPU - Intel i5 6600K 3900MHz Cooler - CoolerMaster Hyper 212 Plus Memory - Kingston HYPERX 16G DDR4 2400Mhz CL15 Graphics - MSI GEFORCE GTX 980 GAMING 4G SSD - Samsung 950 PRO 256GB M.2 NVMe Monitor - Philips 277E 27" 1920x1080 60Hz OS - Windows 10 Home 64bit Flight Controllers - Thrustmaster HOTAS WARTHOG, Saitek COMBAT RUDDER PEDALS, TrackIR 4, Track Clip Pro [sIGPIC][/sIGPIC]
_Dredd Posted December 13, 2015 Posted December 13, 2015 I just noticed this in 1.5.2 Assigning controls there is a bad delay recognising the key input to assign, I have to press the controller button I'm assigning 3 or more times for it to be recognised. I ad the issue with both HOTAS and Cougar MFDs. Current Flight Rig i7 4960X @ 4.6Ghz ASUS Rampage IV Formula G.SKILL TridentX 2400Mhz 32GB DDR3 Crucial 1TB MX300 SSD MSI Gaming X 1080Ti Samsung 55" JS8000 SUHD 4K Windows 10 x64 TrackIR 5, Warthog HOTAS Saitek Pro Flight Combat Pedals Custom Akers-Barnes, MkI eyeball.
Feuerfalke Posted December 13, 2015 Posted December 13, 2015 Probably the same problem as described in this thread. :( http://forums.eagle.ru/showthread.php?t=152231 MSI X670E Gaming Plus | AMD Ryzen 7 7800X3D | 64 GB DDR4 | AMD RX 6900 XT | LG 55" @ 4K | Cougar 1000 W | CreativeX G6 | TIR5 | CH HOTAS (with BU0836X-12 Bit) + Crosswind Pedals | Win11 64 HP | StreamDeck XL | 3x TM MFD
Recommended Posts