Hey guys, quick heads up, thereās currently a Blender bug preventing the transmission passes from being populated when the principled BSDF shader has transmission weight and the new āthin wallā option enabled. This results in glass appearing dark when the final render is rebuilt from passes (which is what Turbo does)
In the meantime, you can replicate the thin walled glass by setting the materialās IOR to 1, and then setting the coat weight to 1 as shown below. Left glass uses the new āthin wallā option, right glass is using the IOR 1 + coat weight method:
hi! longtime user of the addon here. was just wondering if there are any plans for video sequence editor support in the future? and any tips/workarounds for being able to stitch together multiple different scenes? currently just going to render out my scenes totally separate because I just canāt live without this addon.
Morning Xhao. Glad to hear you still canāt live without the addon The VSEās scene switching capabilities donāt play nicely with the compositor unfortunately, particularly when python stability is concerned. So I only use it for adding audio. If I need to render multiple scenes, I just create a render layer node for each in the compositor of the scene Iām rendering from, and that will render them allā¦but it will render all scenes for the entire frame range. If I want to render the sceneās sequentially, then I either manually launch them, or I use a bat file in combination with the command line rendering instructions I provide in the user manual
For anybody wanting to try Turbo Tools at a lower cost, Turbo Tools V4 is now 80% cheaper, and shares the same features (limited to Blender 4.53 and below). The V4 cost will be removed from Turbo X when you update using 20% discount code: ttv4upgrade (only valid for Turbo V4 owners)
To test properly, be sure to follow along with the videos in the quick start guide using the linked scene files. The quick start guide will be in your downloads folder
Hey guys. Quick heads up regarding Blender 5.3 Alpha. Iām working on a big update to support the new compositor effects stack in the properties panel. You can still use Turbo Tools X with 5.3Alpha before I release the update, but youāll need to do a few things:
In the top level compositor effect (which now acts as the main top level compositor tree for the current scene), youāll need to ensure the group input node is replaced with a render layers node, because the group input node doesnāt expose the required passes, it just gets the cycles combined image pass.
when publishing or playing back in the compositor, ensure all group input nodes are replaced with render layer nodes to prevent the 3d scene being computed and rendered.
All render layer nodes you want denoising or stabilising, must be in the top effect in the compositor effect stack, because effects can only output and receive a single colour image, so thereās no way to route the pass data through the effect stack. You can use them elsewhere, they just wonāt be denoised, stabilised, or cached.
Iāll get all this automated before 5.3 is officially released, and also add some new features
Quick test render from one of the simulations in my upcoming simulation course. Using only 16 samples with Turbo Tools X in Blender 5.3 Alpha! Between 4 and 10 seconds per frame on a 4080 Super. Extremely satisfying on loop!
I imagine the legendary Blender developers will fix it pretty rapidly, but until then, when using the publish feature, be careful to not move the mouse over the compositor node editor, otherwise Blender will crash instantly. Generally itās pointless moving the mouse over the node editor during publishing anyway, because the addon locks the UI until publishing completes, so it canāt be interacted with. Moving it anywhere else is fine though, so you can still zoom in and out in the image editor if you want to get a closer look at the interactive flicker removal during publishing (in case you want to cancel, tweak some settings and restart, etc). Playback and rendering arenāt affected
The VSEās scene switching capabilities donāt play nicely with the compositor unfortunately, particularly when python stability is concerned. So I only use it for adding audio. If I need to render multiple scenes, I just create a render layer node for each in the compositor of the scene Iām rendering from, and that will render them allā¦but it will render all scenes for the entire frame range. If I want to render the sceneās sequentially, then I either manually launch them, or I use a bat file in combination with the command line rendering instructions I provide in the user manual 
