Birch bark
In your harnessProcedural textureMIT
Generate tileable PBR maps of birch bark: chalk-white papery bark with horizontal lenticels, chevron branch scars, dark fissured patches and peeling strips. Use on birch trunks and logs.

What it takes and gives
- Entry point
- generate
- Maps
- albedo, normal, roughness, height, ao
- Parameters
- lenticels, lenticel_length, dark_patches, branch_scars, peeling, hue_shift, saturation, brightness
- Presets
- default, silver_aged, river_birch, young_smooth
- Tileable
- yes
- Command line
- python bark_birch.py --size 1024 --seed 7 --preset NAME --out DIR [--width W --height H] [--set NAME=VALUE] [--directx-normal] [--orm]
- Godot material
- material.tres
- Blender builder
- blender_material.build_material(folder)
Limits. Marks are placed at random in texture space; real birch bark changes along the trunk, which a single tile cannot show. Peeling strips are flat bands with a raised lip, not separate geometry. Occlusion is a blurred-height estimate.
Details
- Kind
- Procedural texture
- Engine
- Python 3.10 or later
- Files
- 12 files, 224.8 KB
- Licence
- MIT
- Declared effects
- runs commands, writes files
- Checked with
- Godot 4.7.2, gl_compatibility
- Checks
- command line generates declared maps, maps decode, maps have declared size and channels, maps tile without a seam, normal vectors unit length facing out, maps carry detail, godot imports the maps, godot material template loads every map, godot compatibility render, capture shows the textured surface, blender builds the material
- Techniques
- Capsule strokes for lenticels, V-shaped stamp profile for branch scars, Anisotropic fractional Brownian motion thresholded for dark patches, Worley borders for fissures, Ragged ellipse stamps for peeled strips
- Tags
- texture, pbr, tileable, bark, birch, tree, nature, procedural
- Identity
library.supply.creative_originals.66d19325c6ffbbf6bb8f483b.eed96d545cc7bd5d- Version
eed96d545cc7bd5d0f509dc4db287fdc0c1d6856f3e647979859c21eb0421a2c
The version is the SHA-256 of the item your harness downloads; every file in it names its own checksum.
Something wrong with this item, its rights or its safety? Report it on the support page, or from your harness after a download.
