Hey Tim,
I just checked, and SaveSceneAs works as expected on my side.
The only scenario I can think of where this might happen is if your
compiledPath is either illegal or does not point into a valid Softimage
project.
But if I understood you correctly that can not be your issue as the Save
Dialog opens in the correct target folder and also lets you save
successfully, right?
If you just execute those two lines directly from the Script Editor does it
also behave in the same way?
Cheers, Martin
--
Martin Chatterjee
[ Freelance Technical Director ]
[ http://www.chatterjee.de ]
[ https://vimeo.com/chatterjee ]
On Wed, Mar 1, 2017 at 12:11 PM, Tim Bolland <tim_boll...@hotmail.co.uk>
wrote:
> Hi, I had a script that would compile a filepath and run a SaveSceneAs
> command with that filepath correctly parsed. It used to be that the
> command in the script would save with the correctly and the PPG used to
> generate the filepath would close. Now however when I run the
> Application.SaveSceneAs() command, I get a file pop-up opening on the
> correct directory with the correct name. This is really frustrating because
> I already know the location and the name and I just want it to save, I
> shouldn't need to reaffirm this.
>
>
> What's strange is this script didn't use to do this before, it would work
> correctly and just save. Any ideas what's going on?
>
>
> sCompiledPath = "...\\sceneName.scn"
>
> Application.SaveSceneAs(sCompiledPath, 0)
>
>
> Regards,
>
>
> Tim
>
>
>
> ------
> Softimage Mailing List.
> To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com
> with "unsubscribe" in the subject, and reply to confirm.
>
------
Softimage Mailing List.
To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com with
"unsubscribe" in the subject, and reply to confirm.
