Refresh Mesh Output gives error, and no output mesh about sorcar HOT 11 CLOSED

I installed linux today and tried out Sorcar:

It's working fine, even if I manually add a Shader node and make it the active one.

The only difference is that my blender version is in factory state (except for theme change).
So, this error may be occurring due to other addons. If it's possible, would you be able to test out Sorcar on a fresh install of blender? (or just archive the blender configs temporarily)

from sorcar.

Ok, this has officially become the worst issue ever...

Yes, this might be similar to #26, but Sverchok isn't the source of the problem. Other users have this issue (#42 & #43) as well. I still haven't encountered it and that makes it difficult for me to debug. One user got it solved by deleting the blender settings folder in AppData, so maybe you can try this addon in blender with factory settings (not recommended though)

"ShaderNodeCombineXYZ" is a node usually present in "Shader" node tree ("World" section):

The "sc.execute_node_op" operator takes the active node in the tree and calls "execute()" function. In windows, this works fine and the function is called on "Refresh Mesh Node", not on the "ShaderNodeCombineXYZ" node.
Somehow, the active node in your case is not the Sorcar node and that is why the error pops up (because ShaderNodeCombineXYZ node doesn't have any definition for "execute()" function)

from sorcar.

UPDATE:

Ok I created a new account on my MacBookPro. Downloaded Blender 2.79 clean install from Blender.org. Then I installed Sorcar add-on. The mesh output creation works! And no ShaderXYZ error.

Indeed probably it is clashing with another add-on. We don't know what it is yet. But pretty annoying indeed.

Could it be Animation Nodes or Sverchok or others? I might try and install other addon that I use one by one.

from sorcar.

Ok I created a new account on my MacBookPro. Downloaded Blender 2.79 clean install from Blender.org. Then I installed Sorcar add-on. The mesh output creation works! And no ShaderXYZ error.

Thank you so much for confirming it!
I won't close this issue until I've figured out how to bypass that error. One of the ways in which an addon can interfere with another is execution of a modal operator (every frame/mouse event). Even Sorcar uses one (for realtime preview), but its scope is limited to SC node tree.

from sorcar.

Wow, this is the same issue maybe related to Sverchok ??

#26

from sorcar.

The problem came back, maybe not because of Sverchok because I turned it off, but I also have Animation Nodes... hmm 🤨

from sorcar.

What is exactly ShaderNodeCombineXYZ...

from sorcar.

Hmm... I have to try on a new Apple account. Will see.

But don't close this yet.

from sorcar.

I've encountered this error repeatedly. Typically I can create one, sometimes two simple node Trees. See Attached Image. Then when I go to create the Third node tree and hit "Refrresh Mesh" it gives the error. It only gives the error once; but then fails to execute the node tree from that point forward.

I am running it on a Macbook Pro, and I uninstalled Animation Nodes and Sverchok just to be sure. It didn't help.

I sure hope this can be fixed; as I would like to use this node method as my primary way of modeling; (I make product designs, etc),but this error is standing in the way as it stands.

*Another things to note is that my Node trees are very similar; if not exact duplicates with different mesh selected in the initial 'Custom Mesh' input node. Another interesting thing: It seems that some of the earlier created objects sometimes dissapear after creating new node trees. I did move the input and the generated mesh into a new 'Collection' after creating it; before making a new Node tree setup. I sometimes wonder if moving items around/Visibility/Collections might be causing some kind of conflict.

Hope this helps.

from sorcar.

Sorcar v3 beta is now released: https://github.com/aachman98/Sorcar/releases/download/v3-beta/sorcar-v3-beta.zip

from sorcar.

Improved the system a lot...
Hoping that the new version doesn't run into this sort of problem. Closing this issue for now.

from sorcar.