Jakub Trllo

Current state adds a lot of stuff we're trying to avoid and remove with OpenPype refactor. So I expect this feature will change in near future a lot and will...

> But @iLLiCiTiT will surely have a better opinion on this. I'm glad you've mentioned me, but I'm not the one who should decide. From my point of view it...

First shot ideas `Selection From scene` or `Mark Scene selection`.

> It's trickier due to this being a host specific implementation and we might not want to expose it for all hosts? (For some it might even be irrelevant, etc.)...

Already removed OcioConfig submodule is added back to repository.

> And should maybe set OPENPYPE_LOG_NO_COLORS in FusionAddon.add_implementation_envs like is done for Maya? Yes. That's not "modifiable" env in settings, you just want turn it off to not show wierd...

> wonder if the context is collected only once at start of publishing and then it is not required anymore. Even Integrate is taking Context data from collected, right? @iLLiCiTiT...

It looks like you've removed optional marks for frame key. Default publish template looks like this: `{root[work]}/{project[name]}/{hierarchy}/{asset}/publish/{family}/{subset}/{@version}/{project[code]}_{asset}_{subset}_{@version}.{ext}` `{@frame}` is replaced by content in `project_anatomy/templates/defaults/frame` to make sure frames have same...

It's not related to settings but to how they're applied on plugins. It is still an issue and with addons it will be much bigger issue then it is now.

We have that kind of plugin overrides for a long time. It's in OpenPype settings, but we rather explicitly define what can be changed and what type of value it...