Merge branch 'develop' into substance_integration

website/docs/admin_hosts_maya.md

@@ -106,6 +106,37 @@ or Deadlines **Draft Tile Assembler**.
 This is useful to fix some specific renderer glitches and advanced hacking of Maya Scene files. `Patch name` is label for patch for easier orientation.
 `Patch regex` is regex used to find line in file, after `Patch line` string is inserted. Note that you need to add line ending.
 
+## Load Plugins
+
+### Reference Loader
+
+#### Namespace and Group Name
+Here you can create your own custom naming for the reference loader.
+
+The custom naming is split into two parts: namespace and group name. If you don't set the namespace or the group name, an error will occur.
+Here's the different variables you can use:
+
+<div class="row markdown">
+<div class="col col--5 markdown">
+
+| Token | Description |
+|---|---|
+|`{asset_name}` | Asset name |
+|`{asset_type}` | Asset type |
+|`{subset}` | Subset name |
+|`{family}` | Subset family |
+
+</div>
+</div>
+
+The namespace field can contain a single group of '#' number tokens to indicate where the namespace's unique index should go. The amount of tokens defines the zero padding of the number, e.g ### turns into 001.
+
+Warning: Note that a namespace will always be prefixed with a _ if it starts with a digit.
+
+Example:
+
+![Namespace and Group Name](assets/maya-admin_custom_namespace.png)
+
 ### Extract GPU Cache
 
 ![Maya GPU Cache](assets/maya-admin_gpu_cache.png)
@@ -169,6 +200,17 @@ Most settings to override in the viewport are self explanatory and can be found
 These options are set on the camera shape when publishing the review. They correspond to attributes on the Maya camera shape node.
 
 ![Extract Playblast Settings](assets/maya-admin_extract_playblast_settings_camera_options.png)
+## Include/exclude handles by task type
+You can include or exclude handles, globally or by task type.
+
+The "Include handles by default" defines whether by default handles are included. Additionally you can add a per task type override whether you want to include or exclude handles.
+
+For example, in this image you can see that handles are included by default in all task types, except for the 'Lighting' task, where the toggle is disabled.
+![Include/exclude handles](assets/maya-admin_exclude_handles.png)
+
+And here you can see that the handles are disabled by default, except in 'Animation' task where it's enabled.
+![Custom menu definition](assets/maya-admin_include_handles.png)
+
 
 ## Custom Menu
 You can add your custom tools menu into Maya by extending definitions in **Maya -> Scripts Menu Definition**.

website/docs/artist_hosts_houdini.md

@@ -14,20 +14,29 @@ sidebar_label: Houdini
 - [Library Loader](artist_tools_library-loader)
 
 ## Publishing Alembic Cameras
-You can publish baked camera in Alembic format. Select your camera and go **OpenPype -> Create** and select **Camera (abc)**.
+You can publish baked camera in Alembic format. 
+
+Select your camera and go **OpenPype -> Create** and select **Camera (abc)**.
 This will create Alembic ROP in **out** with path and frame range already set. This node will have a name you've
 assigned in the **Creator** menu. For example if you name the subset `Default`, output Alembic Driver will be named
 `cameraDefault`. After that, you can **OpenPype -> Publish** and after some validations your camera will be published
 to `abc` file.
 
 ## Publishing Composites - Image Sequences
-You can publish image sequence directly from Houdini. You can use any `cop` network you have and publish image
-sequence generated from it. For example I've created simple **cop** graph to generate some noise:
+You can publish image sequences directly from Houdini's image COP networks.
+
+You can use any COP node and publish the image sequence generated from it. For example this simple graph to generate some noise:
+
 ![Noise COP](assets/houdini_imagesequence_cop.png)
 
-If I want to publish it, I'll select node I like - in this case `radialblur1` and go **OpenPype -> Create** and
-select **Composite (Image Sequence)**. This will create `/out/imagesequenceNoise` Composite ROP (I've named my subset
-*Noise*) with frame range set. When you hit **Publish** it will render image sequence from selected node.
+To publish the output of the `radialblur1` go to **OpenPype -> Create** and
+select **Composite (Image Sequence)**. If you name the variant *Noise* this will create the `/out/imagesequenceNoise` Composite ROP with the frame range set. 
+
+When you hit **Publish** it will render image sequence from selected node.
+
+:::info Use selection
+With *Use selection* is enabled on create the node you have selected when creating will be the node used for published. (It set the Composite ROP node's COP path to it). If you don't do this you'll have to manually set the path as needed on e.g. `/out/imagesequenceNoise` to ensure it outputs what you want.
+:::
 
 ## Publishing Point Caches (alembic)
 Publishing point caches in alembic format is pretty straightforward, but it is by default enforcing better compatibility
@@ -46,6 +55,16 @@ you handle `path` attribute is up to you, this is just an example.*
 Now select the `output0` node and go **OpenPype -> Create** and select **Point Cache**. It will create
 Alembic ROP `/out/pointcacheStrange`
 
+## Publishing Reviews (OpenGL)
+To generate a review output from Houdini you need to create a **review** instance. 
+Go to **OpenPype -> Create** and select **Review**.
+
+![Houdini Create Review](assets/houdini_review_create_attrs.png)
+
+On create, with the **Use Selection** checkbox enabled it will set up the first 
+camera found in your selection as the camera for the OpenGL ROP node and other 
+non-cameras are set in **Force Objects**. It will then render those even if 
+their display flag is disabled in your scene.
 
 ## Redshift
 :::note Work in progress

website/docs/project_settings/settings_project_global.md

@@ -255,7 +255,7 @@ suffix is **"client"** then the final suffix is **"h264_client"**.
   | resolution_height | Resolution height. |
   | fps | Fps of an output. |
   | timecode | Timecode by frame start and fps. |
-  | focalLength | **Only available in Maya**<br /><br />Camera focal length per frame. Use syntax `{focalLength:.2f}` for decimal truncating. Eg. `35.234985` with `{focalLength:.2f}` would produce `35.23`, whereas `{focalLength:.0f}` would produce `35`. |
+  | focalLength | **Only available in Maya and Houdini**<br /><br />Camera focal length per frame. Use syntax `{focalLength:.2f}` for decimal truncating. Eg. `35.234985` with `{focalLength:.2f}` would produce `35.23`, whereas `{focalLength:.0f}` would produce `35`. |
 
 :::warning
 `timecode` is a specific key that can be **only at the end of content**. (`"BOTTOM_RIGHT": "TC: {timecode}"`)

website/docs/pype2/admin_presets_plugins.md

@@ -304,7 +304,7 @@ If source representation has suffix **"h264"** and burnin suffix is **"client"**
   | resolution_height | Resolution height. |
   | fps | Fps of an output. |
   | timecode | Timecode by frame start and fps. |
-  | focalLength | **Only available in Maya**<br /><br />Camera focal length per frame. Use syntax `{focalLength:.2f}` for decimal truncating. Eg. `35.234985` with `{focalLength:.2f}` would produce `35.23`, whereas `{focalLength:.0f}` would produce `35`. |
+  | focalLength | **Only available in Maya and Houdini**<br /><br />Camera focal length per frame. Use syntax `{focalLength:.2f}` for decimal truncating. Eg. `35.234985` with `{focalLength:.2f}` would produce `35.23`, whereas `{focalLength:.0f}` would produce `35`. |
 
 :::warning
 `timecode` is specific key that can be **only at the end of content**. (`"BOTTOM_RIGHT": "TC: {timecode}"`)