Set up X-Plane 12 in OBS: choose the right capture, encoder, resolution and audio mix, then fix black screens, blur, stutter and dropped frames.
To stream X-Plane 12, add it to OBS or another broadcasting app as a game, window or display capture; choose hardware H.264 encoding; start at 1080p30; capture simulator and microphone audio separately; then make a local recording under demanding flight conditions before connecting your private stream key and going live.
How do I set up OBS (ОБС) for X-Plane 12?
OBS Studio—sometimes searched for as “обс”—does not require an X-Plane plug-in because it captures the simulator’s rendered video and audio directly.
- Load a demanding flight. Use the aircraft, detailed airport, weather, traffic and add-ons you expect to show. Testing a default aircraft over open countryside can conceal problems that appear at a busy terminal in poor weather.
- Create a dedicated scene. Place the X-Plane capture at the bottom, then add a camera, labels, chat or other overlays above it. Lock each source after positioning it so an accidental drag cannot alter the layout.
- Choose the capture source. Try game or application capture first on Windows. Use window capture for a stable maximised X-Plane window, or display capture if the other methods return a black image or omit detached panels.
- Set the canvas and output. Match the canvas to the source aspect ratio, then perform no more than one downscale when producing the stream. Start with 1920×1080 at 30 frames per second.
- Select a hardware encoder. Hardware H.264 is the safest compatibility choice. Depending on the computer, OBS may identify the encoder as NVIDIA NVENC, AMD, Intel Quick Sync or Apple VideoToolbox. Use AV1 or HEVC only when the destination explicitly accepts it.
- Configure the streaming rate. Use constant bitrate when required by the streaming service, follow its permitted bitrate range and enter its required keyframe interval. Do not copy settings from a different service without checking them.
- Add audio once. Capture X-Plane or system output through one source and the microphone through another. Confirm that both meters respond and that the simulator is not being captured twice.
- Connect the destination. Sign in through OBS or enter the private server address and stream key provided by the service. Never place the key in a visible text source, screenshot or scene.
- Make a local test recording. Include cockpit movement, exterior views, pop-out instruments, loud engine phases, radio audio and switching between applications. Review the encoded file full-screen before attempting a restricted test stream.
Which X-Plane capture source should I use?
Game or application capture offers the best privacy, while display capture is the dependable fallback for black screens and separate instrument windows.
| Capture source | Choose it when | Main drawback |
|---|---|---|
| Game or application capture | You want only X-Plane captured, particularly on Windows | It can return a black frame when graphics adapters, privileges or capture APIs do not match |
| Window capture | X-Plane runs in a stable maximised window | Menus, plug-in windows and detached avionics may be separate from the captured window |
| Display or screen capture | You need maximum reliability or must show pop-out panels | Notifications, account details and other applications can appear live |
| Capture card | A second computer will handle composition and encoding | Adds cost, audio-routing work and another possible resolution or refresh-rate mismatch |
A maximised X-Plane window is usually easiest to manage on one monitor because it permits reliable application switching. Full-screen can also work, but test that the source remains active after switching away and back.
On macOS, grant the broadcasting app screen-recording and microphone permissions, then restart it if the source remains blank. Linux window and display capture may depend on the desktop session and its screen-sharing portal. On a laptop, make sure X-Plane and OBS use the same high-performance graphics adapter if game capture produces black video.
Display capture requires stricter privacy controls. Disable notifications, close password managers and messaging windows, remove personal information from browser tabs, and check every monitor that could accidentally be selected.
What resolution and frame rate should I stream X-Plane 12 at?
We recommend starting at 1920×1080 and 30 fps because it keeps glass-cockpit text readable without imposing the encoding and bandwidth demands of 60 fps.
| Output | Best choice when | Trade-off |
|---|---|---|
| 1920×1080 at 30 fps | You fly airliners, procedures or mixed cockpit and exterior views | Fast camera pans are less fluid than 60 fps |
| 1920×1080 at 60 fps | X-Plane remains comfortably above 60 fps and the encoder and connection have headroom | Needs more encoding capacity and bitrate; cockpit text suffers first when bitrate is restricted |
| 1280×720 at 30 fps | Upload bandwidth or computer performance is limited | Small labels and avionics text are harder to read |
| 1280×720 at 60 fps | Motion matters more than fine cockpit detail | Consumes extra bitrate without improving text resolution |
Do not select 60 fps merely because the monitor operates at 60 Hz. If X-Plane cannot sustain that rate, the broadcast repeats frames and may look less consistent than a stable 30 fps output.
Keep the canvas at the captured resolution and scale once at the output stage. Resizing the source inside the scene and scaling it again during encoding softens PFD, navigation display and autopilot-panel text. For an ultrawide display, crop deliberately or build a 16:9 composition around it; never stretch the image horizontally.
How much upload bandwidth do I need?
Your sustained upload must exceed the combined video and audio bitrate with enough spare capacity for normal connection fluctuations and other network use.
The streaming service’s bitrate limits should decide the exact setting. Use a wired Ethernet connection where practical, pause cloud backups and large uploads, and judge the connection from OBS network-drop statistics during a test stream rather than from one brief speed result.
How much performance headroom does streaming require?
X-Plane 12 must leave enough CPU and GPU capacity for OBS to compose, scale and encode every frame on time.
A hardware encoder reduces CPU demand, but the scene still consumes GPU resources. A mistake we see constantly is tuning X-Plane until the GPU is fully occupied and then expecting the encoder alone to prevent stream stutter. Our guide to identifying CPU and GPU bottlenecks in X-Plane 12 explains how to determine which simulator settings are responsible.
- GPU-limited: reduce rendering resolution, anti-aliasing or shadow quality, simplify animated overlays, and consider 30 rather than 60 fps.
- CPU-limited: reduce rendering distance, world-object density, traffic or processor-heavy plug-ins. Lowering texture quality rarely fixes a main-thread limit.
- VRAM-limited: reduce texture quality, remove oversized aircraft or scenery textures, and close other GPU-accelerated applications.
- Encoder-limited: use a hardware encoder, reduce output resolution or frame rate, and avoid an unnecessarily demanding encoder preset.
OBS statistics separate rendering lag, encoding lag and network dropped frames. They are not interchangeable: rendering lag points to GPU composition pressure, encoding lag to the encoder, and network drops to the connection or excessive bitrate.
Test at the gate and during take-off at the busiest airport you plan to use. Cruise over sparse terrain is usually a poor stress test. If pauses or crashes also occur without OBS open, isolate aircraft, scenery and plug-ins before changing stream settings; our X-Plane add-on installation and conflict guidance covers the relevant folder and troubleshooting basics.
Do I need a second streaming PC?
A second PC is unnecessary for most X-Plane streams when the main computer has a supported hardware encoder and adequate rendering headroom.
Use a dual-PC arrangement when complex production scenes or encoding continue to interfere with the simulator after sensible tuning, or when isolating the broadcast from a simulator crash is essential. A capture card offloads composition and encoding, but it introduces display-cloning, audio-routing and synchronisation work; it does not repair poor X-Plane performance by itself.
How should I mix X-Plane and microphone audio?
The microphone should remain clearly intelligible over engines, weather and radio audio without any source reaching clipping level.
- Use headphones so the stream mix cannot return through speakers and re-enter the microphone.
- Capture simulator sound once. Enabling both application audio and full system audio commonly produces echo or phasing.
- As a practical starting point, let normal speech peak around -12 to -6 dBFS and keep simulator audio several decibels below it. Adjust by listening to the recording, not by watching meters alone.
- Use a noise gate conservatively. A high threshold can cut off quiet speech and the beginning of radio calls.
- Check ATC and voice-client audio separately. Communications may be routed to a headset output that the stream is not capturing.
- Set OBS and the audio devices to the same sample rate, commonly 48 kHz, to reduce resampling and gradual synchronisation faults.
- If recording separate audio tracks, confirm that the complete live mix is still assigned to the track sent to the streaming service.
How do I make cockpit and exterior views easier to watch?
Saved, repeatable camera positions produce a clearer stream than constant free-camera movement.
Keep the PFD, navigation display, engine instruments and autopilot controls clear of chat and camera overlays. Save useful cockpit and exterior positions with X-Plane’s Quick Look system before going live. For smoother transitions and aircraft-specific camera sets, follow our X-Camera installation and configuration instructions.
Window capture may omit a detached instrument because X-Plane treats it as another operating-system window. Switch to display capture or capture that panel separately, then verify its position after every resolution or monitor change.
Why is my X-Plane stream black, blurry or stuttering?
Black video normally indicates a capture conflict, while blur and stutter usually come from repeated scaling, restricted bitrate, network loss or exhausted rendering resources.
| Symptom | Likely cause | Fix |
|---|---|---|
| Black X-Plane image | Unsupported capture method, mismatched application privileges or different laptop graphics adapters | Try window or display capture, run both apps at the same privilege level, and assign them to the same graphics adapter |
| X-Plane is smooth but the stream stutters | OBS rendering or encoder overload | Check its statistics, reduce X-Plane GPU load, simplify overlays, use hardware encoding or lower the output frame rate |
| Dropped network frames | Bitrate exceeds sustained upload capacity or the connection is unstable | Lower bitrate, stop background uploads and use a wired connection |
| Blurry instruments | Multiple scaling stages, low bitrate or excessive motion for the selected frame rate | Scale once, favour 1080p30 over 1080p60, or reduce unnecessary camera movement |
| Missing pop-out display | The panel is a separate window outside the selected source | Capture the display or add the panel as another source |
| Echo or doubled audio | The same output is present in two audio sources or a monitoring loop | Mute the duplicate source and monitor the final mix through headphones |
| Washed-out colours | Operating-system HDR, capture colour space and SDR output do not agree | Use an end-to-end SDR workflow unless every capture, encoding and playback stage is deliberately configured for HDR |
X-Plane’s lighting and rendering controls are not the same thing as producing an HDR video stream. If the live image is grey or washed out while the simulator looks normal locally, check the operating system, capture source and OBS colour settings as one chain rather than increasing X-Plane brightness.
What should I check before going live?
A full-screen local recording followed by a short restricted test stream catches most X-Plane broadcasting faults before an audience sees them.
- Load the busiest aircraft, airport, weather and traffic combination planned for the stream.
- Check OBS statistics for rendering lag, encoding lag and network drops.
- Listen for microphone clipping, doubled simulator sound and missing radio audio.
- Open every pop-out instrument, menu and camera view that will be used.
- Switch away from X-Plane and back to confirm the capture does not freeze or turn black.
- Disable desktop notifications and remove account details, personal messages and stream keys from view.
- Inspect cockpit labels in the encoded recording at normal playback size, not only in the OBS preview.
- Save the working scene and output configuration before experimenting with higher resolution, frame rate or encoder quality.