I'm not necessarily looking for an answer here, I just want to see if anyone else has this continuing problem.

The latest beta 267266 has not fixed this.

When rendering to disc (the amount of geometry, file size, render quality or image size make no difference) the renderer skips to the end and I get the task bar (bottom left) rapidly 'writing picture' but all it does is write a black image.

I have to quit and load several times before I can coax it into writing the 6 hour render properly.

I am certain that this is NOT a hardware problem and I am waiting for a reply from Steve at E-On. I will pass on anything I learn.

System Spec: Windows XP PRo. P4 3GHz 2GB ram, 240GB HD and a G/Force 5900FX 128mb graphics card. System temperature never rises above 35 degrees.

If you have the same problem or can shed any light on this problem please let me know.
Thanks for reading.
Tony Hayes
'bogwoppet'

For me it renders properly to disk:-)

Yeah, had the very same problem when attempting to render anything over 3500 pixels in size. I asked here and had a discourse with E-ON about it.
They said it works for them too.Why not for us eh!

I have similar specs to yours except only 1gig ram.

Would love to hear of a way around this!!

regrds Rokol.

bogwoppet, will try and duplicate this error tonight on a large render to disc as it may take a day or so to render a large scene but I will get back to you on results. Thanks for the heads up and if this is a problem it should be reported and fixed. Regards.

Well the results went well I can render to disc with out any problem in what ever size. I must admit I did have this problem in an earlier version of v4p however it seems to be fixed in the latest update. I would be interested in any error reports or examples of this problem and if is repeatable. Thanks for bring it up. Regards

Thanks for the interest. It's strange, the large scene mentioned above renderes fine at a lower resolution ie: 4096 X 3072 but not above.
A very basic scene (sky and ground) can render at any resolution without problems.
Steve at E-On still thinks that it is memory related and he might well be right but I have 2GB ram - how much does it need?
The only other point that might be giving trouble is the scenes that won't render at high resolution have one thing in common, they all had a poser model imported? - could this be where the problem lies - I need to do some more tests.
Thanks for reading.

I think you are on to the problem Bog I only have a 1 gig of ram and V4P will pop up a window on very large scenes that I want to render in large sizes and say something like this render will require 873g of ram and you have to click ok before it will start any rendering so the program has been modified in my version to at least recognize the situation. 2 gigs should be plenty however as you mentioned Poser can really raise that requirement a lot. My next machine I am going to shoot for at least 5 gigs of ram to avoid some of these limitations. All problems with the program interest me as I am still testing it so thank you for bring this up. Regards.

I have 3.5 GB of ram and am having the same problem. It is a memory problem, though... the more stuff I remove from the scene, the higher my render size can go. Restarting certainly helps, but not nearly enough. Using Windows task manager shows that I have far more than enough resources available for the scene. So far, it seems that chopping the render in two is my only option.

Attached Link: http://petes-oasis.com/tilerendering.html

Thanks, MightyPete. Interesting ideas in that link.