Notifications
Clear all

[Closed] Scene flagged as dirty

Hey guys, we have a bunch of scripts that are running when a file is loaded. I’m trying to pin down which one is flagging the scene as being “dirty” and thus requires a save. Is there a way to find out which script/function is the culprit without going through each and everyone one?

Example:
I load file.max
I immediately go to close file.max, i am prompted “would i like to save changes”, though nothing has changed.

Thanks.

6 Replies
1 Reply
(@denist)
Joined: 11 months ago

Posts: 0

there is no way to know what script causes the dirty flag to the scene if a developer of this script doesn’t mark it. if the scene is dirty the undo stack is not empty. you can check the current undo name. but there’s no more than that.

Yea, thats the goofy thing. the undo buffer is not filled with anything.

I just cleared the calbacks in the start up files, restarted max, and confirmed there were no post open or pre-open callbacks present. The flag is still being set somehow.

So i’m at a loss.

1 Reply
(@denist)
Joined: 11 months ago

Posts: 0

definitely it would make me nervous too. something changes the file exact after its opening and it does it behind my back! damn!

well. what might cause it?

  1. persistence callbacks
  2. startup scripts
  3. expression / script controllers
  4. third party plug-ins
  5. custom attributes

    any other ideas?

I think i found it. Thanks for the help.

1 Reply
(@denist)
Joined: 11 months ago

Posts: 0

what was it?

I think it was some 3rd party plugin i was trying out. I went through and removed the ones i wasn’t using, and it no longer is popping up.