Balzarog Posted February 1, 2018 Posted February 1, 2018 Possible 2.5 Open Beta bug. I haven't been able to contact the ATC at any of the airfields I've tried with any of the aircraft I've tried. I flew a quick mission in my Huey in Normandy yesterday. After I set my radio frequency to 250.25 for Azeville and flipped my battery switch, I pressed my cyclic trigger switch (for comm), selected F5, then F1, then F3 to request startup. My audio radio call started with KRYMSK, not AZEVILLE. I have used that same frequency (as specified in the airfield data box for Azeville in the F10 map) many times before in 1.5.8 Open Beta. I have also tried to select NDBs in the Museum Relic Campaign (both the F-86 and the MiG-15), and heard the wrong morse code. I'm concerned that the frequencies either got borked when merging the maps or maybe some frequencies on the Caucuses map were used in Normandy and Nevada because 1.5 and 2.2 were separate installations. I suspect the former. I intend to investigate it further using Lino's map and other frequency downloads. The only addon I'm using is SimpleRadio Standalone. When all else fails, READ THE INSTRUCTIONS! i-7 8700K Coffee Lake 5 GHz OC CPU, 32GB Corsair 3200 RAM, GTX1080 Ti 11Gb VRAM. Controls - Thrustmaster Warthog H.O.T.A.S., Saitek Pro rudder pedals, TrackIR 5, Oculus Rift S, Rift CV1
Recommended Posts