– 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 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 kommentar(er)
