nerospot.blogg.se - Spriteilluminator gamemaker studio

SPRITEILLUMINATOR GAMEMAKER STUDIO UPDATE

This is only really a problem for 2D in 3D setups, but something to keep an eye on.īut this is all just one sprite! I hear you cry. Batching has the potential to break scene draw order if a mesh comes between a number of sprites that can be batched together. I am looking at ways to get around this at the moment in this thread (if anyone has any ideas!) Making a Batched Sprite Renderer - Selection Issues - Engine Source & GitHub - Unreal Engine ForumsĪnother issue is going to be mixing things rendered via the ScissorRenderer and other unreal mesh types. Unreal does its editor selection logic via what has been rendered onto the screen, but as you are always clicking on geometry that has been rendered via the ScissorRendererActor, it will not select the original actor that represents the geometry in the scene. I am testing this on a i5-3570, 660gt at 1280x720įrom this I can say initial results are looking good performance wise! But there are some downsides to this approach that I am yet to tackle / solve. Keep in mind fps measuring is non linear as you get to very low frame millisecond times, so it is much better to look at the ms per frame for comparison. Currently the benchmark just spawns 5000 identical sprites randomly over the screen. I have setup a quick benchmark test in Scissor2D, Paper2D and Unity(5.6) so we can track performance metrics as the plugin is developed. Also because the ScissorRendererActor just accepts dynamic geometry to render each frame, all Scissor2D components such as sprites, terrain, tilemaps etc will be able to go through the same renderer and be batched and correctly layer sorted. The goal of this approach is to give the performance of using a Paper2DGroupedSpriteComponent while still maintaining the convenience of using individual actors with their own sets of components attached. So for now my plan has been to have a centralised ScissorRendererActor that you place into the scene, other Actor Components can then send scissor draw commands to the ScissorRendererActor that then on its render call, does all the batching / layering magic. Ideally this would be done at a render command level inside the Unreal render loop, but I am having to work with the limitations of what I can do in a plugin. My initial focus has been to prototype ways to make a batched geometry renderer that will allow individual actor components to submit draw calls that can then later be layer sorted and batched together if they are using the same materials and textures.

SPRITEILLUMINATOR GAMEMAKER STUDIO UPDATE

Hi Everyone! Time for a quick progress update on Scissor2D! Probaby out of the scope of this, but if i end up messing around with billboards enough it could be a good example project.A top down character template does sound awesome, I’ll put it on the list!.

Other solutions may come over time depending on demand.

We use Spine in our current workflow so this is something we would be keen to integrate.

If I auto batch these billboards together and send them as one draw call, this will produce incorrect draw order when drawing all 3 items. For example, say you had 2 billboard sprites with another actor with a mesh component in between then when viewed from the camera. This comes down to where I can do the batching of geometry in the render pipeline, while still keeping the functionality in a plugin.

2D in 3d workflow is something I would like to support, but I will need to investigate the implications for auto batching of sprites interfering with other ‘non sprite’ geometry.

Unsure if this falls into the scope of the project though.

A DooM 1 or 2 Like Character Controller would be useful as well.

A Top down character template would be awesome as well.

Being able to use Spine, DragonBones, or Spriter with this toolkit would be useful.

Being able apply a sprite to a billboard similar to Wolf3D or DooM would be awesome.