Seemingly randomly showing up. Has happened a couple times now. The folder is there, and it has a lot of files in it, but not the ones specified (and not the previous one, either, like _29104_10245 stopped at 106).
I wonder if you a hitting a limit to the number of files in a folder.
FAT32 : max. 65,534 files in a folder
NTFS: max. 4,294,967,295 files in a folder
Try deleting all files in that folder.
I will have to make sure the Editor cleans up correctly after itself…
EDIT: Turns out there is a bug and Genome Undo files are not being removed when the Editor dialog is closed. Fixing…
514 items. But the thought of getting up to 4 billion is a bit scary.
These are just the Windows limitations. You are unlikely to get there, but I am fixing the bug that prevented the clean up.
Something else is going wrong on your machine, the cannot create file thing looks like a MAXScript / OS file access problem. I have never experienced it with the Undo files.
I’ve seen it happen too on my machine. Its some rare, randomly occurring permissions error I assume.
It just happened again when I tried to do an undo. Got the error, and my whole Magmaflow was gone. Nuts.
I possibly fixed the “flow gone” problem a minute ago.
If an undo file is not there although it is expected to be, no undo will be performed (which includes calling reset() and then loading the file).
So hopefully in Beta 3, if the Undo file is missing, the flow will just not undo, but will not reset itself into nothing.
I’m getting the same error, first this one:
Could not open file 'C:\Program Files\Thinkbox\Genome MX\Scripts\Genome_MagmaFlow.ms'.And then this one:
Runtime error: FileStream cannot create: C:\Users\Martijn\AppData\Local\Thinkbox\Genome\MagmaFlowUndoRecords\UndoRecord_34064_6626.211Not sure if it’s related, but the last undo file it created is 0kb. I tried deleting the existing (193) files with max still running but that didn’t work as the files were still in use by max (could there be a file handle left open by accident?). A GC() didn’t fix this so I unlocked the files using the unlocker tool and then deleted them. However, even though the target dir is now empty I’m still getting the filestream exception.
I didn’t really expect this to work, but I just tried deleting and creating the MagmaFlowUndoRecords folder again but that didn’t help either.
Martijn
This is using Beta 3, right?
I switched the paths to the Local User folder in hopes it would stop doing that.
I personally have never seen this happening on my system, but it has happened on Darcy’s.
Are you sure you are not running a non-hot-fixed Max 2012 build that would lock any MAXScript file due to the Autodesk error of opening the file twice on creation and failing to close it? (you are too good to be doing that, but just checking 
).
Well you obviously think too much of me, because I seem to have forgotten to install that hotfix on my laptop and never ran into (or noticed) the createFile bug 
I’ll let you know how it goes with the hotfix installed!
Martijn
A Service Pack would be even better, but the (first two I think) HotFixes are almost mandatory.
That bug has haunted us for a year now. It broke Deadline, Krakatoa and many other things.
I admit forgetting to install the fix on my laptop and going to a customer demo once 