TIRE(1)

πŸ“¦
version 7.44.0 Β· 2 versions
, in nixpkgs unstable

πŸ’… TIRE(1) β€” the BRL-CAD manual, bestie edition πŸ›ž

okay so you opened the tire(1) page from the BRL-CAD manual set and honestly? it's a good one. buckle up πŸŽ€


✨ NAME ✨

tire β€” generate a parametric tire model from standard tire dimensions. yes girl, an actual tire, from numbers, in a CAD database πŸ’–


πŸ¦‹ SYNOPSIS πŸ¦‹

tire [options] [obj_name]
tire --list-tread-patterns
tire --demo-file _file.g_

🌸 DESCRIPTION 🌸

so tire creates a curved-sidewall tire, optionally with a wheel and tread, and it drops it in the current open database (that's when you run it from inside mged(1)) or in tire.g when you run it as a standalone command. either way, it's giving main character energy ✨

dimensions follow the common ISO notation (think 235/75R15): width in millimeters, sidewall aspect ratio as a percentage, and rim diameter in inches. with no options at all, the default size is 215/55R17 and the wheel is included. slay.

🫢 heads up: by default tire does not model tread, because tread geometry can significantly increase raytracing times. lowkey important.

tread gets enabled by any of these three:

  • selecting a named preset with -p
  • supplying a custom JSON definition with --tread-pattern-file
  • choosing a legacy shape with -t

the generated assembly stores its resolved settings as tire:: attributes on the top-level combination, including the normalized ISO size and (when tread is generated) the resolved tread pattern JSON. it's organized, it's documented, it's iconic πŸ’…

😭 real talk, no cap: the generated models are intended for procedural geometry, visualization, inspection, and BRL-CAD workflow testing. they are not validated for tire engineering design, roadworthiness, load rating, manufacturing, regulatory compliance, or vehicle safety use. do not put these on a car. i'm so serious.

if no obj_name is given (and -n is not used), a name of the form tire-215-55R17 is derived from the resolved dimensions. cute, self-naming, we love a self-sufficient king πŸ‘‘


πŸŽ€ OPTIONS πŸŽ€

  • -h, -? β€” print a help message and exit. use --list-tread-patterns to see the available tread presets πŸ’–
  • -n name β€” set the name of the top-level database object. the same value is used as the suffix for generated child objects. consistency!! ✨
  • -w bool β€” enable (1) or disable (0) the wheel. the wheel is included by default πŸ›ž
  • -d width/aspectRdiameter β€” specify tire dimensions using ISO-style notation, for example 235/75R15. width is in mm, aspect ratio in percent, and rim diameter in inches.
  • -W # β€” tire width in mm, allowing fractional values. overrides the width from -d. precision babe πŸ’…
  • -R # β€” sidewall aspect ratio (percent), allowing fractional values. overrides the ratio from -d.
  • -D # β€” rim diameter in inches, allowing fractional values. overrides the diameter from -d.
  • -g # β€” tread depth in 32nds of an inch (for example, 11 means 11/32 in). the default is 11.
  • -j # β€” rim (hub) width in inches.
  • -s # β€” maximum sidewall radius in mm, measured from the tire center to the widest point of the sidewall. must lie between the rim radius and the tire radius. ⚠️ no vibes-based values here, it's a real constraint.
  • -u # β€” tire (wall) thickness in mm.
  • -p name β€” select a named tread pattern preset (see --list-tread-patterns). the legacy aliases 1 and 2 map to the legacy-rib and legacy-block presets. mutually exclusive with --tread-pattern-file 🚫
  • -c # β€” number of tread patterns repeated around the tire. each preset has its own valid range (overall 3 to 512); values outside that range are rejected. so don't try it πŸ™ˆ
  • -t # β€” legacy tread shape profile (1 or 2). normally supplied by the selected preset.
  • --tread-pattern-file file β€” read a custom JSON tread pattern definition (see CUSTOM TREAD JSON below). mutually exclusive with -p.
  • --list-tread-patterns β€” list the available named tread presets and exit. window shopping πŸ›οΈ
  • --demo-file file.g β€” write a sampler database to file.g and exit. the sampler builds an all combination arranging varied tire examples (compact car, sedan, performance, SUV, van, pickup, commercial truck, bus, tractor, wheel loader, and mining haul truck) in rows by vehicle class and increasing scale. it's a whole runway show 🌈

🧚 CUSTOM TREAD JSON 🧚

files supplied with --tread-pattern-file are JSON objects. the required fields are type and symmetry; unknown fields are rejected. yes, it's strict, it's a Virgo πŸŽ€

custom tread JSON field contract

{
  "$schema": "https://brlcad.org/schemas/tire-tread-pattern.schema.json",
  "schema_version": 1,
  "type": "rib | lug | block | hybrid",
  "symmetry": "symmetric | directional | asymmetric",
  "terrain": "HT | AT | MT",
  "axle": "steer | drive | trailer | all",
  "void": "number, 0.1 through 0.7",
  "grooves": "integer, 1 through 8",
  "groove_angle": "number, 0 through 60",
  "block": "small | medium | large",
  "pitch": "uniform | variable | {\"type\":\"variable\",\"count\":2..8}",
  "pitch_seq": ["numbers, each 0.5 through 2.0, 2 through 16 entries"],
  "sipes": "none | low | medium | dense",
  "shoulder": "closed | semi-open | open",
  "center": "continuous | broken | ribbed",
  "tie_bars": false,
  "shape": "integer, 1 or 2",
  "pattern_count": "integer within the selected pattern family's range",
  "sketches": [
    [[0.10, 0.20], [0.24, 0.20], [0.24, 0.80], [0.10, 0.80]]
  ]
}

if sketches is supplied, the listed normalized cut polygons are used as the tread geometry instead of procedurally generated sketches. each polygon must have at least three points, and each point is a two-number array. the remaining fields are retained as metadata for round-trip editing πŸ’œ


πŸ”₯ EXAMPLES πŸ”₯

Example 1. Creating a 185/65R15 tire with a highway tread

tire -d 185/65R15 -p highway-rib -n autowheel

generate a 185 mm wide, 65 aspect, 15 in rim tire named autowheel in tire.g, using the built-in highway-rib tread preset. use --list-tread-patterns to see the other presets such as all-terrain, mud-terrain, and winter-siped. the menu is stacked πŸ“

Example 2. Overriding individual dimensions with fractional values

tire -W 225.5 -R 50 -D 18 -g 13 -c 24 -p mud-terrain -n offroad

build a precisely sized tire (225.5 mm wide, 50 aspect, 18 in rim) with a 13/32 in tread depth and 24 mud-terrain pattern repeats (each preset has its own valid repeat range). the -W, -R, and -D flags accept fractional input and override any ISO size from -d. fractional!! she's exact πŸ’…

Example 3. Generating the built-in sampler for visual comparison

tire --demo-file tire_demo.g
mged tire_demo.g

write a database of varied example tires (one per vehicle class) into tire_demo.g, then open it in mged(1). drawing the all combination shows the full set laid out in rows for side-by-side comparison. it's giving science fair but make it fashion ✨


πŸ‘‘ SEE ALSO πŸ‘‘

brlcad(1), mged(1), coil(1), bolt(1) β€” the whole friend group 🫢


⭐ AUTHOR ⭐

BRL-CAD Team πŸ‘‘


this software is Copyright (c) 1989-2026 by the United States Government as represented by U.S. Army Research Laboratory.


πŸ’€ BUG REPORTS πŸ’€

reports of bugs or problems should be submitted via electronic mail to devs@brlcad.org πŸ“¬ don't be shy, they wanna hear it


and that's the whole page, bestie β€” BRL-CAD / TIRE(1), straight from the BRL-CAD manual set, dated with that 1989-2026 copyright run. go build a tire, i'm obsessed πŸ›žπŸ’œ

πŸ“¦ where this page comes from