Eagle7907 Posted May 29, 2020 Share Posted May 29, 2020 (edited) I’ve mentioned this to IronMike a few months ago (maybe longer), but it hasn’t been fixed and no response from any developers. When a player has Jester lock a target, he uses STT. Next, you tell him to use PSTT. I’ve noticed the first time since start of mission he will indeed switch to PSTT. However, after breaking lock from either being commanded or a kill, when Jester is commanded again to lock a target, then commanded to switch to PSTT, he will NOT switch to PSTT. Each time this has happened, I have switched to RIO seat to find the STT mode still on pulse doppler. There seems to be a disconnect with Jester and Pulse STT. Is this still be worked on? Or has this been fixed and somehow I’m screwing something up? This bug is really annoying. Sent from my iPhone using Tapatalk Pro Edited May 29, 2020 by Eagle7907 Win 10, AMD FX9590/water cooled, 32GB RAM, 250GB SSD system, 1TB SSD (DCS installed), 2TB HD, Warthog HOTAS, MFG rudders, Track IR 5, LG Ultrawide, Logitech Speakers w/sub, Fans, Case, cell phone, wallet, keys.....printer Link to comment Share on other sites More sharing options...
Airhunter Posted May 29, 2020 Share Posted May 29, 2020 +1 A workaround would be locking the target with PAL. Link to comment Share on other sites More sharing options...
Eagle7907 Posted May 29, 2020 Author Share Posted May 29, 2020 Yeah I do that when it’s danger close right before merge. But nevertheless it’s still a bug and not correct behavior. Sent from my iPhone using Tapatalk Pro Win 10, AMD FX9590/water cooled, 32GB RAM, 250GB SSD system, 1TB SSD (DCS installed), 2TB HD, Warthog HOTAS, MFG rudders, Track IR 5, LG Ultrawide, Logitech Speakers w/sub, Fans, Case, cell phone, wallet, keys.....printer Link to comment Share on other sites More sharing options...
Recommended Posts