I have been working with the story window to edit motion clips together.
Once edited, I process the tracks to a new clip and save that motion as an external file. (let’s call it exportTracks.fbx )
I may overwrite exportTracks.fbx many times as I continue to edit in story.

I have discovered, though, that if exportTacks.fbx becomes read-only at any time (through a windows process, user process, maya process, etc), motionbuilder will error and not overwrite the file.

Now here is the interesting thing. In such a case it seems that:

- mobu will ask you if you want to overwrite the existing file but,
- mobu will not inform you that the file is read-only
- mobu will not inform you that there was an error
- mobu will continue as if the export process was successful.

The only point at which I found out that something was amiss was when I used the exported data and saw the error. I had to go to the file itself to discover that it had, at some point, become read-only.

Any thoughts?

Hi Jim,

when you say:

I may overwrite exportTracks.fbx many times as I continue to edit in story.

you mean: making the clip writable and adding keys to it?

which version of Motionbuilder are you using?

on the latest version when you try to make clip read-only or export clip in the story, on a clip that is made read-only in windows, it will warn you that you cannot do this operation and ask you to use another name for your file.

is this the behavior you are expecting?

GF

I’m going to throw a theory out here:

Is it possible that the Windows environment is getting “stale” file permissions info from a Linux-based server where the files live?  Is something like Samba in use here?

Just trying to help debug things with you.
Thanks!