As an Amazon Associate I earn from qualifying purchases. Some links on this page may earn RealIRacing a commission at no extra cost to you. Gear I personally race on is called out as such; other picks are researched recommendations.

Most sim racers stream from a single monitor on one PC, which means camera bandwidth competes with encoding bandwidth. Adding a second or third camera to your stream setup means choosing: buy a more expensive capture card, run cameras on a separate PC, or use USB webcams on your streaming PC and accept modest quality. The payoff is real though. A cockpit camera adds immersion and credibility. A rig-wide angle shows your physical setup. A monitor capture proves you're not using assists and keeps viewers locked on the action. Done well, multi-camera angles keep a stream engaging across a longer broadcast.

Why multi-camera matters for sim racing

Viewers are skeptical of sim racing streams by default. A single monitor view leaves questions: Are you using a controller? Assists? Is this actually the iRacing world you claim? A second angle, especially a monitor-input capture or close-up of your wheel and pedals in action, closes that gap. Cockpit cameras also reduce the boredom of long endurance races. When your lap times flatten or traffic builds, cutting to a rig shot keeps the stream visually alive.

The technical barrier is lower than it was five years ago. USB webcams now ship with decent low-light performance. OBS scene switching is reliable and free. The constraint is not technology but your streaming PC's CPU headroom and USB bandwidth. On a system like the one I stream from (RTX 5060 Ti and Ryzen 7 5700 with OBS on one PC), adding two USB cameras is feasible as long as your encoder settings leave room for their overhead.

Start simple

Start with one additional camera before committing to a three-angle setup. Most viewers respond more to consistent, clean audio and a stable 60 fps main feed than to adding a third angle. Add angles only if your PC and internet upload handle them without frame drops.

Camera types and placement for sim racing

Monitor or racing line input capture

The gold standard for a second angle is a direct input capture of your monitor or a separate small display showing the in-game view. This proves the build, the track, your iRating and safety rating, and that you're not using AI opponents or offline practice. If your monitor has HDMI or DisplayPort out, you can route a second output to a capture card on a separate USB 3.0 bus. If not, use an HDMI splitter (one for your display, one for capture).

A capture card approach adds cost (budget ~£80 to £150 for a reliable USB 3.0 card) but uses no PC CPU time after the capture driver loads. If you must avoid extra hardware, screen-region capture in OBS (crop your monitor view) works but will slow your encoder if your main stream already fills your CPU.

Cockpit angle: wheel and pedals

Mount a USB webcam or USB mirrorless camera above or to the side of your wheel to frame your steering input and hand position. This angle is most impactful during high-stress corners or overtakes, and it builds trust that you're actually driving. Position the camera roughly 60 cm from your wheel at an angle that keeps your hands visible without glare or backlighting washing out detail. A ~1080p 30 fps USB webcam is enough; most viewers watch at lower quality anyway.

Wide rig shot

A third camera framing your full cockpit or rig setup is optional but adds production value for long streams. This angle proves you have real hardware, not a controller, and breaks up the visual monotony of hour-long endurance races. Mount it 1.5 to 2 metres away from your seat, slightly elevated, framing seat, wheel, and pedals in one shot.

OBS scene switching and layout

Your stream layout depends on bandwidth and CPU overhead. A common approach: main scene has your monitor capture in the foreground, cockpit camera in a bottom corner (10-15% of frame), and wide rig shot in another corner. During slow racing (lead changes, fuel stops), full-screen the cockpit or rig for 10-15 seconds, then return to the main view. This keeps the visual hierarchy clear (racing action first) while rewarding engaged viewers with extra angles.

  1. Set up each camera as a separate source in OBS: monitor capture via HDMI card, cockpit USB camera, rig wide-angle USB camera
  2. Create two or three scenes: 'Racing Main' (monitor large, cameras in corners), 'Cockpit Focus' (cockpit camera full-screen), 'Rig Wide' (rig angle full-screen)
  3. Use scene-switching hotkeys or a secondary monitor to flip between scenes without cutting awkwardly
  4. Keep each camera input at a consistent resolution (1920x1080 or 1280x720) to avoid re-scaling drops in OBS; use the camera settings or OBS filter to resize before compositing
  5. Set a delay of 2-3 seconds on non-main cameras if your upload bandwidth is tight; a slight audio delay is less noticeable than a video stutter
Test first

Test your full multi-camera setup on a local private lobby before a public stream. Watch the replay and CPU usage in OBS. If your encoding bitrate spikes above 80% CPU usage, drop one camera or reduce a resolution.

USB bandwidth and PC overhead

Two USB 3.0 cameras on the same hub can saturate bandwidth if both are streaming 1080p 30fps. Use separate USB 3.0 buses if your PC has them (many do: front USB 3.0 hub, rear USB 3.0 header, and internal USB 2.0 for less bandwidth-hungry devices). Stagger camera resolutions: cockpit at 1080p 30fps, wide rig at 720p 30fps. This spreads the load and rarely impacts perceived quality on stream.

CPU overhead comes from OBS compositing (blending multiple sources into one output frame). A Ryzen 5700 can handle two USB cameras plus monitor capture and 1080p 60fps encoding if the cameras run at 720p or 1080p 30fps and your encoder bitrate sits at 6000-8000 kbps. Higher bitrates push encoding CPU above 60%, leaving little room for in-game CPU spikes. Lower your resolution or framerate if your CPU usage trends near 70% during a race.

Gear: cameras and capture cards

Budget USB webcams (Logitech C920 or C930e clones, ~£40-60) work for cockpit and rig angles. They struggle in low light and have poor autofocus, but many viewers watch compressed streams at 540p anyway, so the image quality loss is acceptable. Higher-end USB mirrorless cameras (Sony A6400, ~£600+) offer exceptional image quality, fast autofocus, and manual focus; they're overkill for a small cockpit corner but valuable if you're serious about stream presentation and have the budget.

For monitor capture, a dedicated HDMI USB 3.0 capture card (Elgato Cam Link, Magewell USB Capture, ~£100-150) is more reliable than screen-region capture in OBS. Capture cards use hardware to compress the video feed and offload the work from your CPU. If your streaming PC is tight on CPU budget, a capture card pays for itself in stability and available encoder headroom.

Audio and sync

USB cameras do not carry audio to OBS by default. Use your existing headset or microphone input and route it through OBS as a separate audio source. If video encoding lags slightly (a 1-2 frame delay on a camera angle), audio and video stay in sync because OBS handles them separately. Noticeable lip-sync issues only occur if your upload bandwidth is truly maxed and OBS begins dropping frames; that's a sign to reduce camera resolution or bitrate, not to add audio delay compensation.

Practical setup workflow

  1. Install one USB camera first (cockpit angle). Test it in OBS at 720p 30fps for one week of streams. Verify CPU and USB stability
  2. Add a second camera (wide rig) on a separate USB port or hub. Test at 720p 30fps for another week
  3. If CPU and bandwidth are stable, raise the cockpit camera to 1080p 30fps. Monitor your OBS encoding CPU; if it climbs above 70%, drop the rig camera to 480p or reduce your main stream bitrate by 1000 kbps
  4. Add monitor capture last, via capture card or OBS screen crop. Start with a smaller monitor area (1280x720) and scale up only if CPU headroom allows
  5. Create your multi-camera scenes in OBS. Set keyboard shortcuts for quick scene switching during a race. Practice switching without fumbling
  6. Run a 30-minute test stream on a private YouTube stream or Discord channel. Watch the replay for dropped frames, stutters, or desync. Adjust camera resolution or bitrate if needed

Multi-camera streaming on a single PC is achievable and credible. Start small, test thoroughly, and upgrade only when your CPU and upload bandwidth clearly support the next angle. Viewers prefer one stable, high-frame-rate feed with clean audio over three laggy or stuttering angles, so resist the temptation to add cameras faster than your rig can handle them.

From the RealiRacing shop

Before you go live, free up your rig. NWM PitStop is the clean-up + stream-priority script set we run before every session — our own product, not a third-party pick. See NWM PitStop →

The gear in this guide
PickWhy it made the listTested?
NVIDIA GeForce RTX 5060 Ti (8 GB)renders iRacing and NVENC-encodes the stream on the same chipRaced on
AMD Ryzen 7 57008 cores — plenty for iRacing plus OBS on one PCRaced on
1440p 120 Hz+ G-SYNC Compatible Gaming Monitormy single-screen setup — high refresh matters more than sizeRaced on

As an Amazon Associate I earn from qualifying purchases. Some links are affiliate links — I may earn a commission at no cost to you.

Watch it, don't just read about it

I stream and upload iRacing races on my MOZA R9 rig — real laps, real force feedback, real mistakes. See the gear from this guide working before you spend a cent.

▶ Subscribe on YouTube

Skip the trial and error

The force-feedback, pedal and baseline settings I actually race, written up as setup packs for MOZA, iRacing, ACC and Le Mans Ultimate. The opening section of each pack is free to read.

See the setup packs →

Free FFB tuning checklist

The order I tune force feedback in, from rig to wheelbase software to iRacing, plus the clipping check. Enter your email and the checklist opens right here. No spam, unsubscribe anytime.

See the privacy notice.

FAQ

Will adding two USB cameras to my streaming PC tank my frame rate in iRacing?

Not if your PC has spare CPU headroom. USB camera capture itself uses minimal CPU; the overhead comes from OBS compositing them into your output. On a Ryzen 7 5700 with encoding bitrate at 6000-8000 kbps, two cameras at 720p 30fps typically add 5-10% CPU usage. Monitor your OBS encoding CPU during a race. If it's above 70%, reduce camera resolution or bitrate, or run cameras on a second PC.

Should I use a capture card for my monitor or just let OBS screen-crop it?

A capture card (HDMI USB 3.0) is more reliable and offloads CPU work. OBS screen-region capture is free but uses CPU to encode that region, which matters if your PC is already at 60-70% encoding load. If your streaming PC is tight, a ~£100 capture card is worth it. If you have spare CPU, screen crop works fine.

What camera resolution should I use for a cockpit close-up?

Start at 1280x720 30fps. Most viewers watch compressed streams at 540p or lower, so 720p is sharp enough and uses reasonable USB bandwidth. If you have spare USB and CPU, bump it to 1920x1080 30fps. Anything above 1080p is wasted on a small corner inset; save high resolution for a full-screen cockpit or rig shot.

Can I run three USB cameras on one streaming PC without dropping frames?

Rarely without trade-offs. Three USB cameras at 720p 30fps each, plus encoding your main 1080p 60fps feed, can saturate USB bandwidth and CPU. Most single-PC setups max out at two USB cameras running cleanly. If you need three, use a second PC for two cameras and stream via NDI, or use a dedicated USB hub with its own power supply to reduce bus contention.