rdurnin Posted September 25, 2014 Report Share Posted September 25, 2014 We did a cleanup on our test project and the problem went away. I'm not sure how, but I believe we must have created Shots without registering them properly. Pardon me,r Link to comment Share on other sites More sharing options...
Mattias Seebergs Posted September 26, 2014 Report Share Posted September 26, 2014 Not sure where you have everything set up now but I'd suggest that you set up the API and Actions on a central place, you don't need to have it running on each and every machine. You can get a user account by id by calling:ftrack.User(id=<id>)Let me know if anything is unclear and you wan't me to explain anything further. Mattias Link to comment Share on other sites More sharing options...
rdurnin Posted September 30, 2014 Report Share Posted September 30, 2014 The Shots are registered now, and are returning correct types from the 'task' objects being returned by the handler. I should mention though that, it was the user account that started the event watcher process which Ftrack expected to find in it's user list: In our case, the Windows login and the Ftrack user name were different, and it was causing problems. Thanks,r Link to comment Share on other sites More sharing options...
Mattias Seebergs Posted October 1, 2014 Report Share Posted October 1, 2014 Ah ok. Did you set the LOGNAME environment variable? (http://api.ftrack.com/developing/getting_started.html) Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.