Changelog

AYON Core 1.10.0 brings the desktop tools closer to the AYON web app. The Launcher, Workfiles tool, and Loader now share the web app's look and many of its interaction patterns, so if you already know your way around AYON in the browser, the desktop tools should feel familiar too.

Consistent UI Enhancements

The Launcher, Workfiles tool, and Loader now share the color theme of the AYON web app, along with a new folder and task tree that shows each entity's status.

• Performance Improvements: This update also includes performance improvements across the Loader and Publisher.

• Statuses in the folder and task tree: Every folder and task shows its thumbnail and status icon. Hover over the icon to see the status name.

• Launcher: Along with the new tree, the filter for showing only tasks assigned to you has a new icon, at the top right.

• Workfiles tool: Uses the same tree, so you can see folder and task statuses while opening and saving workfiles.

• Notifications: Toast messages follow the same visual language as the web app.

  

Meet the New Loader/Browser

The Loader, which is the same tool as the standalone Browser, got the most updates in this release. Its products area now works like the Products page of the AYON web app:

• Table and cards views: Switch between a detailed table and a cards layout with large thumbnails.

• Filter and Group By: Filter versions, for example to show only the latest, and group them by product, status, or attributes such as Product Group.

• Customize and Views: Use Customize to adjust the layout, such as the row height in the table or the card size in the cards view, and use the Views button at the top left to switch between saved views. These work the same way as on the Products and Versions Page.

• Multiple selection: Select several versions, and their thumbnails are combined into one preview, each shown as a diagonal slice.

The slicer on the left lets you choose how to find versions: by Hierarchy, Reviews, or the new Lists. Select a review session or list to see the versions it holds.

Changelog

Enhancements

• Browser: Added a Lists slicer category with list folders. #2167

• Browser: Group versions by product attributes, such as Product Group, using a new nested Group By menu. #2132

• Browser: Set the product group of selected products with Ctrl+G. #2138

• Browser: The filter bar adds Select all, Clear, and Toggle buttons, and an Excludes toggle to filter out the selected values. #2140

• Browser: The version context menu opens much faster, and selecting versions no longer blocks the UI. #2130

• Browser: The cards view loads only the fields its cards show. #2134

• Browser: Clicking an already selected version no longer starts new background queries. #2142

• Publisher: Faster reset with many instances. #2107

• Publishing: The two hero version integrators are merged into one IntegrateHeroVersion plug-in. This also fixes hero versions not being created for instances with only trait-based representations (broken since 1.9.11). #2117

• Load placeholder: Added hero version support. #2110

• Settings: Complex core settings now have descriptions. #2121

• UI: Overlay messages now match the style of the AYON web app's toasts. #2155

• UI: Disabled checkboxes are drawn faded. #2133

• UI: The project combobox uses the Low style by default. #2158

• UI: Task rows no longer show the task type in the label; the full label is in the tooltip. #2157

• Loader: Rich text in loader labels no longer blocks mouse clicks. #2124

Bug fixes

• Browser: Hero versions are shown and filtered correctly. #2156

• Browser: Fixed views stuck loading in hosts whose log output fails from worker threads, such as DaVinci Resolve on macOS. #2137

• Publisher: Fixed the active toggle in the List view, which re-enabled disabled instances on publish. #2151

• Publishing: Errors are now caught when cleaning up explicit directories. #2168

• Scene Inventory: Fixed the tool showing empty when a container's project is missing. #2112

• Scene Inventory: Fixed containers with the same representation id in different projects using the wrong project's data. #2114

• Load: Fixed the outdated containers check failing when a container's project is missing. #2113

• Nuke Assist: Opens the workfile on launch, like Nuke and NukeX. #2125

• Launcher: The workfile path is normalized before it's added to launch arguments. #2126

For developers

• AbstractTemplateBuilder.open_template accepts a preset. #2162

• EnumDef items support an icon and a tooltip. #2120

• Fixed a segfault in UI tests. #2150

Get the Update

1. Install AYON Core 1.10.0 from the AYON Market.

2. Duplicate your production bundle and edit the copy.

3. Select Core 1.10.0, then create the bundle.

4. Set the new bundle to Staging to test it, then to Production when you're ready.

For more information, see Install Addons.

Control exactly who can see and edit what's in the Planner. Set access per project for events, and lock down individual attributes so sensitive information stays with the people who need it.

🗓️ Event Access

Decide who can view or edit events based on the project they belong to.

• Project Events: Give users access to events through the access groups they have on that project. Someone can be an editor on one project and a viewer on another.

• Studio Events: Set separate access for events without a project, like studio meetings or holidays.

• Access Levels:

  • Editor: Create, move, update and delete events.

  • Viewer: See everything about the event, but can't change it.

  • No Access: The event is redacted. Users can see that something is booked, but not what it is.

For example:

• A freelancer on your commercial project can manage their own bookings there, but only sees "busy" blocks for everything else.

• Leads can edit events on their own show and view the rest of the schedule.

• Everyone can see studio holidays and meetings, but only production can change them.

Required Project: If a user has less than Editor access to studio events, they must select a project when creating an event. This makes sure every event they create lands in a project they can actually work on.

🏷️ Attribute Access

Set who can see or edit each event and resource attribute. Give access to everyone, specific users or access groups.

For example:

• Day Rate: Hidden from artists, visible to supervisors and editable only by producers.

• Budgeted Hours: Visible to leads on the project, editable by production only.

• Client Notes: Kept private to the supervisors on that project.

You can now create recurring events for regular bookings, meetings, working hours, and other repeated events.

🗓️ Flexible Recurrence

Create recurring events for things like:

• Daily: Studio opening hours, morning production meetings, or daily reviews.

• Weekly: Department meetings every Wednesday or a weekly production sync.

• Weekdays: Book a resource from Monday to Friday for a defined period.

• Selected days: Schedule a supervisor every Monday, Wednesday, and Friday.

• Monthly: A production meeting on the last Friday of every month.

• Nth weekday: A review session on the first Monday of each month.

• Intervals: A meeting every other Wednesday.

✏️ Flexible Updates

Changes to recurring events can be applied to the current event, following events, or the entire series. You can also override an individual occurrence without changing the rest of the schedule.

Individual events or entire recurring series can be deleted when no longer needed.