Openers are now fully functional in Blender tasks, allowing predefined actions to run automatically whenever a scene is opened. The system includes the RunChecks feature, which launches checkers in the background.

One of the integrated checkers is Check Sort From Range, designed to identify issues related to frame range ordering. When triggered, users can apply a fix directly from the interface. These checks currently run in a secondary thread, though due to Blender API limitations, execution may be moved to the main thread if stability issues arise.

The panel now allows users to search by name or episode and displays each asset with a preview image, category, asset type, associated episode, and task.

The last task linked to the asset is selected by default, but users can easily change it before confirming. Once imported, the asset appears with all relevant preview and file data ready to use.

A new update improves the traceability of ingest-related tasks within Kraken. Tasks automatically generated during the ingest process for refedits and plates now use clear, descriptive names.

Refedit tasks are named “Refedit Ingest – [SHOT]”, while plate copy tasks are named “Plate Ingest – [SHOT] – [PLATE]”. This makes it much easier to visually identify what is being processed and to monitor the task status—whether it’s pending, in progress, or completed.

Clips no longer need to include the plate name—it's enough for the clip name to match the shot name. The system automatically assigns the role of each clip (refedit, main plate, or additional plate) based on the track's name. Only one track can be set as refedit and one as main plate per shot. When a new assignment is made, any previous assignment of the same type is automatically deactivated.

The panel now includes a resolution selector, allowing users to define whether the shot resolution should come from the main plate, the Hiero sequence, or the project’s technical specifications. Additionally, a color publishing fix ensures that the .mov files now reflect the correct color settings configured within Hiero.

Users can open the panel, refresh checkers, run them individually or by group, and apply fixes when needed—all directly inside Blender. The panel remains functional even after closing and reopening the scene, confirming stable integration.

An issue in the shot creation panel has been fixed where new shots were always being added to the last available sequence, with no option to choose the destination. A new sequence selector has now been introduced, allowing users to define exactly where the shot should be created.

The ingest system has been upgraded to support track-based logic, removing the need to embed plate names into clip filenames manually. As long as the clip name matches the shot name, the ingest tool can now assign the correct role to each file based on its track name.

Tracks named refedit, plate source, or those containing the word main are automatically recognized and assigned as the reference or main plate. Only one of each is allowed, and any remaining clips are treated as additional plates. Users can manually override these assignments if needed.

The system has been updated to improve error handling when accessing unavailable paths. Instead of showing a generic message, it now includes the specific path that could not be reached.

Kraken now features visual progress bars within tasks, providing a quick and intuitive way to assess task completion at a glance. This update improves clarity by displaying task advancement graphically, eliminating the need to check individual status fields manually.

Kraken now includes a new control mechanism to manage whether users are allowed to download files from the system. This feature is linked to a specific property within the Naming Convention model and can be centrally managed by data or infrastructure teams.

New feature now available that enables automatic task creation when generating new assets. When this option is enabled, the system will automatically generate all required tasks as soon as a new asset is created—no manual triggering needed.

The showroom tool now includes advanced sorting capabilities, allowing users to organize content by type, asset ID, filename, or by episode, sequence, and shot association. This update gives users the flexibility to adapt the review view to fit narrative structure, technical breakdowns, or file naming conventions.

A new automated logic has been implemented to manage the Delivery process, fully integrated with task status flow in Kraken. When a Quality Control task is moved to the “internal approval” state, the system automatically triggers an action that gathers the latest published render version from Compo and moves it to the appropriate Delivery path.

The system has been extended to allow users to execute custom actions directly from entity tables such as those for assets. While this capability existed structurally, it is now fully operational and available for production use, with project-specific logic attached.

A new validation step has been introduced in the review creation process for both shot and asset tasks. From now on, when attempting to create a new review, the system will prompt the user to confirm the action before proceeding.
If the user validates the action, the new review is created (for example, R3), and the previous one (such as R2) remains as the prior version. If the user does not confirm, the process is automatically aborted, and no new review is generated.

The production control panel for shot tasks has been updated with a fix to the bulk task creation system. Users can now reliably select multiple shots and generate tasks with a single click, applying the appropriate logic engine rules and initial task states defined in the pipeline.
The selection workflow has also been improved. Selecting shots individually or an entire sequence is now possible by clicking their header.

A new action has been added to the Openers system: RunChecks, now available for both Nuke and Maya. This feature automatically runs checkers whenever a properly set up file (e.g. a PYBLEN file) is opened. If any checks fail, the Checkers window is launched immediately.

A new Precomp system is now available in Compo tasks. This feature allows users to render parts of the node tree before the final render, helping to optimize performance in complex Nuke scripts.
The workflow involves creating a Write node configured to output to a dedicated “Precomp” subfolder.