2026: project creation and OCIO support - #145
Open
miravassor wants to merge 1 commit into
Open
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.
Suppressed comments (1)
client/ayon_flame/hooks/pre_flame_setup.py:221
RuntimeError("App arguments were not solved")is instantiated but never raised, so a missing/emptyapp_argswill silently continue and likely fail later in a less clear way. This should beraise RuntimeError(...).
output = run_subprocess(args, **process_kwargs)
self.log.info("wiretap_com.py output:\n{}".format(output))
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Flame 2026 removed Stone+Wire volumes and replaced SynColor with OCIO. Project creation was not possible.
Projects are now created directly under /projects on 2026.
The OCIO config path is passed to flame as OCIOConfigFile when the project is created. It comes from the OCIO env var, which core's OCIOEnvHook resolves.
→ subsequently, this PR is dependent to this ayon-core PR adding flame to OCIOEnvHook hosts.
SetupDir is dropped from the project settings on 2026. Flame resolves that path itself and rejects the write with "Setups folder is read only", which would abort the launch right after the project was created.
Setup needed
Application env for the flame 2026 variant:
You also need the usual
Core > Color Management > OCIO configprofile, with flame in its host names.Worth knowing
Colour management is only applied when the project is created.
Tested on flame 2026.1.1, new and existing projects, plus a check that the SetupDir write really is rejected.