Godot 3 Renderer Design Explained
Events
Subscribe:  iCal  |  Google Calendar
Orlando US   24, Jul — 27, Jul
Grapevine US   25, Jul — 29, Jul
Los Angeles US   28, Jul — 29, Jul
Los Angeles US   28, Jul — 2, Aug
Helsinki FI   1, Aug — 5, Aug
Latest comments
by Online Payday Loans Alabama
15 min ago

PaydayAlabama offers payday loan services to the people of Alabama and nearby areas who are in need of fast cash immediately. We provide instant approval, hassle free cash loans. Just fill the online application form and get cash loan just by sitting in your home. For more information visit http://www.paydayalabama.com/decatur-al/

by Amit Kuliyal
1 hours ago

I think you were mostly just narrating your career story in this post instead of any teaching or tips. Anyways thanks.Ang good Luck

А по русски кирилл не мог подкаст сделать?

Godot 3 Renderer Design Explained
25 September, 2017
News

Godot is all about a different approach to rendering, trying to accommodate better to most users’ needs. The team behind the tool shared a document that explains the overall design of Godot. This might be a starting point for developers who would like to help the team write rendering code. 

You can also ask the team about anything if you need something to be explained further.

Here is a small piece of the document:

The default VisualServer implementation in Godot is VisualServerRaster, which is a Visual Server designed for rastering. This implementation handles spatial indexing of objects and, every frame, building a render list of objects drawn. It also handles the pairing of objects (lights to geometry, GI to geometry and lights, etc).

Rastering is done via another opaque interface, Rasterizer, which in Godot 3.0, was further optimized to take batches of objects instead of having to call one by one to render (which hurts performance).

RASTERIZER ABSTRACTION

Godot’s rasterizer implementation is also considerably high level. We know it would probably be easier to just abstract a low level drawing API like OpenGL or Direct3D (or use open APIs, such as BGFX). However, this makes our work more complex in the long run.

The reason for this is that, when supporting multiple backends, different techniques may also need to be supported. For example:

  • On GLES3+ we can use UBOs to optimize shader parameters. On GLES2, regular uniforms are used.
  • On GLES3+ we can use VAOs to optimize array configuration. On GLES2 regular glVertexAttribPointer must be used.
  • On GLES3, we can use cool rendering techniques like Clustered or Single Pass Forward. On GLES2, for peformance, only multipass forward makes much sense.
  • On GLES3+ we can use transform feedback for particles or blend shapes, while on GLES2 everything needs to be done using CPU.
  • And the list goes on.

Godot

Make sure to read the full guide here.

Source: Godot

Leave a Reply

avatar