<?xml version="1.0" encoding="UTF-8"?><rss 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" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Daniel S. Lima on Medium]]></title>
        <description><![CDATA[Stories by Daniel S. Lima on Medium]]></description>
        <link>https://medium.com/@daniel3d?source=rss-bc1f470770f5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*fL6k3vUlEo7ACY4Ro3HKag.jpeg</url>
            <title>Stories by Daniel S. Lima on Medium</title>
            <link>https://medium.com/@daniel3d?source=rss-bc1f470770f5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 01:36:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@daniel3d/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[ChopRig System]]></title>
            <link>https://medium.com/blue-sky-tech-blog/choprig-system-b11d4c1e252c?source=rss-bc1f470770f5------2</link>
            <guid isPermaLink="false">https://medium.com/p/b11d4c1e252c</guid>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Daniel S. Lima]]></dc:creator>
            <pubDate>Fri, 10 Aug 2018 19:22:50 GMT</pubDate>
            <atom:updated>2018-08-11T14:04:58.297Z</atom:updated>
            <content:encoded><![CDATA[<p>The process of converting our current character rigs into a multi-threaded solution was one of the most significant challenges that Blue Sky Studios has had to face in recent years. Our goal was to find a solution to deliver our current rigs at a minimum evaluation speed of 24 fps. This solution also needed to be accomplished without compromising the actual rig mechanics or deformation quality of our assets. In the end, the optimization was designed to not hamper the standard rigging workflow or any other department’s standard pipeline processes.</p><p>Our goal was to update our rigging system in Maya® for parallel rig valuation and to maximize the multi-core capabilities of our current desktop architecture. Even though many of the deformers used in our characters were already internally multi-threaded, rigs did not meet our performance targets. This indicated to us that we needed to take a higher level approach to solve the problem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/468/1*nfvsynUhHURY0TR2k6rGLg.png" /><figcaption>ChopRig Pipeline Process. It represents the average character’s performance in FPS Before and After the usage of the chopRig. It also shows the average independent deformer stacks on each chopped piece.</figcaption></figure><h3><strong>The Solution</strong></h3><p>The solution came with the creation of our ChopRig system, which breaks up the work in the rig so more tasks can be scheduled in parallel by the evaluation manager in Maya®. Instead of handing the entire geometry and its deformer stack to the scheduler all at once, we pre-separate the main geometry of the character, transferring the necessary portion of each deformer to each chopped piece. The final deformation of the pieces drove a combined mesh, using our proprietary “SubDeform” plugin, which was designed to be a lightweight evaluation. Doing this allows the scheduler to play a more significant role in load balancing all evaluation tasks across all cores in the machine. The gains were profound, giving us the interactive performance we desired.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SLuNz4WZegMcd6wDt_GazQ.jpeg" /><figcaption>A. The original deformer stack performance as is — B. Multiple independent geometries with its own independent deformer stacks being evaluated in parallel — C. The original body geometry driven by multiple ones with its own independent deformer stack using our proprietary “SubDeform“ plugin. Each color represents a geometry with an independent deformer stack.</figcaption></figure><p>The ChopRig system uses a simple external data format, called DataCut, which is created by the rigger and consists of a pre-selection of edge loops. These edge loops represent where chops should occur in the character geometry. The chop lines can be placed anywhere in character, allowing us to configure the cuts in any way for different performance needs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/927/1*oeo7blsZQI1MNY_gX6k3jA.jpeg" /><figcaption>DataCut set to chop the character’s geometry in half. This configuration will allow the computation of the left and right side in parallel.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/637/1*s7x_dnXCmRbKZild2GoIwA.png" /><figcaption>This image shows an example of a deformer’s weight map painted only at the region of the character’s face. This way tells the ChopRig system to automatically transfer this particular deformer only to the respective points that belong to the proper chopped geometry, in this case, the chopHead geometry.</figcaption></figure><h3>How it Works</h3><p>After the rig is shipped to production, the ChopRig automatically splits the geometry using the DataCut, previously created by the Rigger. Then it transfers deformer nodes to each piece.</p><p>During the transfer, it scans the blendShape deltas and weight map influence of each character’s original deformer on each vertex and then only transfers what is relevant to the designated chopped geometry piece.</p><p>At the end of the ChopRig process, the system collects every chopped piece and uses these meshes to drive a copy of the original character’s mesh. This way we keep the final character topology consistent and entirely compatible with what Materials and Fur department have in hands.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OGJG0fKSca-7TIKMRCwZVw.png" /><figcaption>Different chop configuration. Each color represents a geometry with an independent deformer stack.</figcaption></figure><h3>Conclusion</h3><p>The ChopRig process allowed us to meet a performance target of<br>evaluating character rigs for animation at interactive speeds above<br>24 fps. This solution has proven flexible and easily applied to all<br>kinds of character types. Our solution did not require a re-write of<br>our rigging system to accomplish our goals, and we were able to<br>test and deploy this new system during our character development<br>schedule. To the downstream departments our process was seam-<br>less, and fit right into the pipeline. In addition to achieving real-time<br>performance with our rigs, the ChopRig technology allowed the<br>animation department to develop a new set of workflows for shot<br>animation and asset visualization</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b11d4c1e252c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/blue-sky-tech-blog/choprig-system-b11d4c1e252c">ChopRig System</a> was originally published in <a href="https://medium.com/blue-sky-tech-blog">Blue Sky Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>