rayrayblues Posted July 5, 2020 Posted July 5, 2020 On the ground or carrier deck, I call for start up, no response. When in the air, comms menu doesn't appear. :doh: can't call for inbound etc. This just started happening today. It was fine yesterday. :( Cleanup and repair does not help.dcs.log SLAVA UKRAINI MoBo - ASUS 990FX R2 Sabertooth, CPU - AMD FX 9590 @4.7Gb. No OC RAM - GSkill RipJaws DDR3 32 Gb @2133 MHZ, GPU - EVGA GeForce GTX 1660Ti 6Gb DDR5 OC'd, Core 180MHz, Memory 800MHz Game drive - Samsung 980 M.2 EVO 1Tb SSD, OS Drive - 860 EVO 500Gb SATA SSD, Win10 Pro 22H2 Controls - Thrustmaster T-Flight HOTAS X, Monitor - LG 32" 1920 X 1080, PSU - Prestige ATX-PR800W PSU
Flappie Posted July 5, 2020 Posted July 5, 2020 On the ground or carrier deck, I call for start up, no response. What aircraft are you flying? What was the airfield you were on? What was the carrier you were on? Super Carrier module or regular Stennis/Tarawa/Kuznetsov? When in the air, comms menu doesn't appear. :doh: can't call for inbound etc. Have you tried both * and RAlt + * bindings? When in the air, most of the aircraft need you to use RAlt + *. ---
rayrayblues Posted July 5, 2020 Author Posted July 5, 2020 FA-18 C Khasab Theodore Roosevelt SLAVA UKRAINI MoBo - ASUS 990FX R2 Sabertooth, CPU - AMD FX 9590 @4.7Gb. No OC RAM - GSkill RipJaws DDR3 32 Gb @2133 MHZ, GPU - EVGA GeForce GTX 1660Ti 6Gb DDR5 OC'd, Core 180MHz, Memory 800MHz Game drive - Samsung 980 M.2 EVO 1Tb SSD, OS Drive - 860 EVO 500Gb SATA SSD, Win10 Pro 22H2 Controls - Thrustmaster T-Flight HOTAS X, Monitor - LG 32" 1920 X 1080, PSU - Prestige ATX-PR800W PSU
Flappie Posted July 5, 2020 Posted July 5, 2020 Theodore Roosevelt = Super Carrier. By default, you need to tune your radio to 127.5 AM to communicate with a super carrier. Can you try this please? If it still doesn't work, can you give me the .miz file of the mission so I can check the frequencies? ---
rayrayblues Posted July 5, 2020 Author Posted July 5, 2020 I've never had to tune the radio to any freq with this plane. It's not just this one mission. It's all missions. It was working fine yesterday. I haven't made any changes. It is a simple practice mission for take off and landings. Here you go...SC Test 2 .miz SLAVA UKRAINI MoBo - ASUS 990FX R2 Sabertooth, CPU - AMD FX 9590 @4.7Gb. No OC RAM - GSkill RipJaws DDR3 32 Gb @2133 MHZ, GPU - EVGA GeForce GTX 1660Ti 6Gb DDR5 OC'd, Core 180MHz, Memory 800MHz Game drive - Samsung 980 M.2 EVO 1Tb SSD, OS Drive - 860 EVO 500Gb SATA SSD, Win10 Pro 22H2 Controls - Thrustmaster T-Flight HOTAS X, Monitor - LG 32" 1920 X 1080, PSU - Prestige ATX-PR800W PSU
Flappie Posted July 6, 2020 Posted July 6, 2020 I've never had to tune the radio to any freq with this plane. Then you might have changed the Easy Communication parameter. Please check this is enabled in the Gameplay tab of the Options panel: Please note this parameter can be forced off in missions. For an unknown reason, I cannot open your .miz file. ---
draconus Posted July 6, 2020 Posted July 6, 2020 (edited) On the ground or carrier deck, I call for start up, no response. When in the air, comms menu doesn't appear. :doh: can't call for inbound etc. This just started happening today. It was fine yesterday. :( Cleanup and repair does not help. You probably used simple '\' key for Ground Crew comms. Obviously it won't work in the air or anywhere beside your friendly airbase. Use PTT/Mic comms binding to use the proper radio instead. Edited July 6, 2020 by draconus Win10 i7-10700KF 32GB RTX4070S Quest 3 T16000M VPC CDT-VMAX TFRP FC3 F-14A/B F-15E CA SC NTTR PG Syria
Recommended Posts