Difference between revisions of "Shader"
Line 34: | Line 34: | ||
=== Events === | === Events === | ||
=== Constants === | === Constants === | ||
− | [[Shader | + | '''[[Shader Constants]]''' |
− | + | <!--GIDEROSCST:Shader.CFLOAT 1 a float value--> | |
− | + | <!--GIDEROSCST:Shader.CFLOAT2 2 a vector of two floats--> | |
− | + | <!--GIDEROSCST:Shader.CFLOAT3 3 a vector of three floats--> | |
− | + | <!--GIDEROSCST:Shader.CFLOAT4 4 a vector of four floats--> | |
− | + | <!--GIDEROSCST:Shader.CINT 0 an integer value--> | |
− | + | <!--GIDEROSCST:Shader.CMATRIX 5 a 4x4 float matrix--> | |
− | + | <!--GIDEROSCST:Shader.CTEXTURE 6 a texture--> | |
− | + | <!--GIDEROSCST:Shader.DBYTE 0--> | |
− | + | <!--GIDEROSCST:Shader.DFLOAT 5--> | |
− | + | <!--GIDEROSCST:Shader.DINT 4--> | |
− | + | <!--GIDEROSCST:Shader.DSHORT 2--> | |
− | + | <!--GIDEROSCST:Shader.DUBYTE 1--> | |
− | + | <!--GIDEROSCST:Shader.DUSHORT 3--> | |
− | + | <!--GIDEROSCST:Shader.FLAG_FROM_CODE 4--> | |
− | + | <!--GIDEROSCST:Shader.FLAG_NONE 0--> | |
− | + | <!--GIDEROSCST:Shader.FLAG_NO_DEFAULT_HEADER 1--> | |
− | + | <!--GIDEROSCST:Shader.SHADER_PROGRAM_UNSPECIFIED 0 indeterminate program--> | |
− | + | <!--GIDEROSCST:Shader.SHADER_PROGRAM_BASIC 1 render a plain color shape--> | |
− | + | <!--GIDEROSCST:Shader.SHADER_PROGRAM_COLOR 2 render a colored shape--> | |
− | + | <!--GIDEROSCST:Shader.SHADER_PROGRAM_TEXTURE 3 render a textured shape--> | |
− | + | <!--GIDEROSCST:Shader.SHADER_PROGRAM_TEXTUREALPHA 4 render shape with an alpha texture--> | |
− | + | <!--GIDEROSCST:Shader.SHADER_PROGRAM_TEXTURECOLOR 5 render a colored and textured shape--> | |
− | + | <!--GIDEROSCST:Shader.SHADER_PROGRAM_TEXTUREALPHACOLOR 6 render a colored shape with an alpha texture--> | |
− | + | <!--GIDEROSCST:Shader.SHADER_PROGRAM_PARTICLE 7 used by liquidfun particles--> | |
− | + | <!--GIDEROSCST:Shader.SHADER_PROGRAM_PARTICLES 8 used by [[Particles]]--> | |
− | + | <!--GIDEROSCST:Shader.SHADER_PROGRAM_PATHFILLCURVE 9 used by [[Path2D]] to fill a curve--> | |
− | + | <!--GIDEROSCST:Shader.SHADER_PROGRAM_PATHSTROKECURVE 10 used by [[Path2D]] to draw a curve--> | |
− | + | <!--GIDEROSCST:Shader.SHADER_PROGRAM_PATHSTROKELINE 11 used by [[Path2D]] to draw a segment--> | |
− | + | <!--GIDEROSCST:Shader.SHADER_VARIANT_TEXTURED 1 a textured variant of a standard program--> | |
− | + | <!--GIDEROSCST:Shader.SHADER_VARIANT_3D 2 a 3D variant of a standard program--> | |
− | + | <!--GIDEROSCST:Shader.SYS_COLOR 2 the current color (CFLOAT4)--> | |
− | + | <!--GIDEROSCST:Shader.SYS_NONE 0 not filled by Gideros--> | |
− | + | <!--GIDEROSCST:Shader.SYS_PARTICLESIZE 6 the particle size--> | |
− | + | <!--GIDEROSCST:Shader.SYS_PROJECTION 10 the projection matrix (CMATRIX)--> | |
− | + | <!--GIDEROSCST:Shader.SYS_TEXTUREINFO 5 real extent and texel size of the texture (CFLOAT4)--> | |
− | + | <!--GIDEROSCST:Shader.SYS_TIMER 9 current time (CFLOAT)--> | |
− | + | <!--GIDEROSCST:Shader.SYS_VIEW 8 the view matrix (CMATRIX)--> | |
− | + | <!--GIDEROSCST:Shader.SYS_VP 11 combined view/projection matrix (CMATRIX)--> | |
− | + | <!--GIDEROSCST:Shader.SYS_WIT 7 the World Inverse Transpose matrix (CMATRIX)--> | |
− | + | <!--GIDEROSCST:Shader.SYS_WIT3 3 3x3 World Inverse Transpose matrix--> | |
− | + | <!--GIDEROSCST:Shader.SYS_WORLD 4 the world or matrix (CMATRIX)--> | |
+ | <!--GIDEROSCST:Shader.SYS_WVP 1 the combined world/view/projection matrix (CMATRIX)--> | ||
|} | |} | ||
{{GIDEROS IMPORTANT LINKS}} | {{GIDEROS IMPORTANT LINKS}} |
Revision as of 00:20, 4 November 2023
Supported platforms:
Available since: Gideros 2015.06.30
Inherits from: Object
Description
Gideros internally uses five distinct shaders:
- the ‘Basic’ shader handles shapes with a constant color
- the ‘Color’ shader handles shapes with per-vertex colors (mostly used by Mesh sprite)
- the ‘Texture’ shader handles textured shapes (Bitmaps)
- the ‘TextureColor’ shader handles textured and per-vertex colored shapes
- and the ‘Particle’ shader deals with Box2D particle systems
The shader API allows replacing the default shader used by Gideros with a custom one, on a sprite per sprite basis. You create a Shader object and assign it to one or several sprites. Writing Shaders
That said, since Gideros will use your shader as if it was the standard one, you will have to make sure that your custom shader is compatible with Gideros standard Shader, which essentially means that it takes the same input parameters.
The recommended way is to write your shader code in Lua, it will then be automatically translated to the relevant shader language for the platform you are using, eg GLSL, HLSL or MTL: Lua Shaders
MethodsShader.new creates a new shader Shader:isValid check if this shader was compiled successfully |
EventsConstants |