# Rigging

**NXT (Node eXecution Tree)**

In the simplest of terms, NXT combines multiple layers of nodes into a single composite layer that is then executable. It is something like Photoshop layers for code. Users are able to mute, solo, override, and extend layers of code. The resulting composite clearly visualizes where attributes and values originated. Colors, node paths, and conveniently placed links allow users to quickly debug code.

{% embed url="<https://nxt-dev.github.io>" %}

{% embed url="<https://youtu.be/d3hDD5TckDk>" %}

{% embed url="<https://online.riggingdojo.com/groups/all>" %}
Rigging Course
{% endembed %}

{% embed url="<https://kitestringonline.com/ozone>" %}

{% embed url="<https://youtu.be/E1DAaUzJpRY>" %}

{% embed url="<https://www.hippydrome.com>" %}

{% embed url="<http://www.chadvernon.com/blog/resources/python-scripting-for-maya-artists/>" %}

{% embed url="<http://www.mgear-framework.com/mgear_dist/index.html>" %}

{% embed url="<https://github.com/mgear-dev/mgear>" %}

{% embed url="<http://www.chrisevans3d.com/pub_blog/the-jaw/>" %}

{% embed url="<http://www.hippydrome.com>" %}

![https://anatomy4sculptors.com/](/files/-Ltfzl2_e3LvyLLomqS3)

{% embed url="<https://vimeo.com/111761295>" %}

{% embed url="<https://www.highend3d.com/>" %}

### Xsens + Vive = VCam

Virtual camera using an HTC Vive puck running parallel with an [Xsens](https://www.linkedin.com/company/xsens/) motion capture system, piped into MotionBuilder. Xsens mocap footage is then post-processed and replaces the live data, resulting in extremely high quality 3D Previz (3Viz). [hashtag#virtualproduction](https://www.linkedin.com/feed/hashtag/?highlightedUpdateUrns=urn%3Ali%3Aactivity%3A6605477892367482881\&keywords=%23virtualproduction\&originTrackingId=tPqw0WWvSIiX5A17NT7J7Q%3D%3D) [hashtag#mocap](https://www.linkedin.com/feed/hashtag/?highlightedUpdateUrns=urn%3Ali%3Aactivity%3A6605477892367482881\&keywords=%23mocap\&originTrackingId=tPqw0WWvSIiX5A17NT7J7Q%3D%3D) [hashtag#3viz](https://www.linkedin.com/feed/hashtag/?highlightedUpdateUrns=urn%3Ali%3Aactivity%3A6605477892367482881\&keywords=%233viz\&originTrackingId=tPqw0WWvSIiX5A17NT7J7Q%3D%3D) [hashtag#3dpreviz](https://www.linkedin.com/feed/hashtag/?highlightedUpdateUrns=urn%3Ali%3Aactivity%3A6605477892367482881\&keywords=%233dpreviz\&originTrackingId=tPqw0WWvSIiX5A17NT7J7Q%3D%3D)&#x20;

[Here is the org post](https://www.linkedin.com/posts/theericjacobus_virtualproduction-mocap-3viz-activity-6605477892367482881-yL7c).

### ETC

{% embed url="<https://cascadeur.com/learn/how_to_begin>" %}

ChopRig

{% embed url="<https://medium.com/blue-sky-tech-blog/choprig-system-b11d4c1e252c>" %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://stephanosterburg.gitbook.io/scrapbook/rigging.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.