ATIS and ATC fighting when using dual com receive

:wave: Thank you using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.

Are you using Developer Mode or made changes in it?

No

Which aircraft are you using that experiences this issue?

3rd party: FFX Vision Jet - haven’t tested with default aircraft yet, but I suspect the aircraft doesn’t matter in this case.

Brief description of the issue:

I activated atis on com 2 at the same time as ATC decided to give me an instruction on com 1. As a result ATIS played once (and ATC did not play their instruction) and then the ATC window acted like ATC audio had played as soon as the ATIS was done. ATIS Did not repeat.

Provide Screenshot(s)/video(s) of the issue encountered:

Detailed steps to reproduce the issue encountered:

  • Tune a nearby atis in com 2
  • Activate listen on com 2 (while still listen/transmit on com 1) at the same time as ATC issues you an instruction

This recreate done later, but more detailed steps:

  • Tune a regular ATC function (clearance / ground / etc) to com 1
  • Tune ATIS / AWOS (more reliable with ATIS for some reason) to com 2
  • Make your request to ATC on com 1
  • RIght after your pilot voice is done talking enable dual receive

Tune a nearby atis in com2

PC specs and peripheral set up:

Saitek Yoke, 11th Gen Intel I9K, EVGA GTX 3080, 32 GB Ram, NVME drive for FS

Are you using DX11 or DX12?

12

Are you using DLSS?

no


:loudspeaker: For anyone who wants to contribute to this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

Are you using DX11 or DX12?

Are you using DLSS?

If relevant, provide additional screenshots/video:

For clarity, I don’t know how easy this is to reproduce, but it seems that when this happens, ATIS does not repeat, and ATC thinks they said something. The text appears in the ATC window. I will say that in previous versions when something weird happened with ATC I wouldn’t hear voices anymore for the rest of the flight, but the very next call came through like normal so at least that appears to be greatly improved.

Topic moved to Marketplace because the Bug hasn’t been reproduced using default aircraft with all mods/addons removed. If anyone tests this and can reproduce it using base sim aircraft with all mods/addons removed please ping me and I will move it back.

Cheers

So I decided to test if this was a fluke and it sort of is, but also isn’t.

It does recreate with an empty community folder in the SR22 and TBM 930.

You can recreate it on the ground, but it takes some luck and perfect timing.

Recreate steps:

  • Tune a regular ATC function (clearance / ground / etc) to com 1
  • Tune ATIS / AWOS (more reliable with ATIS for some reason) to com 2
  • Make your request to ATC on com 1
  • RIght after your pilot voice is done talking enable dual receive

You then have about a 50/50 chance if you will simply not receive ATIS at all, or you will receive ATIS, and ATC will just stop until the ATIS is done playing, think that it has played it’s audio and expect a response.

About 10% of the time, this will also lock up the reply controls and you have to switch to com 2 as your primary to finish talking to ATC.

@Speed1994 This is recreated now with an empty community folder, but it’s also the mother of all edge cases, I couldn’t tell you how unlucky I must have been to trip on it originally.

P.S. If you’ve already received that ATIS once, it doesn’t break, no matter how much you mess with it. It must be the first time you receive a particular ATIS broadcast. Not sure why.

2 Likes

Yeah, that’s quite the edge case, I bet not many people have run into this bug!

Thank you for thoroughly testing it :slight_smile:
I’ve moved this back to Aircraft & Systems because you replicated it with default aircraft with no mods/addons, and I’m not aware of any existing pre-Beta Bug Reports for this issue.

I kind of have a feeling that this edge case would have resulted in ATC voices failing pre-SU15 - so probably pre-existed but was buried by another bug.

But yeah, it certainly is unique.

1 Like

I do experience this issue as well. My guess, folks using dual comms would see this problem more often.
Note, if I switch off Comm 2 RX, ATC will start over (repeat) whatever it was saying…