karpiyon Posted May 4, 2023 Posted May 4, 2023 I could not find a place to post it - this is not a bug. What is the minimum required time for key presses in DCS. E.g. let say I want to enter 123 in the F-16 ICP. What would be the min time for the following Action Minimum time in ms Press & hold "1" ? Wait (if required) ? Press & hold "2" ? Wait (if required) ? Press & hold "3" ? Wait (if required) ? 1
silverdevil Posted May 4, 2023 Posted May 4, 2023 2 hours ago, karpiyon said: I could not find a place to post it - this is not a bug. What is the minimum required time for key presses in DCS. E.g. let say I want to enter 123 in the F-16 ICP. What would be the min time for the following Action Minimum time in ms Press & hold "1" ? Wait (if required) ? Press & hold "2" ? Wait (if required) ? Press & hold "3" ? Wait (if required) ? Maybe I am missing something but I am not required to hold any ICP buttons for presses to register. AKA_SilverDevil Join AKA Wardogs Email Address My YouTube “The MIGS came up, the MIGS were aggressive, we tangled, they lost.” - Robin Olds - An American fighter pilot. He was a triple ace. The only man to ever record a confirmed kill while in glide mode.
Solution rob10 Posted May 4, 2023 Solution Posted May 4, 2023 I use 50 millisec on most, bumped to 75 or 100 in a few cases if I don't get it to register consistently. 6 minutes ago, silverdevil said: Maybe I am missing something but I am not required to hold any ICP buttons for presses to register. If you use a UFC or keyboard you likely don't need to worry about this. If you are using something else to emulate button press, DCS won't register the really quick press (near instantaneous) that it may send and you'll get inconsistent presses, thus you need to add a "hold it down" time to get consistency.
karpiyon Posted May 4, 2023 Author Posted May 4, 2023 1 hour ago, rob10 said: I use 50 millisec on most, bumped to 75 or 100 in a few cases if I don't get it to register consistently. If you use a UFC or keyboard you likely don't need to worry about this. If you are using something else to emulate button press, DCS won't register the really quick press (near instantaneous) that it may send and you'll get inconsistent presses, thus you need to add a "hold it down" time to get consistency. So hold down for 50ms, and do you wait between consecutive key presses? I created a plugin for VA which ha been used for quite some time. I am adding a new ability to enter a complete set of navigation points and I want to to take as less as possible to enter. So far I've been using holdDownTime=150ms & waitAfter=100ms
karpiyon Posted May 4, 2023 Author Posted May 4, 2023 I tested with 50ms hold down & 5ms wait after and it is working well for the Button numbers. I'm down to 12sec for the entire data including elevation and time per steer point. null
silverdevil Posted May 4, 2023 Posted May 4, 2023 4 hours ago, rob10 said: I use 50 millisec on most, bumped to 75 or 100 in a few cases if I don't get it to register consistently. If you use a UFC or keyboard you likely don't need to worry about this. If you are using something else to emulate button press, DCS won't register the really quick press (near instantaneous) that it may send and you'll get inconsistent presses, thus you need to add a "hold it down" time to get consistency. ah i understand. i personally use one of these https://www.simgears.com/products/shop-f16-icp-replica/ or click onscreen with mouse. perhaps why i was confused AKA_SilverDevil Join AKA Wardogs Email Address My YouTube “The MIGS came up, the MIGS were aggressive, we tangled, they lost.” - Robin Olds - An American fighter pilot. He was a triple ace. The only man to ever record a confirmed kill while in glide mode.
rob10 Posted May 5, 2023 Posted May 5, 2023 7 hours ago, karpiyon said: So hold down for 50ms, and do you wait between consecutive key presses? I created a plugin for VA which ha been used for quite some time. I am adding a new ability to enter a complete set of navigation points and I want to to take as less as possible to enter. So far I've been using holdDownTime=150ms & waitAfter=100ms Glad it's working for you. I'd test it, but I doubt you need any wait between presses (I'd have to check, but I think I have a few that are consecutive and don't have a wait). You might get away with 25ms. Mine was on F-18. I know there seem to be differences in press time required depending on which system you're pressing in the F-18.
Recommended Posts