Changelog
Help
Dev portal

We love your Feedback!

Please tell us how we can make AYON work better for you. You can also report bugs or ask questions if our Help Portal is not helping.

If you’re looking for developer resources, you can find all of them on our Developer Portal

Feature Request: Pinned Comments & Threaded Replies in Task Activity Feed

Summary: I’d like to propose two enhancements to the comment/activity feed section in AYON’s web task view: Pin Comments — ability to pin one or more important comments to the top of the activity feed (e.g., briefing notes, important decisions, client feedback). Threaded Replies — ability to reply directly to a specific comment in a thread, keeping conversations organized and contextual rather than a flat list. Current Behavior: The activity feed currently shows comments in a flat chronological list. There’s no way to group related replies under a parent comment, or highlight critical comments for visibility. AYON does support Comment Categories for visibility control, but there’s no threading or pinning mechanism. Problem This Solves: In a busy production task with many comments from artists, TDs, supervisors, and clients, it becomes very hard to: Track which reply belongs to which discussion point Keep important notes (like a brief or approval status) visible without scrolling Proposed Solution: Add a “Pin” icon on comments (visible to users with sufficient permissions) that anchors the comment to the top of the feed Add a “Reply” button on each comment that nests responses under it in a collapsible thread, similar to Slack threads or Discord replies Use Case Example: A supervisor pins the shot brief at the top. Artists reply in threads to specific feedback comments. The feed stays clean and everyone knows what’s actionable. Who Benefits: Studios with large teams, review pipelines, and client-facing workflows — especially when combined with the existing Comment Categories feature. I’m happy to discuss further or provide mockups if helpful. Would love to know if this is on the roadmap!

#youssef#

💡

Feature requests

Accepted

Annotations Type Text on Image

Hello, our VFX supe pointed out that they’re very used to typing text when annotating frames during reviews, but currently AYON doesn’t have a text tool. It’s different to typing in the comment, as it means being clearer about to which part of the image the text relates. And on a given frame multiple blocks of text might be required. They also mentioned being able to add arrow shapes to save drawing them.

splidje

💡

Feature requests

Houdini Publish of usd product : Collect Usd Layers Error

The collect USD layers validators error with a very simple scene with the 0.9.7 houdini and 1.8.4 core addon version. Traceback (most recent call last): File "C:\Users\olivier.o\AppData\Local\Ynput\AYON\dependency_packages\ayon_2602231726_windows.zip\dependencies\pyblish\plugin.py", line 528, in __explicit_process runner(*args) File "C:\Users\olivier.o\AppData\Local\Ynput\AYON\addons\houdini_0.9.7\ayon_houdini\plugins\publish\collect_usd_layers.py", line 86, in process child_sublayers = list(layer.subLayerPaths) ^^^^^^^^^^^^^^^^^^^ AttributeError: 'NoneType' object has no attribute 'subLayerPaths' The same error happen if i use a vanilla houdini reference node to load the .usd asset

Olivier Osotimehin

3
🐛

Bugs

Auto-create first workfile at DCC start, by loading or copying scene

In Blender, Ayon's Workfile Builder was replaced by the Templated Workfile Build, since this : https://github.com/ynput/ayon-blender/pull/239 This feature disappeared, but we still need it : the first time a Blender task is launched, we want the first (001) workfile to be created by automatically copying an existing template file. The new behavior is not automatic at DCC start, and when it is manually triggered it is an import (instead of a load or a file copy).

Alain Xerri

1
💡

Feature requests

Hiero effects don't load in Nuke anymore

Since the update of the core where we have a “product type” and a “product base type” we can’t load effect anymore in nuke. I’m trying to figure out where the problem lies but not quite sure if we need to fix it in Hiero, Nuke or Core. If i go back to a older “core” version where “Product base type” isn’t introduced it works again.

Robert Okker

2
🐛

Bugs

More standard available Variables

We need to have more available variables for in the pipeline. Like current Folder name (like shotgrid has shot, sequence, etc etc) For most programs, like houdini, nuke, maya etc you can get around it with getting the “AYON_FOLDER_PATH” split it in ptyhon and source what you need. But again, not artist friendly, an “AYON_FOLDER_NAME” or parent folder or even shot/ sequence etc would be really helpfull. But for let say something like OCIO witch is just a YAML and can’t do any splitting, it’s now impossible to setup a proper OCIO config with show/ shot luts. The only way to use this now is create your own custom pre-launch hook. But this can be problematic, or cumbersome if you want to use the Batch deliver etc. And this is such a massive basic feature to be able to configure your OCIO that this shouldn’t have to be done by manually creating custom pre-hooks etc.

Robert Okker

6
💡

Feature requests

Tabs bar

Space for tabs within the existing bar (not just in the Settings) is limited. If you have a lot of addons that add their frontend part, this bar space can be easily exhausted. Currently, it cuts, effectively hiding any overflowing tabs. Can be easily reproduced just by resizing window width. We could collaps tabs to dropdown menu if real estate is missing, or just add it as the left-most item, or even wrap them on new line.

Ondřej Samohel

💡

Feature requests