Eldur Posted July 24, 2020 Posted July 24, 2020 I've had this for quite some time now and I thought it was kinda related to the abysmal performance of 256. I've got the roll SAS switch mapped to my TMWH throttle unit, but using a Target script that sets most of the buttons to "pulse" so they actually can be mapped as keystrokes without the special 2/3-way edits of the luas. Whenever I flick that switch, it unrealiably does one of those: - ~15% doesn't switch at all - ~5% switches it as required - ~80% switches twice in a row quickly (on/off), so literally no actual effect In other words, the thing is totally useless. I remember it being without issues a fair while ago though. What's up with that? BTW I've seen other switched in some modules do the same, like the RWR PWR switch on the Hornet for example, which had been fixed IIRC (still using a keyboard press though)... I guess that's somehow related to switches with solenoids to them.
RustBelt Posted July 24, 2020 Posted July 24, 2020 This is a DCS interface thing. Sometimes one quick trigger pull causes both my sidewinders to fire at once. It's a Timing thing Try slowing the "pulse".
eatthis Posted July 24, 2020 Posted July 24, 2020 could also be a dirty switch causing bounce. test it using a different switch/button. personally i put the roll sas on the pinky switch in the warthog throttle, easy to flick ina fight and hard to accidentally press 7700k @5ghz, 32gb 3200mhz ram, 2080ti, nvme drives, valve index vr
Home Fries Posted July 25, 2020 Posted July 25, 2020 I found I need to set a KBPress value of at least 50 in TARGET to get DCS to consistently recognize the keystroke. In some aircraft (like the hornet), some keystrokes may need to go up to 80-100ms. -Home Fries My DCS Files and Skins My DCS TARGET Profile for Cougar or Warthog and MFDs F-14B LANTIRN Guide
Airhunter Posted July 25, 2020 Posted July 25, 2020 I bound mine to 3 rocker switches on my Virpil throttle. Works fine for me.
Eldur Posted July 26, 2020 Author Posted July 26, 2020 I found I need to set a KBPress value of at least 50 in TARGET to get DCS to consistently recognize the keystroke. In some aircraft (like the hornet), some keystrokes may need to go up to 80-100ms. Just hit my guess, and yes, some in the Hornet take some considerable time, like the launch bar one. Guess I'll have to delve down the utterly crappy TARGET software again to change that accordingly. That piece of kit is the perfect example of how "user friendly" is not to be made... and I've beaten Trespasser: Jurassic Park aka The Arm Simulator (which would work tremendously well in VR BTW, totally worth a remake) back in the day. Probably also seeing this a lot more often now due to the abysmal performance as of 2.5.6... Nevertheless, this is something that needs to be fixed on DCS's end.
Recommended Posts