- over 1,000 free tools for The Foundry's Nuke
Note:
nuBridge for Nuke 11 does not yet include the tool detail page due to PySide2's incomplete implemtnataion of the QtWebEngine:
https://bugreports.qt.io/browse/PYSIDE-631
this will be updated as soon as PySide2 has been fixed.
Feature Highlights:
-
Access over 1,300 tools right inside of Nuke - no web browser required
-
Browse, search & filter in realtime
-
Filter by author or tool name
-
View html description pages
-
Download directly from inside of nuBridge
-
Manage which tools are loaded upon Nuke startup
-
Single gizmo & .nk files install automatically and show up in current session
-
Create and save lists of your favourites for bulk download (e.g. to quickly set up a new workstation)
-
Python callback to customise post-download behaviour (e.g. for quarantine/approval workflows)
- Available for Windows, OSX and Linux
Comments
does this system work in an enviroment with a common gizmo repository on a share, too?
Have a nice day!
Achim
yes. You can set the environment variable called NKPD_REPO_PATH and point it to a shared directory on your network. nuBridge will then utilise that rather than ~/Nukepedia
This will not replace your existing shared tool repo, but you can set it up to run along side it.
Have a look at the user manual for some more info (though I probably need to update that as well).
Cheers,
frank
First of all congratulations to you on release of nukepdia. I have been waiting for this more than 2 years.
Its very useful for people like me who are always scared to go into programming. Although when i am installing its giving me error saying "Below files could not be installed automatically please go to download area & install them manually.
could you please let me know whats i am doing wrong here.
thanks for the kind words. Yes, I have been trying to get this done for many years now so am quite happy it's been released into the wild.
The message you ares seeing appears when a download cannot be installed automatically because it is not apparent how it should be installed. Currently only .gizmo and .nk files can be installed automatically. There is no way of procedurally telling how python scripts, zip files etc should be prepared for Nuke to use them without looking and interpreting the contents.
I very much than we will see a package manager fr nuke to standardise how tools should be packaged for Nuke to be able to auto-install anything. With such a standard in place I would then be able to make nuBridge install many more files automatically.
I definitely intend to keep improving the installer to be able to install more tools automatically, but without the above mentioned standard it's impossible in some cases.
Can you think of a reason why nuBridge will not save it's position in a Workspace? I'd like to have nuBridge in a tab next to Properties, yet it does not open with the workspace, only an empty tab.
thanks
below is the xml that my workspace is using:
Indeed, I must have stuffed up something in the menu.py that prevents nuBridge from re-inserting itself into saved workspaces.
I will have a look...
I found the problem and it's a simple fix in nuBridge_osx64_v1.0.0/src/controller/menu.py
Please edit line 64:
from
nkpd_widgetInstance.addToPane()
to:
return nkpd_widgetInstance.addToPane()
I am trying to fix one other thing then release an update with the above in place.
Thanks for the report!
I have the following line in my init.py nuke.pluginAddPath('/Users/Addison/.nuke/nuBridge_osx64_v1.0.1')
But when I open Nuke it opens fine but without NuBridge, any ideas?
what has changed since it last worked?
Is the init.py you mention in your ~/.nuke folder?
When inside of Nuke, can you run "nuke.pluginPat h()" in the script editor (without the qutes) and check if the nuBridge plugin path is actually part of the list?
Sorry for the delay.
Of course I'm in the middle of production now :-D
nuBridge will automatically install single .gizmo files and single .nk files. Things like python code, zip files etc can't be automatically installed yet as there is no packaging system that would enable that. I do hope to work with the Foundry on tackling this challenge eventually though.
nuBridge is not dead, I have worked several years to get to this point, but unfortunately the Foundry have still not shipped the missing libraries with Nuke 11 that are required to run nuBridge, despite it being flagged as an issue in April 2017 (which resulted in the August projection at the top of the page).
I have done a lot of work trying to port nuBridge to run with the PySide2 /QT5 to make it compatible with Nuke 11 but the missing piece of the puzzle has to come from the Foundry and is unfortunately out of my control.
The latest Nuke 11 release claimed to have those libraries but when I checked they were still missing and I have had no reply from Foundry regarding this in almost a month.
Rest assured I am at least as frustrated as you are about this situation.
I am happy to reimburse people if they feel that this frustrating delay is too much of an inconvenience.
Cheers,
frank
I fully understand your dilemma, especially when you had a functional plugin (well, still functional for Nuke 10 that is) and not having all the tools to update it to their latest version of Nuke.
Honestly, I don't think anybody wants a refund because we think the setup is a great addon to the site and we believe in it.
The reason why I've posted today was, I haven't heard anything about the progress since last September. It would be great (even if it's redundant) to perhaps write that you or your team hasn't forgotten about it and STILL working on it. just something ;)
Maybe it's just me.
Hopefully, the Foundry will send the missing libraries out soon though.
I have used your prompt to at least update the wording at the top of this page now.
And you are right, I should at least send occasional updates to the nubridge mailing list, twitter and linked in to let people know it's not dead.
Fingers crossed it all falls into place soon!
There are a hand full of general challenges left in the migration to QT5 which I am working on now, and hopefully I can release at least a linux and windows version soon.
Nuke 11.1v2 does ship with the missing libraries but they are broken, which is PySide bug, so not Foundry responsibility.
I will endeavor to temporarily deactivate the details page (the tool web page content that shows up when clicking on a tool in the list), so that at least the rest of nuBridge can function in Nuke 11 until this has been fixed.
import nuke
if nuke.NUKE_VERSI ON_MAJOR < 11:
nuke.pluginAddP ath('/Users/fra nk/.nuke/nuBrid ge_osx64_v1.0.0 ')
https://pastebin.com/GJABpug9
I have two computers.
One of the successful installations can be used
Another error.. E:/software/nuB ridge_win64_v1. 2.0/src/control ler/init.py:err or interpreting this plugin
Detailed description:
Traceback:
file"E/software/nuBridge_win64_v1.2.0/src/controller/init.py",line 4, in
import nuke pedia # for logger
file"src\controller\Nukepedia.py",line 64 in init conterller.Nukepedia
file"src\view\MainWindow.py",line 6, in init view.MainWindow
file"src\view\D etailsPage.py", line 11, in init view.detailsPage
importerror:dll load failed
and forgive me for my terrible English
in your first post there seems to be a white space in the import statement, i.e.:
import nuke pedia # for logger
when it should be:
import nukepedia # for logger
If that is in your actual code it will certainly cause errors.
If that's not the reason, can you send me the details of the error to frank[at]nukepe dia[dot]com please?
that's my spelling mistake,sorry.
can i send details for you email ? this page some character looks error.
If so, can you start Nuke from a terminal with the verbose flag and email me the result?
Quote:It then freezes.
I will have a closer look, but in the meantime, can you try and comment out the line 4 in U:/.nuke/plug-i ns/nuBridge_win 64_v1.2.0/src/c ontroller/init. py
to see if this helps?!
I.e.:
Change this:
Code:
import Nukepedia # for loggerto this:
Code:
#import Nukepedia # for loggerCode:
import Nukepediain ./src/controlle r/init.py seemed to work, thank you.
I am using Windows 10 Pro x64
If you are on windows, try commenting out (or deleting) the lines "import logging" as well as the line starting with "logging" in the ~/.nuke./nuBride/init.py
There is some strange windows 10 issue that randomly seems to hang on these parts. I need to fix this when I'm back in the office as there have been a couple of people experiencing this by now.
Sorry about that!
frank
But there are only these line in init.py
"import Nuke
import os
if nuke.NUKE_VERSI ON_MAJOR < 11:
os.environ['QT_ PREFERRED_BINDI NG'] ='PySide'
nuke.pluginAddPath('./src/controller')
nuke.pluginAddPath('./src/view/resources/icons/nuke')"
remove or comment lines 2, 4, 9 and 16:
import logging
import Nukepedia
logger = logging.getLogger('Nukepedia.init')
logger.critical('INIT ERROR: {}'.format(sys.exc_info()))
If it's the same random windows 10 bug it will work afterwards.
Cheers,
frank
The few people that had reported this before could simply remove the lines in the src/init.py to do with logging (as mentioned above) to get it to run on windows 10. If this does not solve your problem and you cannot see any errors when launching Nuke from a terminal, please get in touch with me directly next month so I can try and figure this out once and or all. I'd be happy to do a TeamViewer session if possible.
Cheers,
frank
The file "init.py" was not found in plugin_path.
This probably means Nuke was not installed correctly
I'm NOT using Non-Commercial FYI. Any help?
My init.py....
nuke.pluginAddPath('/Users/Matt/.nuke/nuBridge_win64_v1.2.0')
I have the folder in my .nuke folder
that sounds weird. So the pluginAddPath command is in your ~.nuke/init.py, right?
And when you remove it the error goes away? Is there any more info in the terminal?
Sorry about the inconvenience, let me know any more info and I will do my best to get this up and running for you.
Worst case, can I use TeamViewer to debug this directly?
Cheers,
frank
RSS feed for comments to this post