I have a very strange problem.

When I work in V6I, I always save very often, always to different copies (the program is not very reliable...). So, in a certain scene I'm now in the 25th version and, suddenly, when I do just a normal preview test render, it crashes and the program exits. Ok, no sweat, I think, I relaunch the program and the scene. It crashes again on render. Ok, let me go to the 24th version, which was just fine and rendered perfectly before. But... surprise, now also this version crashes!... I go back to version 23... and 22... all crash! If I load a completely different scene, it renders just fine. Only that one doesn't. So, it's something in common with all the versions, I think, some temp file that got corrupted and it's used over and over again. So, I deleted all temp files and env files (from the environment folder), tried again... but the problem remains! Now I have hours of work in a scene that doesn't render!
Any clue?!
Thanks a lot!

I have a similar problem I think. I have a scene which is only half rendered, each time I try to resume it the program crashes. I can only think this has something to do with my memory as I only have 1 gig. It does seem strange though that it got halfway but now no longer wants to render. Maybe something has got corrupted like yours. I am using Vue 6 Esprit. If this continues I may have to redo the project, sigh!
I hope someone can help you.

Yes, it seems similar. Mine renders a few lines and... crash. Frustrating!...
I forgot to say that I'm running this in a Windows XP, dual core, 4GB of RAM, no other things running in background except anti-virus and firewall.

Rutra, just to be sure, turn off your anti virus and retry.

I just did: it still crashes.

Are any textures using displacement?  If yes, turn it off and try to render again. 

Thanks for the hint but there's no materials with displacement.

To me this sounds like a memory problem. AND, what I always try to call a "semi crash". What I mean is that because of whatever action Vue goes into a faulty status and produces incorrect results. A faulty saved scene file in your case for example. I had that once when I converted a series of Poser props and #1 Vue crashed something after around 10 imports/savings
and #2 the vobs were faulty and can not be opened in other licenses (beside the fact that even the version that has written them needs ages to open the files). Faulty vobs in my case.

But it happens only after a row of savings in one session in my case, maybe as well  in yours.

What can be done? #1 report it to e-on so that there is a chance that they look into it and find the problem. And #2 more often quit and restart the application so that there is a full reset of memory.

I (more or less) found the problem. I discovered that using a render area it didn't crash. Then I just moved the render area around the picture until it crashed. Ok, I had found the problematic area. There were 3 objects in that area. I deleted all and the problem disapeared. Then, put the objects back again, one by one and found it crashed with any of 2 of them. I replaced the materials in these (which were just mixed material for water in one and mixed material sand in the other) and found that these two materials had been corrupted somehow. Both of them! They were used in other previous pictures without any problem at all. Weird! I built the materials again and it worked fine.
What a weird thing!!

Great job sleuthing the problem. Many of us can learn from your approach, thanks for sharing it!

Rutra - I'm really pleased you were able to sort out your problem. All that time spent hasn't now been wasted!!
I hope to try something similar as you've done on my old piece so that I can complete it. Thanks for the info.

Good sleuthing Rutra!!
The only thing I find annoying is that Vue just crashes when problems like this occur...it really should notice these errors as it loads a scene and then reports the problem in an error message, rather than just crashing!
Then again I have always found E-on make it difficult for us anyway - i.e. when they release an update, they never release a "known issues" list. I have brought this up with them many times and always get the "good idea" response...but they never implement it!!
Come on E-on, make our lives easier! I hate wasting my time filling a bug report only to be told its a known issue!

Cheers