{"id":2409,"date":"2017-05-30T21:42:02","date_gmt":"2017-05-30T21:42:02","guid":{"rendered":"http:\/\/julius-ihle.de\/?p=2409"},"modified":"2018-04-04T08:38:39","modified_gmt":"2018-04-04T08:38:39","slug":"maintain-constraint-offset-in-katana","status":"publish","type":"post","link":"https:\/\/julius-ihle.de\/?p=2409","title":{"rendered":"Maintain Constraint Offset in Katana"},"content":{"rendered":"

\"katana_constraint_offset\"<\/a><\/p>\n

Constraining things in Katana works well, but can seem somewhat limited if you are coming from a full-featured 3D application. One of the things that can potentially give you headaches is a missing option for “maintaining offset” when you are constraining one object or a lightrig to something else. While this is generally not an issue when you are doing LookDev (as your assets most likely have zero’d out transforms) it can be a bit frustrating to not have that option when you are working on shots, so here’s my hacky way of maintaining constraint-offsets.<\/p>\n

Every now and then you have to constraint lights to an object in your scene. Generally the best practice is to create a rig in the Gaffer<\/em> node and constraint it before adding any lights. That way you don’t have to worry about fixing anything later. If you are a day-dreamer like me however it may happen that you add a rig and all your lights to your object before you constraint anything:
\n\"01_KatanaScene\"<\/a><\/p>\n

 <\/p>\n

Consequently when you come to the point of constraining your parent rig (which was most likely in the origin) will move to your constraint target and offset all the carefully placed lights you just created:<\/p>\n

\"02_PCC\"<\/a><\/p>\n

 <\/p>\n

Bummer… However luckily with a few steps you can re-center your rig to where it was before constraining it.
\nTo do that first of all add a ConstraintResolve<\/em> Node. This will convert the constraint data into a matrix to give you the actual world-space position. The resulting numbers for the matrix visible in the Attributes-Tab<\/em> may not really be too much of a help right off the bat. You can add a TransformEdit<\/em> Node and plug in your constrained rig into the path to to show you the actual transforms:
\n\"03_CR_xformEdit\"<\/a><\/p>\n

 <\/p>\n

Now that you know where your rig has been moved to you can reverse this transformation. There are a couple of ways to do that but I personally like to do it in a separate rig:
\n-Add a new child-rig to the rig you have constrained to your object and move all your lights below it
\n-Copy over the transform values from your TransformEdit<\/em> Node to your constraintOffset rig and negate them (-22 becomes 22 \/\/ 749 becomes -749 \/\/ etc.)
\n-Inverse the transformOrder<\/em> (Scale Rotate Translate<\/em> becomes Translate Rotate Scale<\/em>, etc.) and the rotationOrder<\/em> (XYZ<\/em> becomes ZYX<\/em>, etc.). This is assuming you have used the defaults in your rig – adjust them if you have used different orders.<\/p>\n

This way your constraintOffset rig should be perfectly centered out again and your lights should be where they belong:
\n\"04_constraintOffset\"<\/a><\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 
\n_________________________________________________<\/span>
\n If this post has helped you in any way you can express your gratefulness by using the Donate\u00a0<\/em>Button below to buy me a coffee! :)<\/span><\/span>
\n\"\"<\/a><\/p>\n

\n
3M5xNSV7g2NzVpHMqzYKhgoKJZ8CWa644m<\/span><\/span>
\n\"bc_ldgr_qrcode\"<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

Constraining things in Katana works well, but can seem somewhat limited if you are coming from a full-featured 3D application. One of the things that can potentially give you headaches is a missing option for “maintaining offset” when you are constraining one object or a lightrig to something else. While this is generally not an […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1],"tags":[91,93,130,129,136,27,133,131,132,134,135,24,92,28],"class_list":["post-2409","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-cgi","tag-computer-graphics","tag-constraining","tag-constraints","tag-foundry","tag-katana","tag-orientconstraint","tag-parentchildconstraint","tag-pointconstraint","tag-transform","tag-transformation","tag-vfx","tag-visual-effects","tag-workflow"],"jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p3MXK6-CR","jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/julius-ihle.de\/index.php?rest_route=\/wp\/v2\/posts\/2409","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/julius-ihle.de\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/julius-ihle.de\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/julius-ihle.de\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/julius-ihle.de\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2409"}],"version-history":[{"count":8,"href":"https:\/\/julius-ihle.de\/index.php?rest_route=\/wp\/v2\/posts\/2409\/revisions"}],"predecessor-version":[{"id":2589,"href":"https:\/\/julius-ihle.de\/index.php?rest_route=\/wp\/v2\/posts\/2409\/revisions\/2589"}],"wp:attachment":[{"href":"https:\/\/julius-ihle.de\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2409"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/julius-ihle.de\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2409"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/julius-ihle.de\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2409"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}