-
Notifications
You must be signed in to change notification settings - Fork 10
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
Bug with breakdown2 v0.4.0 #79
Comments
Hi @dovanbel thanks for this report. Could you raise this issue on Autodesk support, please? |
Hi @staceyoue |
FYI : I added a log output in tk-framework-qtwidgets\v2.12.2\python\filtering\filter_menu.py Got this :
The filter on the last line has no display_name etc |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I filed an autodesk bug report, but to be sure :
With tk-core v0.21.4, tk-multi-breakdown v.0.4.0 and tk-framework-qtwidgets v2.12.1
In Nuke, when launching breakdown2 (I configured it as panel_mode = False), I get the spinning wheel icon in the interface, and I see this traceback in Nuke's console :
The spinning wheel goes away and is replaced by the scanned items when I change the 'group by' dropdown menu selection. I can do updates but triggering them creates a second log of the aforementioned traceback. When I close the breakdown window the update is actually done (not before)
My config section of the breakdown2 app is 'normal' :
settings.tk-multi-breakdown2.nuke:
hook_scene_operations: "{config}/tk-multi-breakdown2/tk-nuke_scene_operations.py"
panel_mode: False
published_file_filters: []
location: "@apps.tk-multi-breakdown2.location"
The hook scene operations is a custom hook based on the basic nuke hook. It works fine with previous versions of breakdown2
The text was updated successfully, but these errors were encountered: