I'm working on an animation. For the past two days POVRay rendered the frames in
the size set by the drop-down menu on the main POVRay interface window.

Then my system went to sleep automatically. After it came up again, POVRay
refused to render in the size set by the drop-down list (512x384, AA).
Instead it rendered in 800x600.

This was the size set in the POVRAY.INI. So, I changed that to 512x384.

First I changed the Height and Width parameters. This didn't work, so I
commented out the Height and Width parameters. This didn't work either.

I don't know what to do- I have hundreds of frames the size I need, and now the
new frames are too big. I didn't change anything, it happened after a sleep and
a restart.

How can I get POVRay to follow the drop-down menu again?
Interestingly, when I load one of the demonstration POV files, this DOES render
in 512x384, as specified by the drop-down menu. Can anyone tell me what is
happening?
Thankyou

Post a reply to this message

Am 28.08.2016 um 05:06 schrieb Giridhari:

> How can I get POVRay to follow the drop-down menu again?
> Interestingly, when I load one of the demonstration POV files, this DOES render
> in 512x384, as specified by the drop-down menu. Can anyone tell me what is
> happening?

First of all, we need to know what operating system you are using and,
ideally, what version of POV-Ray.

I presume you're not using the Linux version.

However, I can't imagine how POV-Ray for Windows would simply ignore
both the POVRAY.INI and quickres.ini (aka resolutions ini file), so I'd
like to rule out that you're using a Mac OS version (in which case we
can't provide support, sorry).

If we're talking about a Windows version...:

- Make sure you don't have any resolution settings in the command-line
field.

- Make sure you're not invoking the render via an .ini file, or if you
do, that the .ini file does not have any resolution settings.

- Let us know how exactly you are running the render.

- Post the contents of the "Messages" window (after you've started the
render) here.

Post a reply to this message

Thankyou kindly for the quick reply.








Here is the Messages for a single frame (the first)



=========================================================================
Preset INI file is 'C:\USERS\MANGANESE\DOCUMENTS\POV-RAY\V3.7\INI\QUICKRES.INI',
section is '[512x384, AA 0.3]'.
Preset source file is
'C:\Users\Manganese\Documents\POV-Ray\v3.7\scenes\ST\ST_03\ST03.pov'.
File 'C:\Users\Manganese\Documents\POV-Ray\v3.7\scenes\ST\ST_03\\povray.ini'
exists - merging it.
Rendering with 6 threads.
-
Parser Options
  Input file: C:\Users\Manganese\Documents\POV-Ray\v3.7\scenes\ST\ST_03\ST03.pov
  Remove bounds........On
  Split unions.........Off
  Library paths:
    C:\Users\Manganese\Documents\POV-Ray\v3.7\include
    C:\WINDOWS\Fonts
Animation Options
  Initial Frame:        0  Final Frame:      249
  Frame Step:           1
  Initial Clock:    0.000  Final Clock:   10.000
  Cyclic Animation.....Off  Field render.........Off  Odd lines/frames.....Off
Image Output Options
  Image resolution.....800 by 600 (rows 1 to 600, columns 1 to 800).
  Output
file..........C:\Users\Manganese\Documents\POV-Ray\v3.7\scenes\ST\ST_03\ST03000.png,
24 bpp PNG
  Dithering............Off
  Graphic display......On  (gamma: sRGB)
  Mosaic preview.......Off
  Continued trace......Off
Information Output Options
  All Streams to console..........On
  Debug Stream to console.........On
  Fatal Stream to console.........On
  Render Stream to console........On
  Statistics Stream to console....On
  Warning Stream to console.......On

Parser Statistics

Finite Objects:         2163
Infinite Objects:          1
Light Sources:             1
Total:                  2165

Parser Time
  Parse Time:       0 hours  0 minutes  0 seconds (0.109 seconds)
              using 1 thread(s) with 0.109 CPU-seconds total
  Bounding Time:    0 hours  0 minutes  0 seconds (0.000 seconds)
              using 1 thread(s) with 0.000 CPU-seconds total

Render Options
  Quality:  9
  Bounding boxes.......On   Bounding threshold: 3
  Antialiasing.........On  (Method 1, Threshold 0.300, Depth 3, Jitter 1.00,
Gamma 2.50)

Render Statistics
Image Resolution 800 x 600

Pixels:           510200   Samples:          621162   Smpls/Pxl: 1.22
Rays:            1462969   Saved:                 0   Max Level: 2/5

Ray->Shape Intersection          Tests       Succeeded  Percentage

Box                            1374048          642618     46.77
Plane                          2259111         1057296     46.80
Sphere                         1175852          635597     54.05
Bounding Box                  75098358        19433671     25.88

Shadow Ray Tests:           1095341   Succeeded:                301113
Shadow Cache Hits:           299199
Reflected Rays:              331607

Peak memory used:          47415296 bytes

Render Time:
  Photon Time:      No photons
  Radiosity Time:   No radiosity
  Trace Time:       0 hours  0 minutes  0 seconds (0.875 seconds)
              using 6 thread(s) with 4.575 CPU-seconds total
-


I am using Windows 10 and POVRay runs like a dream.

You will notice what appears (at least, to me) to be a contradiction:
First, QUICKRES.INI is loaded with 512x384, AA,
then later (in the Image Output Options, an Image Resolution of 800x600 is
selected.

Here is POVRAY.INI :



;                     PERSISTENCE OF VISION RAY TRACER
;
;                           POV-Ray VERSION 3.7
;
;                         SAMPLE POVRAY.INI FILE
;
;  The general form of the options is "Variable=value".  Everything
;  between the equals sign and the end of the line is considered part
;  of the value.  The spacing and layout is free-form but only one option
;  per line is allowed.  Variables and values are not case-sensitive.
;
;  Note: characters after a semi-colon are treated as a comment
;
;  Traditional POV-Ray switches beginning with + or - are also allowed
;  and they may be given with more than one switch per line.
;
;  Add your own options at the bottom and/or edit these to suit. See the
;  general documentation for full instructions on how to use INI options.
;
; Width of image in pixels.  Accepts integer values.
;
;
;
; Height of image in pixels.  Accepts integer values.
;

Width=512
Height=384
Antialias=On
Antialias_Threshold=0.3


;
; Sets minimum number of objects before auto bounding kicks in.
;
Bounding_Threshold = 3
;
;
; Turn display on
Display=On
;
; Turn verbose mode on
Verbose=On
;
;
; Specify path to search for any files not found in current directory.
; For example: Library_Path="C:\Program Files\POV-Ray for Windows\include"
; There may be some entries already here; if there are they were
; probably added by the install process or whoever set up the
; software for you. At the least you can expect an entry that
; points to the standard POV-Ray include files directory; on
; some operating systems there may also be one which points to
; the system's fonts directory.
;
; Note that some platforms (e.g. Windows, unless this feature is
; turned off via the configuration file) will automatically append
; standard locations like those mentioned above to the library
; path list after reading this file, so in those cases you don't
; necessarily have to have anything at all here.
;
Initial_Clock=0.0
Final_Clock=10.0
Initial_Frame=0
Final_Frame=249

Post a reply to this message

Am 28.08.2016 um 08:23 schrieb Giridhari:

> =========================================================================
> Preset INI file is 'C:\USERS\MANGANESE\DOCUMENTS\POV-RAY\V3.7\INI\QUICKRES.INI',
> section is '[512x384, AA 0.3]'.
> Preset source file is
> 'C:\Users\Manganese\Documents\POV-Ray\v3.7\scenes\ST\ST_03\ST03.pov'.
> File 'C:\Users\Manganese\Documents\POV-Ray\v3.7\scenes\ST\ST_03\\povray.ini'
> exists - merging it.

For some reason you seem to have copied "povray.ini" into the directory
where your scene file resides.

In such a case, POV-Ray reads that "povray.ini" in addition to its
master "povray.ini".

Post a reply to this message

THANKYOU so much!

That was it. The INI you noticed had 800x600 defined in it.

I keep POVRAY.INI files (for clock and frame data) for each segment of the
animation, so when I have finished putting it all together I can re-render each
segment at a higher resolution.

That would have taken me ages to find. Your help is invaluable.

Post a reply to this message

Am 2016-08-28 06:12, also sprach Giridhari:
> THANKYOU so much!
>
> That was it. The INI you noticed had 800x600 defined in it.
>
> I keep POVRAY.INI files (for clock and frame data) for each segment of the
> animation, so when I have finished putting it all together I can re-render each
> segment at a higher resolution.
>
> That would have taken me ages to find. Your help is invaluable.
>
>

Multiple POVRAY.INI files is bad form.  Rather, you should have separate 
named ini files and then specify the one you want on the command line.

My animation has 5 scenes, and the local .ini files for each scene each 
contain
master pov file to render
number of frames in scene.

It sounds like you are doing something similar, except naming them all 
POVRAY.INI

Minimally, you should rename them to scene0.ini, scene1.ini, etc.

-- 
dik

Post a reply to this message

Am 28.08.2016 um 21:26 schrieb dick balaska:

>> I keep POVRAY.INI files (for clock and frame data) for each segment of
>> the
>> animation, so when I have finished putting it all together I can
>> re-render each
>> segment at a higher resolution.
>>
>> That would have taken me ages to find. Your help is invaluable.
>>
>>
> 
> Multiple POVRAY.INI files is bad form.  Rather, you should have separate
> named ini files and then specify the one you want on the command line.
> 
> My animation has 5 scenes, and the local .ini files for each scene each
> contain
> master pov file to render
> number of frames in scene.
> 
> It sounds like you are doing something similar, except naming them all
> POVRAY.INI
> 
> Minimally, you should rename them to scene0.ini, scene1.ini, etc.

I would disagree.

Instead, I would claim that it is bad practice to have multiple scenes
in a single directory.

With only a single scene per directory, there is nothing wrong with
naming the corresponding .ini file `povray.ini`. It even has one major
advantage: You can invoke the render via the .pov file, and the
scene-specific .ini settings will still be respected.

Post a reply to this message

Am 2016-08-28 16:19, also sprach clipka:
> Am 28.08.2016 um 21:26 schrieb dick balaska:
>
> Instead, I would claim that it is bad practice to have multiple scenes
> in a single directory.

I agree. I don't actually have multiple scenes in a single directory.  I 
have a tree with the entire movie, lots of common subdirectories, and a 
single subdirectory for each scene.

I do have multiple .ini files per scene though.  Minimally I chomp the 
scenes at 480### [at] 23976 fps and 720p@30 fps (separate .inis) and I have 
test.ini to sometimes focus on whatever piece I'm working on. Like, just 
exercise the mushroom cloud generator.

I felt bad because my tree is

|
+- tteo
|  |
|  +- tteo.pov
|  +- direct.inc
|  +- beats.inc
|  +- debug.inc
|
+- ttco
    |
    +- ttco.pov
    +- direct.inc
    +- beats.inc
    +- debug.inc

and the povclipse parser totally doesn't care what directory direct.inc 
is in.  It just uses the first one it finds.

I felt bad about this until I noticed that the eclipse php parser 
suffers the same flaw.  If it's broken enough for them, it's broken 
enough for me.  So now I have directTteo.inc and directTtco.inc

-- 
dik

Post a reply to this message