I'm not sure I see the benefit of having a project for each shot and could lead to some issues referencing outside of the project structure if you are using relative paths to keep the project portable in case it needs to be remounted somewhere else. I believe the only file that needs to exist in a directory to make it a valid XSI Project is the hidden xsiproject file. >From there you can have the sub-directories laid out the way you want.
You can create a dummy project to create the xsiproject file which you can store somewhere (maybe in an addon with your pipeline tools). Delete that project directory. Then another script that creates the directory structure and copies the xsiproject file into the project's root folder making it play nice with Softimage. I did this at the last studio I was at and worked quite well and made it easy to simply run a command with some arguments that named the root project folder and a file path where to create the project and have all of our custom folders setup without having to do it all by hand for each of the new projects that came in. I had the directory structure laid out in an XML file so pretty much anyone could go in and tweak it if needed. As for the unfold double UV sets I can only suggest to check that the Unfold operators are frozen out and maybe also deleting the "Unfold" properties that may still be living on the meshes. -------------------------------------------- Eric Thivierge http://www.ethivierge.com On Wed, May 2, 2012 at 11:07 AM, Nick Angus <[email protected]> wrote: > Hi Folks, **** > > ** ** > > I am slowly but surely porting my facility over from Maya to XSI, it will > be a tricky process as I traverse the pro’s and cons (many more pros of > course!)**** > > Our directory structure is currently broken into two categories, Global > and Shots. Global has an XSI project which contains all assets, and Shots > contains an XSI project (per shot) where we do the > layout/animation/lighting.**** > > I am curious as to what best practice is in this case, is it going to > cause problems referencing models from a separate project for instance?*** > * > > ** ** > > The main reason for this question is a strange (and not very > re-producible) problem we are having on referenced models where we get a > second blank set of UV’s. I have checked the Delta and they don’t seem to > be being created post referencing, but they are also not in the original > model file, so it stands to reason that they must be being created post > reference! **** > > Referencing is the area I most need to catch up in, so it may be a symptom > of my knowledge gap as well. It may help to note these uv’s were created > with the built in unfold tool, and are named as such, I do recall having > trouble at one point with unfold but I can’t remember if it was related.** > ** > > ** ** > > Cheers, Nick**** > > **** >
