Skip to content
NAMEFRAMECommercial PreviewApply for Pilot
Apply for Pilot
Quarry

The quarry capture.

A slate pit with terraces and spoil, holding people and industrial props on ground that is nowhere level. The capture that exposed a ground-registration bug: the spawner had bound to one rock of sixty-five. 300 frames, 11,921 labelled instances across 7 classes, graded A · 92.7 out of 100 by the run's own validator — whose findings are listed further down, in full.

Map
Quarry_Slate
Frames in the run
300
Labelled instances
11,921
Resolution
1280×960
Seed
20260817
Validator grade
A · 92.7/100

What it is for

Objects on broken, sloped rock rather than flat ground, where placement and occlusion are both harder.

How the labels were made

Every label was derived from the engine's own per-instance ID buffer and the camera transform that rendered the frame — not from a model, and not by hand. What occludes what is decided by the GPU on the same pass that draws the frame.

Engine
Unreal Engine 5.8
Camera
Zones over the pit, 18–45 m, 1280×960
Classes
person, barrel, crate, haybayle, container, cone, wheelbarrow
Annotation formats
YOLO, COCO, per-instance ID buffers, per-frame metadata JSON
Packaged
300 of 300 frames, across 1 archive
Version
1.0

What the frames look like

One frame from the run, downscaled for the web: the pit filling the frame; the densest quarry frame pointed two thirds at sky. It was picked to show what the scene is, so read it as an illustration rather than as a sample — the archive holds the other 299.

Frame dump__plugin_000270.png of the Unreal Engine quarry capture: the pit filling the frame; the densest quarry frame pointed two thirds at sky
Quarry_Slate1280×960 per frameOne frame from the run, downscaled for the web

Download the archive.

One archive, holding the whole run.

Quarry · complete capture

605 MB

All 300 frames of the run: images, YOLO labels, the same labels as COCO, per-instance segmentation, per-frame camera metadata, the capture contract and the run's own report. 11,921 labelled instances. Depth is left out — it is 1.37 GB per capture of float32 nobody training a box detector will open, and the job files to re-capture it are published.

Frames
300
Annotated instances
11,921
Format
ZIP

Counted from the run’s own labels: 300 of 300 requested frames matched a label file in the export, and the COCO carries boxes rather than polygons because the run was exported as a box dataset.

  • images/ rendered RGB frames, unmodified PNG
  • segmentation/ per-instance ID buffers, one colour per instance
  • labels/ YOLO boxes, one text file per frame
  • annotations/instances.json the same labels in COCO format
  • metadata/ per-frame camera, actor and spawn-manifest records
  • reports/ this capture's own report and validation output
  • capture.json the run contract: classes, camera policy, seed
  • data.yaml class names, ready for a YOLO trainer
Download 605 MB

SHA-2568a50bae28462704aaf46399bac24fba012ba7e234d2c3ae2744fe922eaa3d6ba

Known limitations

The validator graded this run A · 92.7/100, and its report ships inside every archive. Here is what it and we know is wrong with the data.

  • The validator took 7.33 points off for class-imbalance: rarest/commonest class ratio 0.084. It is one of the reasons the run scored 92.7 rather than 100.
  • The capture checked itself for people it could see and did not label: 6/5481 engine-visible people unlabelled (0.11%, 300/300 frames). The check ships inside the pack.
  • One map, one seed and one camera policy. A model trained on this capture alone has seen one place; the eight captures are published together for that reason.
  • The archive carries COCO boxes rather than COCO polygons. The per-instance ID buffers ship alongside them and are the mask ground truth.
  • A detector trained on all eight of these captures and nothing else reached 0.350 recall on real drone footage. Synthetic data alone did not close that gap, and this archive is published so the number can be argued with rather than believed.

The checks behind those numbers, and how a run is graded, are on the dataset quality page, and the validator itself is described under dataset validation.

Terms, plainly

Free to download, read, train on and benchmark against. Publish whatever results you get, including bad ones. What you may not do is repackage the pack and sell it as your own dataset.

The images depict environment and prop content licensed for use inside Unreal Engine projects. Redistribution rights for that underlying content are not granted with these packs, so check the source licence before publishing derivatives. The full text ships as TERMS.txt inside each archive.

Citation

If you publish anything you got out of this data, this is how to point at the exact run it came from. The seed and the map are the part that matters: they are what makes the run reproducible.

NameFrame. "Quarry: synthetic computer-vision dataset." Version 1.0, generated with Unreal Engine 5.8 on Quarry_Slate, seed 20260817. https://getnameframe.com/datasets/quarry

Need this scene, but yours?

This capture came out of one NameFrame run: a map, a class list, a camera policy and a seed. Change any of them and you get a different dataset with the same ground truth guarantees. That is what the generator is for.

How synthetic data generation works in Unreal Engine Apply for a private pilot