Satellite Table Overlaps: The Hidden Geometry That Breaks Remote Surveillance

Satellite table overlaps are not a design flaw β€” they are a deliberate structural exploit baked into the physical layout of multi-pit casino floors, and remote CCTV camera placement consistently fails to account for the parallax displacement they create. If you have ever watched a live dealer feed cut to a ceiling cam and wondered why the chip stacks on table 14 look like they belong to table 15, you are staring at a geometry problem that costs operators millions in disputed hands. 🎰

The core issue is simple and brutal: a satellite table sits at an oblique angle relative to the primary pit table, and when the remote camera array is mounted on a shared truss, the overlapping field of view compresses depth perception. Your satellite table overlaps become a blind zone where card faces, bet placements, and dealer hand movements bleed across table boundaries. Most surveillance integrators never model this. They hang cameras at uniform intervals and call it coverage.

The Parallax Math Nobody Runs Before Mounting Cameras

Here is the technical reality that separates a competent remote CCTV layout from a forensic disaster. When two tables share a vertical sightline from a single camera at height H, the horizontal offset between their surfaces creates a displacement vector proportional to the tangent of the viewing angle. At a typical truss height of 3.2 meters and a table separation of 1.8 meters, the overlap zone spans nearly 40 centimeters of ambiguous surface area. That is enough space for a full card to sit in visual limbo.

The fix is not more cameras. It is angular diversity. You need at least two remote CCTV nodes per satellite cluster with a minimum 25-degree azimuth separation, and you must calibrate the remote CCTV camera layouts against a physical grid mapped to the actual table felt boundaries β€” not the pit carpet. I have audited floors where the camera plan was drawn on a napkin and the resulting overlap error exceeded 60 centimeters. That is not surveillance. That is theater.

Why Standard DVR Analytics Cannot Resolve Overlapping Table Zones

Motion detection zones in consumer-grade and even mid-tier commercial DVR systems operate on pixel-grid masks. When satellite table overlaps exist, those masks cannot distinguish between a dealer's hand reaching across a boundary and a player sliding chips onto an adjacent layout. The analytics fire false positives, the operator ignores the alerts, and the actual exploit β€” a collusive chip transfer disguised as a boundary reach β€” sails through untouched. 🀬

You need polygon-based masking with per-table coordinate anchoring, and you need it refreshed every time a table is repositioned. The hardware exists. The configuration discipline does not. Most pit bosses could not tell you the exact pixel coordinates of their table edges, which means every remote CCTV camera layout on the floor is running on assumptions instead of measurements.

Hardware Placement Rules That Actually Kill the Overlap Problem

Mount remote cameras at differential heights, not uniform truss rails. A 40-centimeter height variance between adjacent nodes collapses the overlap zone by more than half because the parallax vectors diverge instead of converge. Pair this with lens selection: a 2.8mm fixed lens at 3 meters produces a 110-degree horizontal field that swallows two tables whole. Step up to 6mm and the overlap becomes manageable, but you lose the pit-wide context view.

The answer is a hybrid layout β€” one wide context camera per pit, plus dedicated 6mm nodes aimed at each satellite table with a 15-degree downward tilt. This configuration eliminates the satellite table overlaps that plague shared-truss installations and gives your review team clean, attributable footage per table. No ambiguity. No disputed hands. No forensic guesswork at 3 AM.

The operators still running uniform truss-mounted arrays are not saving money. They are pre-paying for every disputed ruling their surveillance team cannot resolve, and the satellite table geometry is quietly compounding the loss every single shift.