Tue, Nov 26, 4:37 PM CST

Renderosity Forums / Vue



Welcome to the Vue Forum

Forum Moderators: wheatpenny, TheBryster

Vue F.A.Q (Last Updated: 2024 Nov 26 6:57 am)



Subject: EMERGENCY: Can anyone help? Error writing file.


johnr1969 ( ) posted Tue, 19 May 2009 at 5:38 AM · edited Tue, 30 July 2024 at 5:53 AM

This is worrying because I have a forthcoming deadline. Can anyone make any suggestions?

Problem is rendering in Vue Infinite 7 [updated to version 7.4]

I am having trouble rendering a Vue scene composed of 62 objects, 1 light and 1,215,276 polygons. Using volumetric model and Global ambience. I am rendering 500 x 240cm at 72dpi. I have previously been able to complete such renders in Vue 6.

The render time is recoreded as 1.39, 55” but I get an error message stating “Error writing file. Please check available disk space and try again".

My computer is a Mac Pro, 2 x 3.2 Quad Core Intel Xeon with 10GB of RAM and NVIDIA Geforce 8800 GT graphics card.

The internal hard drive I was trying to write to is a 500GB hard drive with 421GB free space.

Has anyone got any solutions.

Much appreciated

J


wabe ( ) posted Tue, 19 May 2009 at 5:53 AM

Is there any non-standard character in the name of the folder where you try to save your files? I had this issue on Mac in German with German Umlaute. Didn't worked here with this error message.

Another quick solution might be to use exactly the defaults that Vue proposes as place where things should be saved. It might be a problem with pathnames that you face.

Last but not least, is this happening with all animations you try to render and save? Or is is a specific problem with the scene you work on right now.

And finally, when a deadline is coming and you can't find a solution, it might be an idea to use the help of a professional render farm like The Ranch.

One day your ship comes in - but you're at the airport.


AVANZ ( ) posted Tue, 19 May 2009 at 7:54 AM

When does the message pop-up, before or after finishing the render?
Do you use a network render?

I had a similar problem in 6.5 rendering with HyperVue. In the end HyperVue crashed wile compiling the picture. I think it hit the limit of my system memory or the amount of memory Vue can use.

Oh, by the way, I'm testing Vue7.5 right now and there is a bug that does not allow me to write to anywhere else than the default pictures/e-on software/ Vue... etc. I would not be surprised if the same bug exist in 7.4 If so, you also need enough space on that disk...;-(

Good luck


johnr1969 ( ) posted Tue, 19 May 2009 at 8:08 AM

OK thanks for that advice. Maybe it is this only write to the default e-on software etc. Is there anyway around this? Saving elsewhere I mean? I will try a few dufferent file types


AVANZ ( ) posted Tue, 19 May 2009 at 8:32 AM

Well I noticed it with a HyperVue render in V7.5, don't know if it is also a bug with Render to disk or the Standalone renderer.
There is no way around it on the moment, but luckily I have still enough space on my Startup disk.


johnr1969 ( ) posted Tue, 19 May 2009 at 9:00 AM

OK ... I'm still not 100% sure - I'm making a series of low resolution renders (so far no problem - just rendered at 200x100cm/72) and now trying higher res.  For me the problem seems to be almost exactly the opposite problem to Avanz, that is, It is crashing when I save to the default pictures/e-on software/Vue..etc address. This has quite a complex path name. When I save direct to my second hard drive (no folders) it seems to be OK (so far). Could it just be the complexity of the path name? (as wabe suggests?)

7.5 is VERY quick (good news!) but also seems very tempermental on a MAC (if I press escape during rendering it crashes!

Thanks anyway for everyones help. I will post up what happens.


Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.