xaoslaad Posted July 8, 2016 Posted July 8, 2016 (edited) I can't set the flaps on my throttle for the FW 190. Those three squares are greyed out. I tried removing all the controller files and the problem persisted. Is this a known issue? Edited July 11, 2016 by BIGNEWY TITLE
westr Posted July 8, 2016 Posted July 8, 2016 I have the same problem. RYZEN 7 3700X Running at 4.35 GHz NVIDIA GeForce GTX 1080Ti 32gb DDR4 RAM @3200 MHz Oculus CV1 NvME 970 EVO TM Warthog Stick & Throttle plus 11" extension. VKB T-Rudder MKIV
Art-J Posted July 9, 2016 Posted July 9, 2016 It certainly appeared in 1.5.4. OB. At first I thought it was result of copying old input config files from 1.5.3, but it's still there with clean, default assignments for TH Warthog set. "Falps up/down" work (albeit in a bit strange way), the others are greyed out. i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
ED Team Racoon Posted July 11, 2016 ED Team Posted July 11, 2016 Could you please make screen of options menu. I don't have any blocks in flaps control. Can set them easily. Using fresh update for 1.5.4 release version
ED Team BIGNEWY Posted July 11, 2016 ED Team Posted July 11, 2016 I do not fly the FW-190 a lot, but this is what I am seeing Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
ED Team Racoon Posted July 11, 2016 ED Team Posted July 11, 2016 I do not fly the FW-190 a lot, but this is what I am seeing It's a bug with Hotas throttle for sure. Could you make a report in Mantis please?
ED Team BIGNEWY Posted July 11, 2016 ED Team Posted July 11, 2016 It's a bug with Hotas throttle for sure. Could you make a report in Mantis please? reported, thanks #0035274 Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
ED Team Racoon Posted July 11, 2016 ED Team Posted July 11, 2016 Ok. It's not a bug. It's a feature )) We have new keys for flaps special for HOTAS throttle now because HOTAS have only two keys in three positions switch. You can see buttons mapped for Toggle flaps up and down positions. When middle (MVR) position of the flaps switch can't be mapped but should work correct.
Sporg Posted July 12, 2016 Posted July 12, 2016 Ok. It's not a bug. It's a feature )) We have new keys for flaps special for HOTAS throttle now because HOTAS have only two keys in three positions switch. You can see buttons mapped for Toggle flaps up and down positions. When middle (MVR) position of the flaps switch can't be mapped but should work correct. I made it work! I have the Warthog throttle, and didn't work right away, like reported in here. My fix was to clear the "Toggle Flaps Up" and "Toggle Flaps Dn" key assignments, and then assign them again to Flaps UP and Flaps DN on my Warthog throttle. Now it works perfectly, as described by Racoon: Flaps UP = Flaps up Flaps MVR = Take off flaps Flaps DN = Landing flaps Thanks for helping us use our three-way switches. :) System specs: Gigabyte Aorus Master, i7 9700K@std, GTX 1080TI OC, 32 GB 3000 MHz RAM, NVMe M.2 SSD, Oculus Quest VR (2x1600x1440) Warthog HOTAS w/150mm extension, Slaw pedals, Gametrix Jetseat, TrackIR for monitor use
Shahdoh Posted July 12, 2016 Posted July 12, 2016 I had the same issue, though mine would not clear that way. I had set Gear up/down to the Warthog's flap switch, once I cleared that, the conflict went away and then I could set things as I wish with the new control assignments (Toggle Flaps up/dn).
Sporg Posted July 12, 2016 Posted July 12, 2016 (edited) I had the same issue, though mine would not clear that way. I had set Gear up/down to the Warthog's flap switch, once I cleared that, the conflict went away and then I could set things as I wish with the new control assignments (Toggle Flaps up/dn). My problem was that my WT flaps switch was already assigned to flaps up and flaps down. So I could not see the conflict, only that the controls did not respond. Edit: Now I would love to be able to use for instance my APU Start switch as a 2-way switch for MW50, so that APU Start was "On", and OFF was "Off". :) Edited July 12, 2016 by Sporg System specs: Gigabyte Aorus Master, i7 9700K@std, GTX 1080TI OC, 32 GB 3000 MHz RAM, NVMe M.2 SSD, Oculus Quest VR (2x1600x1440) Warthog HOTAS w/150mm extension, Slaw pedals, Gametrix Jetseat, TrackIR for monitor use
Recommended Posts