Ondřej Samohel

This shouldn't just depend on the artist. Produciton could put together things from different assets, for exports, and so on. Put together stuff like geo, looks, clothes, grooms, ...

> But who or where defines what goes together? That's mostly what I'm asking. Just to figure out the approach to implementation here. we thought about actually using Loader (or...

This needs to be fixed. And >And I'd prefer a studio wide setting to disable Create Render to actually mess with render settings in the scene altogether. shoud be addressed...

Found two issues on Windows: What I did: ```sh git clone https://github.com/OpenAssetIO/OpenAssetIO.git cd openassetio python -m venv .venv ./.venv/Scripts/activate.ps1 python -m pip install --update pip pip install pybind11[global] ``` I...

I've merged it together. One PR to rule them all.

Maybe we can add it as validator for asset name that interested pipelines can add family to. ```python import string import re asset_name = instance.data.get("asset") check_pattern = r"^[{}{}]".format(string.digits, string.punctuation) if...

I've noticed this during the integration step:  That means the results are two files - `OPC_s010_workfileModeling_v098.ma` and `OPC_s010_workfileModeling_v098.mb` - that seems to be a bit confusing. So I guess...

And the job in deadline still points to the original scene: 

So what about doing it like this: ```python import sys import os from openpype.lib import source_hash, run_subprocess ref_scene_name = "some_scene_file.ma" current_file = "current_scene.ma" # instance.data["currentFile"] script = f""" import maya.standalone...

btw is this PR ready for review? I suppose so. Switching from draft, but please correct me if I am wrong.