- User Since
- Nov 13 2018, 8:59 AM (87 w, 15 h)
Sun, Jul 5
I'm having this problem as well.
Unfortunately, replicating it seems a bit random, but the problem is still easy to run into.
Tue, Jun 30
I don't have Windows to test this on so I don't feel comfortable submitting a fix, but I'm pretty sure this is the problem:
The error is caused by the 'Relative Path' option being enabled by default.
Python's os.path.relpath function, which is ultimately called, doesn't work across drives on Windows.
If you don't want to wait for a fix to be commited, disabling 'Relative Path' option each time in the file browser's N-Panel should fix it.
Apr 26 2020
Apr 22 2020
Yes, trying to pass properties like you can to operators was the way I thought to do it at first. Then I found layout.menu() returns nothing and doesn't take any extra arguments to pass anything of use. I looked for a while and couldn't find any other way to sneak a value to the category class.
Apr 20 2020
Apr 11 2020
Replace a removed unused variable as it won't be unused after D7399 is committed.
Mar 28 2020
Ctrl+Shift+Click on a node in a group raises an error when the group output has no sockets.
Mar 23 2020
Mar 21 2020
Oops, really need to remember to include closed tasks in my searches.
Mar 19 2020
"Handle" the error caused by third-party engines changing the node lists after Node Wrangler is enabled.
Instead of displaying a blank menu and printing errors to the console, display a message asking the user to re-enable Node Wrangler.
Ideally I'd just re-enable it automatically, but I've no idea how to do that.
Mar 11 2020
Updated naming to be slightly more clear
Procedurally generate and register the Switch category submenus instead of keeping class stubs.
The only downside of this I've found is that external render engines that register custom node categories (like Radeon ProRender) must be enabled before Node Wrangler or the switch menu will be empty and print errors to the console.
Mar 10 2020
Mar 3 2020
Feb 28 2020
Here's an image I tested with (though I tested with quite a few others) along with a blend file with it packed in.
Opening the latter instantly shows the yellow box.
I did a clean rebuild along with completely deleting the config directory and it still happens.
Reverting the mentioned commit fixes it.
Are you sure you're on the right commit? It was the very latest when I ran into it.
If you still can't reproduce it, I'll wait for the official builds to catch up to see if it's a problem with my build.
Jan 22 2020
Jan 21 2020
Jan 13 2020
I'm pretty sure this is the same problem I've had on my local (Arch) builds for a while now (a year or more?).
Except the problem doesn't occur using release builds from blender.org.
And seeing that the Arch pkgbuild does it's own build instead of downloading, makes me think it's a build environment problem and might be out of the developer's scope.
I'd suggest downloading from blender.org to see if you still have the problem.
Dec 12 2019
Fixed in 03bd44a1ca49
Dec 11 2019
Can confirm and it affects Weight, Vertex, and Texture Paint modes as well. Object and Edit mode are fine.
Oct 25 2019
Sep 29 2019
The committed workaround breaks meshes/objects. Trying to move the default cube in object mode just moves the origin and not the mesh.
Opening a file saved pre-commit moves all meshes (but not object origins) and empties to the world center.
Sorry if this isn't the place to report it and I'll open a new bug report if it's just on my end.
(Linux / 2070)