New post
0

Guide for integrating Shotgun Desktop with current SGTK?

Avatar
Jacob Medendorp
None
Follow

I downloaded the Shotgun Desktop app for Windows, but as soon as I put the site information in, I'm getting an error:

Error starting the Toolkit, please contact support.

"NoneType" object is not iterable.

If I launch the app again, I get:

Error starting the Desktop engine, please contact support.

Cannot create a Configuration from path 'C:\blahblah\AppData\Roaming\Shotgun\<studiowebsite>\site' - this path does not belong to an Sgtk Project!

I know that I will need to get the Desktop engine, but I would like to test this in my own Pipeline Configuration and not in our studio release area.  How will it know which pipeline config to use?

Are there any guides for setting up with app with projects that are already using SGTK?  And using the inherited studio configuration?  We'd like to start testing this as soon as possible.

Thanks!

-Jacob

Date Votes

1 comment

  • 0
    Avatar
    Rob Blau

    Hi Jacob,

    Sorry, I think you may be hitting a bug where the bootstrap logic for the application fails if there is an existing toolkit install in the default PYTHONPATH.  Do you have your systems setup like that?  If so, if you run the desktop without that path in your PYTHONPATH, does the error go away?

    The desktop engine will setup a new configuration linked to the Template project.  By default, the configuration is self contained, will be kept in your AppData area, and will be auto-updated by the desktop app itself.  Because of this the install will leave your studio configuration alone.

    For the project setup, if you have multiple configurations available to you, once you switch into a project in the desktop app, the menu in the upper right of the screen will show the configuration choices you have.  You can do all of your setup of the desktop in one of those and then push it out when you are ready.

    There is a migration that installs the desktop engine into an existing toolkit project and copies the apps from the tk-shell engine over to the new engine.  That is the easiest way to get up and running, but if you want to do it manually, then from an existing config's point of view the tk-desktop engine is an engine just like any other.  You can use the tank command line to install it and add apps to it, then update the project environment's configuration to get it to behave like you want.

    Here is a link to the desktop configuration settings: https://support.shotgunsoftware.com/entries/95442947

    Let me know if any of that didn't make sense and I can provide more details.

Please sign in to leave a comment.