Just saved my current file just about an hour ago, went out for a Starbucks run to refortify myself ;-), and returned to being unable to open the file (.vue or .bak) even though I can clearly see that they are there! Even see the preview for the scene in the little display thingie!
I'm able to open other .vue's with no problem, it's JUST this one in particular (and it's only 15Mb, so size is not the problem here!)
Any ideas or help would be greatly appreciated!!!
==steve

I don't think you'll be able to use the corrupted files.

A word of advice: I always try to plan for the worse when I'm working on a scene. Part of my plan is to save scenes with incrementally numbered file names.

When the scene is completed and rendered, then I delete the older files. I've saved myself a lot of heartache by doing this.

An additional plus is that you no longer need Vue's .bak file saves and can turn it off via the options.

Charles :|

Well, that's what I sorta expected?!?, Charles!!
...so looks like it's back to the rendering board...
...sigghhhh...the worst part being that this one was named 1.vue as it was my very first file ( as I, too am in the habit of starting a folder and then just incrementally increasing the number on my saved files saved there)'fore going and inevitably tweaking the heck out of it...LOL!!!
Oh, well...just hafta go and play with one of the other files sitting around just dying to be finished ;-)!!
==steve

Well, i have it from time to time too. My feeling it is a runtime thing that causes the problem. Three days ago i have had it too (with my last egrets project) - i tried to have 100 copies of a flower in it. It took ages (soemthing around an hour) to save the file and the result was a corupted .vue. In this case i was lucky that i had still the .bak file, renamed it to .vue and went on again. But the original plan was much richer, much more details etc - simply not possible. By the way, i am on a Mac!

Ahhhhh, wabe!! For a second there I thought you'd supplied the solution as I wasn't renaming the .bak file before trying to open that one, but ALAS, that, too seems to be corrupted...siggghhhh!
Oh well, just hafta move on, I guess
(unfortunately not to a Mac as they're a bit out of my price range at the moment'-)!!==steve

For future referance. If you group objects then put them on hidden layers and then save the file will open much more quickly. Why are you guys having this problem I'm not sure. Can't say I've ever had it saving files that where almost 3/4 gig in size. Fragged up hard drive? Defrag it first. Oh if you have a bak file then you have already did the dreaded save over last file name. Don't do that ever. Save project1 project2 project3.... get the idea? There already posts by me explaining what happens to the DOS when trying to overwrite huge files and saving the BAK and then saving the one in memory. If you want trouble do it this way.

get the idea?>> Yepp!! ==steve

Sometimes when I get this problem, I can right click the file and use open with, then select vue, and it opens. When I use open inside vue, it don't work. So you could try that.

Then tell us if it worked.....

Nope! No, I'm not not gonna tell ya if it worked ;-)! Nope, as in already tried that and it did not work! Already wrote this off as a learning experience and will never, or until the next time I forget, save over an old file again!! ALREADY up to version 7 on a file that's only half an hour old...LOL!!! ==steve