Hardware and Windows requirements
DMA means direct memory access. nullcam reads Bodycam through a hardware reader connected to your game PC and draws the overlay on a separate Windows PC. The download provides the software; the reader and the second computer are separate requirements.
- A game PC running Bodycam.
- A separate overlay PC running Windows 10 or 11, x64, with a working graphics driver.
- Compatible DMA reader hardware, its connection cable, and its USB driver.
- An internet connection on the overlay PC for downloads, updates, and the first download of matching map data.
If you use a display fuser to combine the game and overlay outputs, configure it for a black overlay background. A fuser does not replace the reader or either computer.
Check compatibility and download
Check the current compatibility status before starting. Updated means the published release matches the game build observed by the website. Updating means a compatible release is still needed. Checking means the website cannot confirm a fresh match yet.
Download nullcam.exe to the overlay PC. The portable executable includes its runtime and reader libraries and extracts them automatically on first launch. You do not need a separate .NET installation or an activation key for the current development release.
If you need to check a download, compare its SHA-256 checksum with the value under Release notes & checksum. Use the checksum belonging to the same release as your file.
Connect the reader
Connect the reader and install the driver supplied for your hardware. The control panel’s USB driver setup menu opens the official driver page. Close other applications using the reader before starting nullcam; only one application should use it at a time.
Leave memory detection on its automatic setting first. If your hardware needs an explicit memory map, select a map generated for your game PC through the Memory map menu. A map copied from a different computer may not describe your hardware correctly.
Apply display and memory-map changes before starting the overlay. If it is already running, stop it and start again after changing these settings.
Choose a display and start
- Run
nullcam.exeon the overlay PC. - Start Bodycam on the game PC.
- Select the intended overlay output in the control panel’s Display list. With a fuser, select the output connected to it.
- Select Start overlay.
- Press 9 to open live visual settings.
If a newly connected output is missing, use Refresh displays, choose it again, and restart the overlay. Check the selected display before changing drawing or visibility settings.
Map data and visibility
On the first visit to a supported map, nullcam downloads matching visibility data and saves verified files for offline use. Keep the overlay PC online for that first download and check the control panel’s map status if data is unavailable.
Visibility needs both a supported map and matching game-build data. A new map or game update may need new data even when the application starts normally. An amber VIS ? means visibility is unverified; it is not a confirmed visible or covered result.
No manual map export or Engine.ini change is required. If you previously added r.CustomDepth=0 only for nullcam, remove that entry or restore its previous value, preserve your other settings, and restart Bodycam.
Visual settings and updates
Use 9 to adjust player color, labels, health bars, drawing distance, opacity, and visibility. Visible and covered bones can use different settings. Changes save automatically; use the control panel to stop the overlay when finished.
If player markers are missing, first check the selected display, enabled drawing options, distance, and opacity. If only visibility is unknown, follow the visibility troubleshooting steps.
After a Bodycam update, check compatibility again and use the current published nullcam release. Reinstalling the same older release does not establish compatibility with a new game build. Settings are retained across normal application updates.