Falcon BMS Forum
    • Register
    • Login
    • Search
    • Categories
    • Unread
    • Recent
    • Unsolved
    • Popular
    • Website
    • Wiki

    4.33 AWACS/GCI Comms clutter.

    Technical Support (BMS Only)
    5
    5
    158
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • sir_quacksalot
      sir_quacksalot last edited by

      I didn’t see if anyone else has posted about this but it is certainly something that is driving me nuts.

      With the update to 4.33, I am sure that the way AWACS AI works is very different. However, the Radio chatter on UHF 13 (307.3) is ridiculous now. Not only is the information that it is putting out not useful, but it is extremely distracting to us as pilots. It pretty much kills my SA. Also, when I do send a request for info to AWACS it doesn’t seem like it replies as all it sends is a constant stream of updates about radar contacts somewhere around the theater.

      This seems like a pretty obvious issue but hopefully someone can shed light on it or that the AWACS AI is being addressed in some future update coming soon that will reduce the amount of chatter we are getting on the primary frequency. Not being able to get GCI to targets very much reduces our ability to find and attack air threats.

      1 Reply Last reply Reply Quote 0
      • Sting
        Sting last edited by

        Yes it is a known issue. The work around is to use the radios. If you are on channel 13 you are gonna get hammered. These days I usually hangout on VHF 1 and UHF 6 (Package), only going to 13 if I get bored.

        In the UI I would recommend changing the F1 channel from 307.300. Otherwise briefing is painful.

        Dee-Jay 1 Reply Last reply Reply Quote 0
        • Dee-Jay
          Dee-Jay @Sting last edited by

          Use of CH13 i flight has never been useful nor realistic.

          ASUSTeK ROG MAXIMUS X HERO / Intel Core i5-8600K (4.6 GHz) / NVIDIA GeForce RTX 3080 Ti FE 12GB / 32GB DDR4 Ballistix Elite 3200 MHz / Samsung SSD 970 EVO Plus 2TB / Be Quiet! Straight Power 11 1000W Platinum / Windows 10 Home 64-bit / HOTAS Cougar FSSB R1 (Warthog grip) / SIMPED / MFD Cougar / ViperGear ICP / SimShaker JetPad / Track IR 5 / Curved LED 27'' Monitor 1080p Samsung C27F396 / HP Reverb G2 VR Headset.

          Blu3wolf 1 Reply Last reply Reply Quote 0
          • Blu3wolf
            Blu3wolf @Dee-Jay last edited by

            Im seriously thinking about setting our wing default to take this into account. I am thinking of setting the UI default UHF channel, and the ‘AWACS/COBRA’ channel, to both something other than 307.300 because of the clutter.

            Is there any chance an update might deliver the ability to filter the type of radio calls you hear in the UI? And possibly 4.34 can dynamically assign radio frequencies to operating areas, so that each area gets its own ABM and control frequency.

            Red Dog 1 Reply Last reply Reply Quote 0
            • Red Dog
              Red Dog @Blu3wolf last edited by

              Yeah we agree it’s unbearable. We’re trying to find ways to overcome the chatter….

              Red Dog
              Reality if for ppl who can't handle simulation

              1 Reply Last reply Reply Quote 0
              • First post
                Last post

              54
              Online

              10.1k
              Users

              19.2k
              Topics

              327.5k
              Posts

              Benchmark Sims - All rights reserved ©