Find files, editable templates and browser test targets by what you need to make or test. Explore complete business kits for connected records, templates and expected results.
Page 93 of 221; 24 results per page.
One cube on one node, with translation, rotation and scale each driven by a five-key sampler that is linearly interpolated. Three files differing only in `interpolation`: the cleanest way to prove an animation player implements all three modes rather than treating everything as linear.
One cube on one node, with translation, rotation and scale each driven by a five-key sampler that is held (STEP): the value jumps at each key. Three files differing only in `interpolation`: the cleanest way to prove an animation player implements all three modes rather than treating everything as linear.
A longer tube skinned to a four-joint chain, every joint but the root animated, so the whole limb curls rather than hinging once. Exercises joint-matrix accumulation down a hierarchy: the step that a two-bone rig cannot catch.
A tube skinned to a two-joint chain with inverse bind matrices, unsigned-byte JOINTS_0 and float WEIGHTS_0, plus a three-second rotation animation on the elbow. The shipped models category had no skinned mesh at all; this is the smallest complete one: rig, bind pose, weights and clip in a single self-contained GLB.
The same two-joint skinned bend as readable glTF JSON with its buffer embedded as a base64 data URI: the file to open in a text editor when a GLB's skin, sampler or inverse bind matrices are not doing what you expect.
The 24-level spiral as readable JSON, so the `children` arrays and per-level TRS can be traced by eye. Useful when a converter flattens or re-parents a hierarchy and you need to see exactly where.
The same sphere with its buffer inlined as a base64 data URI: one self-contained text file, at roughly a third more bytes than the binary it encodes. The middle point of the three storage strategies in this group.
A glTF whose single buffer is a relative URI to a sibling .bin: the layout every DCC tool writes by default, and the one that breaks the moment an asset is moved or served from a different directory. Download the .bin in this group alongside it.
Geometry 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.
A 10 mm cube as text glTF 2.0: the JSON scene with its binary buffer embedded as a data URI, the human-readable sibling of the GLB. For testing glTF parsers and GLB↔glTF conversion.
The same six-cube ring with translation, quaternion rotation and scale spelled out per node. Read it next to the matrix twin to check a decomposition routine, or to confirm that your quaternion component order really is xyzw.
The same textured sphere with the PNG inlined as a base64 data URI in `images[0].uri`: a single portable text file. The variant that makes a glTF e-mailable and that some loaders quietly refuse.
Minimal textured glTF SAMPLE (external PNG + BIN) for glTF loaders and material tests.
The three-scene asset as readable JSON, where the top-level `"scene": 1` is one line you can point at in a bug report. Also the fixture for round-tripping multi-scene assets through tools that keep only one scene.
GML 2.1 packed coordinates into a single `gml:coordinates` string whose decimal, coordinate and tuple separators are all declared as attributes and can be anything. GML 3 replaced it with `gml:posList`, but WFS 1.0 servers still emit this, and a parser that assumes the default separators mis-reads any file that changes them.
The same five towns as the territory GML twin, but declared with the CRS84 URN instead of the EPSG one, which flips the axis order to longitude first. The two files are otherwise identical in structure, so together they isolate axis-order handling from everything else.
GML calls a multipolygon a MultiSurface and its parts surfaceMembers, and nests exterior and interior rings under named elements rather than relying on ring order. This feature holds the holed lake and a solid parcel in one geometry, which is the shape a WFS response usually takes.
Go generics helper for gopls / highlighter fixtures.
Intentionally lint-bait SAMPLE go snippet (errcheck-invalid) for rule-engine tests.
`go mod graph` output: a flat edge list, one `parent@version child@version` pair per line with no indentation at all, the simplest graph serialisation in this category and the easiest to diff. Every package, version, hash and licence is fictional: the tree describes nothing real.
A Go panic followed by the runtime's full goroutine dump: four goroutines with their wait states, two-line frames and a created by attribution, separated by blank lines. Blank-line separation defeats multi-line rules that treat an empty line as the end of an event.
The classic hello-world in Go (package main, an import, and fmt.Println, tab-indented like gofmt) for testing highlighters, the Go compiler, and parsers.
Intentionally invalid Go syntax for gofmt/parser failure tests.
A realistic Go program: a worker pool with structs and methods, goroutines, buffered channels, and a sync.WaitGroup, tab-indented like gofmt, for testing highlighters, go vet, and parsers.
We use Google Analytics and show ads via Adsterra. Non-essential cookies and ad scripts run only after you allow the matching categories. See our cookie policy.
