{"id":1711,"date":"2017-03-25T13:15:40","date_gmt":"2017-03-25T13:15:40","guid":{"rendered":"http:\/\/avastar.online\/?page_id=1711"},"modified":"2022-05-12T20:53:24","modified_gmt":"2022-05-12T20:53:24","slug":"update","status":"publish","type":"page","link":"https:\/\/avalab.org\/avastar\/293\/help\/n-panel\/avastar\/rig-inspector\/rig-update-tool\/update\/","title":{"rendered":"Update"},"content":{"rendered":"<div class=\"row-fluid\">\n<div class=\"rhcol span10\">\n<h2><image src=\"\/avastar\/292\/wp-content\/uploads\/2019\/08\/approve_logo_280.png\" style=\"width:120px;vertical-align:middle;margin-left:0px;margin-right:10px;\"><\/image> Migrate Rig to newest version<\/h2>\n<\/div>\n<div class=\"rhcol span2\">\n<a class=\"mamap\" href=\"\/wp-content\/uploads\/2021\/02\/map-rig-update.png\" target=\"_blank\"><img decoding=\"async\" alt=\"\" src=\"\/wp-content\/uploads\/2021\/02\/map-rig-update.png\" \/><\/a>\n<\/div>\n<\/div>\n<p>When you open a Blend file that contains an older version of an Avastar Armature, then Avastar checks if the older rig is compatible with the current Avastar version. If Avastar detects an incompatibility then it first tries to adjust the rig to match with the current Avastar version.<\/p>\n<div class=\"row-fluid\">\n<div class=\"rhcol span7\">\n<p>But for older Rigs this is often not possible, maybe even not wanted. when this happens, then Avastar greats you with a big Popup Window where it reports its finds and kindly asks you to do the manual Update.<\/p>\n<p>For this purpose the Rig Inspector panel provides a Rig Update function (see further below what the Rig Update Tool does) where you can configure how the update shall be performed.<\/p>\n<\/div>\n<div class=\"rhcol span5\">\n<p><a href=\"https:\/\/avalab.org\/avastar\/293\/wp-content\/uploads\/2021\/02\/Image1387.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignleft size-full wp-image-7493\" src=\"https:\/\/avalab.org\/avastar\/293\/wp-content\/uploads\/2021\/02\/Image1387.png\" alt=\"\" width=\"419\" height=\"296\" srcset=\"https:\/\/avalab.org\/avastar\/293\/wp-content\/uploads\/2021\/02\/Image1387.png 419w, https:\/\/avalab.org\/avastar\/293\/wp-content\/uploads\/2021\/02\/Image1387-300x212.png 300w, https:\/\/avalab.org\/avastar\/293\/wp-content\/uploads\/2021\/02\/Image1387-400x284.png 400w\" sizes=\"auto, (max-width: 419px) 100vw, 419px\" \/><\/a><\/p>\n<\/div>\n<\/div>\n<p>&nbsp;<\/p>\n<p>Lets step over the Update Tool Panel for this situation:<\/p>\n<h3>The Header Section<\/h3>\n<p>The header section begins with a convenient function to Switch your Rig from the Current <strong><span style=\"color: #3366ff;\">Pose Position<\/span><\/strong> to <strong><span style=\"color: #3366ff;\">Rest position<\/span><\/strong>. Note: The same selector is also in Blender&#8217;s Armature Rig data Properties section (right side of the Blender Screen)<\/p>\n<p>Next you find some rig specific selections:<\/p>\n<div class=\"row-fluid\">\n<div class=\"rhcol span7\">\n<p><strong><span style=\"color: #3366ff;\">Source Rig:<\/span><\/strong> Is always AVASTAR<\/p>\n<p><strong><span style=\"color: #3366ff;\">Target Rig:<\/span> <\/strong>You can select either <em><span style=\"color: #ff6600;\">Basic<\/span><\/em> Legacy Rig or <em><span style=\"color: #ff6600;\">Extended<\/span> <\/em>Bento Rig (with hands, face, wings, &#8230;)<\/p>\n<p><strong><span style=\"color: #3366ff;\">Joint Type:<\/span><\/strong> &#8216;Pivot&#8217; or &#8216;POS&#8217; (Pivot is the most likely setting)<\/p>\n<\/div>\n<div class=\"rhcol span5\"><img loading=\"lazy\" decoding=\"async\" class=\"alignleft wp-image-6080 size-full\" src=\"https:\/\/avalab.org\/avastar\/293\/wp-content\/uploads\/2020\/08\/Image916.png\" alt=\"\" width=\"311\" height=\"170\" srcset=\"https:\/\/avalab.org\/avastar\/293\/wp-content\/uploads\/2020\/08\/Image916.png 311w, https:\/\/avalab.org\/avastar\/293\/wp-content\/uploads\/2020\/08\/Image916-300x164.png 300w\" sizes=\"auto, (max-width: 311px) 100vw, 311px\" \/><\/div>\n<\/div>\n<div class=\"row-fluid\">\n<div class=\"rhcol span7\">\n<p>Sometimes you may see an additional section named<em><span style=\"color: #ff6600;\"> Alignment Options<\/span><\/em><\/p>\n<p>This section appears for example when the Origin of the Armature does not match with the origin of the Rootbone. Newer versions of Avastar do not at all like this. But you can let Avastar fix this for you. More details see further down.<\/p>\n<\/div>\n<div class=\"rhcol span5\">\n<p><a href=\"https:\/\/avalab.org\/avastar\/293\/wp-content\/uploads\/2021\/02\/Image1388.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignleft size-full wp-image-7498\" src=\"https:\/\/avalab.org\/avastar\/293\/wp-content\/uploads\/2021\/02\/Image1388.png\" alt=\"\" width=\"419\" height=\"173\" srcset=\"https:\/\/avalab.org\/avastar\/293\/wp-content\/uploads\/2021\/02\/Image1388.png 419w, https:\/\/avalab.org\/avastar\/293\/wp-content\/uploads\/2021\/02\/Image1388-300x124.png 300w\" sizes=\"auto, (max-width: 419px) 100vw, 419px\" \/><\/a><\/p>\n<\/div>\n<\/div>\n<h3>The Rig Update Options<\/h3>\n<div class=\"row-fluid\">\n<div class=\"rhcol span7\">\n<p>The Import Options allow you to define in more detail how exactly your old Rig shall be Updated. Finding the right options is tricky at times, depending on the nature of your Rig. The options are explained below:<\/p>\n<\/div>\n<div class=\"rhcol span5\"><a href=\"https:\/\/avalab.org\/avastar\/293\/wp-content\/uploads\/2021\/02\/Image1389.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignleft wp-image-7499 size-full\" src=\"https:\/\/avalab.org\/avastar\/293\/wp-content\/uploads\/2021\/02\/Image1389.png\" alt=\"\" width=\"419\" height=\"228\" srcset=\"https:\/\/avalab.org\/avastar\/293\/wp-content\/uploads\/2021\/02\/Image1389.png 419w, https:\/\/avalab.org\/avastar\/293\/wp-content\/uploads\/2021\/02\/Image1389-300x163.png 300w\" sizes=\"auto, (max-width: 419px) 100vw, 419px\" \/><\/a><\/div>\n<\/div>\n<p><strong><span style=\"color: #3366ff;\">Enforce SL Bone Roll:<\/span> <\/strong>The Bone roll is the rotation of bones along their long axis. If the Bone Roll is wrong then you can end up with very odd issues. This option tries to reset the Bone Rolls of your armature Bones to the Roll as used with the Default SL Avatar. This option is only rarely necessary, but very handy when it is needed.<\/p>\n<p><strong><span style=\"color: #3366ff;\">Apply Rot&amp;Scale:<\/span> <\/strong>Often your Meshes contain Scale and Rotation in Object space. While this is not entirely wrong, it often creates unwanted and unforeseeable issues. So it is normally best to apply Scale &amp; Rotation during the update.<\/p>\n<p><strong>Rebuild Avastar Meshes: <\/strong>Often you do not want to see the Avastar Meshes. But sometimes it better to &#8220;recreate&#8221; the Avastar Meshes as reference. This option is rarely used.<\/p>\n<p><strong><span style=\"color: #3366ff;\">Adjust Structure Bones:<\/span><\/strong> Avastar evolves and so does its rig. This option ensures that your updated Rig has all Bones used and recognized by the current Avastar version. This is also used to repair rigs of which Bones have been removed intentionally or by accident.<\/p>\n<p><strong><span style=\"color: #3366ff;\">Check for Joint edits:<\/span> <\/strong>When you update a rig then Avastar needs to make sure that the Rig was either not modified, or it must collect the exact modification information to setup the Rig.When this option appears, then Avastar can not find this information in the outdated Rig. In most cases you want to enable this option.<\/p>\n<p><strong><span style=\"color: #3366ff;\">Keep Joint Edits:<\/span> <\/strong>This option is related to the previous one, however Avastar actually has found Joint edits and allows you to keep those edits intact after updating. In most cases you want to enable this option.<\/p>\n<p><strong><span style=\"color: #3366ff;\">Generate IK Offsets:<\/span> <\/strong>IK Bones are normally placed automatically by Avastar. However when you have special custom Rigs where your IK Bones are placed at unusual places, this option attempts to treat the IK Bones just like all other bones and move the IK Bones along with the sliders . This option is not used normally as the automatic placement of IK Bones works nicely in most cases.<\/p>\n<p><strong><span style=\"color: #3366ff;\">Generate Tail Offsets:<\/span> <\/strong>Technically we only need the Bone Head information to support Sliders on edited Rigs. However sometimes you want to also edit the Bone tails for whatever reason. This option is there just for that. Normally you want to enable this option.<\/p>\n<p><strong><span style=\"color: #3366ff;\">Preserve Bone Colors:<\/span><\/strong> Avastar uses a color scheme for Bone groups. However you might have edited the bone colors for your own purposes. When you enable this option then your custom colors are preserved.<\/p>\n<p><strong><span style=\"color: #3366ff;\">Fix Reference meshes:<\/span> <\/strong>This option is related to Appearance Sliders. The reference Meshes contain the meshes at the moment when they where bound to the Rig. But during a Rig Update it is possible that the reference Meshes no longer match with the updated rig and you might end up with highly distorted models. This option makes sure the reference meshes are rebuilt.<\/p>\n<h3>Alignment Options<\/h3>\n<div class=\"row-fluid\">\n<div class=\"rhcol span7\">\n<p>In Avastar-2 the Rig must follow a couple of rules to preserve the entire Rig integrity. This has become necessary so that we can support Sliders also for edited rigs.<\/p>\n<p>When a rig does not follow the rules, then the Update tool provides up to 3 more options to fix integrity. Those options only show up when needed!<\/p>\n<\/div>\n<div class=\"rhcol span5\"><img loading=\"lazy\" decoding=\"async\" class=\"alignleft wp-image-6084 size-full\" src=\"https:\/\/avalab.org\/avastar\/293\/wp-content\/uploads\/2020\/08\/Image919.png\" alt=\"\" width=\"311\" height=\"310\" srcset=\"https:\/\/avalab.org\/avastar\/293\/wp-content\/uploads\/2020\/08\/Image919.png 311w, https:\/\/avalab.org\/avastar\/293\/wp-content\/uploads\/2020\/08\/Image919-300x300.png 300w, https:\/\/avalab.org\/avastar\/293\/wp-content\/uploads\/2020\/08\/Image919-150x150.png 150w\" sizes=\"auto, (max-width: 311px) 100vw, 311px\" \/><\/div>\n<\/div>\n<p><strong><span style=\"color: #3366ff;\">Origin:<\/span><\/strong> The origin of the Armature must match the location of the Armature&#8217;s Origin bone. The Origin Option allows to either move the Armature Origin to the Origin bone, or it moves the Origin Bone to the Armature. Click the double Arrow on the right side to apply the setting.<\/p>\n<p><strong><span style=\"color: #3366ff;\">COG Align to:<\/span><\/strong> The <span style=\"color: #008000;\">COG<\/span> must be aligned to the <span style=\"color: #008000;\">Pelvis<\/span>. Also in some rigs <span style=\"color: #008000;\">Pelvis<\/span> and <span style=\"color: #0000ff;\">mPelvis<\/span> are not aligned. In this case you can specify which of the 2 pelvis bones is the master bone.<\/p>\n<p><strong><span style=\"color: #3366ff;\">Rig Align to:<\/span><\/strong> Avastar 2 expects that the green Animation Rig is strictly aligned to the blue Deform Rig at all times. In earlier Avastar releases this was not necessarily needed. Although we always recommended to keep the 2 rigs aligned. This option allows the user to either align the Animation Bones to the Deform Bones or vice versa.<\/p>\n<h3>The Operator section<\/h3>\n<p>When the Rig Inspector tool is in update mode, then the Operator button is labeled <em><span style=\"color: #ff6600;\">Migrate Rig <\/span><\/em>(see image below)<\/p>\n<div class=\"row-fluid\">\n<div class=\"rhcol span7\">\n<p><strong><span style=\"color: #3366ff;\">The Snowflake icon:<\/span><\/strong> When this option is enabled, then the original rig is applied to the meshes (the current pose is baked) before updating.<\/p>\n<\/div>\n<div class=\"rhcol span5\"><a href=\"https:\/\/avalab.org\/avastar\/293\/wp-content\/uploads\/2021\/02\/Image1390.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignleft wp-image-7501 size-full\" src=\"https:\/\/avalab.org\/avastar\/293\/wp-content\/uploads\/2021\/02\/Image1390.png\" alt=\"\" width=\"419\" height=\"128\" srcset=\"https:\/\/avalab.org\/avastar\/293\/wp-content\/uploads\/2021\/02\/Image1390.png 419w, https:\/\/avalab.org\/avastar\/293\/wp-content\/uploads\/2021\/02\/Image1390-300x92.png 300w\" sizes=\"auto, (max-width: 419px) 100vw, 419px\" \/><\/a><\/div>\n<\/div>\n<p>Below the Migrate Rig button you find an information section which tells you some details about your Rig and the bound meshes:<\/p>\n<div class=\"row-fluid\">\n<div class=\"rhcol span7\">\n<ul>\n<li><strong><span style=\"color: #3366ff;\">Creator<\/span><\/strong> (avastar release that created the rig)<\/li>\n<li><strong><span style=\"color: #3366ff;\">Rig ID<\/span><\/strong> (the Rig Version number)<\/li>\n<li><span style=\"color: #3366ff;\"><strong>Joint offsets<\/strong><\/span> (number of edited bones)<\/li>\n<li><strong><span style=\"color: #3366ff;\">Custom Mesh<\/span><\/strong> (number of custom meshes)<\/li>\n<li><strong><span style=\"color: #3366ff;\">System Mesh<\/span><\/strong> (number of Avastar meshes)<\/li>\n<\/ul>\n<\/div>\n<div class=\"rhcol span5\">\n<p><a href=\"https:\/\/avalab.org\/avastar\/293\/wp-content\/uploads\/2021\/02\/Image1391.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignleft wp-image-7502 size-full\" src=\"https:\/\/avalab.org\/avastar\/293\/wp-content\/uploads\/2021\/02\/Image1391.png\" alt=\"\" width=\"419\" height=\"196\" srcset=\"https:\/\/avalab.org\/avastar\/293\/wp-content\/uploads\/2021\/02\/Image1391.png 419w, https:\/\/avalab.org\/avastar\/293\/wp-content\/uploads\/2021\/02\/Image1391-300x140.png 300w\" sizes=\"auto, (max-width: 419px) 100vw, 419px\" \/><\/a><\/p>\n<\/div>\n<\/div>\n<h2>Questions and Answers<\/h2>\n<h3>What happens during the update<\/h3>\n<p>When all settings are done, then you click the Migrate Rig button (see image above). Avastar will now step through following activities:<\/p>\n<ul>\n<li>The original Armature is applied to the Meshes (when snowflake icon enabled)<\/li>\n<li>The meshes are unbound<\/li>\n<li>A new Avastar armature is created (Basic or Extended)<\/li>\n<li>The Avastar bones are aligned to match the original rig (If check for joint edits is enabled)<\/li>\n<li>The meshes are bound to the new Avastar armature<\/li>\n<li>Depending on the other options the new Avastar meshes are kept, hidden or deleted<\/li>\n<\/ul>\n<h3>When the update fails<\/h3>\n<p>Sometimes the Update Tool creates odd or wrong results. This is either a bug in the tool or it is a wrong option setting. Here are some known cases:<\/p>\n<ul>\n<li><strong>Meshes jump to different locations after update:<br \/>\n<\/strong>Enable the Snowflake Icon (see above) and try again<\/li>\n<li><strong>Armature reverts to Default rig:<\/strong><br \/>\nEnable the option check for joint edits<\/li>\n<li><strong>Moving the sliders after update fails:<\/strong>\n<ul>\n<li>Open the Skinning Tools Panel<\/li>\n<li>Select No Sliders<\/li>\n<li>Select SL Appearance<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<div class=\"symple-box  blue center \" style=\"text-align:left;\"> If you can not get your update to work, you may need to do it manually.<br \/>\nPlease feel free to ask for Help in our <a href=\"https:\/\/discord.gg\/7F8cWfZ\" class=\"symple-button default blue   \" target=\"_self\" title=\"Visit Site\" style=\"border-radius:3px\" rel=\"\"><span class=\"symple-button-inner\" style=\"border-radius:3px\">Discord Help Channel<\/span><\/a><\/div>\n","protected":false},"excerpt":{"rendered":"<p>Migrate Rig to newest version When you open a Blend file that contains an older version of an Avastar Armature, then Avastar checks if the older rig is compatible with the current Avastar version. If Avastar detects an incompatibility then it first tries to adjust the rig to match with the current Avastar version. But [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":7493,"parent":7525,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","footnotes":""},"categories":[4,6,8],"tags":[],"class_list":["post-1711","page","type-page","status-publish","has-post-thumbnail","hentry","category-fragment","category-help","category-reference"],"_links":{"self":[{"href":"https:\/\/avalab.org\/avastar\/293\/wp-json\/wp\/v2\/pages\/1711","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/avalab.org\/avastar\/293\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/avalab.org\/avastar\/293\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/avalab.org\/avastar\/293\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/avalab.org\/avastar\/293\/wp-json\/wp\/v2\/comments?post=1711"}],"version-history":[{"count":1,"href":"https:\/\/avalab.org\/avastar\/293\/wp-json\/wp\/v2\/pages\/1711\/revisions"}],"predecessor-version":[{"id":43619,"href":"https:\/\/avalab.org\/avastar\/293\/wp-json\/wp\/v2\/pages\/1711\/revisions\/43619"}],"up":[{"embeddable":true,"href":"https:\/\/avalab.org\/avastar\/293\/wp-json\/wp\/v2\/pages\/7525"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/avalab.org\/avastar\/293\/wp-json\/wp\/v2\/media\/7493"}],"wp:attachment":[{"href":"https:\/\/avalab.org\/avastar\/293\/wp-json\/wp\/v2\/media?parent=1711"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/avalab.org\/avastar\/293\/wp-json\/wp\/v2\/categories?post=1711"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/avalab.org\/avastar\/293\/wp-json\/wp\/v2\/tags?post=1711"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}