Skip to content
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

Report when no connection could be made to Resolve on AYON menu launch #13

Open
2 tasks done
BigRoy opened this issue Jul 31, 2024 · 0 comments
Open
2 tasks done
Assignees

Comments

@BigRoy
Copy link
Contributor

BigRoy commented Jul 31, 2024

Is there an existing issue for this?

  • I have searched the existing issues.

Please describe the feature you have in mind and explain what the current shortcomings are?

When using Resolve Free (which is not supported) or for any other reason the script can't connect to your Resolve or Fusion session it would be great if we could still report that message nicely to the user.

Currently the only hint in the logs is:

>>> [ Assigning resolve module to `ayon_resolve.api.bmdvr`: None ] 
>>> [ Assigning resolve module to `ayon_resolve.api.bmdvf`: None ] 

Which means that it can't connect to Resolve/Fusion here

How would you imagine the implementation of the feature?

When that results in None values we are maybe best off logging a way more explicit error message that can also hint things like:

This may happen if you using the free version of Resolve. Only Resolve Studio is supported because we need network API access which the free version of Resolve does not support.

Or whatever to make it clear that it is very likely due to that.

Are there any labels you wish to add?

  • I have added the relevant labels to the enhancement request.

Describe alternatives you've considered:

Or we may even just throw a pop-up in their faces as a Qt dialog so it's even clear without the logs.

Additional context:

No response

@BigRoy BigRoy added the type: enhancement Improvement of existing functionality or minor addition label Jul 31, 2024
@dee-ynput dee-ynput removed the type: enhancement Improvement of existing functionality or minor addition label Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants