Full-screen world scan pulse from depth
In your harnessGodot shaderMIT
Full-screen scanner effect: world positions are rebuilt from the depth buffer and bright rings expand from a world point across every surface, with a fading trail, a world grid inside the trail and edge highlights.

What it takes and gives
- Shader type
- spatial
- Render modes
- unshaded, cull_disabled, depth_test_disabled, depth_draw_never, skip_vertex_transform, fog_disabled
- Parameters
- screen_texture (sampler2D), depth_texture (sampler2D), pulse_color (vec4 = 0.25, 1, 0.85, 1), center_x (float = 0), center_y (float = 0), center_z (float = 0), pulse_speed (float = 4), pulse_period (float = 3) and 4 more
- Use it on
- A world position for the pulse origin (set the three centre uniforms from a script).
- Result
- The scene with a glowing cyan ring sweeping outward over floors and objects, leaving a gridded trail.
- Renderers
- compatibility: compiled and rendered, forward plus: not verified, mobile: not verified
- Placement
- res://baltor/godot_shaders/scan_pulse_world/
Limits. Only opaque geometry is in the depth buffer, so transparent objects are not scanned. The grid uses 3D world coordinates, so it shows lines on all faces. One pulse centre at a time.
Details
- Kind
- Godot shader
- Engine
- Godot 4.3 or later
- Files
- 11 files, 68.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
- World position reconstruction from depth with inverse projection and view matrices, Distance-based expanding ring with trail, Derivative anti-aliased 3D grid
- Tags
- godot shader, spatial, post-process, scan, pulse, sonar, depth buffer, world position
- Identity
library.supply.creative_originals.473a97de78d23b5f8d850566.4bcf711b22db2653- Version
4bcf711b22db265376807f7486c447177af7f1596a613eb00081a86c42165656
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.


