By | November 13, 2022

Major Feature Release – Turbo Tools V3 now with Temporal Stabilizer and the option to use animation optimised sample pre-sets!
Turbo Tools is a full rendering pipeline addon that includes:

Turbo Render – Vastly superior render results in a fraction of the time. Retains image quality the standard denoisers can’t maintain even when providing them with images rendered for 120X longer! For complex scenes you can expect your single frame renders to be reduced from several hours to several minutes! Check out the below video to see how Turbo Render was able to get a gtx 1070 to destroy an rtx 4090!

Temporal Stabilizer – Although only a single checkbox, this massive new feature provides per pass temporal stabilization, allowing animation render times to be reduced by up to 40x! Check out the YouTube introduction video to find out more:

Turbo Comp – A full compositor suite with real-time playback and compositing directly in the compositor backdrop, branch caching, resaving of file output nodes without re-rendering, automatic file output node creation, publishing and lots more.
In difficult to render scenes (indoor scenes, volumes, scenes containing glossy materials with detailed textures, SSS, etc) Turbo Render provides results that OIDN/Optix could require you to render up to 120x longer in order to match Turbo Render’s results. When no denoiser is used you could expect to render up to 960x longer to achieve the same results produced by Turbo Render (scene dependant). Additionally it simplifies the entire rendering process thanks to render setting pre-sets designed to help you get the result you need without diving into the complex render settings. It even works with complex compositing setups without the need to do any rewiring yourself! The results are remarkable as can be seen below.

Classroom scene using the new draft mode. Total render time (including denoising) was under 17 seconds on a gtx1070 with an i7-7700k !!!!!!!!

The following tests were created using cycles X in blender 3.1. To give OIDN and Optix the best possible chance, they were set to use albedo and normals to assist with the denoising process. OIDN had Prefilter set to Accurate, and I also tried setting prefilter to NONE to see if it would improve the texture comparison results (it didn’t).

Scene 1 – heavy DOF , strong SSS, film set to transparent to test alpha.
Click here to download test scene 1

Test scene 2 Available from the shop.

Turbo render is able to maintain reflection clarity at extremely low samples. OIDN required over 4 minutes of rendering to achieve a similar quality.

The image is rendered with film set to transparent to produce an alpha channel. The white background (top of the image) is then added in the compositor to highlight the difference in quality. OIDN required a 4 min render to get close to Turbo Render’s 10 second render result, but there was still visible noise (video to follow)

Scene 2 – Indoor scene to test geometry detail and texture detail.

Above we can see that even after 30 minutes of rendering, OIDN is still unable to retain as much texture detail as Turbo Render can at on 1 min!

Even with a 15 second render, that’s a whopping 120x faster than the 30 min render used by OIDN, Turbo Render can still maintain texture detail using it’s ‘Enhanced Textures’ option:

Above we can see that the bottom of the cupboard area is getting quite badly mangled up by OIDN and even worse with OPTIX. This is because denoisers can struggle with dark edges of geometry that meet with shadows due to a lack of contrast. Turbo Render can achieve much better results using it’s ‘slow (all passes mode), even at very low samples (as shown above bottom right).

Below shows that even when rendering at 1 min per frame (240x less time per frame than the ground truth 4 hours per frame), we can still get excellent results without any noticeable flicker. To do this with OIDN and maintain the same geometry, texture and reflection detail we’d need to render at 30 mins per frame (as can be seen in the above texture comparison still image examples, and youtube video examples at ).

Notice how turbo render (on the right) has vastly superior image quality when compared to OIDN (left). The most noticeable improvements in this image are the crisp shadows on the notice board and the clarity of the reflections under the desk.

The UI is very simple to understand, and offers options to ensure the best possible results for any scene and sample settings.

It’s extremely important to understand that Turbo Render can only provide a speed up if the samples are set lower than when you weren’t using Turbo Render. This is because Turbo Render provides a speed up by being able to produce high quality results from renders that are too noisy for the denoisers in the render panel to produce high quality results from. So take the samples as low as possible without reducing image quality, either by using the sample pre-sets, or using the ‘user’ sample pre-set mode which allows you to enter the sample setting manually.

It’s also important to understand that the biggest gains (often several hours) are to be had on renders that take a long time when not using Turbo Render. Scenes that already render quickly (under a minute or two) can’t be reduced as significantly. For scenes that already render quickly it’s advisable to use the ‘fast/draft’ denoise mode unless you notice wobbly geometry, or if you need to work with the individually denoised passes in the compositor after rendering). Here’s a video explaining the draft/fast mode usage:

Turbo Render is designed with ease of use being a top priority. In the Turbo Render Options area, simply click enable, choose a sample preset to automatically set up the sample settings to the desired quality, choose the cleaning mode (combined image or clean passes), tell it what’s in the scene, and render. That’s it! Turbo render will then analyse the scene and other render settings to produce the final render. IMPORTANT ensure a default project cache folder for new scenes is specified in the addon preferences, and that each scene has a valid cache folder set prior to rendering. The scene’s cache folder can be set at the bottom of the Turbo Render options, or in the compositor’s N panel turbo tab. If you the ‘User’ sample pre-set, then to achieve the biggest speed gains, you should reduce your samples below what you would usually need. Turbo Render is so fast because it’s able to produce clean images from noisier render results than other denoisers can. The cache folder must not be a relative path (a path that starts with ‘//’), so when setting it, make sure you uncheck the relative option in the Blender file explorer as shown below:

Turbo Render is compatible with:

Still renders
Existing compositor trees
Rendering of multiple scenes and view layers from a single compositor (all scenes will use their own Turbo render settings).
All Turbo Comp features (caching, publishing, resaving file output nodes without re-rendering etc)
Denoising Modes –

Draft (clean image pass only) – The new draft mode offers extremely fast denoising, and when combined with the ‘enhance textures’ option will provide results that could be considered to far surpass what would be expected of a draft render, even at extremely low samples. Also suitable for renders which render to a denoisable level in under 10 seconds, thanks to it’s fast processing times.
Medium (clean image pass only) – The medium option is slightly slower than Draft, but on noisier images will offer better all round detail, particularly in reflections.
High (clean image pass only) – The high mode will offer the best lighting, shadows and reflections of all but the ultra mode. This is suitable for final renders where the individually denoised passes aren’t needed for compositing.
Ultra(cleans all necessary passes)- This will clean individual passes for use in the compositor afterwards, and can also be used to resolve any geometry wobbliness present in lower pre-sets. The passes which are cleaned is decided by scene content and render settings. This mode can also be used if the other modes are not producing good geometry detail. IMPORTANT – If you intend to use the individually cleaned passes in a 3rd party compositor, you can either use the render layer cache exr’s found in the cache folder you set, or if you prefer another format, you can set up a file output node directly from the render layer node. Blender’s output can be set to something light such as a ffmpeg because it’s only able to output the denoise image pass, not the other denoised passes. If your passes include data passes such as cryptomattes, it’s advisable to use EXR 32 bit.

Cycles Speedup Options –

Optimise HDRI – This will optimise the importance map, leading to potentially faster renders and less RAM usage. The improvement will be most noticeable with HDRI world environments which are 8k or above, and will reduce memory consumption during rendering by around 1GB for a 16k HDRI.
Prevent Fireflies – Recommended. This will reduce the chance of fireflies and also provide a potentially massive render time reduction (scene dependant). 

Downloads: show love to dev by purchasing if you can afford it



Official Discord :

Recommended link below => FULL SPEED.


for mega and g drive links – contact admin.

4 Replies to “Blender 2.9+ Turbo Tools V3 – Turbo Render v3.0.5 Crack Download”

Leave a Reply

Your email address will not be published. Required fields are marked *