

I have a hard time believing Adobe would release the “stable” version of this add-on without testing and fixing something as huge as node connections, but then again the word “ocurred” is misspelled in their error message, so their review process may not be incredibly rigorous in regard to this particular freebie. Is this a bug/feature, or are these industry-standard best practices? In either case, I’d prefer to save some PNGs in 8-bit. Each format seems to be locked to one value – TGA to 8-bit, PNG to 16-bit, JPG to 32-bit – which confuses me. This may be more of an aside than a bug, but another issue I have is the bitdepth of the image formats. Of course, I can connect the nodes manually and BAM – working material, so I have a workaround. sbars from Adobe,, and more, and all of them doink out. sbar into images just fine, and fills the material with nodes, but it doesn’t connect any of the nodes.

RuntimeError: Error: Cannot add socket to built-in node sbar file I get repeats of these two error messages: Error: Substance 3D in Blender: An error ocurred while setting the material įile "/Users/***/Library/Application Support/Blender/3.4/scripts/addons/Substance3DInBlender/material/manager.py", line 192, in create_material Installed them fresh into Blender 3.4.0, no problem, but when I load a.

