Hi,

I fixed up the quickres.ini for a final image of 2100 x 1575 and it
doesn't work.  I get
a INI file error.  Bad option syntax or error opening .ini/.def file
'x'.  I tried the render on lower res'es, and those of course, still
worked.  So, I assume the engine doesn't like my numbers.  Is the a
limit to the amount of pixels an image can be?  I just KNOW I've heard
of larger ones somewhere around here...

Any thoughts?

Post a reply to this message

"Chad Kruger" <ckr### [at] telusplanetnet> wrote in message
news:3B6B2668.5FD8487C@telusplanet.net...
> Hi,
>
> I fixed up the quickres.ini for a final image of 2100 x 1575 and it
> doesn't work.  I get
> a INI file error.

    There is a limit, IIRC, but it is nowhere near 2100x1575. Post the
relevant script.

Post a reply to this message

In article <3B6B2668.5FD8487C@telusplanet.net> , Chad Kruger 
<ckr### [at] telusplanetnet>  wrote:

> Bad option syntax or error opening .ini/.def file 'x'

Does your name have spaces while others don't?  The error message suggests
you pass a name with spaces because the clearly says it cannot *open* the
ini file.  If your ini file can't be opened, how can your scene possibly be
rendered? -- I would suggest you go back to the original quickres.ini, copy
one entry can modify it to include your higher resolution.  Then carefully
look at the name of the section and make sure you really save the file again
(also without spaces in the filename).  Of course, you could also always use
the command line options w and h to change the image resolution (they are in
the documentation/helpfile).  There is no need to modify quickres.ini for
every resolution you may desire.

BTW, in general its a good idea to read the error message (which doesn't say
anything about a size limit of images) before jumping to random conclusions
:-)


    Thorsten

Post a reply to this message

Chad Kruger wrote:
> 
> Hi,
> 
> I fixed up the quickres.ini for a final image of 2100 x 1575 and it
> doesn't work.  I get
> a INI file error.  Bad option syntax or error opening .ini/.def file
> 'x'.  I tried the render on lower res'es, and those of course, still
> worked.  So, I assume the engine doesn't like my numbers.  Is the a
> limit to the amount of pixels an image can be?  I just KNOW I've heard
> of larger ones somewhere around here...

I've rendered at 5100x3400, so 2100x1575 is not a limit!

There has to be a limit somewhere though, I mean come on, unsigned long
only goes up to 4.3 billion...

-- 
David Fontaine  <dav### [at] faricynet>  ICQ 55354965
My raytracing gallery:  http://davidf.faricy.net/

Post a reply to this message

David Fontaine wrote:

> I've rendered at 5100x3400, so 2100x1575 is not a limit!
> 
> There has to be a limit somewhere though, I mean come on, unsigned long
> only goes up to 4.3 billion...

...but PovRay uses signed integers, so the limit is 2147483647. I have
actually tried it with a one pixel wide image. I had to disable display
though, as Windows couldn't allocate a display buffer that size.

If you want to try rendering a maximum size image, make sure you have
enough disk space to hold the 12 exabyte large file.

/Ib

Post a reply to this message

Ib Rasmussen <ib### [at] ibrasdk> wrote:
: If you want to try rendering a maximum size image, make sure you have
: enough disk space to hold the 12 exabyte large file.

  Windows (at least 9x) can only create a file of 4 Gigabytes at max. However,
it can only open a file of 2 Gigabytes at max, so 2GB is the practical maximum
file size. Linux has similar limitations (although I think they can be
overridden by writing a special program which uses 64-bit file handlers or so).

  Also certain file formats have a maximum resolution limitation of
65535x65535 pixels as they use 16-bit values for specifying the resolution.

-- 
#macro N(D,I)#if(I<6)cylinder{M()#local D[I]=div(D[I],104);M().5,2pigment{
rgb M()}}N(D,(D[I]>99?I:I+1))#end#end#macro M()<mod(D[I],13)-6,mod(div(D[I
],13),8)-3,10>#end blob{N(array[6]{11117333955,
7382340,3358,3900569407,970,4254934330},0)}//                     - Warp -

Post a reply to this message

If you had the drive space, BeOS can easily handle the 12 exabyte file.
It does use a 64-bit file system.

Warp wrote:
> 
> Ib Rasmussen <ib### [at] ibrasdk> wrote:
> : If you want to try rendering a maximum size image, make sure you have
> : enough disk space to hold the 12 exabyte large file.
> 
>   Windows (at least 9x) can only create a file of 4 Gigabytes at max. However,
> it can only open a file of 2 Gigabytes at max, so 2GB is the practical maximum
> file size. Linux has similar limitations (although I think they can be
> overridden by writing a special program which uses 64-bit file handlers or so).
> 
>   Also certain file formats have a maximum resolution limitation of
> 65535x65535 pixels as they use 16-bit values for specifying the resolution.
> 
> --
> #macro N(D,I)#if(I<6)cylinder{M()#local D[I]=div(D[I],104);M().5,2pigment{
> rgb M()}}N(D,(D[I]>99?I:I+1))#end#end#macro M()<mod(D[I],13)-6,mod(div(D[I
> ],13),8)-3,10>#end blob{N(array[6]{11117333955,
> 7382340,3358,3900569407,970,4254934330},0)}//                     - Warp -

Post a reply to this message