Pipeline

Environment and Installation

Content

• <NEMO>/depends runtime dependency of loading plugin

  Linux users need to append this path to LD_LIBRARY_PATH before launching Maya

• <NEMO>/extern third-party packages

• <NEMO>/modules config files used for exporting

• <NEMO>/scripts tools main code

• <NEMO>/lib prebuilt Nemo library

• <NEMO>/plug-ins Maya plugin

Environment

• NEMO_LOAD_TOPMENU=0 Hide top bar menu

  Advanced users can directly call nemo.m2n for highly customizable behavior, referring to nemo.interface

• __GL_SYNC_TO_VBLANK=0 turn off vsync

  Linux user can consider setting this to save frame refreshing time for performance

• NEMO_PROFILES_EXPORT export profile storage

  This varaible can be used to share or regularize export settings

Intermediate Files

For complicated or long cycle project, it's good practice to keep all these intermediate files.

• __GRAPH.json

  Describes computing logic of rig. Nodes in original file may apper in vertices anonymously.

• __EXPORT.zip

  For assembling usage, details hiding from common users.

  • __RESOURCE.nemodata storage for geometry, skin weight, blend shape, painting, etc.

  • __SCENE.json controller related data

  • __DEBUG.json for checking reason of unmatched result Nemo Check

  • MAT（json & ma） geometry material information.

• __BINARY.zip

  • Compiled binary result (dll/so)

  • __CONFIG.json information to load binary at runtime

__EXPORT.zip contains confidential data about character apperance or designing. Please keep it to yourself，and don't share it with anyone else (including us).

Publish Nemo Rig

Apart from Maya file, Nemo Rig depends on following files：

• binary(dll/so), the computation unit Nemo compiled. It's okay to put both togther if the asset needs to be cross-platform. The plugin would choose correct version based on OS.

• resource nemodata, asset data for runtime usage.

• config json，description of binary. It also contains (relative) path to binary and resource.

• mat json，description of geometry materials. You can modify this config and reopen file to debug material problem.

Users need to access all these files for Nemo Rig usage, so they need to be published togther with maya file. As mentioned in Assembling, it's possible to store these depends files apart from maya file. It's also possible to change file layout by setting attributes of Nemo node after assembling.

Publish Animation Cache

There are three way to publish cache of animation created with Nemo Rig:

1. Switch to Geometry Mode for publishing

2. Switch to original rig for publishing

3. Use Nemo's publish feature to directly publishing animation curves. The benefits of this approach are:

   1. Animation curves have much smaller size than geometry cache (like Alembic).

   2. Animation curves are more friendly for department like CFX since they can output much more resonable decimal frames.

Among current supported DCCs, the performance of Nemo computation is always better than playing Alembic cache.