-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chore: Use AYON entities #165
Conversation
…se-ayon-folder-entity
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works in Max now.
It also does happen in the develop so not related to this PR |
Yup, likely has to do with the review instance 'attaching' itself to the model main instance in this case so likely "removing" itself and merging the instance with the model main instance or alike. Likely that does not happen if the review instance is not attached. |
Cool, I no longer see previous errors.
|
Didnt find any issues in |
Cool, I no longer see previous errors.
|
Tested again and can confirm that has been fixed! |
Tested in Houdini, So far so good.
Regards workfiles: I hit an issue when switch context using workfiles tools.. And, I was able to reproduce the same behavior in develop. |
I'll dm you, but won't be fixed in this PR if happens in develop too. Please check |
Nuke is now working also with Farm rendering and publishing |
In Resolve following error occurs if I try to start Creator from Ayon menu:
It seems to be unrelated from this PR subject. Update: |
In Resolve during loading this had been blocking the loading. Again, I am not sure if it is related to this PRs changes.
EDIT: |
Resolve is working fine now. I was testing publishing and loading and workfiles and all was fine in the end. But during inventory management there was an issue and this is something I could not figure out. It is happening during update to different version of loaded container. It seems that
|
Should be fixed, please revalidate. |
Changelog Description
This PR is removing
ayon_core.client
and replaces it's usage withayon_api
calls. That changed structure of all entity types from OpenPype compatible to AYON.Additional info
I did what I could to change every line of code which are working with entities to work properly, but I've probably missed something so please report anything you hit. And I didn't test most of the changes.
Entity structure changes sometimes required change of logic and function arguments. Some of those changes happened on the spot, so if you hit a change that is questionable then please comment. I'll mention few questionable changes myself. In some cases I did more changes than just change of query and used keys because it helper me with other changes, or I couldn't resist to refactor few lines.
Major changes
ayon_core.client
. Its functions were replaced with function fromayon_api
.initialize_ayon_connection
inayon_core.lib.ayon_connection
to initialize ayon connection. Initialization of the connection happened automatically when a call inayon_core.client
happened. It is automatically called whencli.main
is called and on host install or ayon plugin install, so all important places should be covered. This affects local root overrides so it is important to happen as soon as possible in any process that might work with Anatomy.get_product_name
).get_current_asset_name
>get_current_folder_path
,get_current_project_task
>get_current_project_folder
."asset"
and"subset"
keys, but"folder"
and"product"
.Notes
I was very struggling with changes in unreal host. There is a lot of "asset" naming that is not related to OpenPype asset, and also there was a lot of unusuall way of working with representations and what is stored to container data. If it is working as expected now then it's fine, details can be changed when unreal will be in separated addon.
Questions
FunctionChanged the function to expect task name and task type instead of task entity.get_product_name
now expects task entity, but from api point of view it might be better to expecttask_name
andtask_type
as that's what is really needed for the function.initialize_ayon_connection
is really important and I'm not sure if should stay inayon_core.lib
, I couldn't find more suitable place and name.Testing notes:
Please consider that some of the bugs may not come from this PR, as was found out many times in previous PRs.
Keep in mind that this PR will completelly break compatibility with almost any other addon, so ftrack, shotgrid, kitsu, slack etc. won't work.
Test every host, every addon, every possible action that can be done should be tested. Create, Publish, Load, Manage in scene inventory. Open old scene, with previously created instances and loaded containers, all of that should be working as nothing changed (the scenes should be from AYON mode).
All tools should show correct data and should work as expected. Console should not log any errors.
Hosts
Other