Tim Olson - is there a way to recover a damaged file? Just lost 2 days. When I quit V14 and re-opened, file and backups were damaged.

Attached here..

Any help appreciated.

How do you know that this file is damaged? Sometimes large files simply take a long time to open, and during this time, ViaCAD seems to be frozen. Check the task manager to see if the process has CPU activity.

*afaik* corrupted files (probably damaged by the undo function) cannot be recovered.

As always, do not save one (1) file only but, at least for important stuff, do a 'save as' by adding an incrementing version number "xyz.01.sfx" etc.

I know, doesn't help yet...

Posh.de

You are exactly correct. I just performed an UNDO on another model - saved, closed the file, it would not re-open - same damaged file message. Even with multiple copies I'm scared to close any file at the moment...

Can I mention another issue with phong views in 2D views format ?
It does not print to pdf unless the rendered view is fully displayed on the monitor.
- If the phong view is not fully visible it will not be complete in the pdf.
- If I do "view all" before, most of the time the pdf result is at very low resolution...

JL

the document already gets corrupted during modeling, saving the corrupt state to a file leads to the corrupt doucment finally.

Trying to undo a (complex) e.g. surface modeling operation by reverse calculating the previous state seems to be prone for the resulting geometry getting corrupt by design because of e.g. unavoidable rounding errors which do add up with every further undo.

If you open your CAD file in a text editor such as "TextEdit" scroll down to the last line and see the word "SUCCESS". If it is not there the file is bad.

Assuming the file is still open in your CAD program, look for unresolved links and fix them, or try compacting. Save again and see if you now get "SUCCESS". If you have multiple backups check to see if earlier ones were successful, if so consider what changes have been made since then to help resolve the issue.

So what you're saying is save hundreds of back ups just incase? Who has space/time for that? For arguments sake small files yes maybe, get something of a few hundred MB and you'll need a serious storage space to keep it all on the off chance it becomes corrupt! If you have a file of a hundred mb for example are you really going to sit there clear the resolve errors, clean then part, save the part, wait for it to save, go check it's saved ok. If not then somehow get a stp out of it before you get a crash or something? Then start again?
It would be better to find why they become corrupt. I started using v8 of this software and not once did I experience a corrupt file, v9 and 10 again not once was there a corrupt file in the years of using them.
V11 and 12 it was almost every job I did it became corrupt. Something happened, and it should be found and fixed.
I've had back up files which saved fine and opened fine suddenly not open. I checked whether it was network saving or local saving that did it, nothing made a difference. In the end I gave up......

And what do we learn from this? All versions after V9 Build 1162 are a complete waste of money.

If the Save or Save-As kept a history file of the commands done, you then technically do not need countless revisions saved. A history "manifest" where such feature allows you to record a user selected number, like last 20 or 100 edits made. I know there's that Deep Select tool that allows you to remove something like a fillet, but just need a history for the Undo feature, etc.