There is no equivalent of a savecopyscene in Softimage. I think copying an already saved scene to another location is the way to go. Any scripting language can do that without the need of the sdk, except for getting the current scene path. I know the workflow is different with Max but f.y.i. Softimage will not allow anybody to overwrite a scene once it's pick up by a node on the farm. In that case, the user has to change his scene file name if he want to save his scene.
On Thu, Jan 3, 2013 at 7:52 PM, James Vecore <[email protected]> wrote: > Hello Everyone,**** > > ** ** > > I’m new to the mailing list. My company (Pluto Post) is getting started > with Softimage and ICE. My first task was to setup a custom Qube render job > for V-Ray for Softimage. The issue I have run into is that there seems to > be no way to save a scene and NOT change the current scene’s save location. > 3dsmax has a very simple maxscript command to do this and we used it in our > custom max submit. The reason we use SaveCopyAs is that we like to save a > copy of current scene at submission time as a snapshot of the scene in the > output folder. This way we always have a copy of the scene exactly as it > was when the render was submitted and the user is free to continue to > save/version his current scene at his or her discretion without messing > with the render job. **** > > ** ** > > I could not find a way to do this in softimage without double saving > (which I want to avoid, especially with 1GB+ files). I only see two command > related to saving: SaveScene and SaveSceneAs. I also searched the C++ sdk > for anything that would let me achieve what I want and I could not find > anything. My current solution is to save the current scene to the current > path and copy the scene file to the destination. This is not ideal since > the user may not always want to overwrite their scene save before render > (especially our artists that use to the existing 3dsmax workflow). I could > also force a version up save, but that is also not ideal and will generate > many more save versions that necessary.**** > > ** ** > > Obviously it is not a deal breaker if SaveCopyAs is not possible, but it > would help ease our transition if anyone has any idea how to accomplish it. > **** > > ** ** > > Thanks,**** > > ** ** > > -James**** >
