It's been a month since the second progress report, and progress continues towards the new Godot renderer. This milestone was (and will likely be) the most difficult, due to the techniques that had to be implemented.
As a result, many of the goals for it were not met (will have to be moved to a new Milestone 4), but hopefully everything that remains is simpler.
Here's the list of tasks for the current milestone and the next one:
Glow effects are most commonly done by taking the whole screen, shrinking it, blurring it and then blending it back (using screen, additive or soflight blending modes).
Godot 2.0 already supported this in a more or less limited fashion, so the challenge for 3.0 was, how to make glow much better? how to make it totally awesome?
Godot 3.0 implements glow in what is called a "multi-stage" configuration. The screen is blurred to successive mipmaps (i.e.
screen_size/8, etc). From there on, it's up to the user to decide which ones to enable:
The lower mipmaps give objects an aura (similar to Godot 2.0), while the higher ones produce a beautiful bloom effect:
Of course, an usual problem with doing glow this way is that you can see arctifacts related to linear interpolation (the glow is "blocky"). To avoid this, an optional bicubic upscaler is provided:
As was mentioned in previous posts, Godot 3.0 renderer works entirely in linear space (Gamma is no longer supported). This workflow allows for something nice called "tone mapping", which means that the output image in linear space can be applied a curve to make some details more visible.
Godot 2.0 supported only Linear and Reinhard tonemappers. Godot 3.0 supports Linear, Reinhard, Filmic and Aces tonemappers.
Godot 3.0 supports the same auto-exposure scale method as Godot 2.0, which worked pretty well. The advantage is that it can be combined much better with the new Bloom, allowing fantastic looking effects:
Godot 3.0 supports far and near depth of field blur, in different quality settings to have better performance/quality options.
For the FAR depth of field, Godot 3.0 implements the typical weighted blur based on distance, this works nicely:
NEAR DOF is considerably more difficult to implement, and correct implementations are usually demanding in GPU (two separable convolution buffers must exist in parallel).
As the aim of Godot is to run nicely on low end hardware, a novel algorithm was implemented, which allows high quality bluring of near objects in a single separable pass:
The result is a little less correct, but the performance benefits are large.
Both DOF effects can be used together for specifying focal regions:
The new GI probe implementation in Godot is a game changer, and gives Godot 3.0 an edge in quality over existing mainstream engines.
GIProbe is a new node that is placed in the scene in a similar way as you place a reflection probe. It must be pre-baked for dynamic scenario geometry, but it offers support for full dynamic lights and dynamic objects.
It works by implementing voxel cone tracing in a way that is friendlier with low end GPUs and high end mobile.
The light voxel is computed on CPU, allowing all types of dynamic lights, then uploaded to a 3D texture (with optional real-time compression, to improve memory usage and performance) used by the shader:
Here's how an area that receives no light at all gets lit by indirect bounces!
Support for materials with emission also exists, allowing full scene lighting using emissive materials:
A great advantage of this technique compared to other implementations (such as Enlighten or any other lightmap-based baking), is that full reflections are possible, with much higher quality than using reflection probes:
Finally, dynamic objects get full light and reflections from the GIProbe when they move around inside, without having to use any kind of probe groups:
The last remaining big feature is the new particle system, then everything else is simpler, and includes cleaning up the implemented techniques. Hoping that by the end of January, the new renderer will be mostly done!
If you are interested in seeing what each feature looks like in the code, you can check the gles3 branch on GitHub.