How do you prevent grasshopper in replacing your files? It's urgent!

Every time I change something in one of the components in my system in grasshopper, I can't undo and the program replaces all previously saved versions of the file with the new changed version (I haven't saved).

I've tried to turn autosave off in grasshopper settings>enable autosave but have anyone other suggestions? Could the multisave function have anything with this to do and if - how can I turn it off? (I'm not sure it's on or off)

It's urgent - I have 8hours to finish it. Hope there is someone who has the time.

Thank you in advance.

Replies to This Discussion

Permalink Reply by David Stasiuk on March 11, 2013 at 3:17pm

I have never seen that before. But if you're looking at a serious deadline instead of spending time trying to figure out how to fix it now I suggest that every time you hit a milestone you want to keep you save it, then do a "save as" named as the next version. Then every time you tinker in it, it will only save to your newer version, and if you want to go back to your milestone, you'll have it. Good luck!

Permalink Reply by Cin Petersen on March 11, 2013 at 3:23pm

I've tried it but it also replaces versions that are saved under another name - unfortunately. It's really a huge problem. But thanks for your answer anyway.

Permalink Reply by David Rutten on March 11, 2013 at 3:30pm

I can't undo and the program replaces all previously saved versions of the file with the new changed version (I haven't saved).

I'm confused. What happens when you try to undo? Is there an error, a crash? What does "replaces all previously saved versions" mean? All the *.gh files on the disk that are related to the current file?

Multisave is merely a last-ditch attempt to avoid data loss. If you have open files when Rhino closes that have not been saved or which have been modified, multi-save kicks in and allows you to save them all. It's just like regular save.

Do you have version 0.9.0005 or newer? Autosave works different in 0.9.0005 onwards, all autosave files are placed in a single folder.

Can you give me a screenshot of a file you're currently editing and also a screenshot of the Windows Explorer window containing it?

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by Cin Petersen on March 11, 2013 at 4:11pm

- I can't click on it - it's not highlighted. Like then there is nothing to go back to... There is no crash or eror. Yes all related file get replaced.

- Thanks for the explanation.

Do you have version 0.9.0005 or newer? Autosave works different in 0.9.0005 onwards, all autosave files are placed in a single folder.

- Version 0.9.0014 so it can't be the problem.

Can you give me a screenshot of a file you're currently editing and also a screenshot of the Windows Explorer window containing it?

As you can see, several of the elements in grasshopper are red after it chose to delete all previous versions - this means there is no longer anything to see in Rhino and everything must be done all over again :-(

I really appreciate your help and hope you have a solution

Permalink Reply by Cin Petersen on March 11, 2013 at 4:28pm

Here is the file if it's any help to find a solution.

Attachments:

trianglefacade5000.gh, 43 KB

Permalink Reply by David Rutten on March 11, 2013 at 4:45pm

Those screenshots have been downscaled, I can't actually read anything from them. Can you post unscaled versions?

Is this the only file you have loaded in GH at this time, or are others loaded as well?

So the Undo menu item is greyed out? The Undo menu is only ever greyed out if there is (A) no document currently loaded or (B) the document has no undo records. Since undo records are not stored in the *.gh file, I won't be able to check what's going on exactly. Although the undo buffer cannot be empties manually, it can be done through code.

I'm rushing this a bit since almost midnight and I can see you need this solved quick. I've loaded your file and any changes I make are duly recorded in the undo buffer. I don't see how the file could ever work with "open - factor" as a VB script input name. Variables in VB are not allowed to contain spaces or dashes. Another VB script component uses two identically named inputs (flaplength) which also can't possibly work. Unfortunately I currently haven't got a working VB editor so I can't open these script components.

David Rutten

david@mcneel.com

Poprad, Slovakia

RSS