BeyondATC works with Microsoft Flight Simulator in PC VR, but its window is external. Learn how to set up audio, push-to-talk and an in-headset view.
Yes. BeyondATC can run alongside Microsoft Flight Simulator 2020 or 2024 while the simulator is in VR on a Windows PC. The catch is that BeyondATC is a separate desktop application, not a native cockpit panel, so its normal window does not automatically appear inside the headset.
What actually works in BeyondATC VR?
All core ATC functions can continue while Microsoft Flight Simulator is rendering in VR, provided BeyondATC is connected and its audio and controls are configured correctly.
| Feature | Behaviour in VR |
|---|---|
| Connection to MSFS | Works independently of the simulator’s 2D or VR display mode |
| Controller and ATC voices | Work through the Windows audio device selected for BeyondATC |
| Voice input and push-to-talk | Work when the correct microphone and an accessible button or key are assigned |
| Desktop interface | Does not automatically become an MSFS cockpit panel |
| Xbox or PlayStation | Not supported because BeyondATC requires its Windows companion application |
The important distinction is between VR-compatible ATC and a native VR interface. BeyondATC can handle the flight while you remain in the headset, but viewing or clicking its desktop window may require an additional overlay. Our comparison of BeyondATC with other MSFS ATC add-ons explains where that external-application design differs from in-simulator alternatives.
How do you set up BeyondATC for MSFS VR?
Reliable VR use comes from completing the desktop setup before putting on the headset.
- Load the flight in 2D first. Open Microsoft Flight Simulator and BeyondATC, load into the aircraft and confirm that BeyondATC has connected before entering VR.
- Check the route and aircraft details. Make sure the callsign, departure, destination and planned route agree with the flight management system. A route mismatch can look like an ATC or VR fault when the applications are simply working from different plans.
- Select the audio devices explicitly. Set BeyondATC’s output to the VR headset or to the headphones you actually use. Select the intended microphone rather than relying on the Windows default, which can change when a headset connects.
- Assign push-to-talk and response controls. Use buttons or keys that BeyondATC can receive while MSFS has focus. Avoid bindings already used for the parking brake, VR reset, cockpit interaction or the simulator’s own radio controls.
- Avoid running two ATC systems. Do not contact the default MSFS controller while BeyondATC is managing the flight. Disable AI radio assistance or automatic ATC responses if they produce duplicate calls.
- Enter VR only after testing one call. Confirm that you can hear the controller and that your push-to-talk or response control registers. Then use the normal MSFS VR command; our steps for entering and leaving MSFS VR correctly cover the simulator side of the process.
Can you see the BeyondATC window inside the headset?
The standard BeyondATC desktop window is not automatically displayed inside the virtual cockpit. If you need continuous access, use the desktop-view or window-pinning facility provided by your VR software, where available.
A pinned desktop is useful when selecting responses or monitoring the flight, but it can consume screen space, capture mouse focus and add rendering overhead. For the lightest setup, use voice interaction and physical controls, checking the desktop only when necessary. Frequencies and clearance notes can also be copied to a kneeboard; our practical guide to using a kneeboard in MSFS VR covers the available methods.
- Choose a pinned window if you regularly need clickable responses or visual monitoring.
- Choose voice and hardware controls if immersion and VR performance matter more than seeing the interface.
- Choose a kneeboard for static information such as clearances, frequencies and taxi notes; it is not a live BeyondATC control panel.
Which VR headsets and platforms work?
BeyondATC is largely headset-agnostic because it communicates with Microsoft Flight Simulator rather than rendering the VR scene itself. If a headset works with the PC version of MSFS through the appropriate OpenXR setup, BeyondATC can continue operating beside it.
This does not extend BeyondATC to Xbox or PlayStation. Even when a console supports Microsoft Flight Simulator or VR hardware, it cannot run the required Windows companion application. The distinction between console support and the PC and OpenXR requirements for MSFS VR matters here.
Why does BeyondATC stop responding in VR?
Most BeyondATC VR problems are caused by audio routing, lost control focus or conflicting ATC rather than VR incompatibility.
- No controller voices: Check BeyondATC in the Windows volume mixer and select the headset output directly. If the headset was connected after the application started, restart BeyondATC after changing the device.
- Push-to-talk does nothing: Verify the microphone input, Windows microphone permission and assigned control. Run MSFS and BeyondATC at the same Windows privilege level—normally neither should need administrator mode.
- The app works but its window is missing: This is expected when entering VR. Open the VR runtime’s desktop view or pin the window if that facility is supported.
- Two controllers speak at once: Stop using the built-in MSFS ATC and turn off radio-assistance features that answer it automatically.
- VR performance drops: Close or unpin the live desktop overlay while leaving BeyondATC connected. If performance improves, the overlay rather than the ATC engine is the likely cause.
BeyondATC therefore works well as VR ATC on PC when operated primarily through audio, voice and hardware bindings. The main limitation is interface access inside the headset, not communication with Microsoft Flight Simulator.