Procedural fire on a camera-facing card
In your harnessGodot shaderMIT
Fire on a single quad that always faces the camera: rising distorted noise shaped into a flame silhouette and coloured through a heat ramp, with no textures or particles.

What it takes and gives
- Shader type
- spatial
- Render modes
- unshaded, blend_add, cull_disabled, depth_draw_never, shadows_disabled
- Parameters
- core_color (vec4 = 1, 0.95, 0.6, 1), mid_color (vec4 = 1, 0.5, 0.08, 1), tip_color (vec4 = 0.6, 0.05, 0.02, 1), rise_speed (float = 1.6), noise_scale (float = 5), distortion (float = 0.35), flame_width (float = 0.55), flame_height (float = 0.9) and 1 more
- Use it on
- A QuadMesh placed where the fire burns; its bottom edge is the base of the flame.
- Result
- A flickering flame with a pale core and red tips that faces the camera from every angle.
- Renderers
- compatibility: compiled and rendered, forward plus: not verified, mobile: not verified
- Placement
- res://baltor/godot_shaders/fire_billboard/
Limits. A single card: seen from directly above the flame flattens. Additive blending means it cannot occlude and looks weak on bright backgrounds. It casts no light; add an OmniLight3D for that.
Details
- Kind
- Godot shader
- Engine
- Godot 4.3 or later
- Files
- 11 files, 54.0 KB
- Licence
- MIT
- Declared effects
- reads files, runs commands
- Checked with
- Godot 4.7.2, opengl3 compatibility (Mesa llvmpipe, Xvfb)
- Checks
- contract static, engine run, engine log clean, shader in scene, capture written, render not uniform, shader changes pixels
- Techniques
- Spherical billboard by replacing the modelview rotation, Height-weighted domain distortion, Fractional Brownian motion turbulence with a heat colour ramp, Value noise with quintic interpolation and fractional Brownian motion
- Tags
- godot shader, spatial, fire, flame, billboard, procedural, vfx
- Identity
library.supply.creative_originals.de44057a74139ce99fcb5f55.679b89bb018dd9b4- Version
679b89bb018dd9b4558c6f60b38b2234a979b68853405580c8a9f8872f7dbdd4
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.


