NativeCAD Arena · proof of concept · By FeatureBoard Labs

A deathmatch game that runs on checked CAD data

NativeCAD Arena is a browser deathmatch game whose map is 991 NativeCAD B-rep bodies, proven sealed before any game data is made from them, with every check pinned in Pinpoint on the part it is about.

991
B-rep bodies: 844 closed solids and 147 curved sheets
20 of 20
checks pass, each one a pin on the model
10,602,605
cells of play space flooded from the spawns; none reaches outside
5,459
collision hulls baked from the checked bodies

Play it

A classic deathmatch map layout with arena-shooter movement, 9 weapons, 37 pickups, 3 jump pads and bots that find their way on a graph baked from the same data. It needs a keyboard and a mouse.

The arena as the game draws it: lit concrete walls and a jump pad

The game loads when you press Play. Click inside it to take the mouse; Esc gives it back.

Open in its own tab

WASD move Space jump Ctrl crouch Mouse 1 fire 1-9 / wheel weapons C gauntlet R shotgun G grenades E rockets Q lightning F railgun V plasma Enter use item X inspect weapon F11 full screen F8 field report Tab scores Esc menu

The game's menu also has Host a game and Join. Multiplayer passes its tests on a simulated network; two machines through the lobby have not been tried yet, so that goal is still open in the project below.

Pinpoint: every check, on the model

Pinpoint is NativeCAD's project viewer: the model, the goals it started from, and a pin for every check. This is the arena's own project, replayed in your browser. The map is shown as CAD data, each body its own part; the pins are the checks that had to pass before the game data was made.

Overlays
Loading the map…
Drag to orbit, scroll or pinch to zoom, click a part or a pin.

Click a part to read its record: where it came from, what it is made of and what was checked on it.

Groups. 13 groups. The sky and the outer hull are hidden at first so you can see in; Sealed puts them back. The 71 clip volumes and 3 jump-pad triggers are volumes, not things you see in the game: turn them on from the group buttons.

Overlays. Flood is the leak test: the surface of the space reached from the 9 spawns. Jump pads draws one flight the gate flew from each pad, to its checked landing. Bot graph is the 2,444 places and 17,303 links the bots plan on. Hulls outlines what stops a player or a shot. Break it removes one sky body and shows what the gate then reports.

Pins. 21 are shown: the 20 checks of the latest run and 0 open defect a person pinned by hand. 7 carry a point on the model; a check about the whole game sits on the part Pinpoint filed it under. The project holds 40 pins in all, the rest from an earlier run of the same checks.

Worked in Pinpoint: one issue, from a pin to a proof

Pinpoint is where the map was looked at and where its problems were worked, not only where the checks land. This is one issue as the project recorded it, pin 10 in the list above.

  1. Pinned on the model

    2026-11-10 05:39 UTC

    Looking round the streamed model, the owner put a defect pin on the wall walls_0728: “lots of Z fighting walls - need to boolean it”. Two solids had been drawn in the same place, and the viewer drew their faces in turn.

  2. Measured by a new check

    86 pairs as drawn

    The gate gained a check for it: no overlapping solids, which intersects every pair of solids whose boxes touch. On the map as drawn it is red: 86 pairs of solids share 4,870,856 cubic units.

  3. Fixed in the build

    67 brushes cut back

    Each brush is cut back by the ones before it, along their planes, and the convex pieces are kept: 67 brushes now stand as 109 bodies, and none of the 768 solids shares volume with another. All 991 of 991 bodies still pass the kernel's full check.

  4. Proven, then closed

    42 minutes, pin to close

    The check passes and sits on the model with the rest of the run (pin 13); the defect was closed in Pinpoint at 2026-11-10 06:21 UTC. The person who saw the problem and the check that proves it gone are in one record, on the part they are about.

The defect pin where it was placed, on the face between two touching solids; that face is now inside the model and is not drawn
The pin, where it was put: on the face between two solids. That face is inside the model now, and this viewer, like the game, no longer draws it.
The whole map with the pieces of brushes that were cut back tinted by piece
The whole map: every piece the fix cut back, in colour.

From map to game, with a gate in the middle

  1. Map source

    800 brushes · 147 curved patches

    A classic deathmatch map layout as text: convex brushes cut by planes, and grids of curve control points.

    Guards against: a brush whose planes do not close is refused by name.

  2. B-rep bodies

    844 solids · 147 B-spline sheets

    One closed convex solid per brush or cut piece, with plane faces over shared edges, and one exact B-spline sheet per patch. The worst solid differs from its own convex volume by 2.0e-11 of it. As drawn, 86 pairs of brushes overlapped; 67 brushes were cut back into 109 convex pieces, so no two solids share volume.

    Guards against: geometry that only looks right. 991 of 991 bodies pass the kernel's full check.

  3. Watertight gate

    10 of 10 checks pass

    768 solids must close the play space. It is cut into 8-unit cells and flooded from every spawn: 10,602,605 cells, and none touches the edge, so no opening wider than 16 units leads outside. Then spawns, items and jump pads are checked in that space.

    Guards against: a leak. With the body sky_0181 removed the gate goes red and reports the way out, 67 cells long.

    The flooded play space inside the sealed map
    Sealed: the flood stays in.
    With one sky body removed, a red path runs from a spawn out through the gap
    One body removed: the path out, in red.

  4. Bake

    5,459 hulls · 36,443 triangles

    From the checked bodies only: 839 brush hulls and 4,620 wedges under the curved patches, the drawn mesh in 20 material chunks, a 2,048 × 2,048 lightmap, and the bots' graph.

    Guards against: game data from an unchecked map. The bake refuses a map whose gate is red.

  5. Game

    9 weapons · 37 pickups · 9 spawns

    The game loads that data and nothing else: it collides with the hulls, draws the mesh, and its bots walk the graph, 10 of whose links ride the 3 jump pads.

    Guards against: drift. The game's own tests are pins in the project too.

What is made here

Borrowed: the layout, and 3 recorded gunshots that the Vanguard mode's guns play over their own synthesised sound (public-domain recordings, credited here), and the bots' radio, 6 files of speech rendered offline by an open speech model. Every other sound is synthesised in the browser. Image files shipped with the game: 25, of which 10 are lightmaps computed by the bake and 15 are key art and a map overview rendered from the game's own data.

Concrete, trim and metal surfaces painted by the page

Textures

14 materials are painted on canvases in the page when the game starts. No texture file is downloaded.

Lamp light and moonlight on the arena floor

Lighting

Computed in the bake at 8 units a texel: 145 lamp emitters from the map's lamp faces, a moon and a night sky through the sky bodies, and 15 glows at pickups and pads.

The player models side by side

Player models

4 characters, each a set of kernel solids on a jointed frame. Turn them round.

The weapon and pickup models

Weapons and pickups

31 models, every part a closed kernel solid. See them all.

Sounds

Synthesised in the page as you play: shots, pickups, jump pads, footsteps. There is no audio file to fetch.

About this page

The model here is every body of the build, 0.9 MB in all: the curved sheets, columns and volumes as the kernel tessellated them, and each solid as its faces less the parts another solid lies against (2,544 faces wholly covered, 350 trimmed), the same pieces the game draws, so no two faces fight for one place. Goals and pins are the project's record as Pinpoint holds it; where a recorded line named the map's source, those words are replaced and the row is marked. Lengths are in the map's units or in model millimetres, as each check recorded them. What the gate cannot see: a crack narrower than one 8-unit cell.

More demos

All demos →

Build your own part with NativeCAD

Try it free with the keyless evaluation · $200 per seat per year · Kernel SDK for products.