wolle Posted December 21, 2019 Posted December 21, 2019 (edited) I have not flown the Anton in a couple of months, but I flew it many times prior to that. I used to have two communications buttons mapped: "backslash" and "Ralt-backslash", one I used to bring up the comm menu on the ground, the other in the air. I can still bring up the comm menu on the ground, but not in the air any more. What am I doing wrong?:helpsmilie: Edited December 21, 2019 by wolle [sIGPIC][/sIGPIC] Intel Core I7 4820K @4.3 GHz, Asus P9X79 motherboard, 16 GB RAM @ 933 MHz, NVidia GTX 1070 with 8 GB VRAM, Windows 10 Pro
Bearskin Posted December 23, 2019 Posted December 23, 2019 (edited) I have the same problem in the F18, I can bring up the comms menu on the ground to refuel, re arm and choose a mission, but I cannot bring the comms menu up whilst in the air. So if I manage to kill the enemy plane, I have to land again to set up another mission. I have mine bound to joy 4 (the pinky lever on the joystick) plus the top thumb switch on the throttle, (the one that works the speed break). Just to add, I have the same setup in the Hog and it works flawlessly. Edited December 23, 2019 by Bearskin Z790, 13700K, RTX4080, 32 gig RAM, Warthog, WarBRD base , Virpil Pedals, Pico 4
Cunctator Posted December 23, 2019 Posted December 23, 2019 It works for me. In the Fw 190 A8, the "COMM Push to talk" button (Ralt + \) brings up the com menu while being airborne. I've mapped it to my stick, but the default key command functions too.
Frederf Posted December 23, 2019 Posted December 23, 2019 I have not flown the Anton in a couple of months, but I flew it many times prior to that. I used to have two communications buttons mapped: "backslash" and "Ralt-backslash", one I used to bring up the comm menu on the ground, the other in the air. I can still bring up the comm menu on the ground, but not in the air any more. What am I doing wrong?:helpsmilie: Nothing as far as I know. There are different methods of transmitting verbal information. Speaking aloud by itself is not productive for example when airborne. The act of keying an electric radio may be. You can think of the '\' as simply shouting words to the few meters around you and certain modules make things like engine noise and canopy state factors in communication. A lot of modern aircraft have ground intercoms where a telephone is plugged into the side of the vehicle overriding such engine/canopy state concerns.
Rolds Posted December 24, 2019 Posted December 24, 2019 I have this same problem, my push to talk keybind sometimes works and sometimes doesn't. When it doesn't, fiddling with seemingly unrelated things (such as auto/manual prop pitch governor, clothes heating circuit breaker) eventually results in it working again but not in a consistent way so I am not sure if any of these are related to the problem.
LeCuvier Posted December 24, 2019 Posted December 24, 2019 (edited) I have not flown the Anton in a couple of months, but I flew it many times prior to that. I used to have two communications buttons mapped: "backslash" and "Ralt-backslash", one I used to bring up the comm menu on the ground, the other in the air. I can still bring up the comm menu on the ground, but not in the air any more. What am I doing wrong?:helpsmilie: I have deleted my earlier post because I had only tested airborne. I simply did not know that the command "COMM Menu" (keyboard command "\") is only supposed to work on the ground. I have re-tested the command "COMM Menu" (keyboard command "") on the ground and in the air with Bf-109, FW-190A, FW-190D, P-51 and F-5E. The command works on the ground but not in the air. And I think that's how it is supposed to work. In the air, the command "COMM Push-to-talk" (RAlt + "\") works for me. That's where Wolle seems to have a problem. So Wolle might have a problem somewhere in his setup which can be tricky to find unless the good old "Repair" helps. Edited December 24, 2019 by LeCuvier LeCuvier Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5
LeCuvier Posted December 24, 2019 Posted December 24, 2019 I have the same problem in the F18, I can bring up the comms menu on the ground to refuel, re arm and choose a mission, but I cannot bring the comms menu up whilst in the air. So if I manage to kill the enemy plane, I have to land again to set up another mission. I have mine bound to joy 4 (the pinky lever on the joystick) plus the top thumb switch on the throttle, (the one that works the speed break). Just to add, I have the same setup in the Hog and it works flawlessly. In the F/A-18 you should set up the appropriate channels for Radio 1 and Radio 2 and use the switches COMM 1 and COMM 2. I won't go into detail because this is a FW-190A thread. The flight manual covers the subject well. LeCuvier Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5
Bearskin Posted December 24, 2019 Posted December 24, 2019 Thanks LeCuvier, I guess I should have RTFM. My bad for talking about the F-18 in the FW-190A thread, I followed the link from the DCS home page and thought it was a generic comms thread. Z790, 13700K, RTX4080, 32 gig RAM, Warthog, WarBRD base , Virpil Pedals, Pico 4
wolle Posted December 24, 2019 Author Posted December 24, 2019 Thanks guys, I'll hopefully be able to do some more tests over Xmas! [sIGPIC][/sIGPIC] Intel Core I7 4820K @4.3 GHz, Asus P9X79 motherboard, 16 GB RAM @ 933 MHz, NVidia GTX 1070 with 8 GB VRAM, Windows 10 Pro
wolle Posted December 27, 2019 Author Posted December 27, 2019 This is what I found. If I map "" to any other HOTAS button other than throttle-mic-switch-depress on my Warthog, it works. There must be some conflict with this button. Since the problem only appeared after a recent update, I assume the conflict is possibly with the new game-integrated voice-over-internet-protocol or SRS.... [sIGPIC][/sIGPIC] Intel Core I7 4820K @4.3 GHz, Asus P9X79 motherboard, 16 GB RAM @ 933 MHz, NVidia GTX 1070 with 8 GB VRAM, Windows 10 Pro
LeCuvier Posted December 27, 2019 Posted December 27, 2019 This is what I found. If I map "" to any other HOTAS button other than throttle-mic-switch-depress on my Warthog, it works. There must be some conflict with this button. Since the problem only appeared after a recent update, I assume the conflict is possibly with the new game-integrated voice-over-internet-protocol or SRS.... check bindings under UI_Layer! I had a binding to the MIC switch depress button there that conflicted with bindings in other modules. LeCuvier Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5
Recommended Posts