In the addon file 3.4/scripts/addons/Substance3DInBlender/material/manager.py use a plain text editor (better to use Brackets or Visual Studio Code for this!) to comment out these lines (prefix with '#') a couple lines after "Initialize shader sockets" to disable the crashing code, as shown:
Simply update the official plug-ins by adding k30n1 changes from above to the official plug-ins: Your mileage may vary and this may not be a fully correct solution, but this seems to have fixed the plugin crash for me that started with Blender 3.4. Note that python is very sensitive to indentation! The new code should be very similar in indentation to the original version of the old code. (_socket, _socket)Įlif _socket = "output" and _socket not in grptree.outputs: If _socket = "input" and _socket not in grptree.inputs: # _items].outputs.new(_socket, _socket)Īfter those lines, put this alternate code that uses the preferred method from the developer site: # elif _socket = "output" and _socket not in _items].outputs: # if _socket = "input" and _socket not in _items].inputs: In the addon file 3.4/scripts/addons/Substance3DInBlender/material.py use a plain text editor to comment out these lines (prefix with '#') a couple lines after "Initialize shader sockets" to disable the crashing code, as shown:
Blender changed an internal Python API - here's what I edited to get the plugin v1.0.1 working with Blender 3.4.
0 kommentar(er)
