dr.sybren
/
rignodes
11
14
Fork 2
Code Issues Pull Requests 5 Projects Releases Wiki Activity

Relative remapping of locations #7

Open
Denys Hsu wants to merge 1 commits from cgtinker/powership:remap_location_node into main
pull from: cgtinker/powership:remap_location_node
merge into: dr.sybren:main

When changing the target branch, be careful to rebase the branch in your fork to match. See documentation.
Conversation 0 Commits 1 Files Changed 2 +30
Denys Hsu commented 2023-06-16 10:48:22 +02:00
Contributor
Copy Link

Remapping position can be very useful if you want to remap locations from rig to rig or from points to a rig. I've been using this concept quiet a lot but it's not super intuitive to use.

From Origin: The previous location in the chain to remap
From Destination: The location to actually remap
To Origin: The location of the origin to remap to (b.e. a bone head)
To Destination: The location of the destination to remap to (b.e. a bone tail)

Result: The designated location based on the target origin and destination

The main goal of this setup is to remap a locations relative from an origin to bones of an arbitrary rig. As rigs have different setups, using bones directly usually leads to issues as the bone chains may consist of an arbitrary amount of bones.

Remapping position can be very useful if you want to remap locations from rig to rig or from points to a rig. I've been using this concept quiet a lot but it's not super intuitive to use. From Origin: The previous location in the chain to remap From Destination: The location to actually remap To Origin: The location of the origin to remap to (b.e. a bone head) To Destination: The location of the destination to remap to (b.e. a bone tail) Result: The designated location based on the target origin and destination The main goal of this setup is to remap a locations relative from an origin to bones of an arbitrary rig. As rigs have different setups, using bones directly usually leads to issues as the bone chains may consist of an arbitrary amount of bones.
Denys Hsu added 1 commit 2023-06-16 10:48:24 +02:00
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u remap_location_node:cgtinker-remap_location_node
git checkout cgtinker-remap_location_node

Merge

Merge the changes and update on Gitea.
git checkout main
git merge --no-ff cgtinker-remap_location_node
git checkout main
git merge --ff-only cgtinker-remap_location_node
git checkout cgtinker-remap_location_node
git rebase main
git checkout main
git merge --no-ff cgtinker-remap_location_node
git checkout main
git merge --squash cgtinker-remap_location_node
git checkout main
git merge cgtinker-remap_location_node
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: dr.sybren/rignodes#7
No description provided.
Delete Branch "cgtinker/powership:remap_location_node"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?