Wondering whether it is possible to keep the engine as is but then use custom hooks in the config that use the python API
I checked for you.
A few months ago we embarked on a little mission to see if a fully python engine would now be possible but we ran into various missing things in the Python API, one of which is the way UI’s are made.
Thsings may have improved since then but we decided not to move forward.
You can however run python commands in substance from the hooks of the engine 
Hope that helps?
We also fixed some bugs, here is our fork:
2 Likes
I’m currently trying to integrate tk-substancepainter in a distributed environment, but the repository seems focused of centralized setup. I’ve been adding the files from the repo to my distributed config, but I can’t see the icon in the desktop app, and I’m not sure why…
I’m a newbie to FPTR and still learning about it, though I’ve successfully integrated Unreal Engine in past few days. I would really appreciate any resources or guidance on how to approach this in a distributed setup.
I’ve also never used the Tank command and understand it might not be necessary in a distributed configuration. Any insights would be greatly appreciated!
Thanks in advance for your help!
The readme may be focussed on a centralized setup but you can definitely add it as a distributed config app.
Just define the location of the repo and version.
1 Like
Thank you for this! I was able to deploy it on our config. However when launching Substance I get a connection was lost error [Plugin - shotgun_bridge] Shotgun engine | Shotgun Substance Painter Engine connection was lost. Restarting engine...
Do you have any clues on why this could be happening? I did have to force the .exe file in Shotgrid software list for it to appear on SG Desktop in order to be able to launch so not sure if that could be contributing to it.
I have exactly the same issue. Leaving a comment to find a solution.
There’s a high chance the solution for tk-photoshop would work for tk-substancepainter if the frameworks were also updated and made compatible with the engine.
Did you find a solution for this? We’re attempting to integrate using the lola-post fork of tk-substancepainter. I had one successful launch of painter including the engine, however, subsequent launches result in the same issue: Shotgun Substance Painter Engine connection was lost. Restarting engine.
We’re working with Substance Painter v10.0.1.0 since the next releases introduce python3.11 and there are a new host of QT compatibility issues. I’d love to know if anyone has overcome these issues, as well.
Thanks!
1 Like
Okay, turns out this was just the engine failing to load (introduced by updating the compatibility_dialog_min_version setting to a float). FYI, run this in the console to start the engine manually to see your traceback error,
import sgtk
tk = sgtk.sgtk_from_path(<project path>)
ctx = sgtk.Context.deserialize(os.environ.get("SGTK_CONTEXT"))
sgtk.platform.start_engine("tk-substancepainter", tk, ctx)
1 Like