Op Find DAT is a hidden gem in TouchDesigner. While simple in concept, it can be tricky for users the implement it effectively in their projects. How do the callbacks work? How do the filters work? How do I add custom columns?
Notch's root node can confuse new users. It's both the central node but it's also your active render context. What happens when you want to quickly render another texture in the background and use it as a mask, displacement map, or material texture?
TouchDesigner is always growing in its Python capabilities. Whether it’s the newer and shinier, like OpenCV and Script TOP, or more under the hood features like optimized expressions. One TouchDesigner Python feature that has been missed by many TouchDesigner developers is the tdu module.
Picking up where we left off in part 1, we dive deeper into Zig Sim Pro and look at the capabilities it has when it comes to it's depth sensor and ARkit features.
It’s always a great time of year when a big TouchDesigner release is dropped. Over the years we’re seeing a change of pace in development from a constant flow of new features appearing in the stable branch towards a bigger stable release happening while new features get tested in experimental.
We have full-on super computers in our pockets. The latest iPhones have everything from built in AR, depth cameras, facial tracking, marker tracking, and a smorgasbord of sensors like gyroscopes, accelerometers, and more.
There are so many operators in TouchDesigner it can be hard to learn every single one. So many handy operators go un-used by newer users just because they're a bit more obscure or the operators were only recently released.