[QUOTE=Mambo4;24304]Have I thanked everyone for their replies yet? thanks!
We hired a new Technical Director who has better perforce chops and things are being smoothed out.
My current concern is about tools exporting content to the right spot when everyone can potentially create their own work space configuration.
I like parallel source and production directories. My export tools ‘figure out’ where to place the exported asset by replacing the root level folder in the path string
so
“<source_art_path>\characters\heroGuy\mesh\heroGuy.max”
becomes
“<production_art>\characters\heroGuy\mesh\heroGuy.fbx”
but perforce lets a variety of work spaces be created all over the place,
and I need a reliable way to determine what is <source_art_path> and <production_art>.
based on either:
1.) make artists choose the right spot manullay
2.) somehow getting info from perforce
3.) enforcing a convention for work spaces on the art team.
3.) seems like the obvious approach. If so, can I script the creation of the workspace to force artists to adapt a common workspace configuration?
If so what scripting language? .bat with command lines? C# api? pyhton?
any experience you can share would help.[/QUOTE]
As part of our tool setup process, I end up mapping everyone’s source depot to a virtual drive using the subst command.
It ends up causing some headaches when scripting perforce, because perforce still thinks the files are located elsewhere, but overall it is much easier to maintain then our old system of trying to account for every absurd way that someone can build a workspace.