Alpine1 Posted April 15, 2019 Posted April 15, 2019 After the last update,I cannot bring up the comms menu after take off.I can do so while still on the ground.Any ideas?
gonk Posted April 15, 2019 Posted April 15, 2019 Use Right Ctrl \ and Right Alt \ for comms 1/2 Intel Intel Core i7-8086K 32 Gig RAM 1 Tb Nvme SSD EVGA 1080Ti Win 10 64 Pro LG 34UM95 34 inch Monitor Track IR 5 Oculus Rift HOTAS Warthog...mod'd TDC SIMPEDS Pedals
Alpine1 Posted April 15, 2019 Author Posted April 15, 2019 Nope.Must be an update that doesn't like me,but thanks.
fitness88 Posted April 15, 2019 Posted April 15, 2019 Verify the comms menu is actually mapped to a key.
Alpine1 Posted April 15, 2019 Author Posted April 15, 2019 Still not it.It's like I said,only once that I have taken off do I loose the ability to bring up the comms menu.It's fine while on the ground and only with the Hornet.
ANE Posted April 16, 2019 Posted April 16, 2019 I had the same issue. On the ground you need to use whatever you have mapped for “communication Window”. In the air you need to use whatever you have mapped for “COMM 1” and “COMM 2”. Hope this helps :-)
fitness88 Posted April 16, 2019 Posted April 16, 2019 I had the same issue. On the ground you need to use whatever you have mapped for “communication Window”. In the air you need to use whatever you have mapped for “COMM 1” and “COMM 2”. Hope this helps :-) Yes there is a separate command for the ground crew communications.
A2597 Posted April 16, 2019 Posted April 16, 2019 I'll just tag into this thread... Is there ever a reason to tune the radio in single player? The Comms menu shows all the available frequencies (towers, JTACs, AWACS, etc) and just selecting them via the menu options I always get the response, no need to tune into the frequency... Is that intentional? Or just part of Early Access?
hornblower793 Posted April 16, 2019 Posted April 16, 2019 I think that is because you are running with Easy Communications ON Windows 11 Home ¦ Z790 AORUS Elite AX motherboard ¦ i7-13700K ¦ 64GB Corsair Vengeance DDR5 memory @ 5600MHz ¦ Samsung 990 Pro 1TB SSD for OS, Samsung 980 Pro 2TB SSD for DCS ¦ MSI GeForce RTX 4090 Gaming X Trio 24GB ¦ Virpil WarBRD base with VFX grip, Thrustmaster A10c and F/A-18 grips ¦ VKB Gunfighter Mk4 and MCG Pro ¦ Thrustmaster Warthog Throttle ¦ VKB STECS Throttle ¦ Virpil TCS rotor base with Shark and AH-64D grips ¦ MFG Crosswinds ¦ Total Controls Multi-Function Button Box ¦ Pimax Crystal
Tenkom Posted April 16, 2019 Posted April 16, 2019 Speaking of the the comms menu. Wouldn't it be great if the comms menu worked like the jester menu in the tomcat?
Gierasimov Posted April 16, 2019 Posted April 16, 2019 True and valid I had the same issue. On the ground you need to use whatever you have mapped for “communication Window”. In the air you need to use whatever you have mapped for “COMM 1” and “COMM 2”. Hope this helps :-) This ^^ Intel Ultra 9 285K :: ROG STRIX Z890-A GAMING WIFI :: Kingston Fury 64GB :: MSI RTX 4080 Gaming X Trio :: VKB Gunfighter MK.III MCG Ultimate :: VPC MongoosT-50 CM3 :: non-VR :: single player :: open beta
Alpine1 Posted April 17, 2019 Author Posted April 17, 2019 Still no luck.Only when airborne does the comms menu not appear, regardless of what I have mapped to that command.Will keep trying,thanks.
Alpine1 Posted April 17, 2019 Author Posted April 17, 2019 Tried mapping switches 'comm 1 &2' to the "comm 1&2 g xmt's They worked.Switched them back to "comm 1' and 2 and they remained mapped.So every thing is good,thanks again.
Recommended Posts