Skip to main content
Participant
April 26, 2023

Substance 3D in Blender: [Code_Response.toolkit_not_running_error] Error while updating the Substanc

  • April 26, 2023
  • 10 replies
  • 1961 views

Hi!

Im on a Mac trying to install the plugin but when i try to install the integration tools it shows me this message , can you help me please?

10 replies

Adobe Employee
December 21, 2024

Hi @fire24180811lydl , in your case it looks like you may be on Mac correct?
If so, you'll want to make sure that you're not downloading with Safari as that unzips the addon file and messes with some quarantine stuff when Blender tries to open it. Instead download with Firefox or Chrome, or disable the open safe files option in Safari. 


If you haven't already, I would also try to remove the integration tools manually and reinstall them in a new Blender sessions, as that reset solves most of the tools issues to do that, delete the Substance3DIntegrationTools folder from the following directory

  • Windows: C:\Users\(username)\AppData\Roaming\Adobe
  • Mac: /Users/(username)/Library/Application Support/Adobe/Substance3DIntegrationTools
  • Linux: /home/(username)/Adobe/Substance3DIntegrationTools
Participant
December 16, 2024

Hello ! 

 

I have the same issues here. I'm on Blender 4.2 and i've download the last version of the pluging (2.1.1 for the addon and the integration tool). I can install the addon but can't install the integration tool. 

 Here is a screenshot of the terlinal when i try to install the integration tool. 

 

Thnak you for your help ! 

Adobe Employee
August 27, 2024

Glad to hear it!
We'll document this on our add-on troubleshooting page while we expand support.
Do let us know if you have any other feedback.

 

Happy Blending!
Aldo

Participating Frequently
August 27, 2024

Good grief!
Yes that works!! 🙂

Thank you so much.

Adobe Employee
August 27, 2024

@abstract_mentor5EFA  Knowing it's on Linux does help. The add-on is intended to work primarily with CentOS distors, so if you are on another flavor of Linux you may encounter issues like this. We're looking to expand support where possible.

That being said, another member of the community on Discord did share a fix that worked for them. Could you try the following?

 

"For anyone else trying to run on Arch or other distros, this is just an installation error. To fix it, install the blender plugin, use it to install the integration tools (which will fail). Then delete the files installed in ~/Adobe/Substance3DIntegrationTools/ except for "version.txt". Finally, unzip the Substance3DIntegration tools .zip into ~/Adobe/Substance3DIntegrationTools/ and restart blender. It should work now."

 

Aldo

Participating Frequently
August 27, 2024

Thanks for getting back to me Aldo.

Unforutnately I am still getting the same error and have been using the latest plugin(s)

I am on Linux, does that help understand why I might be getting the error still?

Adobe Employee
August 27, 2024

Hi @abstract_mentor5EFA , this issue should be fixed in the latest version of our plugin here.
If you still encounter it then we can inspect your console log for a more detailed readout of the error that may pinpoint the cause.

On Windows, this can be done easily by navigating to the top menu bar in Blender and choosing Window > Toggle System Console.
On Mac you will need to launch blender from the Terminal app using the following code:

cd /Applications/Blender.app/Contents/MacOS
./Blender

Make sure that "Blender.app" matches the directory name in your applications folder.

Once that is done, try re-installing the plugin with the console log open and share a screenshot of the log here when the issue is encountered.

 

Best,
Aldo

Participating Frequently
August 24, 2024

Hi I am having this error over a year later, with Blender 4.2

Did you ever find the solution you were working on?

Thanks!

Yann5E1A
Participating Frequently
April 8, 2024

Hi,
I have the same problem on my Linux. If you need some feedback for the resolution, just let me know.

Community Manager
April 28, 2023

Hi, This is a known issue and we are currently working on fixing it. Please expect an update from us soon.