You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
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:
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:Or whatever to make it clear that it is very likely due to that.
Are there any labels you wish to add?
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
The text was updated successfully, but these errors were encountered: