I remember a million years ago when Mac switched from os9 to osx. I was getting something mastered. I asked the engineer if he was going to install it. He said “why would I do that? Everything works”
As a VFX artist I had the opportunity to work for a famous studio, at their new branch in my city. So while most of the pipeline being implemented came from the main office, there was the opportunity to do and implement new ideas at this new branch. So half way through the 1st show, it was decided that they would do a company wide upgrade to the latest version of the software that most artists used, which was tested only on the animation department where it worked well.... except that once it was roll out across all the departments, most of them were running into lots of issues with the company tools and in some cases roadblocks where you couldn't even publish work. So they had to revert back to the older version and then do what is an industry standard where they have different variations of a software that would load with the specific tools needed for each particular show and department. That way the animation dept benefited from the new tools and faster response of the new update while the rest were working on the previous version that did work with all the tools needed to complete the show. The big studios do get the latest and greatest even weeks prior to the official release of certain software's, but it has to go through a phase of testing to ensure changes on the code would still work correctly with the existing tools. I found that most small studios tend to be running always on the latest versions of almost everything, likely their testing phase for migrating doesn't take as long as they likely don't have to deal with lots of legacy tools dating back to 15+ years.
I work as an editor/visual/bim manager in an architecture firm. Some jobs last several years. For larger scale buildings, we only switch to a new version if the feature is fast and stable. Since we have several people working on a project at the same time (archicad teamworks/bimcloud), it is not easy to switch. We have to test everything, if something doesn't work it can be a serious financial loss. ~1 year after the release of the new version because we have to create new templates, training for colleagues, etc.
I'm freelancing atm, it is a nightmare... I have archicad 22-27 installed because of various long-lasting projects (COVID and the current economic situation makes projects drag, being refinanced, altered, cancelled, restarted, argh), even different builds because one company uses this, another that. Instead of worrying on solving design issues and getting the construction details right, more and more time is being spent on battling with software. By the time one release gets stable enough, it is time to upgrade your template to the next version. -.- Right now we are debating whether to keep a currently on-hold project on 26 (attribute management is a disaster) or do the leap of faith with 27 being out for quite a while now, although it has known regressions (MEP) which we possibly won't need, but has design options and the "old" attribute manager again. TL;DR: annual releases have become cancer in the AEC industry as well...
Another point to note: in any level of film production, an unexpected cost can literally end a production or even the studio itself, overnight. That means at least dozens of people won't get paid. Hidden costs are poison in the film industry, that's why everything needs to be clearly and transparently planned and calculated for, meticulously. If you're relying on software like, say, Unreal Engine and the company suddenly decides that you will now need to pay a monthly license per user (as they've just done), that can be CRIPPLING for even a successful VFX Studio. The reliability of the software company in question is just as important as the reliability of the software itself - HENCE so many companies now create and use their OWN proprietary in-house software.
Thanks for the info. Once upon a time I planned to make some movie/video with some VFX, and once in a while I thought how does some studios(atleast bigger than being solo) think and plan. I hope u sort it out soon. I think there's some reddit/forum if not discord where people with similar path gather.
Seens like only small studio can afford to use newest version of those soft at small risk on small project actually. I personaly used unreal 4.12 for years before in company with small project actually knowing the 4.18 was there with update and later 4.20 but just because of the same risky thinks everywhere else, pipeline and plug-in in most case we used what we have that was looking old. Thanks for sharing again🔥
In the studio, we are forced to use new versions of some of our main packages due to subscription modes. It always, no exceptions, breaks pipelines, breaks workflows and costs enormous amounts of money, because certain companies NEVER EVER alpha-beta-rc test their software. They just roll it out and let us suffer. You sometimes have to use all your leverage to force software companies to provide you with NON-recent versions JUST to get the job done.
Often, when new features comes to CG software I'm waaay too eager to want to utilize it with dreams of a massive time saving bit of code, but more often than not it doesn't work under certain conditions and you are the only one who pushed it too far and suddenly you are trying to drive a vehicle that lost its wheels.
This kind of Applies to all VFX Studios. Every VFX studios that knows what they are doing both in indie and large studios knows that you shoudn't switch from old version they started a production with, to recently released version immediately.
A changed label or node can be a massive pain in the ass to deal with. From version 1 require to 6 nodes to do a direct basic simulation to the new release requiring 5 with a feature you specifically need being in a node you would've never guess to try. Now imagine its not just 1 node but 2-3 of them. That's the type of shit that would have you thinking you might need to look up keyboard prices. Add-ons not working in the new version that automated some of the things you did now you really have to learn how to do it from scratch.
For instance when the Foundry changed the channel text display expression code from [value in] to [value in1], then you update and everything looks different.
6:55 rigging and animation always happen in the same software, that claim makes no sense, if they update it all of them will, and then simulations are baked before exporting into the rendering software, so it's not bcs of "algorithms and stuff", but for other reasons, meaning that claim makes no sense too, I find this video a bit dishonest tbh
Dude, you do not need to make any videos on this topic. It is simple Studios and production environment has a lot of scripting and hardcore pipeline for years so they can do work in a streamline
but this subscription model force you psychologically to run the latest update and companies want that you send bug fixes for them. if that is the case then i think why not use opensource software and send bug fix there, even the software will mature day by day and you dont have to pay for license. i think microsoft realize this game that future of coding is open-source and they smartly make purchase of Github even it is open-source. after covid, open-source projects are really taking off and it is just the time that will dictate.
What do you mean they don't?? ILM and that New Zealand studio do it all the time!! Half of them sit on corridor crew's couch every saturday and discuss new technology on new movies. Video game studios themselves do it all the time.
Coz the industry is fascist and paranoia that's why they need some kind of proof what the latest technology can bring. Good example is 2012 the movie, the story is shit coz it's made to promote the tech and the movie magic same like animal movie that just show off the fur effect while the story is crap and yes they need sponsors or endorsement for the new product, you don't destroy your old habit while you have to pay for the new habit.
