From 4bc31b040673917bfacad4590b91fe50eb70244e Mon Sep 17 00:00:00 2001 From: Ynbot Date: Thu, 9 May 2024 15:49:55 +0000 Subject: [PATCH] [Automated] Release --- CHANGELOG.md | 71 +++++++++++++++++++++++++++++++++++++++++++++ openpype/version.py | 2 +- pyproject.toml | 2 +- 3 files changed, 73 insertions(+), 2 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 1e419797eba..c3776b56b82 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,6 +1,77 @@ # Changelog +## [3.18.10](https://github.com/ynput/OpenPype/tree/3.18.10) + + +[Full Changelog](https://github.com/ynput/OpenPype/compare/3.18.9...3.18.10) + +### **🆕 New features** + + +
+Arnold Scene Source Raw - OP-8014 #6182 + +This PR is to try and re-instate some flexibility to the `Arnold Scene Source` family, which got restricted by https://github.com/ynput/OpenPype/pull/4449The proxy workflow introduced was actually broken due to https://github.com/ynput/OpenPype/pull/4460.We can now have any nodes directly in the instance set, which should be backwards compatible of the `Arnold Scene Source` before the overhaul in https://github.com/ynput/OpenPype/pull/4449.The `content` and `proxy` sets works as well, but not at the same time as the raw nodes directly in the instance set. There is a validator in place to prevent using a single instance for both workflows.Now the question is whether we should have this as a single family or split somehow?The workflow of having nodes directly in the instance set, compared to `content` and `proxy` set, can be documented, so I see this as most a matter of terminology.`Arnold Scene Source` makes sense to have as a family, but only if its a the raw output with little to no validation, similar to `Maya Scene`. But then I'm not sure what to call the other family that has more of a workflow in place, which is similar to `Model` and `Pointcache`. + + +___ + +
+ + +
+Nuke: Push to project - AY-742 #6245 + +This introduces the "Push to Project" menu item in Nuke.This enables users to push the current workfile to a different project and copy all files from Read nodes to a `resources` folder next to the workfile. Containers will be baked to normal Read nodes.Also gizmos will be baked to groups. + + +___ + +
+ +### **🚀 Enhancements** + + +
+Max: Implementation of Validate Render Passes #6138 + +This PR is to enhance the current validator of checking the render output before deadline publish. It does the following: +- The validator `Render Output for Deadline` would be renamed as `Validate Render Passes` +- The validator would not only check on the invalid render output folder but the invalid filename of render passes. + + +___ + +
+ + +
+Max : Optional validator to check invalid context data #6198 + +Add optional validator check on invalid context data for asset and task in 3dsMax + + +___ + +
+ +### **🐛 Bug fixes** + + +
+Maya: Account for no Alembic overrides. #6267 + +Fix for if no overrides are present in `project_settings/maya/publish/ExtractAlembic/overrides` + + +___ + +
+ + + + ## [3.18.9](https://github.com/ynput/OpenPype/tree/3.18.9) diff --git a/openpype/version.py b/openpype/version.py index 66ad9861ff0..e2e2ae21650 100644 --- a/openpype/version.py +++ b/openpype/version.py @@ -1,3 +1,3 @@ # -*- coding: utf-8 -*- """Package declaring Pype version.""" -__version__ = "3.18.10-nightly.2" +__version__ = "3.18.10" diff --git a/pyproject.toml b/pyproject.toml index 8a714e6b06f..ae46de341cf 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -1,6 +1,6 @@ [tool.poetry] name = "OpenPype" -version = "3.18.9" # OpenPype +version = "3.18.10" # OpenPype description = "Open VFX and Animation pipeline with support." authors = ["OpenPype Team "] license = "MIT License"