Andycadd nous apporta ses lumieres en ce 08/10/2006 00:25:
> Warp <war### [at] tagpovrayorg> wrote:
>> Andycadd <And### [at] comcastnet> wrote:
>>> Is there a reason for the default "block style" rendering in 3.7 rather that
>>> the "scan-line style" of 3.6?
>>   Yes: SMP.
>>
>>> But.....  both of the Beta renders crashed after the first frame
>>> (rendering to png with default settings) while the 3.6 render continued onto
>>> the next frame. I haven't tried any other output formats yet but I probably
>>> will.
>>   Could you provide a short scene (and rendering settings) that shows this?
>>
>> --
>>                                                           - Warp
> 
> 
> 
> When I remove some of the model  it renders just fine in animation mode
> when I crank the resolution down it runs just fine in animation mode
> probably if I turn off display it would work fine also
> ----------------
> It must be that a GIG of ram is just on the line for a successful render at
> 8000 X 2000 with a rather large model file
> ----------------
> Strange that it would start and render/display the first frame
> 
> not so Strange that it works just fine with 3.6 but not 3.7 as 3.7 probably
> uses a little more memory overhead
> 
> ''''''''''''''''
> what follows is the log for the first frame a very large model (I put a
> cropped portion in the images directory titled "future hotel") rendered in
> 3.6
> ''''''''''''''''
> 
> Render Options
>   Quality:  9
>   Bounding boxes.......On   Bounding threshold: 3
>   Antialiasing.........On  (Method 1, Threshold 0.040, Depth 3, Jitter 1.00)
> Render Statistics
> Image Resolution 8000 x 2000
> Pixels:         17004000   Samples:         4247388   Smpls/Pxl: 0.25
> Rays:           21251388   Saved:                 0   Max Level: 1/6
> Ray->Shape Intersection          Tests       Succeeded  Percentage
> Cone/Cylinder                  1294518               0      0.00
> CSG Merge                       215753               0      0.00
> Mesh                          21797976         1498108      6.87
> Sphere                        42502776        42502776    100.00
> Triangle                    1718215371        28586386      1.66
> Bounding Box                2302667593      1172313524     50.91
> Shadow Ray Tests:            884757   Succeeded:                338247
> Shadow Cache Hits:           338169
> Smallest Alloc:                   0 bytes
> Largest  Alloc:                   0 bytes
> Render Time:
>   Photon Time:      No photons
>   Radiosity Time:   No radiosity
>   Trace Time:       0 hours  8 minutes 45 seconds (525.734 seconds)
>               using 4 thread(s) with 991.436 CPU-seconds total
> 
> End of First Frame
> 
> '''''''''''''''''
> here is the error messages
> '''''''''''''''''
> Possible Parse Error: Cannot find file 'C:povtsstone9bel11.pov', even after
> trying to append file type extension.
> Parse Error: Cannot open input file.
> Possible Parse Error: Cannot parse input.
> Possible Parse Error: Cannot find file 'C:povtsstone9bel11.pov', even after
> trying to append file type extension.
> Parse Error: Cannot open input file.
> Possible Parse Error: Cannot parse input.
> Render failed
> -
> CPU time used: kernel 78.80 seconds, user 8602.11 seconds, total 8680.91
> seconds.
> Elapsed time 4525.23 seconds, CPU vs elapsed time ratio 1.92.
> 
> 
> 
> 
> 
> 
> 
I've been hit by that error somes times doing animations. Render some frames, 
then it looks like the path to the source file get lost. The can't find file 
error message always reffers to the actual scene file. It looks like the file 
gets actualy parsed, then the error pops up.

-- 
Alain
-------------------------------------------------
Inside every older person is a younger person wondering what happened.

Post a reply to this message