• Categories
  • Recent
  • Tags
  • Popular
  • Users
Collapse
Just Flight Community Forum

MSFS BAE-146 - Com-2 Monitoring

Scheduled Pinned Locked Moved 146 Professional
6 Posts 3 Posters 367 Views
    • 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.
  • R Online
    R Online
    rbringh
    wrote on last edited by
    #1

    Anyone know how to get Com2 to monitor properly for the right seat. I have the Com2 select button down and volume on max on the right side controls. I put the local ATIS frequency on the right side system and selected. No audible sound. Strange thing is I switched to outside view and could hear the ATIS information. Switch back to cockpit view and nothing. I can get it using the left side Com equipment but that messes with air traffic communications for some reason.

    1 Reply Last reply
    0
  • MartynM Offline
    MartynM Offline
    Martyn JF Staff
    wrote on last edited by Martyn
    #2

    Just checked here and it's working OK.

    The audio selector volumes are dictated by the selected camera view. With the pilot view selected, the left audio selector panel controls the volumes, and with the co-pilot view selected, it's the right panel.

    Note that it's just the round VHF 2 audio volume selector that you need to push in and rotate to control volume. The square button above that is the microphone selector and pushing that in will switch to transmitting on COM 2.

    VHF_COM2.JPG

    Martyn - Development Manager

    R J 2 Replies Last reply
    1
  • R Online
    R Online
    rbringh
    replied to Martyn on last edited by
    #3

    @martyn - yes that was my issue. Just Flight support replied to me this morning with pretty much the same answer.

    Push the round button down to monitor selected Com.

    Thanks, now if MSFS could get this working better, twice today Com communications was off, well it was in this plane.

    1 Reply Last reply
    1
  • J Offline
    J Offline
    jmarkows
    replied to Martyn on last edited by
    #4

    @martyn I was trying both ADFs and though they were tracking a nearby NDB, I couldn't hear any ID. I had them depressed and the volume maxed, and I tried all ADF modes.

    MartynM 1 Reply Last reply
    0
  • MartynM Offline
    MartynM Offline
    Martyn JF Staff
    replied to jmarkows on last edited by
    #5

    @jmarkows I've checked our code and it's correctly setting the ADF ident variables in MSFS, so this appears to be another WASM bug in the simulator. We'll report it to Asobo.

    Martyn - Development Manager

    J 1 Reply Last reply
    1
  • J Offline
    J Offline
    jmarkows
    replied to Martyn on last edited by
    #6

    @martyn I've done a little testing and I often get the same thing with Nav 1, it's incorrect or silent. I've confirmed it with other planes as well.

    I do have Navigraph updating the MSFS data and removing that did fix that for the C152 but not the 146, but it was a quick test and I didn't use the same VOR so I wouldn't say it's conclusive just yet, need to poke around more.

    1 Reply Last reply
    0

  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Users