<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>Co-Creating 3D Data Animations With Code — BCON26</title>
        <link>https://video.blender.org/videos/watch/5bc7112a-09a8-43e6-b561-b3a294f9e1eb</link>
        <description>"Co-Creating 3D Data Animations With Code" by Neele Dijkstra, Torben Hanegraaf, Jop van Roosmalen at Blender Conference 2026 In this talk, we (five data animation developers from Rijkswaterstaat) showcase how we used Blender to create our informative video "The Dutch Rivers" and the novel process we used in generating it. We used a fully code-based workflow that integrates with Git version control. This means that co-creating in Blender is easier, it is faster to go from water data to animation, and animations can readily be regenerated on the basis of new data. We'll show you how to adopt a code-based workflow that still takes advantage of Blender's strengths and combines keyframe animation with custom callback animations to improve efficiency. – Learn more about Blender Conference 2026 at https://conference.blender.org/2026/</description>
        <lastBuildDate>Thu, 24 Sep 2026 16:39:35 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>PeerTube - https://video.blender.org</generator>
        <image>
            <title>Co-Creating 3D Data Animations With Code — BCON26</title>
            <url>https://video.blender.org/lazy-static/avatars/83e44c73-9c22-453c-a454-c4efe225fd4d.png</url>
            <link>https://video.blender.org/videos/watch/5bc7112a-09a8-43e6-b561-b3a294f9e1eb</link>
        </image>
        <copyright>All rights reserved, unless otherwise specified in the terms specified at https://video.blender.org/about and potential licenses granted by each content's rightholder.</copyright>
        <atom:link href="https://video.blender.org/feeds/video-comments.xml?videoId=5bc7112a-09a8-43e6-b561-b3a294f9e1eb" rel="self" type="application/rss+xml"/>
        <item>
            <title><![CDATA[Co-Creating 3D Data Animations With Code — BCON26 - jns]]></title>
            <link>https://video.blender.org/w/ckjvRPQY6Ld8K9ML1nUwAg;threadId=12559</link>
            <guid>https://video.blender.org/w/ckjvRPQY6Ld8K9ML1nUwAg;threadId=12559</guid>
            <pubDate>Wed, 23 Sep 2026 15:51:24 GMT</pubDate>
            <content:encoded><![CDATA[<p><span><a href="https://video.blender.org/a/blender/video-channels" class="u-url mention" target="_blank" rel="noopener noreferrer">@<span>blender</span></a></span> </p><p>This was an interesting video - I had no idea lakes could have tilt :) - the plugin which converts a node tree to python looks quite useful. </p><p>There's a few important details in this video which I hope the blender team takes to heart:</p><p>1) They had to add code to restart blender when it crashes - this mirrors my experience as well, I found it getting less and less stable with every release.</p><p>I wish blender would just slow way way way down, stop adding features for a while, and only focus on tech-debt and bugfixes.</p><p>2) They commented the python docs were poor and speculated it gets little use - </p><p>That's not quite true, blender python gets a lot of use - but more use within the plugin ecosystem, and less so these days with big projects like this.  -   I have tried using blender python in the past for large projects and got burned by the fact that it's very much a moving target. - Breaking changes between major versions can completely cripple a large complex project like this, and that's rather disheartening. Keeping up with breaking changes is exhausting in something like this, especially when you've got a small team. </p><p>This again is an argument for blender to slow the heck down, document things properly, be more considerate when functions are deprecated. It should be avoided, and when it happens it should be well announced and documented.</p><p>(also please keep llm slop away from the project, it will only amplify these issues)</p>]]></content:encoded>
            <dc:creator>jns</dc:creator>
        </item>
    </channel>
</rss>