Undo in the KCM window seems to just reset it. Redo then does nothing. Not sure if it’s easy to reproduce or not.
- Chad
This is likely fixed in my current build.
I wasn’t escaping some property values correctly (for example when setting property names in Input nodes), so running the MagmaScript generated as Undo record was causing the flow to be reset but then the saved flow did not load properly.
Do you remember whether the flow in question had any object-based nodes (InputGeometry, InputParticles etc.)?
Looking at the other bug (InputTexmap), viewtopic.php?f=29&t=6205
the Undo buffer clearing the flow could have been that, too. Same issue, a map value written out without proper handling on load. Fixed, too.
It happens all the time here still.
Try again tomorrow it is just because today is Friday the 13th 
There were several bugs in Magma itself where the handling of node references (e.g. Object, Geometry input etc.) were off. We fixed that.
Right now, the main cause for this would be running Max 2012 without hotfixes / Service Packs. This would trigger the MAXScript bug that leaves text files open which made the original release of Max 2012 unusable in production.
If Max 2012 Service Packs ARE installed and it is still losing the Undo, I need to see the latest Undo file when this happens.
It can be found by executing the following:
shellLaunch (GetDir #plugcfg + "\\Krakatoa\\MagmaFlowUndoRecords") ""That was it! Running great with SP2, good to know.