ZoscheHH Posted May 6, 2017 Share Posted May 6, 2017 Noticed this bug when I used my newly bought Puma flight trainer in the new Argo campaign. Bug seems to only appear when using certain analoque hardware input devices. Haven't noticed it before while using the Hotas X Stick. That might be because now I'm not using an additional keyboard-to-stick overlay program such as Joytokey anymore. MSI H170M-A Pro with i5-6600K @ 3.5 Ghz, 16Gb DDR4-2133, ASUS GTX 1080 TI 11 Gb DDR5 352bit, Win10 Pro, PUMA Flight Trainer, DCS 1.5, 2.5 open beta, UH-1H, KA50, Mi8-MTV2, Gazelle. Have a safe flight ! Link to comment Share on other sites More sharing options...
Sharkku Posted June 4, 2017 Share Posted June 4, 2017 Yes, I have this too. You have to "bring it to life" by moving it with the mouse or keyboard first, after that it works. It's been reported in another thread as well. Guess it's not a high priority bug, since it's not game breaking. Link to comment Share on other sites More sharing options...
mr_mojo97 Posted June 4, 2017 Share Posted June 4, 2017 Yeah I noticed this too. It's quite annoying. As above, use the mouse wheel to crank it up about halfway then you'll be able to use the axis as normal. MSI M5 z270 | Intel i5 7600k (OC) 4.8GHz | MSI GTX1080ti Gaming X 11Gb | 500gb Samsung 970 Evo NVME M.2 (DCS World) | 500gb Samsung 850 Evo SSD (OS and Apps) | 32Gb 2400MHz DDR4 - Crucial Ballistix | Be Quiet Silent Loop 240mm | NZXT H440 case | Thrustmaster Warthog - 47608 with Virpil Mongoose joystick base | MFG Crosswinds - 1241 | Westland Lynx collective with Bodnar X board | Pilot's seat from ZH832 Merlin | JetSeat | Oculus Rift S | Windows 10 | VA | Link to comment Share on other sites More sharing options...
Recommended Posts