Perforce Integration

[rob]

Hi there!

There are some limitations in our 2014 implementation that makes it more of a proof of concept than something we’ve seen studios successfully use in production. The implementation requires running a daemon that polls the p4 server and also needs everybody to have the depot checked out to the same path on each machine.

The thing we are considering (from the roadmap) is a big iteration on perforce integration to make it more flexible and easier to setup. As an official feature it should work with minimal configuration out of the box, rather than requiring a lot of heavy lifting to get going.

That said, there are studios that have successfully implemented p4 hooks for our loader and publisher, which can be simpler to setup. You can see this thread for a few more details:

Help setting up perforce integration

The perforce framework isn’t worth using. It’s much more maintainable to roll your own at this point. Create a generic hook that has syncing and checkout functions in it. Use that as the base hook for any tk-multi-workfiles2 and tk-multi-loader hooks. A publish plugin can handle submitting files. I create items for the scene and any textures or other files you want to submit. Accept any file that is currently checked out and I always accept the item for the current scene. Validate makes s…