Shaders and advanced rendering

This page is part of the GenPy Ren'Py learning path. It focuses on practical Ren'Py 8.x production and links each concept back to the GenPy workflow.

Learning goals

• Understand when shaders are justified.
• Register shader parts with clear variable names.
• Test web and mobile targets before relying on GPU effects.

Core syntax

• mesh True
• shader
• renpy.register_shader
• uniform
• GLSL
• Model-Based Rendering

Runnable example

transform crt:
    mesh True
    shader "example.scanline"

show bg room at crt

Study outline

• Start with the smallest example for shaders and advanced rendering.
• Test the key terms in a clean Ren'Py project: mesh True, shader, renpy.register_shader, uniform.
• Move the pattern back into your real project only after the example runs.
• Use GenPy docs and validation to keep the feature connected to story, assets, and export readiness.

Common pitfalls

• Shader failures can look like black or missing images rather than friendly syntax errors.
• Always test Web and mobile targets before depending on custom GPU effects.
• Test the smallest working script before layering on visual or UI complexity.
• Run Ren'Py Lint before release builds, even when the script appears to run locally.
• Keep examples in standard .rpy files so they remain editable outside GenPy.

Official references

• Ren'Py official reference: https://www.renpy.org/doc/html/model.html
• Ren'Py text reference: https://www.renpy.org/doc/html/custom_text_tags.html
• Ren'Py official reference: https://www.renpy.org/doc/html/transform_properties.html

How this fits in GenPy

• Use GenPy shader/plugin docs for preset-based workflows when possible.
• Verify custom shaders in real Ren'Py runtimes before publishing.

Recommended GenPy docs:

• Plugins
• Code editor
• Desktop App