Hi, isn't that a nice error message? It says: impossible to read the file... And that after one day of work on this scene!! Has anybody ran into this as well and does have an idea what happened? And how to avoid that in the future? I think that happened the second time here on my machine. My feeling is, that it has to do with the OpenGL driver (the mouse pointer suddently disapeared) and probably Vue was "semy-crashed" already while saving the scene. AND (to give me the rest), the backup-file (.bak) became corrupted to!!! I am not pleased. I think that is understandable! To make it not so easy, i am using Vue 4.1 on a Mac!!! Hope someone can help! Maybe only with some good words to help me over that loss. Walther

Walther if you have configured Vue to backup your work, you can find in your Vue folder a file called "deer_at_dawn.bak". Rename that folder with the extension *.vue and then open it. You only will have lost a little of your work. This happens sometimes that vue cannot open a file when the saving has been interrupted for any reason. Always create two savings of all your work. Also you always have one which stays OK. I'm sorry about that, but I cannot help more. Hopefully you have a backup file:-) Guitta

Tja, bad luck. I tried that. But the ".bak" file became corrupted as well. Which is a little anoying. So the deer is probably gone with the wind. Walther

This NEVER happend to me. How the bak file can get corrupted too???? Vue backs-up only about every 3 savings.

Well. I think, when Vue is doing a backup, it has to copy the old version to ###.bak and save the new version. Anw when Vue is "semi-crashed already even this copy process has as result a corrupted file as well. That is the only explanation for this effect i have. By the way, in the other case (this is the second time that that happened) the .bak file was corrupted too. :--(( Walther

How much memory, do you have on your machine, and how many .dxf or similar not vue objects have you used?

1 GB memory, 4-5 DXF-files imported (unluckily i can't check anymore) Maybe one reason was, that sometimes i switch between Vue and an old game under classic (to play a little while waiting for the rendering) and that perhaps confuses the grafic drivers of Vue. So that the mouse pointer disapears. Sometimes i can manage it to get the pointer back after a while this time i prefered to leave Vue while saving the changes i made. Touch Walther

The safest bet is too create incremental saves (ie. file names - 001...999). You may be working on a corrupted file and not even know it. After a project is done, one can always go back and delete the extra saves.

Charles

Thanks everybody, It looks like that there is definetly no way to recover the project. Bad luck. Anyway, life goes on. Maybe one day i will redo this one. By the way, normally i say to beginners that only the scared are doing backups :-)). But in this case... Thanks again, Walther

Hi Walther,I would suggest not to delete the corrupted files before de-and reinstalling Vue first.Sometimes Vue loses internal programm links which create that kind of errors too.I had some problems like that in the beginng.Further on dont play while youre rendering in vue,especially when you`re not runnig Win NT or 2000 !!! Greetings Fredi :-)

Thanks Fredi, i will test that later. BUT I HAVE TO PLAY WHILE WAITING :-)) - and i am using a Mac. thanks again everybody, i will redo the scene one day - promised! Walther

Walther, If you have to play while waiting (as I do), then do what I do - render on one machine and play on another. I use a KVM switch so that I don't even have to look at a different screen. ReFlash