Repository navigation
Help client_plugins
Launch Batch Render with the film button beside the project selector in the main window. The account menu also lists enabled client tools available to your groups. Launching does not open Configuration; errors appear as notifications. Disabled, denied or unavailable plugins have no launch action.
Open Configuration -> Client plugins after signing in and selecting a project. These tools run in Handler. The project's original TACTIC server stores and publishes their releases; TACTIC Stream is not required.
Click Refresh to list plugins. Clicking a row only selects it. Use its Launch button to open the tool; an already running tool offers Show window. The main-window film button and account-menu actions remain direct launch commands. Enabled makes that plugin available for this client and server/project; it does not launch it. Disabling does not interrupt a running queue. The list shows the available release and, while open, the running release. Before launch Handler checks the current server version and your group access. An open plugin keeps its version; close it and open it again to use an update. A changed server/account/project does not reuse another context's cache or access. Keep your session stable while a render queue is running.
Build plugin package… creates a ZIP for publishing a desktop plugin on the server. A Batch Render package includes its Python code, native interface, web panel, release description and checksums. Python remains source code; this does not compile an EXE. Building alone does not install or publish an update, start rendering or change user settings. A compatible plugin update does not require rebuilding the whole Handler application.
This is an administrator or plugin-author tool, not a normal launch command. If you already have a ready-to-publish ZIP, skip building and publish it directly.
- Edit the Batch Render sources at
plugins/batch_renderin the Handler source checkout. Do not edit the managed installed copy in a client profile; it belongs to the updater and is not the development source folder. - Open Configuration -> Client plugins, select the plugin row and click Build plugin package…. Without a selection the button is disabled; the dialog shows the selected plugin name.
- Enter a new three-part version of the plugin, for example 1.3.1. This is not the Handler application version. The field starts empty.
- Click Build ZIP. In the first folder dialog choose
plugins/batch_renderitself: the source folder withplugin.jsondirectly inside it. Do not select the whole Handler checkout, the installed plugin copy or a ZIP file. Choose sources manually; the code in theirplugin.jsonmust match the selected plugin. A different plugin source folder is rejected. - In the second dialog choose an output folder outside the source folder,
for example
plugin_releasesbeside the checkout. Do not save packages inside the plugin sources: their files would enter subsequent builds. - Wait for the ZIP-created message. This example produces
th_batch_render-1.3.1.zipandth_batch_render-1.3.1.zip.sha256. Publish the ZIP; the adjacent checksum file lets you verify its integrity.
Select the folder with plugin.json at its top level, for example:
batch_render/
plugin.json
entry.py
controller.py
ui/
web_assets/
The builder packages files from that folder and its subfolders for the original legacy TACTIC server. No compiler or separately installed Python is required. Cancelling a folder selection publishes nothing. An existing ZIP with the same name is not overwritten; use a new version for a changed release.
- Check the connected server address and selected project. Publication uses the current connection and project; building a ZIP does not change them.
- Click Publish ZIP…, select the ready-to-publish
th_batch_render-1.3.1.zipand confirm publication. A file namedth_batch_render-1.3.1-source.zip, if supplied, is a source archive, not a release for this button. Extract its sources before building. - Users receive the published release automatically on their next plugin launch, provided it is enabled and their groups allow it. There is no need to reinstall Handler or manually copy code to each workstation.
- An already open Batch Render keeps its current code. Let its queue finish, close the Batch Render window and launch it again to receive the update. Manually modified installed files block replacement; preserve your changes separately and resolve the reported conflict.
To roll back, publish a previously built ZIP of the required version and reopen the plugin. Keep tested release packages outside the installed code folder. Rolling back code does not undo completed renders or server data changes.
BUILD_BATCH_PLUGIN.bat is an alternative builder requiring Python 3.
The modular plugin includes a native render queue and its own web control panel. Its original
stream/batch/dispatcher_runner group access rules also control plugin launch;
existing legacy buttons and scripts continue using their own original paths.
Packages contain executable desktop Python. Publish trusted code and keep secrets, settings and tickets outside source packages. Legacy web routes may expose package source publicly; group launch restrictions are not source-code encryption or a sandbox. A download/checksum/compatibility error prevents loading the new code. Actual Maya/Redshift rendering needs separate validation on your workstation.
Start … automatically is a separate checkbox for each plugin. Only checked, enabled and permitted plugins open after sign-in and project selection. It does not apply to every installed or enabled plugin. The option belongs to the current server/project. Batch Render restores its queue paused; use Start queue to render.
Installed code is in plugins/batch_render under this client's profile folder. There are no protocol, server, project or version directories. Reopening checks server permissions and updates this one folder. A running tool keeps its code; close it before updating or opening it for another server/project. Settings are separate: settings/batch_render.json, settings/batch_render_window.json and settings/batch_render_queue.json. Each file keeps account/server/project entries inside JSON so another context cannot restore your queue. Version numbers remain package metadata, not local directory names. Previously installed source folders are not configuration files and need not be copied to a new client.
Batch Render's search and status filters update immediately without another server request. Empty and unfamiliar render statuses are available as filters. Web panel opens its web panel; copy the protected LAN link for another computer. The render settings select its port and access protection. An occupied port is reported in the window; close the plugin to stop its web panel. The native summary uses Tactic Frame; the browser panel remains a separate remote interface.
Adding an episode discovers its shots without changing the server task status or starting Maya. Click Start queue to release staged episodes, even if an older queue was running when you added them. Run only this and Test render are explicit start commands. Restored queues always open paused.
A new profile shows all configured render statuses except Проверен and No render status. Saved filter choices are preserved. Shift-click selects a shot range; Ctrl-click toggles a shot. Ctrl+A selects the current episode's shots, arrow keys move focus and Shift+arrows extend the range. Space or a selected shot's checkbox includes/excludes the selection. The episode checkbox changes all editable shots and shows a mixed state for partial inclusion. Completed, active and unconfirmed-save shots are protected. Drag the grip to reorder, including excluded shots. Ordinary selection preserves both lists' scroll.
The native and web panels use the Handler interface language and the same item heights, previews, indentation and house theme roles. Project titles and statuses remain unchanged. Selection updates only the changed rows; render output is coalesced without dropping log events. Close/reopen an already running plugin for a published update to take effect.
TACTIC-Handler · Releases · Issues · English · Русский
English
- Home
- Installation
- Feature tour
- User guide
- Assistant
- Dashboards
- Knowledge Base
- Maya / Shelf
- Plugins / Плагины
Русский
- Главная
- Установка
- Обзор возможностей
- Руководство пользователя
- Помощник
- Дашборды
- База знаний
- Maya / Shelf
- Plugins / Плагины
Development / Разработка