Does Vue5 need to be loaded on drive C, the main Windows Drive. The reason I ask, I've loaded V5 on another HD I have & Vue keeps crashing, when I get so far in a scene, when I check the Win error log...it rambles on that the error is C:Documents....obviously, since I don't have Vue on C drive, should I move it???

After the crash, it would not even load up the .bak file correctly....it was "loading"(not the bar going, it had stopped) for around 30m, when I clicked on render. The pic rendered OK...however I noticed that a whole layer was missing. The objects were still in place in main view...but the layer gone. In addition, all my objects turned jet black.

Thanks!

Systems specs = WinXPro
2g mem
100G HD space avail.

Background draw/OpenGL were all turned off.
This was a Windows error...Vue did not give any warning msg. The scene was small 5m polys with only 4 PZ3's in it.

Message edited on: 11/02/2004 11:03

If it doesn't do it when it's on drive "c" then I'd say there's probably some connection that Vue is trying to maintain (like a file that is hardpathed in the program for it to look for only on the c:) That's my only guess. Also, I've noticed Vue rarely actually gives you the warning message that Eon says it is supposed to give you, it usually just crashes outright or does the vue5.eon error before crashing. I've also noticed that it seems to not be able to handle as many poly's as easily as Vue 4 used to (one of many reasons Vue 4 is still on my system) but I've noticed the same thing when running Vue 4 Pro on a much better system than my Vue 4 is presently installed on. Hope this helps!

Thanks Nano....In that Win error msg...it also referred to 2 .dlls, that it was looking for. Well I guess, I'll install Vue on drive C & keep my libraries on my bigger HD...darn :(. I'm hoping the fix, they come out with this week correct this. I can't imagine that 5mil polys is too much. Strange thing, I've never got a memory error msg. I think I'll post this over at e-on as well. Thanks again.

That's typically what I've been doing with Vue 4 Pro on my work computer, keeping all my data in my own directory structure on the D: drive instead of on c: where the program's installed. I wouldn't expect 5mil poly's to be too much either as it really doesn't take long to reach that mark at all, and I'm used to dealing in scenes that run on average 30mil polys and usually higher.

Ditto, nano...my scenes are always well over the 15mil mark. I really wanted Vue on bigger/less full HD :(. Oh well....will start rearranging things tonight.

I am running Vue5 (and Vue4 and VurPro) on my H: drive which is located on a second hard drive. I have not run into that problem with e-on looking for files on the C: drive with Vue5. I do have out of memory errors - got one this afternoon working on a scene that has 83,000 polygons (which is ridiculous). It sounds like your file was corrupted with the crash which is unfortunate. I think I'd do a re-install of Vue and be sure to clean out the directory of any old Vue keys before the reinstall.

Hi- I run Vue 5 on my SATA G: drive with no problems. The drive has 250 GB of storage. I think it just depends on where you install it. I also have Vue 4 on the same drive- just in case I may need it for something- but have not touched it since getting Vue 5...

Thanks...I'll leave it where it is for now. I'm still going to post over at e-on...I'm confused as to why I got a Windows error & not an e-on error before crash. What I find even more disturbing is the /bak file was corrupted as well. I worked all day on a scene...V5 crashed with Win error. BAK file corrupt. Started scene again, saved periodically as usual....crashed again when trying to create a new mat file....bak file corrupt again. Have started a 3rd time, no crash...waiting for e-on fix :P...LOL Thanks guys & gals :)

Did yo ucheck your disk for errors? Could also be the cause?

Yep, Petshoo, in addition to Virus/Defrag etc. the whole shabang :). LOL Posted at e-on as well. Till I/they figure it out..the work on the scene has come to a halt ;). For now, I'll read & shop :D.