BIN — glTF External Buffer Payload
The binary payload the external-buffer glTF in this group points at: tightly-packed positions, normals and indices with 4-byte alignment padding. Not viewable on its own — its bufferViews live in the JSON.
| Field | Value |
|---|---|
| Role | glTF buffer (external) |
| Byte length | 10656 |
| Contents | POSITION + NORMAL + indices |
| Referenced by | external-buffer.gltf |
| Alignment | padded to 4 bytes |
Specifications
- Format
- raw glTF buffer
- Bytes
- 10656
- Contents
- POSITION, NORMAL, indices
- Alignment
- 4-byte padded
- Referenced By
- external-buffer.gltf
Testing contract
Reference control- Scenario
- Fetch this file at the byteOffset/byteLength of each bufferView in external-buffer.gltf.
- Expected result
- Every view lies inside the 10656-byte payload and each accessor's element count matches its declared type and componentType.
What is a .bin file?
A .bin file is a generic binary blob with no specific format — raw bytes whose meaning depends entirely on the producing application (firmware images, memory dumps, serialized payloads). The extension signals only 'not text.'
How to use this file
Use an example .bin file to test binary/hex viewers, file-type sniffing, octet-stream handling, and download pipelines that must not corrupt arbitrary bytes.
How to use this file for testing
“BIN — glTF External Buffer Payload” is a deterministic Novus Examples fixture for Conversion testing, Error handling. The same content exported across many formats and linked as a group, so you can convert one and diff against the expected twin.
Documented properties for this file: raw glTF buffer. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.
3D and CAD fixtures carry one small, documented solid or scene. Convert and inspect against the known geometry, units, and structure; format twins let you diff interchange fidelity, and the 3D viewer previews the actual mesh.
Related files
- gltfglTF — External Texture URIGeometry inline, texture out of line: the image is a relative URI to a sibling PNG while the buffer is embedded, which is the mixed layout that trips asset packers expecting all-or-nothing. Download the PNG in this group with it.
- arAR - Empty Archive (magic only)The smallest valid archive in this catalog: the 8-byte ar magic and nothing after it. ar has no trailer record, so end-of-file is the only end marker, and this is what an empty static library or an empty .deb control archive looks like on disk.
- cpioCPIO - Empty Archive (trailer only)An empty cpio archive is a single TRAILER!!! header record - a full 110-byte newc header with every numeric field zero - plus its alignment padding. Readers that look for member data before checking the name find none and must still report a valid, empty archive.
- jsonCucumber JSON — Failing Step with Stack TraceOne step of one scenario fails with an assertion message and a stack frame; every other step passes. In cucumber.json a scenario has no status of its own — it is failed if any of its steps is — so this file catches reporters that look for a scenario-level field that does not exist.
- jsonCucumber JSON — Undefined, Pending and Skipped StepsThe three non-failure statuses BDD runners produce and dashboards routinely collapse into "failed": undefined (no step definition matched), pending (explicitly unimplemented) and skipped (never attempted). Whether the run is red depends on the runner's strict setting, which is exactly the decision this file forces.
- xmlCucumber JUnit XML — Checkout RunThe same six pickles reported as JUnit XML, which is what a BDD suite hands to a generic CI dashboard. One <testcase> per pickle means the three expanded outline rows appear as three tests with identical names — enough to break any store keyed on name alone.
Generated by generation/models_p7.py. Free for any use, no attribution required — license.