The application will not start
Confirm that the overlay PC runs Windows 10 or 11 x64 and has a working graphics driver. The current nullcam.exe includes its runtime and native reader libraries, so instructions for older ZIP releases that require a separate .NET installation do not apply.
Download a fresh copy from the official download if the file is incomplete or damaged. Compare its SHA-256 checksum with the matching release under Release notes & checksum. A different checksum means you should replace the file before investigating the reader.
If the control panel opens but the overlay exits, read the error shown in the panel and use Open logs. Record the exact error and whether the failure happens before or after selecting Start overlay.
The reader cannot connect
- Close other applications that might be using the reader.
- Check the reader’s connection to the overlay PC and that the game PC is running.
- Use USB driver setup in the control panel to reach the official driver page, and check the driver for your hardware.
- Start with automatic memory detection. If an explicit map is required, choose one generated for your game PC from Memory map.
- Stop and restart the overlay after changing the map or reconnecting hardware.
If it still fails, keep the reader’s model, driver version, selected memory-map mode, and the exact connection error for your report. Do not repeatedly change unrelated visual settings while diagnosing a reader connection.
The overlay or player markers are missing
Check the Display selection first. Use Refresh displays if you recently connected or rearranged screens. Display changes apply on the next start, so stop and restart the overlay after choosing an output.
With a display fuser, check that nullcam draws on its connected output and that the fuser uses a black overlay background. A working reader does not confirm that the overlay is on the intended screen.
Press 9 and check that your intended drawing options are enabled. Review drawing distance, player color, and opacity. Covered-bone options can hide covered parts of a player, so distinguish a drawing setting from a missing connection.
If the overlay stops responding, stop it through the control panel, start it once more, and check the logs if the same problem returns.
Visibility stays unknown (VIS ?)
Amber VIS ? means nullcam does not have validated visibility for that result. Do not interpret it as confirmed line of sight. Starting the overlay successfully and having valid map visibility are separate checks.
- Keep the overlay PC online and check the control panel’s map-download status.
- Allow the first download of matching data to finish. Verified map files are cached for later offline use.
- Check the current game and nullcam releases. New game builds or unsupported maps may need updated data.
The current version uses automatic map data; it does not require a manual map export or an Engine.ini edit. If you added r.CustomDepth=0 only for an older nullcam setup, restore its previous value or remove that entry, preserve unrelated settings, and restart Bodycam.
When reporting persistent unknown visibility, include the map name, game build, nullcam release, and the displayed map status. These details help distinguish unavailable data from a local connection problem.
Status says Updating or Checking
Updating means the website has detected a game-build mismatch and is waiting for a compatible nullcam release. The download button pauses during that state. Refreshing the page or installing the same older file cannot establish compatibility.
Checking means a fresh compatibility result is unavailable. The page retries automatically. Updated means the published release matches the game build in the latest valid website check; individual map-data availability still matters.
Use the homepage’s current status rather than an old screenshot or release filename. If the website is unavailable, retry later instead of using an unofficial mirror.
Collect details for a bug report
The control panel provides Open logs and Copy diagnostics. Review diagnostics before sharing them, and include only the relevant information:
- The nullcam release, game build, and map name.
- Your Windows version and reader model.
- The exact error or status, plus the step where it appears.
- Whether the issue started after an update and which checks above you already tried.
Remove license keys and personal file paths from anything you post. Share your report in the nullcam development discussion. A short, repeatable description is more useful than a screenshot with no version or map details.