- Fri May 07, 2010 5:07 pm
#323436
Hello,
I am looking to achieve the following workflow:
- author a 'master scene' in Studio, models, materials, etc
- I'd like to be able to specify a folder in the file system, which contains a bunch of image files.
- Maxwell would then look through the image files in the folder, taking each one replace a given "target" image file already existing within the scene, and then export an MXS named similarly to that artwork file.
Basically, I want to create a bunch of MXS files where the only difference is one image in one material, and do so by providing a folder full of files. Ideally I could also have it export an MXS for two different cameras in the scene.
In looking through the scripting reference, the only path related functions seem to be associated with setting SCENE paths and the like, not material map paths.
So my questions are:
1. can this be done within Studio? I know I can script Maya to do this upon export but would like to remain 3d platform agnostic if possible.
2. Is the scripting reference comprehensive? Are there any additional path-related functions?
I am looking to achieve the following workflow:
- author a 'master scene' in Studio, models, materials, etc
- I'd like to be able to specify a folder in the file system, which contains a bunch of image files.
- Maxwell would then look through the image files in the folder, taking each one replace a given "target" image file already existing within the scene, and then export an MXS named similarly to that artwork file.
Basically, I want to create a bunch of MXS files where the only difference is one image in one material, and do so by providing a folder full of files. Ideally I could also have it export an MXS for two different cameras in the scene.
In looking through the scripting reference, the only path related functions seem to be associated with setting SCENE paths and the like, not material map paths.
So my questions are:
1. can this be done within Studio? I know I can script Maya to do this upon export but would like to remain 3d platform agnostic if possible.
2. Is the scripting reference comprehensive? Are there any additional path-related functions?
mo cores, mo problems