b3dClearScreenShader

Clears active screen shader and reverts to default rendering (same as b3dApplyScreenShader(0)). Takes no parameters. Returns nothing. Sets g_activeScreenShader3D = 0 (clears active shader, reverts to default rendering). Use to disable custom post-processing (return to normal rendering after using shader), deactivate effect conditionally (clear shader when condition no longer met), or reset state (clear before applying different shader, clean slate). Clear behavior: sets active shader to 0 (g_activeScreenShader3D = 0, default rendering), immediate next frame (no shader applied starting next b3dRenderWorld call), doesn't free shader (shader remains loaded in memory, can reapply later with b3dApplyScreenShader), safe to call anytime (always succeeds, even if no shader active). Use cases: (1) Disable effect (b3dClearScreenShader() revert to normal after using CRT effect), (2) Conditional disable (If Not underwater Then b3dClearScreenShader() clear underwater shader on surface), (3) Before switch (b3dClearScreenShader() before b3dApplyScreenShader(newShader) explicit clear), (4) Reset state (b3dClearScreenShader() ensure default before scene change), (5) Temporary effect (apply shader for few frames, then clear when done). Common patterns: disable = b3dClearScreenShader() revert to default; conditional = If condition Then b3dApplyScreenShader(shader) Else b3dClearScreenShader() toggle based on state. Typical workflow: load shader (shader = b3dLoadScreenShader("effect.hlsl")), apply shader (b3dApplyScreenShader(shader) activate), use for frames (shader applies automatically each frame), clear shader (this function when done, reverts to default), shader still loaded (can reapply without reloading, or free with b3dFreeScreenShader if truly done). Difference from free: clear deactivates (shader no longer applied, but remains loaded in memory), free destroys (shader removed from memory, must reload to use again), clear for temporary disable (can reapply quickly, no reload cost), free for permanent removal (releases GPU resources, frees memory). Default rendering: no post-processing shader (scene rendered directly to back buffer, no custom effects), engine's built-in pipeline (standard 3D rendering, no user shader), same as never calling ApplyScreenShader (pristine state, no shader overhead). Shader persistence: shader remains loaded (in g_screenShaders3D map, not affected by clear), parameters remain configured (shader.parameters unchanged, ready for reapply), can reapply instantly (b3dApplyScreenShader(shader) reactivates without reload). Performance: clear cost zero (flag set, trivial operation), next frame faster (no shader processing, default rendering cheaper ~0.1-5ms saved depending on shader complexity), useful for performance (clear expensive shaders when not needed, enable when required). Validation: no parameters (nothing to validate), always succeeds (flag set can't fail), safe to call multiple times (clearing already-cleared state harmless, no-op). No return value: void function (doesn't indicate success/failure), assumes success (always works, flag set), silent operation (no error messages, no confirmation prints). Related: b3dApplyScreenShader applies shader (opposite of this function, activates shader), b3dSetDefaultScreenShader same as this function (identical behavior, both clear active shader), b3dFreeScreenShader frees shader (alternative for permanent removal, releases memory), b3dLoadScreenShader loads shader (creates shader cleared by this function).