Iron Sky – Day 84
Yeah. I’m still having issues with Ozone, turns out that one of the bug fixes I was sent wasn’t part of the installer used to put ozone on one of the other machines to do render tests. That in turn confused ozones “core” (why is it that everyone wanted to call their apps core for a while? its a stupid name/idea as we have seen – its not sexy, I don’t care what marketing says. HardCore (porn), C4D CORE (rotten to the core?) all come to mind when I hear it) installation on the local system and thus fails as it does some kind of version check before rendering. What a bad way to do a plug-in – like really… do you need all that extra gack? A render node certainly doesn’t. All of this garbage is so they can protect the software, rather than make it faster, work better or hell, be cheaper or easier to install. E-On totally fails in my book on that count. Oh but there is more. On the one box that I can get it to run on which is my workstation here at Iron Sky, a 1280×960 resolution frame with no AA of a Spectral sky at night with some poofy clouds wants almost an hour to render per frame. 640×480? Oh, only about 10 minutes. Per frame – and no AA whatsoever, no motion blur, nothing. DIRT SLOW. And this box is no slacker. It’s 12 threads, i7 980 or something with 24GB of DDR3 doomsday ram. I think Ozone4 and even 3 rendered faster 3 years ago on the AMD phenom 9750 boxes I had at Front Street working on LTOTGC and Fireball. It’s just stupid how slow Ozone’s rendering is. I can’t even imagine how silly slow Vue is with a full eco-system. Brutal. Anyway, enough complaining for a moment. Let’s talk siggraph! NewTek obviously didn’t have a booth but Kiko did manage to chat with Rob Powers about why the lack of a foot print presence. It basically comes down to “is it really worth it”. I was under the impression NT wasn’t going to be there at all, but apparently several people from NT are there and doing the rounds quietly with studios, and users – building up to something much larger than what siggraph in vancouver could contain I think. I haven’t a clue what that really is, but I can guess. I won’t do that here though because too many people on the NT forums are speculating wildly – some even suggesting NT is going to sell LW (never happen, trust me) to Autodesk or some other company. Like come on…. no. Even if they wanted to I think that boat sailed a while back. My main concern right now for LightWave’s future is getting more good solid reliable people up to speed on the software in production environments so that I can crew up for shows like Iron Sky quickly and know we have a good roster of talent to choose from. Things are only going to get busier for LightWave artists who really know the application and have the knowledge of how it works in production work flows because it’s become clearer to people now that used to scoff at LightWave that it really is a very very solid tool and not only that, a cost savings one from both actual purchasing to the fact that you can do more with less people or way more faster with the same amount of people if they are using LightWAve and your going to get predictable results. It’s that simple. And thats where things are today for me. Back later. I have clouds to fight with. Among other volumetric stuff (which I am not fighting with and getting amazing results out of LightWave natively). Cheers. PS the wild boar wasn’t all that great and certainly not for 12 euros or whatever it cost me. Brutal.
« Iron Sky – Day 83 (Previous News)
(Next News) Lightwave Plugin of the Week: AE Link »