0

Core update and shell context

Hi

I've just updated to the new core update (v0.14.69), and I have a question about context. Previously from a shell, I could call the tank file from a specific Project and run an app using the Project context.

eg projectSpecificTank Project 101 launch_asset_manager.

However the new update has removed the need to specify the project context as it is already inferred by the fact I have called the tank file for that project configuration. But I don't seem to be able to run / see the apps available to run from a project context.

projectSpecificTank launch_asset_manager  -- this wont work

projectSpecificTank Asset @81234  launch_asset_manager -- this will work but isn't in the context I want.

 

How do run a project specific app though the shell now? running the projectSpecificTank command returns this at the end, 

Your current context ('Empty Context') does not have a matching Sgtk Environment.

 

I have realised that I can still run a project specific app by calling main/non project specific tank file and specify the Project.

 

thanks

 

Phil

 

 

 

2 comments

  • 0
    Avatar
    Permanently deleted user

    Hello Phil!

    Thanks for reporting this! We heard this from a couple of clients, so we have pushed a change relating to this, but it is still pending QA in the app store. Here's the change: https://github.com/shotgunsoftware/tk-core/commit/4f89e9397a473c90736aa1e0587430260e492836.

    If you want to try it out before we release it, you can download the v0.14.73 tag directly from github - hopefully it will fix the issue for you!

    Also, another way to explicitly run the project context would be to pass the project path rather than the project id, e.g. projectSpecificTank /path/to/project launch_asset_manager.

    Apologies for the inconvenience and hope this gives you a couple of ways to solve this problem. Let us know how it goes!

    Thanks!
    Manne

  • 0
    Avatar
    Philip Scadding

    Thanks Manne

    That answers my question, I wasn't sure if it was a bug or not. I'll wait for the full release.

    thanks

    Phil

Please sign in to leave a comment.