Maxer wrote:I'm sorry but if NL does release V1.0 full of bugs they are going to get a verbal lashing like they did when RC1 was released except I expect it to be much worse.
I guess I'll be bending my promise somewhat by making these few statments but que sera.
Even if Maxwell is release without any bugs (which in the computer programming world is like coding nirvana), NL has admitted that they're going to back off of having certain feature available until version 2.0. So in a sense, V1.0 is going to fall short of the promised capabilities for those of us who bought into MR very early on.
However, I do see even RC5 being a vast improvement for somethings. It has already proven itself as a viable renderer (notwithstanding speed) for product design and engineering (and maybe even rapid prototyping which I know is a stretch given the current core's speed). So it has it's uses in this regard.
For architectural visualization purposes, maxwell will be 'usable' however, it seems that there is still going to be a heavy dose of post production work needed for noise removal and compositing caustics through glass (1 render with glass + 1 without = maxwell archviz). So in a way, it's not as unbiased, as I'm sure it is still being touted to be.
With that being said, for me, Maxwell is going to be simply an alternative or option for whatever project requirements I may have. I'm not going to rely on it so heavily that anything short of nirvana will cause me to storm the castle doors nor am I going to completely dismiss it because like everyone else this is an investment in my professional career (NOTE: not putting word in or defining anyone opinion or approach on this matter, just stating my own).
All we can do I guess, is adapt and adjust. Maxwell at this point is simply going to be an alternate method, sometimes better, sometimes worse, good for somethings and bad for others. Yet isn't this true of almost all software?
So if MRV.10 falls short of it's promises all I can say is roll with the punch.
