Sprite lamp vs spriteilluminator update#

camera add ( renderTexture ) // set object's renderTarget, so it will be rendered only on its texture and won't appear on any camera. Here is a usage example for it: // create render target with the size of 256 by 512 pixels var renderTexture : FlxRenderTarget = new FlxRenderTarget ( 256, 512 ) // specify camera which will be used for calculation of drawable sprites positions on this render texture. I took the idea from Phaser's RenderPass object, which has a very simple API. Basically it's the same as a FlxSprite, but you can render other sprites to its texture through underlying OpenGL calls (not with BitmapData's draw() method). Multipassįor more complex effects which require multi-pass rendering, I've added FlxRenderTarget which extends the FlxSprite class. But in case you have many sprites with different materials and you want them not to be batched (to minimize the amount of data which will be reuploaded to the GPU), you could set it to false to force this behavior ( = false ). This means that the renderer will try to batch objects with this material. The material class also has a batchable:Bool property which is true by default. Setting a material's shader you will break the batch, but if several sprites share the same material, then they will be batched together again. Say your shader has a uFill uniform after setting material.shader = m圜ustomShader, you can set the value of this uniform like this: material. If you do set a material's shader property, then the material will create a data object ( ) to store info about shader uniforms which you could set later. So when you do sprite.blend = BlendMode.ADD, in reality you change the blend mode of its material.īy default, objects have materials without shaders (shader is null), which means that the renderer will use default shader and batch this object. A material stores information about an object's blend mode, smoothing, shader to use, data for the shader (values of shader uniforms) and an array of textures to use. Now a few more details about sprite materials.Įach sprite, tilemap, etc. addLight ( light ) // and create normal map and apply it to our material var normalMap : FlxNormalMap = new FlxNormalMap ( 0, 0, 'assets/rock_n.png' ) lightMaterial. YELLOW, 0.2 ) // add light source light = new FlxLight ( 0, 0, 0.3 ) light. material = lightMaterial // tune light material properties lightMaterial. Here is an example of how it can be used right now: // create regular sprite shadedWall = new FlxSprite ( 100, 200, 'assets/rock.png' ) add ( shadedWall ) // create custom lighting material and apply to our sprite lightMaterial = new FlxLightingMaterial () teapot. I've updated the flixelighting lib by Pixelbear to make it work with the new material system on my fork here. This enables more complex effects like 2D-lighting (by using normal maps generated with tools like SpriteIlluminator). Currently, it's just a single render-pass material with multiple textures support. I've added a FlxMaterial class (see here). You can follow my progress in the new pull request here. Note: I've switched to working on a new branch and closed the previous pull request.

Sprite lamp vs spriteilluminator update#

I want to give you a quick status update regarding my work towards making Flixel compatible with the latest versions of OpenFL again. As you may know, HaxeFlixel is currently stuck with outdated versions of OpenFL and Lime due to some rendering incompatibilities, and updating it has turned out to be more work than expected.