I think it is some related bug. maybe I am wrong.
Hi there!
I’m getting this error with the latest BW version:
Python: Traceback (most recent call last):
File "N:\Blender\Scripts\addons\BakeWrangler\nodes\node_tree.py", line 1024, in execute
bpy.ops.bake_wrangler.discard_vertcols(node=self.node, tree=self.tree)
File "N:\Blender\Builds\stable\blender-3.5.0+stable.1be25cfff18b\3.5\scripts\modules\bpy\ops.py", line 113, in __call__
ret = _op_call(self.idname_py(), None, kw)
RuntimeError: Operator bpy.ops.bake_wrangler.discard_vertcols.poll() failed, context is incorrect
I thnink one day i managed to solve it by adding a color attribute, but i can’t seem to get it working anymore
Its an issue with the class template order overriding the nodes poll function. I’ve actually already fixed it, I just didn’t push the update out.
Even though there are bunch of bug reports on the issue I think it’s ‘working as intended’.
Did this only start with Blender 3.5? Your error is saying context incorrect, the context expected is context.area.type == "NODE_EDITOR" and context.space_data.tree_type == "BakeWrangler_Tree"
No it also happens on previous versions (at least 3.4 and 3.2.2).
Yeah i don’t get why the context is wrong as i use the bake button from the node tree as anyone would.
I’ll try to make a bake with only BW addon enabled. Last time it solved an issue.
Is there any way to turn this off when I click Bake? I went through the addon prefs but none of them did it.
Mhhhh… ok; with a factory startup it works…
Will investigate 
I second this. Those mouse over popups that immediately disappear when leaving it with the mouse make no sense. If I click bake, I expect it to bake. I don’t want to confirm the action with another OK button.
Instead, I would just use the ‘INFO’ type of status bar report to tell the the user “See console for progress information and warnings”. And if there is an error, I would once again just use the ‘ERROR’ type status bar message 
1 Like
Happens for me as well in both 3.5 and 3.6.
The fault seems to lie with the “Messages to Text Editor” setting, which opens up a window over the node editor. When the cursor is over it, the context is switched. Turning that off fixed it for me.
@Darknoodles & @Piotr_Adamowicz if its the popup window I can change the order of operations, but also the context check is probably not needed so I could just drop it entirely. Though it would be interesting to confirm the issue.
@obsurveyor There is no option to turn the confirmation off, but it seems reasonable enough to add one!
2 Likes
I disabled what @Piotr_Adamowicz suggested and it worked
Good to know! I’m going to remove those context checks since I don’t think they are needed any…
This unfortunately leads to option creep. Sooner or later with this approach, the addon will have a space shuttle cockpit control panel in place of settings.
Better question is if the confirmation popup is truly warranted. If there’s a valid reason to not print information, warnings or errors using Blender’s built in report function for printing information, warnings or errors.
Especially frustrating is the wrong default syndrome. Where some setting defaults to a certain state but most people expect the other state. A great example of this is where 3 years ago, pretty much every Blender introduction tutorial started by the person instructing you to go to preferences and switch selection from right click to left click.
So if you decide to have the option to disable confirmation, then it’s also important to consider what the default state of that option should be, and if you conclude that the default state should be for confirmations to be disabled, then it’s reasonable to consider whether to have the option at all.
The default settings are all based around “what will let a new user figure out how to use this”.
So, the confirmation box is really only there to tell new users if they did something wrong and what it was without them having to find the log the file. If I just used the blender notifications I can’t really tell them what the problem was.
But once you know how to use everything the confirmation just becomes an extra click…
The problem is how it’s implemented. Blender has those terrible confirmation popups where they are tiny and disappear as soon as mouse cursor leaves them. It has happened to me so many times already that I clicked bake, switched window to something else to continue work, came back after expecting the bake to be done, and realized in horror that I moved the mouse so fast I didn’t click the OK button.
You can easily tell new users if they did something wrong by printing a big, red warning in the status bar. That’s what the status bar is for.
I mean look at it this way. Entire rest of Blender uses the status bar to tell the users if they did something wrong. For example if operator fails because they did not have active object of something. If the users are capable of noticing that, while they use Blender, then they will certainly be able to notice that also with your addon, since you addon is hosted inside Blender.
And it makes all the less sense to display that dialog when everything is correct, and they did nothing wrong.
There’s a big “Bake” button. Everyone expects that after clicking it, the bake starts. No one expect additional popup, and there should not be any. Especially not if there’s no error.
1 Like
You could always split the difference and just show it the first time Bake is clicked and then don’t show it again until the addon is reloaded(or once an hour or if Bake is clicked multiple times under some time limit, etc.), if the checkbox you’re adding in the prefs isn’t checked. I get the need to inform new users about where they need to go to see things but new users aren’t new users for very long(at least in regards to that popup) so it doesn’t need to be seen all that often, certainly not every time you click Bake.
The thing I was trying to avoid, which I’ve found with other addons, is you press a button and nothing happens and you don’t know why. I did only want it to appear when there was a problem, but at the time I guess I couldn’t figure out a way to do that…
I will revisit it and see if I can have it only popup the box on there being an error or warning.
So I want to do a redesign of the preferences and settings stuff.
For settings, having a bunch of separate nodes isn’t doing it for me. I’m thinking that they should all just be on a single large node? I still want to hide some things under Advanced arrows, but I think the current hidden things are not all the best choices. Color for example shouldn’t be hidden and instead should probably just be a button that turns on or off the alpha channel?
What do people think about this?
For preferences I’m thinking that instead of most of the current stuff, there would be button in the side panel or on the node that sets its current state as the default preferences. That could also lead into having templates that allow you to configure a settings node instantly from a list of previously saved states…
Thoughts?
Also I updated the versions available. Latest one has full functionality for vertex color output (hopefully) and various bug fixes to do with Blender 3.5 and other issues people raised here 
Hi @netherby
I have a quick question! How can I call bake all from a script? We tried but we have problems with bpy context 
, thanks in advance for your help!