Razor18 Posted April 28, 2020 Posted April 28, 2020 (edited) Hi There, not a big thing, but the long button presses (Sensor Control Switch FWD LONG for LHAQ and HARM/RAID/FLIR FOV LONG for TGP CCD/FLIR toggle) only switch to their "long" press function after you release the button, instead of at 0.8 sec of pressing (so that you know, it was pressed already "long enough"). If you hold the button for 10 sec, then it will be 10 seconds for the switch, when you release. I dunno how is it in RL Hornet, but it doesn't make too much sense as it is, as there is no subsequent "third function" to wait for, when pressing longer than 0.8 sec. Good example is the A-10C, where the same BUTTON LONG function works flawless. If you press short, it switches instantly, if you hold it, it switches at 0.8 sec even if you still hold it. Edited April 28, 2020 by Razor18
SDsc0rch Posted April 28, 2020 Posted April 28, 2020 yes... agree completely this is a little annoying you press-and-hold - expecting something to happen....... then it doesn't and you wonder if you understood correctly then release and.. "oh! there it is!" TECHNICALLY they're correct - but....... that's also kinda not what we're expecting i7-4790K | Asus Sabertooth Z97 MkI | 16Gb DDR3 | EVGA GTX 980 | TM Warthog | MFG Crosswind | Panasonic TC-58AX800U [sIGPIC][/sIGPIC]
Harker Posted April 28, 2020 Posted April 28, 2020 yes... agree completely this is a little annoying you press-and-hold - expecting something to happen....... then it doesn't and you wonder if you understood correctly then release and.. "oh! there it is!" TECHNICALLY they're correct - but....... that's also kinda not what we're expecting I actually think they're not correct. The topic has been brought up before and the consensus is that it should actuate as soon as the time limit is reached and not wait for release. The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord. F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3 - i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro
Razor18 Posted April 28, 2020 Author Posted April 28, 2020 Absolutely! Especially in a task saturated situation I expect a feedback to my button command, because probably I'm doing a dozen other things multitasking, and might even freeze up my thumb or finger waiting, as "nothing changed" since I pressed and held my button...
Darcwaynard Posted April 28, 2020 Posted April 28, 2020 Agreed if the button is held longer than a short press it should trigger the long press action once 0.8 seconds is reached. It's not like you can change your mind or press a cancel button. If it's not programmed this way IRL then wtf Boeing. Sent from my SM-A530W using Tapatalk [sIGPIC][/sIGPIC] Amd Fx 8350 4.3 GHz - MSi Gtx 1060 6gb - 16gb DDR3 A-10C - AV8B - F-5E - Mig-21 - FC3 - CA - UH-1H - Black Shark - AJ3-37 - M-2000C - F-16C Viper - F-86F - Spitfire - Fw-190 - F/A-18C - F-14 - Normandy - NTTR - Persian Gulf
Tholozor Posted April 28, 2020 Posted April 28, 2020 If it's not programmed this way IRL then wtf Boeing. McDonnell Douglas. REAPER 51 | Tholozor VFA-136 (c.2007): https://www.digitalcombatsimulator.com/en/files/3305981/ Arleigh Burke Destroyer Pack (2020): https://www.digitalcombatsimulator.com/en/files/3313752/
Darcwaynard Posted April 28, 2020 Posted April 28, 2020 McDonnell Douglas.DOH megafacepalm Sent from my SM-A530W using Tapatalk [sIGPIC][/sIGPIC] Amd Fx 8350 4.3 GHz - MSi Gtx 1060 6gb - 16gb DDR3 A-10C - AV8B - F-5E - Mig-21 - FC3 - CA - UH-1H - Black Shark - AJ3-37 - M-2000C - F-16C Viper - F-86F - Spitfire - Fw-190 - F/A-18C - F-14 - Normandy - NTTR - Persian Gulf
Recommended Posts