the main purpose of auto-backup is to have a most recent before max crashed version of your scene.
so many times an artist just happy to get anything saved it shouldn’t be a problem to merge things saved per layer.
it can be per-layer settings (custom attributes for example) how often the layer must be saved. backup file name can contain a layer name…
when max merges nodes from file it ‘merges’ their layers, or puts them in the same layers if they exist.
Oh yes, that’s true, especially to find the objects or materials you recently worked on a couple of hours but forgot to save
actually i have another ‘backup’ tool. it saves only scene materials in a similar manner as auto-backup
Lets talk now about objects. If classof object is geometry then we have vertex number, modifiers. If any modifier value, number of vertices or vertex position where modified then we have to add this object to our array2bSaved.
Is there any callback to see that we entered subobject mode?
Sorry, just found
nodeVertsChange = nodeEventCallback subobjectSelectionChanged:exampleFn
It means we can get the object without scanning vertex position, which I think will be fast enough, what do you think about this?
just monitor all node events… every node once used with any event was probably changed.
Do you mean selectionChanged?
i mean ALL