Nothing failing for me yet - as mentioned the project only got dropped on my lap and I had been told it wasn’t compatible - and assumed that was correct. My first instinct was to research alternatives (hence topic).
I do have a pretty significant code base that is reliant on studio conventions, processes and tools that I’ve been building for over a decade - obviously there have been plenty of start overs in that time.
We don’t use shotgun (I wrote my own that’s been adopted) and I’m not looking to implement another tool with a large feature set that overlaps what I’ve already written (cohesion/automation across toonboom, maya, 3dsmax, nuke, unreal, unity, after effects and various rendering systems etc)
The pipeline definitely isn’t “pyblish” only - but I do love to have it in our pipeline as I’ve found it’s a great way for me to control what the artists are doing and ensuring QA with validation/integration etc.
Perhaps I should have tested whether pyblish_maya wasn’t compatible first as advised so I didn’t appear foolis on posting, but I didn’t have an install yet (start planning tmrw) and there was pretty limited info available online given the release date of 2022.
I suppose it’s always good to know what else is out there but, if I can get it running tomorrow that’s by far the best outcome.