I used to get this error quite frequently but then it went away. Today I started seeing it again; about half the times I tried to save a file in Vue, this happened. Needless to say, there's no problem with disk space. Anyone have any ideas on this? I'm running the latest official update on win XP Pro, 2Gb RAM, and 111Gb left on the HD. The scene is a simple one with one ecosystem, volumetric lighting, and about 8 imported objects of varying sizes.

holy crap, 111Gb? That's massive! But no, I've never had that error before - is it only when you try to save over a file, or with fresh save as saves too?

This time is appears to be just on saving over an existing file. When I got this a few months ago, it was on both new and existing files. I think I'll put a support ticket in to e-on and see what happens. It's really annoying not being able to be sure that you can save changes to your scene :-(

I had this message several times (190 gig free..on my drive though) Just an idea.. have you the disk shared on a network ? because it seemed to disappear after changing that on mine. Maybe it is not related but who knows?

I get that error when trying to weld objects(not all but some)

No, it's not a networked drive - just the local HD. Although there is one shared directory - and one of the textures used in the scene was from that shared folder. Could all be part of the same problem I guess, so I'll turn sharing off and see what happens. Many thanks for the suggestion.

I seem to recall this problem was an issue with a previous build but was fixed with the more recent ones, but I could be wrong.

Interesting. One of the objects I imported did have to be welded, but I tried leaving it unwelded and it didn't seem to make any difference. I wonder if I should have imported the object, saved it as a .vob, then loaded that into my scene instead of importing the .obj file directly? I'll try it - thanks.

Never had that problem, and some of the textures I use are in a shared folder too. Did you try saving it to another file name? Does flushing history help before saving? Did you abort a render before saving?

Yes to the first, and it saved okay, fortunately. Haven't tried flushing the history - I'll try this, thanks. Aborting renders - yes, I do that a lot - is it a Bad Thing?

Not a bad thing, but when you abort a render, Vue records the rendered bits for re rendering later, and I think that if yo save an unfinished rendered scene, the info is stored in the .vue file, and it gets very big. Not sure this is the problem here anyway, but maybe a lead.

I had that error when something in the pathname where you want to save is wrong. Which strangely enough does not seem to be the case here. I had that regularily when i tried to save to a folder with the name "5/11/2005" which is on Mac an absolute correct filename. After i changed the folder name to "5_11_2005" all went well. Could you imagine what happened in my first Vue installation where the folder name was 3"D/Paint". I had a lot of pleasures until i found out what the reason was and renamed the folder!

I stop and restart renders all of the time. Never seen this error.

Thanks for the comments, everyone. I will send in a support request and let you know if anything turns up. Steve

I've had this problem. I think it is due to V5I running out of memory when saving a file that has large numbers of small imported objects distributed with ecosystem?

I watched Windows Task Manager when saving, and memory requirements ramped-up dramatically, then I got the same error you did -- with about 200GByte of available disk space! When I reduced the eco object number count, I could get the file to save. BTW, hopefully you saved a backup file, as you will lose the file that failed to save. File header, and a few KBytes is all that will remain.

I was able to repeat this problem, and did report this to tech. support.

Just be careful. When you get this error vue will try to save and copy your last .vue to the .bak and then fail on this save creating a corrupt .vue file. If you try it again vue will again copy the .vue file to the .bak and then fail on the save. This leaves you with two corrupt files. A .vue and a .bak. Ouch. When this happens the first time you should rename the .bak file to something else to have a saved backup that you can get back to. I have reported this problem to e-on.

How do you use the .bak's??

Each file of .vue is backed up to a .bak file when you save. This allows you a second backup, one save stage behind the first. You can use this if you stuff up an image and want to revert back to a previous save. You can go to your scene save directory in explorer and rename the .bak file to another file name with a .vue file extension and then load that file into Vue.

Oh - didn't know that - cool...

Anyone know of any progress on this problem? Responses from tech support? Has everyone gone back to a previous build? I've never been able to pinpoint a possible cause, or would've reported it, too. For ex, I thought it was ecosystem related, like others, but my latest scene doesn't have any eco's.... just 3 Poser figures (using reduced maps) and a standard terrain. Thanks

Tech support couldn't duplicate the problem I was having, but they have logged it and will look at it, so who knows...

Thanks for the response, Steve. As it turns out, I did have an ecosystem on my terrain... maybe even dozens???

Since I could no longer save the scene I was working on, I tried saving it out as vob files to rebuild. That, Vue would let me do. As a precaution, I thought I removed the 2 ecosystems I had on the terrain before vob'ing. Upon import of the terrain in a clean file, it seemed eco-less... no questions about auto-populating, and no eco icons on the mat preview. What I discovered later was that this almost empty scene saved at 78MB, just for standard terrain at 1024. Should've saved at 2MB (this was before adding the Poser figures). Anyways, when I tried to examine the terrain's mixed material, the ecosystems were showing up at every level, til I got 5 levels deep. At that point Vue went nuts. Graphics were jumping and flashing all over the place, immediately followed by a series of OOM errors. Even after Vue shut down, the OOM errors kept popping up. All this for 5 rocks, 3 plants, and 2 objects (aprox 40,000 polys each). I'd like to send this to tech support, but how do you pack up a file that won't save?