Escape studios renderman courseware1/10/2024 I hope that this insight helps you understand the importance and raison d’être of the VFX Reference Platform as well as the consequences of your decision. I have started to train on your software a bit before this announcement, hoping to find a position in a studio using it, but I’m not too confident now seeing that your decision impacts pipeline development, I don’t think many studios will be willing to take the risk of having to revise a working pipeline every few years, with all the financial implications it means, to be able to benefit of the latest improvements of Blender. So yes, like many people have already said, this decision is unfortunately throwing a spanner into the further adoption and deployment of Blender in studios, which I think is the opposite of what you would like to see. That’s the reason why the VFX Reference Platform is important and should be followed. No studio wants to go through this kind of thing every few years, as well as having different DCCs requiring different Python versions because it becomes a nightmare to manage. I’m sure there are still a lot of studios out there which haven’t started this transition and will do it when they will be cornered. Production budgets don’t account for these kind of things, it is an investment done by the studio (no producer wants to see the show’s budget go into something that won’t be seen on screen or won’t help artists). To summarise, that’s a lot of organisation, work, time and money spent. – Deployment has to be done with extreme caution as you want to disturb productions as little as possible, for shows that are running full steam you just don’t transition them as it is too risky. – Thousands of in-house scripts that have to be modified and tested. – Thousands and thousands of dependencies that have to be checked to make sure they have a compatible version, find an alternative if not and adapt where needed. I can describe roughly what it means to switch from two python versions which are not compatible for a studio: The last company I worked for was Animal Logic, I was there during the time when the studio transitioned from Python2.7 to Python3.7, and left before it was finished. I’m a pipeline TD with 10+ years of experience in the industry, worked on animation and hybrid features. This decision was made considering the arguments presented in the bf-committers list, besides a meeting with the Blender admins and Foundation chairman Ton Roosendaal. We are still committed to preserve file format compatibility and to avoid library conflicts for integrations with binary add-ons. With that in mind, the decision was made that Blender will no longer stick to the VFX Reference Platform.įor the Blender community and eco-system as a whole it is more important to be able to use the latest Python versions and other libraries. We’d be happy to collect useful information for studios on for it and welcome their contributions. We are aware that not following the VFX reference platform generates friction for developing add-ons and integration in studios pipelines. Contrary to that, for us it was perceived as a limitation with users lacking benefits such as the latest Python version in Blender. It will facilitate the industry to contribute to Blender.ĭuring the past two years there was little evidence of any of those outcomes.It will help adopting Blender in a big studio environment.When it was decided that Blender would follow the VFX Reference Platform, there were a couple of assumptions made: Nexus VI by Fensch Toast, VFX by Romain Toumi.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |