Kayos Posted December 21, 2019 Posted December 21, 2019 Seem every time I fire a missile in the F-16 lately it launches 2. Sometime 4 at the same time. Anyone experience this? It's not happening with other modules and only started this week. [sIGPIC][/sIGPIC]
RaceFuel85 Posted December 21, 2019 Posted December 21, 2019 No.... I think you may have an issue with your control hardware sending multiple input impulses
Kayos Posted December 21, 2019 Author Posted December 21, 2019 No.... I think you may have an issue with your control hardware sending multiple input impulses Only does it with the F-16 though. I'll try remapping it. [sIGPIC][/sIGPIC]
unknown Posted December 21, 2019 Posted December 21, 2019 Never had that problem, would also guess there is a controller problem. Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings
falcon_120 Posted December 21, 2019 Posted December 21, 2019 Never had that problem, would also guess there is a controller problem. Looks like a controller issue, look in your windows control pannel if that specific button is "flashing" when you press it. You could also: -Try assigning the missile launch to a different button -Check that is not double mapped inadvertently
Frederf Posted December 21, 2019 Posted December 21, 2019 Seem every time I fire a missile in the F-16 lately it launches 2. Sometime 4 at the same time. Anyone experience this? It's not happening with other modules and only started this week. Yes both with AIM-120 and AIM-9. It's some bug. You can't even fire an AIM-120 without a prolonged press which negates the possibility that it's a controller issue.
unknown Posted December 21, 2019 Posted December 21, 2019 (edited) Yes both with AIM-120 and AIM-9. It's some bug. You can't even fire an AIM-120 without a prolonged press which negates the possibility that it's a controller issue. Would be nice to know what controller you and Kayos are using. Maybe your controller is repeating to send the signal instead of a "ON until release of button -> OFF" signal (ON/OFF/ON/OFF...) I can press and hold the weapon release button for minutes(ok, tested only for 30 seconds) and i shoot only one AIM-120 or AIM-9. Or every press one missile. Edited December 21, 2019 by unknown Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings
ED Team cofcorpse Posted December 21, 2019 ED Team Posted December 21, 2019 It's very hard to say anything specific without track. Could you record a short one?
NeMoGas Posted December 21, 2019 Posted December 21, 2019 I have this happen all the time too. I will mostly chock it up to my TMW switch registering multiple presses per one press, and even sometimes on release. I commonly have up to 4 missiles launch all at the exact same time, hitting each other about 200m in front of me. This would be avoided if we had the delay with missile releases, but as of right now it seems instant.
Wizzard Posted January 2, 2020 Posted January 2, 2020 I have this issue with my CH fighterstick. For some reason DCS doesn't pick up the pickle press every time. So I just switched it out to the trigger and it works perfectly now.
Eldur Posted January 2, 2020 Posted January 2, 2020 I've had this a few times, only in the F-16 and 18 so far, could be the 14 as well, don't remember exactly. Might be the stick FFB2 here) sending multiple presses (well, it's not a Logitech mouse though - these are built to do exactly that after about three weeks of normal usage, simply Swiss quality). But just a proposal: Why not implement a protection for this that doesn't fire another missile if multiple presses are registered within a certain short timeframe, like 100ms? Especially if the "second" press is being held (read: User presses and holds trigger, but the controller might send 2 or 3 and just hold the last one)... just keep this as optional, and separate for different triggers... I just wouldn't put that at a high priority personally. BTW this could also be done at the user's end with AutoHotkey, most probably.
Harlikwin Posted January 2, 2020 Posted January 2, 2020 I've had it happen with the viper. No issues with other modules. New hotness: I7 9700k 4.8ghz, 32gb ddr4, 2080ti, :joystick: TM Warthog. TrackIR, HP Reverb (formermly CV1) Old-N-busted: i7 4720HQ ~3.5GHZ, +32GB DDR3 + Nvidia GTX980m (4GB VRAM) :joystick: TM Warthog. TrackIR, Rift CV1 (yes really).
Strong05 Posted January 6, 2020 Posted January 6, 2020 (edited) Same problem here, I also submitted a bug report, but the track file size limitations prevented me from loading the track file. I also get a problem using a modifier with an assigned controller button for F2 view, and only F2. F10 and F1 work fine. No problem with any other module, so something weird is going on with the controls of the Viper. Edited January 6, 2020 by Strong05 5800X3d, 32GB DDR4@3400, 6800 xt, Reverb G2, Gunfighter/TMWH
Wilbus Posted January 9, 2020 Posted January 9, 2020 Same issue here. I believe I managed to save the track file while offline and HOTAS fumbling with something completely different after flying the Hornet and KA50 (my muscle memory was at the right place at the time). Fired Two Aim 9's at the exact same time with one press. It only happens in the Viper so not a control issue. Will see if I can get the file uploaded.
fudabidu Posted January 12, 2020 Posted January 12, 2020 Years ago I opened up an older Saitek stick because the trigger was acting strange. Inside I found switches identical to those used in computer mice. Grabbed an old mouse, spent 15 minutes soldering and the joystick was fixed. After 6 years my left mouse button would start double-clicking instead of single-clicking / holding. A friend of mine also had the same issue with his Logitec mouse. In both cases the exact same switches were used again. So, this behavior is exactly what I'd expect from a broken switch. Map the pickle button to something else and if it works fine there is your problem.
Recommended Posts