Kirk Andrews schrieb:

 > It seems that
> as soon as I'm ready to finish a scene and crank up the settings for an 
> overnight render, this happens.
> 
> I had successfully rendered the scene at lower resolutions, although not 
> all of the quite the same for things like radiosity, media, number of 
> trees, or resolution of height_fields.
> 
> It parses fine; it seems to always happen about 5% of the way through 
> the render itself.  There doesn't seem to be anything particularly 
> unique in the image at the point at which it stops.  In fact, sometimes 
> it will render fine with the camera one way, but if I rotate the camera, 
> then the access violation will occur.  Yet, it is not random--that is, 
> if I leave the scene the same way, it will happen 100% of the time.
> 
> The access violation code number seems to be consistent every time.
> 
> ---
> 
> I'm using beta 34, 64 bit version on a 64 bit Vista system with 2 cores.
> 
> Current settings:  +W2400 +H1200 +fn16 +a0.2 +WL0 -RVP +SP8 +EP8
> 
> In the scene are several high-resolution height_fields, ~160k POV-Trees, 
> low-grade radiosity and media, a low-quality area light, and an infinite 
> plane.  The height_fields are created using functions made from tga 
> files from World Machine.
> 
> I use a averaged object pattern to generate a simple proximity function 
> that governs several textures on the height_fields.

Would you mind getting one of the 100% offending scenes to me (either in 
p.b.scene-files, or to "christoph" at the server "lipka-koeln.de"), 
along with image files & .ini / command line settings, so I can have a 
look at it with the debugger?

Post a reply to this message