Trigger Posted December 27, 2022 Posted December 27, 2022 (edited) What am I doing wrong? When activating the gun, the message "Coincidence" appears. The message only appears when choosing "Gun". Nevertheless, all weapons (also rockets) are blocked. Didn't happen before. Edited December 27, 2022 by Trigger Win 10/64 Pro, Asus ROG Z390-E 1151 v2, Intel Core i7-9700K@3,60 GHz, RTX 4070 Ti Super Phoenix GS 64 GB, DCS: NVMe SSD 970 EVO 1TB, Maps: SSD870 EVO 1TB, Cougar HOTAS (U2nxt) modified, Simpeds, TIR 5
admiki Posted December 27, 2022 Posted December 27, 2022 Coincidence means that both you and CPG have selected gun. What do you mean by blocked?
Trigger Posted December 27, 2022 Author Posted December 27, 2022 Blocked ment to me, that no weapons at all were functioning. BUT-finally I found the (my) mistake. Key binding. Had put the trigger on BUCS instead first detent. Now, all is perfect. Even The "Coincidence" doesn't matter. Thanks for your help. And forgive my poor English. It's not my native language Win 10/64 Pro, Asus ROG Z390-E 1151 v2, Intel Core i7-9700K@3,60 GHz, RTX 4070 Ti Super Phoenix GS 64 GB, DCS: NVMe SSD 970 EVO 1TB, Maps: SSD870 EVO 1TB, Cougar HOTAS (U2nxt) modified, Simpeds, TIR 5
bradmick Posted December 27, 2022 Posted December 27, 2022 (edited) 8 hours ago, admiki said: Coincidence means that both you and CPG have selected gun. What do you mean by blocked? Coincidence means that you have selected the gun, and for some reason it is not “coincident” with your LOS. I.e. there is an error between where you are looking and where the gun is reporting it’s looking. Both crew members literally can’t have the gun actioned at the same time. Edited December 27, 2022 by bradmick 1
Solution Trigger Posted December 28, 2022 Author Solution Posted December 28, 2022 Thanks for the detailed explanation, bradmick. In the meantime, I found further explanations in "Chuck's AH-64 Guide, part 14, offence weapons & armament". Interesting for me: after solving my problem by finding the right key, the "coincidence" message still exists, without any consequences when firing the gun. Also shows the Cp/G´s IHADSS "PGUN", which means to me that the pilot, not Cp/G, actually is in command. Anyway, all is fine for now and thanks to all, who tried to help Win 10/64 Pro, Asus ROG Z390-E 1151 v2, Intel Core i7-9700K@3,60 GHz, RTX 4070 Ti Super Phoenix GS 64 GB, DCS: NVMe SSD 970 EVO 1TB, Maps: SSD870 EVO 1TB, Cougar HOTAS (U2nxt) modified, Simpeds, TIR 5
Recommended Posts