'.format(value)}
items.append(message)
- self.show_interface(items, title, event, user, username, user_id)
+ self.show_interface(
+ items, title, event, user, username, user_id, submit_btn_label
+ )
def trigger_action(
self, action_name, event=None, session=None,
diff --git a/openpype/modules/default_modules/ftrack/scripts/sub_event_processor.py b/openpype/modules/default_modules/ftrack/scripts/sub_event_processor.py
index 51b45eb93b..d1e2e3aaeb 100644
--- a/openpype/modules/default_modules/ftrack/scripts/sub_event_processor.py
+++ b/openpype/modules/default_modules/ftrack/scripts/sub_event_processor.py
@@ -13,6 +13,11 @@ from openpype_modules.ftrack.ftrack_server.lib import (
from openpype.modules import ModulesManager
from openpype.api import Logger
+from openpype.lib import (
+ get_openpype_version,
+ get_build_version
+)
+
import ftrack_api
@@ -40,9 +45,11 @@ def send_status(event):
new_event_data = {
"subprocess_id": subprocess_id,
"source": "processor",
- "status_info": {
- "created_at": subprocess_started.strftime("%Y.%m.%d %H:%M:%S")
- }
+ "status_info": [
+ ["created_at", subprocess_started.strftime("%Y.%m.%d %H:%M:%S")],
+ ["OpenPype version", get_openpype_version() or "N/A"],
+ ["OpenPype build version", get_build_version() or "N/A"]
+ ]
}
new_event = ftrack_api.event.base.Event(
diff --git a/openpype/modules/default_modules/ftrack/scripts/sub_event_status.py b/openpype/modules/default_modules/ftrack/scripts/sub_event_status.py
index 8a2733b635..004f61338c 100644
--- a/openpype/modules/default_modules/ftrack/scripts/sub_event_status.py
+++ b/openpype/modules/default_modules/ftrack/scripts/sub_event_status.py
@@ -2,6 +2,7 @@ import os
import sys
import json
import threading
+import collections
import signal
import socket
import datetime
@@ -165,7 +166,7 @@ class StatusFactory:
return
source = event["data"]["source"]
- data = event["data"]["status_info"]
+ data = collections.OrderedDict(event["data"]["status_info"])
self.update_status_info(source, data)
@@ -348,7 +349,7 @@ def heartbeat():
def main(args):
port = int(args[-1])
- server_info = json.loads(args[-2])
+ server_info = collections.OrderedDict(json.loads(args[-2]))
# Create a TCP/IP socket
sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
diff --git a/openpype/modules/default_modules/ftrack/scripts/sub_event_storer.py b/openpype/modules/default_modules/ftrack/scripts/sub_event_storer.py
index a8649e0ccc..5543ed74e2 100644
--- a/openpype/modules/default_modules/ftrack/scripts/sub_event_storer.py
+++ b/openpype/modules/default_modules/ftrack/scripts/sub_event_storer.py
@@ -14,7 +14,11 @@ from openpype_modules.ftrack.ftrack_server.lib import (
TOPIC_STATUS_SERVER_RESULT
)
from openpype_modules.ftrack.lib import get_ftrack_event_mongo_info
-from openpype.lib import OpenPypeMongoConnection
+from openpype.lib import (
+ OpenPypeMongoConnection,
+ get_openpype_version,
+ get_build_version
+)
from openpype.api import Logger
log = Logger.get_logger("Event storer")
@@ -153,9 +157,11 @@ def send_status(event):
new_event_data = {
"subprocess_id": os.environ["FTRACK_EVENT_SUB_ID"],
"source": "storer",
- "status_info": {
- "created_at": subprocess_started.strftime("%Y.%m.%d %H:%M:%S")
- }
+ "status_info": [
+ ["created_at", subprocess_started.strftime("%Y.%m.%d %H:%M:%S")],
+ ["OpenPype version", get_openpype_version() or "N/A"],
+ ["OpenPype build version", get_build_version() or "N/A"]
+ ]
}
new_event = ftrack_api.event.base.Event(
diff --git a/openpype/modules/default_modules/python_console_interpreter/window/widgets.py b/openpype/modules/default_modules/python_console_interpreter/window/widgets.py
index d7a043a151..0e8dd2fb9b 100644
--- a/openpype/modules/default_modules/python_console_interpreter/window/widgets.py
+++ b/openpype/modules/default_modules/python_console_interpreter/window/widgets.py
@@ -387,8 +387,6 @@ class PythonInterpreterWidget(QtWidgets.QWidget):
self.setStyleSheet(load_stylesheet())
- self.resize(self.default_width, self.default_height)
-
self._init_from_registry()
if self._tab_widget.count() < 1:
@@ -396,16 +394,23 @@ class PythonInterpreterWidget(QtWidgets.QWidget):
def _init_from_registry(self):
setting_registry = PythonInterpreterRegistry()
-
+ width = None
+ height = None
try:
width = setting_registry.get_item("width")
height = setting_registry.get_item("height")
- if width is not None and height is not None:
- self.resize(width, height)
except ValueError:
pass
+ if width is None or width < 200:
+ width = self.default_width
+
+ if height is None or height < 200:
+ height = self.default_height
+
+ self.resize(width, height)
+
try:
sizes = setting_registry.get_item("splitter_sizes")
if len(sizes) == len(self._widgets_splitter.sizes()):
diff --git a/openpype/settings/defaults/system_settings/applications.json b/openpype/settings/defaults/system_settings/applications.json
index 842c294599..cfdeca4b87 100644
--- a/openpype/settings/defaults/system_settings/applications.json
+++ b/openpype/settings/defaults/system_settings/applications.json
@@ -195,7 +195,7 @@
"environment": {}
},
"__dynamic_keys_labels__": {
- "13-0": "13.0 (Testing only)",
+ "13-0": "13.0",
"12-2": "12.2",
"12-0": "12.0",
"11-3": "11.3",
@@ -331,7 +331,7 @@
"environment": {}
},
"__dynamic_keys_labels__": {
- "13-0": "13.0 (Testing only)",
+ "13-0": "13.0",
"12-2": "12.2",
"12-0": "12.0",
"11-3": "11.3",
diff --git a/repos/avalon-core b/repos/avalon-core
index b3e4959778..1e94241ffe 160000
--- a/repos/avalon-core
+++ b/repos/avalon-core
@@ -1 +1 @@
-Subproject commit b3e49597786c931c13bca207769727d5fc56d5f6
+Subproject commit 1e94241ffe2dd7ce65ca66b08e452ffc03180235
diff --git a/website/docs/admin_openpype_commands.md b/website/docs/admin_openpype_commands.md
index d6ccc883b0..7a46ee7906 100644
--- a/website/docs/admin_openpype_commands.md
+++ b/website/docs/admin_openpype_commands.md
@@ -55,7 +55,7 @@ openpype_console tray --debug
---
### `launch` arguments {#eventserver-arguments}
You have to set either proper environment variables to provide URL and credentials or use
-option to specify them. If you use `--store_credentials` provided credentials will be stored for later use.
+option to specify them.
| Argument | Description |
| --- | --- |
@@ -63,16 +63,13 @@ option to specify them. If you use `--store_credentials` provided credentials wi
| `--ftrack-url` | URL to ftrack server (can be set with `FTRACK_SERVER`) |
| `--ftrack-user` |user name to log in to ftrack (can be set with `FTRACK_API_USER`) |
| `--ftrack-api-key` | ftrack api key (can be set with `FTRACK_API_KEY`) |
-| `--ftrack-events-path` | path to event server plugins (can be set with `FTRACK_EVENTS_PATH`) |
-| `--no-stored-credentials` | will use credential specified with options above |
-| `--store-credentials` | will store credentials to file for later use |
| `--legacy` | run event server without mongo storing |
| `--clockify-api-key` | Clockify API key (can be set with `CLOCKIFY_API_KEY`) |
| `--clockify-workspace` | Clockify workspace (can be set with `CLOCKIFY_WORKSPACE`) |
To run ftrack event server:
```shell
-openpype_console eventserver --ftrack-url= --ftrack-user= --ftrack-api-key= --ftrack-events-path= --no-stored-credentials --store-credentials
+openpype_console eventserver --ftrack-url= --ftrack-user= --ftrack-api-key=
```
---
diff --git a/website/docs/artist_hosts_nuke_tut.md b/website/docs/artist_hosts_nuke_tut.md
new file mode 100644
index 0000000000..4d116bd958
--- /dev/null
+++ b/website/docs/artist_hosts_nuke_tut.md
@@ -0,0 +1,337 @@
+---
+id: artist_hosts_nuke_tut
+title: Nuke
+sidebar_label: Nuke
+---
+
+:::note
+OpenPype supports Nuke version **`11.0`** and above.
+:::
+
+## OpenPype global tools
+
+- [Set Context](artist_tools.md#set-context)
+- [Work Files](artist_tools.md#workfiles)
+- [Create](artist_tools.md#creator)
+- [Load](artist_tools.md#loader)
+- [Manage (Inventory)](artist_tools.md#inventory)
+- [Publish](artist_tools.md#publisher)
+- [Library Loader](artist_tools.md#library-loader)
+
+## Nuke specific tools
+
+
+
+
+### Set Frame Ranges
+
+Use this feature in case you are not sure the frame range is correct.
+
+##### Result
+
+- setting Frame Range in script settings
+- setting Frame Range in viewers (timeline)
+
+
+
+
+
+
+
+
+
+
+1. limiting to Frame Range without handles
+2. **Input** handle on start
+3. **Output** handle on end
+
+
+
+
+### Set Resolution
+
+
+
+
+
+This menu item will set correct resolution format for you defined by your production.
+
+##### Result
+
+- creates new item in formats with project name
+- sets the new format as used
+
+
+
+This menu item will set correct Colorspace definitions for you. All has to be configured by your production (Project coordinator).
+
+##### Result
+
+- set Colorspace in your script settings
+- set preview LUT to your viewers
+- set correct colorspace to all discovered Read nodes (following expression set in settings)
+
+
+
+It is usually enough if you once per while use this option just to make yourself sure the workfile is having set correct properties.
+
+##### Result
+
+- set Frame Ranges
+- set Colorspace
+- set Resolution
+
+
+
+
+
+
+
+
+
+### Build Workfile
+
+
+
+
+This tool will append all available subsets into an actual node graph. It will look into database and get all last [versions](artist_concepts.md#version) of available [subsets](artist_concepts.md#subset).
+
+
+##### Result
+
+- adds all last versions of subsets (rendered image sequences) as read nodes
+- ~~adds publishable write node as `renderMain` subset~~
+
+
+
+
+
+
+
+
+
+## Nuke QuickStart
+
+This QuickStart is short introduction to what OpenPype can do for you. It attempts to make an overview for compositing artists, and simplifies processes that are better described in specific parts of the documentation.
+
+### Launch Nuke - Shot and Task Context
+OpenPype has to know what shot and task you are working on. You need to run Nuke in context of the task, using Ftrack Action or OpenPype Launcher to select the task and run Nuke.
+
+
+
+
+:::tip Admin Tip - Nuke version
+You can [configure](admin_settings_project_anatomy.md#Attributes) which DCC version(s) will be available for current project in **Studio Settings → Project → Anatomy → Attributes → Applications**
+:::
+
+### Nuke Initial setup
+Nuke OpenPype menu shows the current context
+
+
+
+Launching Nuke with context stops your timer, and starts the clock on the shot and task you picked.
+
+Openpype makes initial setup for your Nuke script. It is the same as running [Apply All Settings](artist_hosts_nuke.md#apply-all-settings) from the OpenPype menu.
+
+- Reads frame range and resolution from Avalon database, sets it in Nuke Project Settings,
+Creates Viewer node, sets it’s range and indicates handles by In and Out points.
+
+- Reads Color settings from the project configuration, and sets it in Nuke Project Settings and Viewer.
+
+- Sets project directory in the Nuke Project Settings to the Nuke Script Directory
+
+:::tip Tip - Project Settings
+After Nuke starts it will automatically **Apply All Settings** for you. If you are sure the settings are wrong just contact your supervisor and he will set them correctly for you in project database.
+:::
+
+### Save Nuke script – the Work File
+Use OpenPype - Work files menu to create a new Nuke script. Openpype offers you the preconfigured naming.
+
+
+The Next Available Version checks the work folder for already used versions and offers the lowest unused version number automatically.
+
+Subversion can be used to distinguish or name versions. For example used to add shortened artist name.
+
+More about [workfiles](artist_tools#workfiles).
+
+
+:::tip Admin Tips
+- **Workfile Naming**
+
+ - The [workfile naming](admin_settings_project_anatomy#templates) is configured in anatomy, see **Studio Settings → Project → Anatomy → Templates → Work**
+
+- **Open Workfile**
+
+ - You can [configure](project_settings/settings_project_nuke#create-first-workfile) Nuke to automatically open the last version, or create a file on startup. See **Studio Settings → Project → Global → Tools → Workfiles**
+
+- **Nuke Color Settings**
+
+ - [Color setting](project_settings/settings_project_nuke) for Nuke can be found in **Studio Settings → Project → Anatomy → Color Management and Output Formats → Nuke**
+:::
+
+### Load plate
+Use Load from OpenPype menu to load any plates or renders available.
+
+
+
+Pick the plate asset, right click and choose Load Image Sequence to create a Read node in Nuke.
+
+Note that the Read node created by OpenPype is green. Green color indicates the highest version of asset is loaded. Asset versions could be easily changed by [Manage](#managing-versions). Lower versions will be highlighted by orange color on the read node.
+
+
+
+More about [Asset loader](artist_tools#loader).
+
+### Create Write Node
+To create OpenPype managed Write node, select the Read node you just created, from OpenPype menu, pick Create.
+In the Instance Creator, pick Create Write Render, and Create.
+
+
+
+This will create a Group with a Write node inside.
+
+
+
+:::tip Admin Tip - Configuring write node
+You can configure write node parameters in **Studio Settings → Project → Anatomy → Color Management and Output Formats → Nuke → Nodes**
+:::
+
+#### What Nuke Publish Does
+From Artist perspective, Nuke publish gathers all the stuff found in the Nuke script with Publish checkbox set to on, exports stuff and raises the Nuke script (workfile) version.
+
+The Pyblish dialog shows the progress of the process.
+
+The left column of the dialog shows what will be published. Typically it is one or more renders or prerenders, plus work file.
+
+
+
+The right column shows the publish steps
+
+##### Publish steps
+1. Gathers all the stuff found in the Nuke script with Publish checkbox set to on
+2. Collects all the info (from the script, database…)
+3. Validates components to be published (checks render range and resolution...)
+4. Extracts data from the script
+ - generates thumbnail
+ - creates review(s) like h264
+ - adds burnins to review(s)
+ - Copies and renames components like render(s), review(s), Nuke script... to publish folder
+5. Integrates components (writes to database, sends preview of the render to Ftrack ...
+6. Increments Nuke script version, cleans up the render directory
+
+Gathering all the info and validating usually takes just a few seconds. Creating reviews for long, high resolution shots can however take significant amount of time when publishing locally.
+
+##### Pyblish Note and Intent
+
+
+Artist can add Note and Intent before firing the publish button. The Note and Intent is ment for easy communication between artist and supervisor. After publish, Note and Intent can be seen in Ftrack notes.
+
+##### Pyblish Checkbox
+
+
+
+Pyblish Dialog tries to pack a lot of info in a small area. One of the more tricky parts is that it uses non-standard checkboxes. Some squares can be turned on and off by the artist, some are mandatory.
+
+If you run the publish and decide to not publish the Nuke script, you can turn it off right in the Pyblish dialog by clicking on the checkbox. If you decide to render and publish the shot in lower resolution to speed up the turnaround, you have to turn off the Write Resolution validator. If you want to use an older version of the asset (older version of the plate...), you have to turn off the Validate containers, and so on.
+
+More info about [Using Pyblish](artist_tools#publisher)
+
+:::tip Admin Tip - Configuring validators
+You can configure Nuke validators like Output Resolution in **Studio Settings → Project → Nuke → Publish plugins**
+:::
+
+### Review
+
+
+When you turn the review checkbox on in your OpenPype write node, here is what happens:
+- OpenPype uses the current Nuke script to
+ - Load the render
+ - Optionally apply LUT
+ - Render Prores 4444 with the same resolution as your render
+- Use Ffmpeg to convert the Prores to whatever review(s) you defined
+- Use Ffmpeg to add (optional) burnin to the review(s) from previous step
+
+Creating reviews is a part of the publishing process. If you choose to do a local publish or to use existing frames, review will be processed also on the artist's machine.
+If you choose to publish on the farm, you will render and do reviews on the farm.
+
+So far there is no option for using existing frames (from your local / check render) and just do the review on the farm.
+
+More info about [configuring reviews](pype2/admin_presets_plugins#extractreview).
+
+:::tip Admin Tip - Configuring Reviews
+You can configure reviewsin **Studio Settings → Project → Global → Publish plugins → ExtractReview / ExtractBurnin**
+Reviews can be configured separately for each host, task, or family. For example Maya can produce different review to Nuke, animation task can have different burnin then modelling, and plate can have different review then model.
+:::
+
+### Render and Publish
+
+
+
+Let’s say you want to render and publish the shot right now, with only a Read and Write node. You need to decide if you want to render, check the render and then publish it, or you want to execute the render and publish in one go.
+
+If you wish to check your render before publishing, you can use your local machine or your farm to render the write node as you would do without OpenPype, load and check your render (OpenPype Write has a convenience button for that), and if happy, use publish with Use existing frames option selected in the write node to generate the review on your local machine.
+
+If you want to render and publish on the farm in one go, run publish with On farm option selected in the write node to render and make the review on farm.
+
+
+
+### Version-less Render
+
+
+
+OpenPype is configured so your render file names have no version number until the render is fully finished and published. The main advantage is that you can keep the render from the previous version and re-render only part of the shot. With care, this is handy.
+
+Main disadvantage of this approach is that you can render only one version of your shot at one time. Otherwise you risk to partially overwrite your shot render before publishing copies and renames the rendered files to the properly versioned publish folder.
+
+When making quick farm publishes, like making two versions with different color correction, care must be taken to let the first job (first version) completely finish before the second version starts rendering.
+
+### Managing Versions
+
+
+
+OpenPype checks all the assets loaded to Nuke on script open. All out of date assets are colored orange, up to date assets are colored green.
+
+Use Manage to switch versions for loaded assets.
+
+## Troubleshooting
+
+### Fixing Validate Containers
+
+
+
+If your Pyblish dialog fails on Validate Containers, you might have an old asset loaded. Use OpenPype - Manage... to switch the asset(s) to the latest version.
+
+### Fixing Validate Version
+If your Pyblish dialog fails on Validate Version, you might be trying to publish already published version. Rise your version in the OpenPype WorkFiles SaveAs.
+
+Or maybe you accidentaly copied write node from different shot to your current one. Check the write publishes on the left side of the Pyblish dialog. Typically you publish only one write. Locate and delete the stray write from other shot.
\ No newline at end of file
diff --git a/website/docs/assets/nuke_tut/nuke_AnatomyAppsVersions.png b/website/docs/assets/nuke_tut/nuke_AnatomyAppsVersions.png
new file mode 100644
index 0000000000..92e1b4dad7
Binary files /dev/null and b/website/docs/assets/nuke_tut/nuke_AnatomyAppsVersions.png differ
diff --git a/website/docs/assets/nuke_tut/nuke_AssetLoadOutOfDate.png b/website/docs/assets/nuke_tut/nuke_AssetLoadOutOfDate.png
new file mode 100644
index 0000000000..f7f807a94f
Binary files /dev/null and b/website/docs/assets/nuke_tut/nuke_AssetLoadOutOfDate.png differ
diff --git a/website/docs/assets/nuke_tut/nuke_AssetLoader.png b/website/docs/assets/nuke_tut/nuke_AssetLoader.png
new file mode 100644
index 0000000000..e52abdc428
Binary files /dev/null and b/website/docs/assets/nuke_tut/nuke_AssetLoader.png differ
diff --git a/website/docs/assets/nuke_tut/nuke_Context.png b/website/docs/assets/nuke_tut/nuke_Context.png
new file mode 100644
index 0000000000..65bb288764
Binary files /dev/null and b/website/docs/assets/nuke_tut/nuke_Context.png differ
diff --git a/website/docs/assets/nuke_tut/nuke_Create.png b/website/docs/assets/nuke_tut/nuke_Create.png
new file mode 100644
index 0000000000..2c843c05df
Binary files /dev/null and b/website/docs/assets/nuke_tut/nuke_Create.png differ
diff --git a/website/docs/assets/nuke_tut/nuke_Creator.png b/website/docs/assets/nuke_tut/nuke_Creator.png
new file mode 100644
index 0000000000..454777574a
Binary files /dev/null and b/website/docs/assets/nuke_tut/nuke_Creator.png differ
diff --git a/website/docs/assets/nuke_tut/nuke_Load.png b/website/docs/assets/nuke_tut/nuke_Load.png
new file mode 100644
index 0000000000..2a345dc69f
Binary files /dev/null and b/website/docs/assets/nuke_tut/nuke_Load.png differ
diff --git a/website/docs/assets/nuke_tut/nuke_ManageVersion.png b/website/docs/assets/nuke_tut/nuke_ManageVersion.png
new file mode 100644
index 0000000000..c9f2091347
Binary files /dev/null and b/website/docs/assets/nuke_tut/nuke_ManageVersion.png differ
diff --git a/website/docs/assets/nuke_tut/nuke_NukeColor.png b/website/docs/assets/nuke_tut/nuke_NukeColor.png
new file mode 100644
index 0000000000..5c4f9a15e0
Binary files /dev/null and b/website/docs/assets/nuke_tut/nuke_NukeColor.png differ
diff --git a/website/docs/assets/nuke_tut/nuke_Publish.png b/website/docs/assets/nuke_tut/nuke_Publish.png
new file mode 100644
index 0000000000..b53b6cc06c
Binary files /dev/null and b/website/docs/assets/nuke_tut/nuke_Publish.png differ
diff --git a/website/docs/assets/nuke_tut/nuke_PyblishCheckBox.png b/website/docs/assets/nuke_tut/nuke_PyblishCheckBox.png
new file mode 100644
index 0000000000..2c5d59c9d5
Binary files /dev/null and b/website/docs/assets/nuke_tut/nuke_PyblishCheckBox.png differ
diff --git a/website/docs/assets/nuke_tut/nuke_PyblishDialogNuke.png b/website/docs/assets/nuke_tut/nuke_PyblishDialogNuke.png
new file mode 100644
index 0000000000..e98a4b9553
Binary files /dev/null and b/website/docs/assets/nuke_tut/nuke_PyblishDialogNuke.png differ
diff --git a/website/docs/assets/nuke_tut/nuke_PyblishDialogNukeNoteIntent.png b/website/docs/assets/nuke_tut/nuke_PyblishDialogNukeNoteIntent.png
new file mode 100644
index 0000000000..3519ecc22d
Binary files /dev/null and b/website/docs/assets/nuke_tut/nuke_PyblishDialogNukeNoteIntent.png differ
diff --git a/website/docs/assets/nuke_tut/nuke_RenderLocalFarm.png b/website/docs/assets/nuke_tut/nuke_RenderLocalFarm.png
new file mode 100644
index 0000000000..4c4c8977a0
Binary files /dev/null and b/website/docs/assets/nuke_tut/nuke_RenderLocalFarm.png differ
diff --git a/website/docs/assets/nuke_tut/nuke_RunNukeFtrackAction.png b/website/docs/assets/nuke_tut/nuke_RunNukeFtrackAction.png
new file mode 100644
index 0000000000..75faaec572
Binary files /dev/null and b/website/docs/assets/nuke_tut/nuke_RunNukeFtrackAction.png differ
diff --git a/website/docs/assets/nuke_tut/nuke_RunNukeFtrackAction_p3.png b/website/docs/assets/nuke_tut/nuke_RunNukeFtrackAction_p3.png
new file mode 100644
index 0000000000..27fec32ae4
Binary files /dev/null and b/website/docs/assets/nuke_tut/nuke_RunNukeFtrackAction_p3.png differ
diff --git a/website/docs/assets/nuke_tut/nuke_RunNukeLauncher.png b/website/docs/assets/nuke_tut/nuke_RunNukeLauncher.png
new file mode 100644
index 0000000000..a42ee6d7b9
Binary files /dev/null and b/website/docs/assets/nuke_tut/nuke_RunNukeLauncher.png differ
diff --git a/website/docs/assets/nuke_tut/nuke_RunNukeLauncher_p2.png b/website/docs/assets/nuke_tut/nuke_RunNukeLauncher_p2.png
new file mode 100644
index 0000000000..2a36cad380
Binary files /dev/null and b/website/docs/assets/nuke_tut/nuke_RunNukeLauncher_p2.png differ
diff --git a/website/docs/assets/nuke_tut/nuke_ValidateContainers.png b/website/docs/assets/nuke_tut/nuke_ValidateContainers.png
new file mode 100644
index 0000000000..78e0f2edd7
Binary files /dev/null and b/website/docs/assets/nuke_tut/nuke_ValidateContainers.png differ
diff --git a/website/docs/assets/nuke_tut/nuke_WorkFileNamingAnatomy.png b/website/docs/assets/nuke_tut/nuke_WorkFileNamingAnatomy.png
new file mode 100644
index 0000000000..115a321285
Binary files /dev/null and b/website/docs/assets/nuke_tut/nuke_WorkFileNamingAnatomy.png differ
diff --git a/website/docs/assets/nuke_tut/nuke_WorkFileSaveAs.png b/website/docs/assets/nuke_tut/nuke_WorkFileSaveAs.png
new file mode 100644
index 0000000000..661f44632a
Binary files /dev/null and b/website/docs/assets/nuke_tut/nuke_WorkFileSaveAs.png differ
diff --git a/website/docs/assets/nuke_tut/nuke_WorkfileOnStartup.png b/website/docs/assets/nuke_tut/nuke_WorkfileOnStartup.png
new file mode 100644
index 0000000000..450589ee3a
Binary files /dev/null and b/website/docs/assets/nuke_tut/nuke_WorkfileOnStartup.png differ
diff --git a/website/docs/assets/nuke_tut/nuke_WriteNode.png b/website/docs/assets/nuke_tut/nuke_WriteNode.png
new file mode 100644
index 0000000000..5ce3e81aab
Binary files /dev/null and b/website/docs/assets/nuke_tut/nuke_WriteNode.png differ
diff --git a/website/docs/assets/nuke_tut/nuke_WriteNodeCreated.png b/website/docs/assets/nuke_tut/nuke_WriteNodeCreated.png
new file mode 100644
index 0000000000..b283593d6a
Binary files /dev/null and b/website/docs/assets/nuke_tut/nuke_WriteNodeCreated.png differ
diff --git a/website/docs/assets/nuke_tut/nuke_WriteNodeReview.png b/website/docs/assets/nuke_tut/nuke_WriteNodeReview.png
new file mode 100644
index 0000000000..68651cdd6c
Binary files /dev/null and b/website/docs/assets/nuke_tut/nuke_WriteNodeReview.png differ
diff --git a/website/docs/assets/nuke_tut/nuke_WriteSettings.png b/website/docs/assets/nuke_tut/nuke_WriteSettings.png
new file mode 100644
index 0000000000..cf00adbee6
Binary files /dev/null and b/website/docs/assets/nuke_tut/nuke_WriteSettings.png differ
diff --git a/website/docs/assets/nuke_tut/nuke_versionless.png b/website/docs/assets/nuke_tut/nuke_versionless.png
new file mode 100644
index 0000000000..fbb98c55e2
Binary files /dev/null and b/website/docs/assets/nuke_tut/nuke_versionless.png differ
diff --git a/website/docs/module_ftrack.md b/website/docs/module_ftrack.md
index 005270b3b9..8e3806828d 100644
--- a/website/docs/module_ftrack.md
+++ b/website/docs/module_ftrack.md
@@ -51,10 +51,7 @@ There are specific launch arguments for event server. With `openpype_console eve
- **`--ftrack-user "your.username"`** : Ftrack Username
- **`--ftrack-api-key "00000aaa-11bb-22cc-33dd-444444eeeee"`** : User's API key
-- **`--store-crededentials`** : Entered credentials will be stored for next launch with this argument _(It is not needed to enter **ftrackuser** and **ftrackapikey** args on next launch)_
-- **`--no-stored-credentials`** : Stored credentials are loaded first so if you want to change credentials use this argument
- `--ftrack-url "https://yourdomain.ftrackapp.com/"` : Ftrack server URL _(it is not needed to enter if you have set `FTRACK_SERVER` in OpenPype' environments)_
-- `--ftrack-events-path "//Paths/To/Events/"` : Paths to events folder. May contain multiple paths separated by `;`. _(it is not needed to enter if you have set `FTRACK_EVENTS_PATH` in OpenPype' environments)_
So if you want to use OpenPype's environments then you can launch event server for first time with these arguments `openpype_console.exe eventserver --ftrack-user "my.username" --ftrack-api-key "00000aaa-11bb-22cc-33dd-444444eeeee" --store-credentials`. Since that time, if everything was entered correctly, you can launch event server with `openpype_console.exe eventserver`.
@@ -64,8 +61,6 @@ So if you want to use OpenPype's environments then you can launch event server f
- `FTRACK_API_USER` - Username _("your.username")_
- `FTRACK_API_KEY` - User's API key _("00000aaa-11bb-22cc-33dd-444444eeeee")_
- `FTRACK_SERVER` - Ftrack server url _(")_
-- `FTRACK_EVENTS_PATH` - Paths to events _("//Paths/To/Events/")_
- We do not recommend you this way.
@@ -103,10 +98,12 @@ Event server should **not** run more than once! It may cause major issues.
`sudo vi /opt/openpype/run_event_server.sh`
- add content to the file:
```sh
-#!/usr/bin/env
-export OPENPYPE_DEBUG=3
-pushd /mnt/pipeline/prod/openpype-setup
-. openpype_console eventserver --ftrack-user --ftrack-api-key
+#!/usr/bin/env bash
+export OPENPYPE_DEBUG=1
+export OPENPYPE_MONGO=
+
+pushd /mnt/path/to/openpype
+./openpype_console eventserver --ftrack-user --ftrack-api-key
```
- change file permission:
`sudo chmod 0755 /opt/openpype/run_event_server.sh`
@@ -146,9 +143,11 @@ WantedBy=multi-user.target
- add content to the service file:
```sh
@echo off
-set OPENPYPE_DEBUG=3
-pushd \\path\to\file\
-openpype_console.exe eventserver --ftrack-user --ftrack-api-key
+set OPENPYPE_DEBUG=1
+set OPENPYPE_MONGO=
+
+pushd \\path\to\openpype
+openpype_console.exe eventserver --ftrack-user --ftrack-api-key
```
- download and install `nssm.cc`
- create Windows service according to nssm.cc manual
diff --git a/website/sidebars.js b/website/sidebars.js
index 3a4b933b9a..38e4206b84 100644
--- a/website/sidebars.js
+++ b/website/sidebars.js
@@ -18,7 +18,7 @@ module.exports = {
label: "Integrations",
items: [
"artist_hosts_hiero",
- "artist_hosts_nuke",
+ "artist_hosts_nuke_tut",
"artist_hosts_maya",
"artist_hosts_blender",
"artist_hosts_harmony",