Tweet
I reckon it's more that they want to do things right rather than caring about finishing something. Splutterfish made the mistake of putting a definite release date on brazil 1.0 which they missed by quite a bit, they won't make that mistake again by not announcing a final date for brazil 2.0. Next limit shot themselves in the foot by releasing stuff that didn't work as rc and beta setups - they really didn't care about their users and released a so called 1.0 which most people seem to think still doesnt work and is far worse than the beta.
Chaos care more about their users than most companies I've dealt with. 1.47.03 is a really stable production worthy release (admittedly one or two quirks but minor ones) that I absolutely hammered rendering the milk ads in. It used every single feature that was in 1.47 (features like displacement and 3d motion blur that still aren't in brazil) and it did it without falling over. Recently I had an issue on a job where I needed a patch release for vray to render pflow ojects with 3d motion blur. I dropped Vlado a mail and he had a build to me the next day that solved that problem and got me through. I found one or two other bugs in it such as rendering refractive objects which you can see in my fog tutorial:
The black in the refractions is a bug in the release that I was using when I wrote that tutorial and I figured out that the problem wasn't in 1.47.03. Personally working refractions are far more commonly used by me than particles so I switched back to 1.47.03 as the standard build that our company uses. The irritating thing about doing this type of software is as you fix something you break something else so if you take my case vlado gave me a build where my particles worked fine but my refractions didn't - wouldnt it be a huge pain in the ass to try and remember which features you need to render a scene without error and have to sintall the vray beta build which corresponded with it? If Vlado kept releasing updated builds every month or two purely to keep us amused it'd mean loads of scene files floating around that could be broken in the very next build of vray that arrived which is a bad thing for the end user.
I saw a lot of this stuff using the beta of Arnold a few years back where the brightness of renders would change between builds, features would stop working and materials would look completely different. First of all it meant that if we needed to re visit an old scene it'd take us time to either reinstall the old plugins or figure out how to make renders in the new builds look like renders from the old builds and it was a huge pain in the arse from a production point of view. you know well enough if you have a deadline you want something that is as reliable as possible and at the moment Vlado believes that is 1.47.03 hence why it's still up on the download section. Admittedly there's a few nice bits and pieces in the newer builds that may save some time in the future but not at the expense of haveing predictable results imo.
I'm sure that Vlados as annoyed as anyone else about not having 1.5 out yet but I think he has the best interests of his customers in releasing somethign that meets his own standards rather than doing a next limit on it and going on holidays...
Chaos care more about their users than most companies I've dealt with. 1.47.03 is a really stable production worthy release (admittedly one or two quirks but minor ones) that I absolutely hammered rendering the milk ads in. It used every single feature that was in 1.47 (features like displacement and 3d motion blur that still aren't in brazil) and it did it without falling over. Recently I had an issue on a job where I needed a patch release for vray to render pflow ojects with 3d motion blur. I dropped Vlado a mail and he had a build to me the next day that solved that problem and got me through. I found one or two other bugs in it such as rendering refractive objects which you can see in my fog tutorial:
The black in the refractions is a bug in the release that I was using when I wrote that tutorial and I figured out that the problem wasn't in 1.47.03. Personally working refractions are far more commonly used by me than particles so I switched back to 1.47.03 as the standard build that our company uses. The irritating thing about doing this type of software is as you fix something you break something else so if you take my case vlado gave me a build where my particles worked fine but my refractions didn't - wouldnt it be a huge pain in the ass to try and remember which features you need to render a scene without error and have to sintall the vray beta build which corresponded with it? If Vlado kept releasing updated builds every month or two purely to keep us amused it'd mean loads of scene files floating around that could be broken in the very next build of vray that arrived which is a bad thing for the end user.
I saw a lot of this stuff using the beta of Arnold a few years back where the brightness of renders would change between builds, features would stop working and materials would look completely different. First of all it meant that if we needed to re visit an old scene it'd take us time to either reinstall the old plugins or figure out how to make renders in the new builds look like renders from the old builds and it was a huge pain in the arse from a production point of view. you know well enough if you have a deadline you want something that is as reliable as possible and at the moment Vlado believes that is 1.47.03 hence why it's still up on the download section. Admittedly there's a few nice bits and pieces in the newer builds that may save some time in the future but not at the expense of haveing predictable results imo.
I'm sure that Vlados as annoyed as anyone else about not having 1.5 out yet but I think he has the best interests of his customers in releasing somethign that meets his own standards rather than doing a next limit on it and going on holidays...
Comment