I would also like to thank Jeremy. Until the middle of the twenty-tens serious rendering was an extremely complex artform, it generally meant fiddling with countless esoteric settings with no real world equivalents. What worked on one scene or camera angle likely failed in closely related scenarios. Computer power was a limiting factor, one needed to cheat and cut corners practically everywhere. CAD users couldn’t create their images inside their Nurbs modeller, one needed to export meshes to 3DSMax, Maya and such, to at all get access to the good stuff.
Maxwell, which appeared in Beta in 2004 worked like a physical camera. The first published test images blew me a away and best of all: One could recreate them – the engine worked reliably for anyone with a basic understanding of photography. And for more than a decade it was JD who made this Tech accessible directly inside Rhino.
The quality of Plug-Ins is often measured by its fit to the concepts of the host-application: The closer, the better. I applaud Jeremy for not even trying to take this route – the Rhino eco-system at that time clearly wasn’t – and I have to say – still isn’t quite there. JD’s Maxwell Plug-In was a complete new development and it had things to offer which simply weren’t doable with native means. Maxwell ran in a separate process from the beginning – rendering therefore never blocked further editing. All Maxwell Editors were non modal and drag and drop-aware a decade ago. Changing the tiling of maps in a dozen slots in four different layers in one go? No problem at all. Slick, time saving features of this kind made his tool a joy to use.
Thank you + All the best Jeremy – we are already curious what you have got under your sleeve for Rhino :o)