Hi. I noticed that when working on wildcat tasks, we're presented with various projects, each requiring different workflows, Low workflow, EGG workflow, MAPLE workflow... and so on. The technical requirements are all there in the documents, but it's not the "what" that's missing, but the "why". Some of the workflows strict conditions don't make sense unless we get some sort of clarification as to why certain models need to be done a certain way. For example LOW workflow, for low poly models, is meant for real time, game engines, AR VR etc... but the EGG workflow doesn't make sense at the moment, and I think I'm not the only one, as I keep saying the same projects requiring EGG workflow keep being taken but put back in the list of tasks after a month or so, maybe it's time to update Wildcat's workflows documentation?
In order to post an answer, you need to sign in.