1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973
1974
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2099
2100
2101
2102
2103
2104
2105
2106
2107
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
2130
2131
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
2237
2238
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
2258
2259
2260
2261
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
2272
2273
2274
2275
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292
2293
2294
2295
2296
2297
2298
2299
2300
2301
2302
2303
2304
2305
2306
2307
2308
2309
2310
2311
2312
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
2323
2324
2325
2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348
2349
2350
2351
2352
2353
2354
2355
2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366
2367
2368
2369
2370
2371
2372
2373
2374
2375
2376
2377
2378
2379
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404
2405
2406
2407
2408
2409
2410
2411
2412
2413
2414
2415
2416
2417
2418
2419
2420
2421
2422
2423
2424
2425
2426
2427
2428
2429
2430
2431
2432
2433
2434
2435
2436
2437
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
2448
2449
2450
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460
2461
2462
2463
2464
2465
2466
2467
2468
2469
2470
2471
2472
2473
2474
2475
2476
2477
2478
2479
2480
2481
2482
2483
2484
2485
2486
2487
2488
2489
2490
2491
2492
2493
2494
2495
2496
2497
2498
2499
2500
2501
2502
2503
2504
2505
2506
2507
2508
2509
2510
2511
2512
2513
2514
2515
2516
2517
2518
2519
2520
2521
2522
2523
2524
2525
2526
2527
2528
2529
2530
2531
2532
2533
2534
2535
2536
2537
2538
2539
2540
2541
2542
2543
2544
2545
2546
2547
2548
2549
2550
2551
2552
2553
2554
2555
2556
2557
2558
2559
2560
2561
2562
2563
2564
2565
2566
2567
2568
2569
2570
2571
2572
2573
2574
2575
2576
2577
2578
2579
2580
2581
2582
2583
2584
2585
2586
2587
2588
2589
2590
2591
2592
2593
2594
2595
2596
2597
2598
2599
2600
2601
2602
2603
2604
2605
2606
2607
2608
2609
2610
2611
2612
2613
2614
2615
2616
2617
2618
2619
2620
2621
2622
2623
2624
2625
2626
2627
2628
2629
2630
2631
2632
2633
2634
2635
2636
2637
2638
2639
2640
2641
2642
2643
2644
2645
2646
2647
2648
2649
2650
2651
2652
2653
2654
2655
2656
2657
2658
2659
2660
2661
2662
2663
2664
2665
2666
2667
2668
2669
2670
2671
2672
2673
2674
2675
2676
2677
2678
2679
2680
2681
2682
2683
2684
2685
2686
2687
2688
2689
2690
2691
2692
2693
2694
2695
2696
2697
2698
2699
2700
2701
2702
2703
2704
2705
2706
2707
2708
2709
2710
2711
2712
2713
2714
2715
2716
2717
2718
2719
2720
2721
2722
2723
2724
2725
2726
2727
2728
2729
2730
2731
2732
2733
2734
2735
2736
2737
2738
2739
2740
2741
2742
2743
2744
2745
2746
2747
2748
2749
2750
2751
2752
2753
2754
2755
2756
2757
2758
2759
2760
2761
2762
2763
2764
2765
2766
2767
2768
2769
2770
2771
2772
2773
2774
2775
2776
2777
2778
2779
2780
2781
2782
2783
2784
2785
2786
2787
2788
2789
2790
2791
2792
2793
2794
2795
2796
2797
2798
2799
2800
2801
2802
2803
2804
2805
2806
2807
2808
2809
2810
2811
2812
2813
2814
2815
2816
2817
2818
2819
2820
2821
2822
2823
2824
2825
2826
2827
2828
2829
2830
2831
2832
2833
2834
2835
2836
2837
2838
2839
2840
2841
2842
2843
2844
2845
2846
2847
2848
2849
2850
2851
2852
2853
2854
2855
2856
2857
2858
2859
2860
2861
2862
2863
2864
2865
2866
2867
2868
2869
2870
2871
2872
2873
2874
2875
2876
2877
2878
2879
2880
2881
2882
2883
2884
2885
2886
2887
2888
2889
2890
2891
2892
2893
2894
2895
2896
2897
2898
2899
2900
2901
2902
2903
2904
2905
2906
2907
2908
2909
2910
2911
2912
2913
2914
2915
2916
2917
2918
2919
2920
2921
2922
2923
2924
2925
2926
2927
2928
2929
2930
2931
2932
2933
2934
2935
2936
2937
2938
2939
2940
2941
2942
2943
2944
2945
2946
2947
2948
2949
2950
2951
2952
2953
2954
2955
2956
2957
2958
2959
2960
2961
2962
2963
2964
2965
2966
2967
2968
2969
2970
2971
2972
2973
2974
2975
2976
2977
2978
2979
2980
2981
2982
2983
2984
2985
2986
2987
2988
2989
2990
2991
2992
2993
2994
2995
2996
2997
2998
2999
3000
3001
3002
3003
3004
3005
3006
3007
3008
3009
3010
3011
3012
3013
3014
3015
3016
3017
3018
3019
3020
3021
3022
3023
3024
3025
3026
3027
3028
3029
3030
3031
3032
3033
3034
3035
3036
3037
3038
3039
3040
3041
3042
3043
3044
3045
3046
3047
3048
3049
3050
3051
3052
3053
3054
3055
3056
3057
3058
3059
3060
3061
3062
3063
3064
3065
3066
3067
3068
3069
3070
3071
3072
3073
3074
3075
3076
3077
3078
3079
3080
3081
3082
3083
3084
3085
3086
3087
3088
3089
3090
3091
3092
3093
3094
3095
3096
3097
3098
3099
3100
3101
3102
3103
3104
3105
3106
3107
3108
3109
3110
3111
3112
3113
3114
3115
3116
3117
3118
3119
3120
3121
3122
3123
3124
3125
3126
3127
3128
3129
3130
3131
3132
3133
3134
3135
3136
3137
3138
3139
3140
3141
3142
3143
3144
3145
3146
3147
3148
3149
3150
3151
3152
3153
3154
3155
3156
3157
3158
3159
3160
3161
3162
3163
3164
3165
3166
3167
3168
3169
3170
3171
3172
3173
3174
3175
3176
3177
3178
3179
3180
3181
3182
3183
3184
3185
3186
3187
3188
3189
3190
3191
3192
3193
3194
3195
3196
3197
3198
3199
3200
3201
3202
3203
3204
3205
3206
3207
3208
3209
3210
3211
3212
3213
3214
3215
3216
3217
3218
3219
3220
3221
3222
3223
3224
3225
3226
3227
3228
3229
3230
3231
3232
3233
3234
3235
3236
3237
3238
3239
3240
3241
3242
3243
3244
3245
3246
3247
3248
3249
3250
3251
3252
3253
3254
3255
3256
3257
3258
3259
3260
3261
3262
3263
3264
3265
3266
3267
3268
3269
3270
3271
3272
3273
3274
3275
3276
3277
3278
3279
3280
3281
3282
3283
3284
3285
3286
3287
3288
3289
3290
3291
3292
3293
3294
3295
3296
3297
3298
3299
3300
3301
3302
3303
3304
3305
3306
3307
3308
3309
3310
3311
3312
3313
3314
3315
3316
3317
3318
3319
3320
3321
3322
3323
3324
3325
3326
3327
3328
3329
3330
3331
3332
3333
3334
3335
3336
3337
3338
3339
3340
3341
3342
3343
3344
3345
3346
3347
3348
3349
3350
3351
3352
3353
3354
3355
3356
3357
3358
3359
3360
3361
3362
3363
3364
3365
3366
3367
3368
3369
3370
3371
3372
3373
3374
3375
3376
3377
3378
3379
3380
3381
3382
3383
3384
3385
3386
3387
3388
3389
3390
3391
3392
3393
3394
3395
3396
3397
3398
3399
3400
3401
3402
3403
3404
3405
3406
3407
3408
3409
3410
3411
3412
3413
3414
3415
3416
3417
3418
3419
3420
3421
3422
3423
3424
3425
3426
3427
3428
3429
3430
3431
3432
3433
3434
3435
3436
3437
3438
3439
3440
3441
3442
3443
3444
3445
3446
3447
3448
3449
3450
3451
3452
3453
3454
3455
3456
3457
3458
3459
3460
3461
3462
3463
3464
3465
3466
3467
3468
3469
3470
3471
3472
3473
3474
3475
3476
3477
3478
3479
3480
3481
3482
3483
3484
3485
3486
3487
3488
3489
3490
3491
3492
3493
3494
3495
3496
3497
3498
3499
3500
3501
3502
3503
3504
3505
3506
3507
3508
3509
3510
3511
3512
3513
3514
3515
3516
3517
3518
3519
3520
3521
3522
3523
3524
3525
3526
3527
3528
3529
3530
3531
3532
3533
3534
3535
3536
3537
3538
3539
3540
3541
3542
3543
3544
3545
3546
3547
3548
3549
3550
3551
3552
3553
3554
3555
3556
3557
3558
3559
3560
3561
3562
3563
3564
3565
3566
3567
3568
3569
3570
3571
3572
3573
3574
3575
3576
3577
3578
3579
3580
3581
3582
3583
3584
3585
3586
3587
3588
3589
3590
3591
3592
3593
3594
3595
3596
3597
3598
3599
3600
3601
3602
3603
3604
3605
3606
3607
3608
3609
3610
3611
3612
3613
3614
3615
3616
3617
3618
3619
3620
3621
3622
3623
3624
3625
3626
3627
3628
3629
3630
3631
3632
3633
3634
3635
3636
3637
3638
3639
3640
3641
3642
3643
3644
3645
3646
3647
3648
3649
3650
3651
3652
3653
3654
3655
3656
3657
3658
3659
3660
3661
3662
3663
3664
3665
3666
3667
3668
3669
3670
3671
3672
3673
3674
3675
3676
3677
3678
3679
3680
3681
3682
3683
3684
3685
3686
3687
3688
3689
3690
3691
3692
3693
3694
3695
3696
3697
3698
3699
3700
3701
3702
3703
3704
3705
3706
3707
3708
3709
3710
3711
3712
3713
3714
3715
3716
3717
3718
3719
3720
3721
3722
3723
3724
3725
3726
3727
3728
3729
3730
3731
3732
3733
3734
3735
3736
3737
3738
3739
3740
3741
3742
3743
3744
3745
3746
3747
3748
3749
3750
3751
3752
3753
3754
3755
3756
3757
3758
3759
3760
3761
3762
3763
3764
3765
3766
3767
3768
3769
3770
3771
3772
3773
3774
3775
3776
3777
3778
3779
3780
3781
3782
3783
3784
3785
3786
3787
3788
3789
3790
3791
3792
3793
3794
3795
3796
3797
3798
3799
3800
3801
3802
3803
3804
3805
3806
3807
3808
3809
3810
3811
3812
3813
3814
3815
3816
3817
3818
3819
3820
3821
3822
3823
3824
3825
3826
3827
3828
3829
3830
3831
3832
3833
3834
3835
3836
3837
3838
3839
3840
3841
3842
3843
3844
3845
3846
3847
3848
3849
3850
3851
3852
3853
3854
3855
3856
3857
3858
3859
3860
3861
3862
3863
3864
3865
3866
3867
3868
3869
3870
3871
3872
3873
3874
3875
3876
3877
3878
3879
3880
3881
3882
3883
3884
3885
3886
3887
3888
3889
3890
3891
3892
3893
3894
3895
3896
3897
3898
3899
3900
3901
3902
3903
3904
3905
3906
3907
3908
3909
3910
3911
3912
3913
3914
3915
3916
3917
3918
3919
3920
3921
3922
3923
3924
3925
3926
3927
3928
3929
3930
3931
3932
3933
3934
3935
3936
3937
3938
3939
3940
3941
3942
3943
3944
3945
3946
3947
3948
3949
3950
3951
3952
3953
3954
3955
3956
3957
3958
3959
3960
3961
3962
3963
3964
3965
3966
3967
3968
3969
3970
3971
3972
3973
3974
3975
3976
3977
3978
3979
3980
3981
3982
3983
3984
3985
3986
3987
3988
3989
3990
3991
3992
3993
3994
3995
3996
3997
3998
3999
4000
4001
4002
4003
4004
4005
4006
4007
4008
4009
4010
4011
4012
4013
4014
4015
4016
4017
4018
4019
4020
4021
4022
4023
4024
4025
4026
4027
4028
4029
4030
4031
4032
4033
4034
4035
4036
4037
4038
4039
4040
4041
4042
4043
4044
4045
4046
4047
4048
4049
4050
4051
4052
4053
4054
4055
4056
4057
4058
4059
4060
4061
4062
4063
4064
4065
4066
4067
4068
4069
4070
4071
4072
4073
4074
4075
4076
4077
4078
4079
4080
4081
4082
4083
4084
4085
4086
4087
4088
4089
4090
4091
4092
4093
4094
4095
4096
4097
4098
4099
4100
4101
4102
4103
4104
4105
4106
4107
4108
4109
4110
4111
4112
4113
4114
4115
4116
4117
4118
4119
4120
4121
4122
4123
4124
4125
4126
4127
4128
4129
4130
4131
4132
4133
4134
4135
4136
4137
4138
4139
4140
4141
4142
4143
4144
4145
4146
4147
4148
4149
4150
4151
4152
4153
4154
4155
4156
4157
4158
4159
4160
4161
4162
4163
4164
4165
4166
4167
4168
4169
4170
4171
4172
4173
4174
4175
4176
4177
4178
4179
4180
4181
4182
4183
4184
4185
4186
4187
4188
4189
4190
4191
4192
4193
4194
4195
4196
4197
4198
4199
4200
4201
4202
4203
4204
4205
4206
4207
4208
4209
4210
4211
4212
4213
4214
4215
4216
4217
4218
4219
4220
4221
4222
4223
4224
4225
4226
4227
4228
4229
4230
4231
4232
4233
4234
4235
4236
4237
4238
4239
4240
4241
4242
4243
4244
4245
4246
4247
4248
4249
4250
4251
4252
4253
4254
4255
4256
4257
4258
4259
4260
4261
4262
4263
4264
4265
4266
4267
4268
4269
4270
4271
4272
4273
4274
4275
4276
4277
4278
4279
4280
4281
4282
4283
4284
4285
4286
4287
4288
4289
4290
4291
4292
4293
4294
4295
4296
4297
4298
4299
4300
4301
4302
4303
4304
4305
4306
4307
4308
4309
4310
4311
4312
4313
4314
4315
4316
4317
4318
4319
4320
4321
4322
4323
4324
4325
4326
4327
4328
4329
4330
4331
4332
4333
4334
4335
4336
4337
4338
4339
4340
4341
4342
4343
4344
4345
4346
4347
4348
4349
4350
4351
4352
4353
4354
4355
4356
4357
4358
4359
4360
4361
4362
4363
4364
4365
4366
4367
4368
4369
4370
4371
4372
4373
4374
4375
4376
4377
4378
4379
4380
4381
4382
4383
4384
4385
4386
4387
4388
4389
4390
4391
4392
4393
4394
4395
4396
4397
4398
4399
4400
4401
4402
4403
4404
4405
4406
4407
4408
4409
4410
4411
4412
4413
4414
4415
4416
4417
4418
4419
4420
4421
4422
4423
4424
4425
4426
4427
4428
4429
4430
4431
4432
4433
4434
4435
4436
4437
4438
4439
4440
4441
4442
4443
4444
4445
4446
4447
4448
4449
4450
4451
4452
4453
4454
4455
4456
4457
4458
4459
4460
4461
4462
4463
4464
4465
4466
4467
4468
4469
4470
4471
4472
4473
4474
4475
4476
4477
4478
4479
4480
4481
4482
4483
4484
4485
4486
4487
4488
4489
4490
4491
4492
4493
4494
4495
4496
4497
4498
4499
4500
4501
4502
4503
4504
4505
4506
4507
4508
4509
4510
4511
4512
4513
4514
4515
4516
4517
4518
4519
4520
4521
4522
4523
4524
4525
4526
4527
4528
4529
4530
4531
4532
4533
4534
4535
4536
4537
4538
4539
4540
4541
4542
4543
4544
4545
4546
4547
4548
4549
4550
4551
4552
4553
4554
4555
4556
4557
4558
4559
4560
4561
4562
4563
4564
4565
4566
4567
4568
4569
4570
4571
4572
4573
4574
4575
4576
4577
4578
4579
4580
4581
4582
4583
4584
4585
4586
4587
4588
4589
4590
4591
4592
4593
4594
4595
4596
4597
4598
4599
4600
4601
4602
4603
4604
4605
4606
4607
4608
4609
4610
4611
4612
4613
4614
4615
4616
4617
4618
4619
4620
4621
4622
4623
4624
4625
4626
4627
4628
4629
4630
4631
4632
4633
4634
4635
4636
4637
4638
4639
4640
4641
4642
4643
4644
4645
4646
4647
4648
4649
4650
4651
4652
4653
4654
4655
4656
4657
4658
4659
4660
4661
4662
4663
4664
4665
4666
4667
4668
4669
4670
4671
4672
4673
4674
4675
4676
4677
4678
4679
4680
4681
4682
4683
4684
4685
4686
4687
4688
4689
4690
4691
4692
4693
4694
4695
4696
4697
4698
4699
4700
4701
4702
4703
4704
4705
4706
4707
4708
4709
4710
4711
4712
4713
4714
4715
4716
4717
4718
4719
4720
4721
4722
4723
4724
4725
4726
4727
4728
4729
4730
4731
4732
4733
4734
4735
4736
4737
4738
4739
4740
4741
4742
4743
4744
4745
4746
4747
4748
4749
4750
4751
4752
4753
4754
4755
4756
4757
4758
4759
4760
4761
4762
4763
4764
4765
4766
4767
4768
4769
4770
4771
4772
4773
4774
4775
4776
4777
4778
4779
4780
4781
4782
4783
4784
4785
4786
4787
4788
4789
4790
4791
4792
4793
4794
4795
4796
4797
4798
4799
4800
4801
4802
4803
4804
4805
4806
4807
4808
4809
4810
4811
4812
4813
4814
4815
4816
4817
4818
4819
4820
4821
4822
4823
4824
4825
4826
4827
4828
4829
4830
4831
4832
4833
4834
4835
4836
4837
4838
4839
4840
4841
4842
4843
4844
4845
4846
4847
4848
4849
4850
4851
4852
4853
4854
4855
4856
4857
4858
4859
4860
4861
4862
4863
4864
4865
4866
4867
4868
4869
4870
4871
4872
4873
4874
4875
4876
4877
4878
4879
4880
4881
4882
4883
4884
4885
4886
4887
4888
4889
4890
4891
4892
4893
4894
4895
4896
4897
4898
4899
4900
4901
4902
4903
4904
4905
4906
4907
4908
4909
4910
4911
4912
4913
4914
4915
4916
4917
4918
4919
4920
4921
4922
4923
4924
4925
4926
4927
4928
4929
4930
4931
4932
4933
4934
4935
4936
4937
4938
4939
4940
4941
4942
4943
4944
4945
4946
4947
4948
4949
4950
4951
4952
4953
4954
4955
4956
4957
4958
4959
4960
4961
4962
4963
4964
4965
4966
4967
4968
4969
4970
4971
4972
4973
4974
4975
4976
4977
4978
4979
4980
4981
4982
4983
4984
4985
4986
4987
4988
4989
4990
4991
4992
4993
4994
4995
4996
4997
4998
4999
5000
5001
5002
5003
5004
5005
5006
5007
5008
5009
5010
5011
5012
5013
5014
5015
5016
5017
5018
5019
5020
5021
5022
5023
5024
5025
5026
5027
5028
5029
5030
5031
5032
5033
5034
5035
5036
5037
5038
5039
5040
5041
5042
5043
5044
5045
5046
5047
5048
5049
5050
5051
5052
5053
5054
5055
5056
5057
5058
5059
5060
5061
5062
5063
|
<!-- This file copyright Persistence of Vision Raytracer Pty. Ltd. 2003-2004 -->
<html>
<head>
<!-- NOTE: In order to users to help find information about POV-Ray using -->
<!-- web search engines, we ask you to *not* let them index documentation -->
<!-- mirrors because effectively, when searching, users will get hundreds -->
<!-- of results containing the same information! For this reason, the two -->
<!-- meta tags below disable archiving and indexing of this page by all -->
<!-- search engines that support these meta tags. -->
<meta content="noarchive" name="robots">
<meta content="noindex" name="robots">
<meta content="no-cache" http-equiv="Pragma">
<meta content="0" http-equiv="expires">
<title>3.1.2 Command-line Options</title>
<link href="povray35.css" rel="stylesheet" type="text/css">
</head>
<body>
<table class="NavBar" width="100%">
<tr>
<td align="left" nowrap="" valign="middle" width="32">
<a href="s_94.html"><img alt="previous" border="0" src="prev.png"></a>
</td>
<td align="left" valign="middle" width="30%">
<a href="s_94.html">3.1.1 Notation and Basic Assumptions</a>
</td>
<td align="center" valign="middle">
<strong class="NavBar">POV-Ray 3.6 for UNIX documentation</strong><br> <strong>3.1.2
Command-line Options</strong>
</td>
<td align="right" valign="middle" width="30%">
<a href="s_96.html">3.2 Scene Description Language</a>
</td>
<td align="right" nowrap="" valign="middle" width="32">
<a href="s_96.html"><img alt="next" border="0" src="next.png"></a>
</td>
</tr>
</table>
<h3><a name="s03_01_02">3.1.2 </a>Command-line Options</h3>
<p>
The reference section describes all command line switches and INI file keywords that are used to set the options of
POV-Ray. It is supposed to be used as a reference for looking up things. It does not contain detailed explanations on
how scenes are written or how POV-Ray is used. It just explains all features, their syntax, applications, limits,
drawbacks, etc.
</p>
<p>
Options may be specified by switches or INI-style options. Almost all INI-style options have equivalent <code> +</code>/
<code>-</code> switches and most switches have equivalent INI-style option. The following sections give a detailed
description of each POV-Ray option. It includes both the INI-style settings and the <code> +</code>/ <code>-</code>
switches.
</p>
<p>
The notation and terminology used is described in the tables below.
</p>
<table width="100%">
<tr>
<td width="30%">
<code>Keyword=</code>bool
</td>
<td width="70%">
Turn <code>Keyword</code> on if bool equals <code>true</code>, <code> yes</code>, <code>on</code> or <code>1</code>
and Turn it off if it is any other value.
</td>
</tr>
<tr>
<td>
<code>Keyword=true</code>
</td>
<td>
Do this option if <code>true</code>, <code>yes</code>, <code> on</code> or <code>1</code> is specified.
</td>
</tr>
<tr>
<td>
<code>Keyword=false</code>
</td>
<td>
Do this option if <code>false</code>, <code>no</code>, <code> off</code> or <code>0</code> is specified.
</td>
</tr>
<tr>
<td>
<code>Keyword=</code>filename
</td>
<td>
Set <code>Keyword</code> to filename where filename is any valid file name.
<p class="Note">
<strong>Note:</strong> some options prohibit the use of any of the above <code> true</code> or <code>false</code>
values as a file name. They are noted in later sections.
</p>
</td>
</tr>
<tr>
<td>
n
</td>
<td>
Any integer such as in <code>+W320</code>
</td>
</tr>
<tr>
<td>
n.n
</td>
<td>
Any float such as in <code>Clock=3.45</code>
</td>
</tr>
<tr>
<td>
0.n
</td>
<td>
Any float < 1.0 even if it has no leading 0
</td>
</tr>
<tr>
<td>
s
</td>
<td>
Any string of text
</td>
</tr>
<tr>
<td>
x or y
</td>
<td>
Any single character
</td>
</tr>
<tr>
<td>
path
</td>
<td>
Any directory name, drive optional, no final path separator ("\" or "/", depending on the
operating system)
</td>
</tr>
</table>
<p>
Unless otherwise specifically noted, you may assume that either a plus or minus sign before a switch will produce
the same results.
</p>
<h4><a name="s03_01_02_01">3.1.2.1 </a>Animation Options</h4>
<a name="s03_01_02_01_i1"><a name="s03_01_02_01_i2">
<p>
Internal animation loop, automatic output file name numbering and the ability to shell out to the operating system
to external utilities which can assemble individual frames into an animation, greatly improved the animation
capability. The internal animation loop is simple yet flexible. You may still use external programs or batch files to
create animations without the internal loop.
</p>
<h5><a name="s03_01_02_01_01">3.1.2.1.1 </a>External Animation Loop</h5>
<a name="s03_01_02_01_01_i1"><a name="s03_01_02_01_01_i2">
<table width="100%">
<tr>
<td width="30%">
<code>Clock=</code>n.n
</td>
<td width="70%">
Sets <code><a href="s_97.html#s03_02_01_03_06">clock</a></code> float identifier to n.n
</td>
</tr>
<tr>
<td>
<code>+K</code>n.n
</td>
<td>
Same as <code>Clock=</code>n.n
</td>
</tr>
</table>
<a name="s03_01_02_01_01_i3"><a name="Clock, ini-option"></a>
<p>
The <code>Clock=</code><em>n.n</em> option or the <code> +K</code><em>n.n</em> switch may be used to pass a single
float value to the program for basic animation. The value is stored in the float identifier <code>clock</code>. If an
object had a <code>rotate <0,clock,0></code> attached then you could rotate the object by different amounts over
different frames by setting <code> +K10.0</code>,<code>+K20.0</code>... etc. on successive renderings. It is up to the
user to repeatedly invoke POV-Ray with a different <code> Clock</code> value and a different <code> Output_File_Name</code>
for each frame.
</p>
<h5><a name="s03_01_02_01_02">3.1.2.1.2 </a>Internal Animation Loop</h5>
<a name="s03_01_02_01_02_i1">
<table width="100%">
<tr>
<td width="30%">
<code>Initial_Frame=</code>n<a name="s03_01_02_01_02_i2"><a name="Initial_Frame, ini-option"></a>
</td>
<td width="70%">
Sets initial frame number to n
</td>
</tr>
<tr>
<td>
<code>Final_Frame=</code>n<a name="s03_01_02_01_02_i3"><a name="Final_Frame, ini-option"></a>
</td>
<td>
Sets final frame number to n
</td>
</tr>
<tr>
<td>
<code>Initial_Clock=</code>n.n<a name="s03_01_02_01_02_i4"><a name="Initial_Clock, ini-option"></a>
</td>
<td>
Sets initial clock value to n.n
</td>
</tr>
<tr>
<td>
<code>Final_Clock=</code>n.n<a name="s03_01_02_01_02_i5"><a name="Final_Clock, ini-option"></a>
</td>
<td>
Sets final clock value to n.n
</td>
</tr>
<tr>
<td>
<code>+KFI</code>n<a name="s03_01_02_01_02_i6">
</td>
<td>
Same as <code>Initial_Frame=</code>n
</td>
</tr>
<tr>
<td>
<code>+KFF</code>n<a name="s03_01_02_01_02_i7">
</td>
<td>
Same as <code>Final_Frame=</code>n
</td>
</tr>
<tr>
<td>
<code>+KI</code>n.n<a name="s03_01_02_01_02_i8">
</td>
<td>
Same as <code>Initial_Clock=</code>n.n
</td>
</tr>
<tr>
<td>
<code>+KF</code>n.n
</td>
<td>
Same as <code>Final_Clock=</code>n.n
</td>
</tr>
</table>
<p>
The internal animation loop relieves the user of the task of generating complicated sets of batch files to invoke
POV-Ray multiple times with different settings. While the multitude of options may look intimidating, the clever set
of default values means that you will probably only need to specify the <code>Final_Frame</code>=<em>n</em> or the <code>+KFF</code><em>n</em>
option to specify the number of frames. All other values may remain at their defaults.
</p>
<p>
Any <code>Final_Frame</code> setting other than -1 will trigger POV-Ray's internal animation loop. For example <code>
Final_Frame=10</code> or <code>+KFF10</code> causes POV-Ray to render your scene 10 times. If you specified <code><a href="s_95.html#s03_01_02_04_02">Output_File_Name</a>=file.tga</code>
then each frame would be output as <code>file01.tga</code>, <code>file02.tga</code>, <code>file03.tga</code> etc. The
number of zero-padded digits in the file name depends upon the final frame number. For example <code>+KFF100</code>
would generate <code>file001.tga</code> through <code>file100.tga</code>. The frame number may encroach upon the file
name. On MS-DOS with an eight character limit, <code>myscene.pov</code> would render to <code>mysce001.tga</code>
through <code>mysce100.tga</code>.
</p>
<p>
The default <code>Initial_Frame=1</code> will probably never have to be changed. You would only change it if you
were assembling a long animation sequence in pieces. One scene might run from frame 1 to 50 and the next from 51 to
100. The <code>Initial_Frame</code>=<em>n</em> or <code> +KFI</code><em>n</em> option is for this purpose.
</p>
<p class="Note">
<strong>Note:</strong> if you wish to render a subset of frames such as 30 through 40 out of a 1 to
100 animation, you should not change <code>Initial_Frame</code> or <code>Final_Frame</code>. Instead you should use
the subset commands described in section "<a href="s_95.html#s03_01_02_01_03">Subsets of Animation Frames</a>".
</p>
<p>
Unlike some animation packages, the action in POV-Ray animated scenes does not depend upon the integer frame
numbers. Rather you should design your scenes based upon the float identifier <code><a href="s_97.html#s03_02_01_03_06">clock</a></code>.
By default, the clock value is 0.0 for the initial frame and 1.0 for the final frame. All other frames are
interpolated between these values. For example if your object is supposed to rotate one full turn over the course of
the animation, you could specify <code>rotate 360*clock*y</code>. Then as clock runs from 0.0 to 1.0, the object
rotates about the y-axis from 0 to 360 degrees.
</p>
<p>
The major advantage of this system is that you can render a 10 frame animation or a 100 frame or 500 frame or 329
frame animation yet you still get one full 360 degree rotation. Test renders of a few frames work exactly like final
renders of many frames.
</p>
<p>
In effect you define the motion over a continuous float valued parameter (the clock) and you take discrete samples
at some fixed intervals (the frames). If you take a movie or video tape of a real scene it works the same way. An
object's actual motion depends only on time. It does not depend on the frame rate of your camera.
</p>
<p>
Many users have already created scenes for POV-Ray 2 that expect clock values over a range other than the default
0.0 to 1.0. For this reason we provide the <code>Initial_Clock</code>=<em>n.n</em> or <code>+KI</code><em>n.n</em> and <code>Final_Clock</code>=<em>n.n</em>
or <code>+KF</code><em>n.n</em> options. For example to run the clock from 25.0 to 75.0 you would specify <code>Initial_Clock=25.0</code>
and <code>Final_Clock=75.0</code>. Then the clock would be set to 25.0 for the initial frame and 75.0 for the final
frame. In-between frames would have clock values interpolated from 25.0 through 75.0 proportionally.
</p>
<p>
Users who are accustomed to using frame numbers rather than clock values could specify <code> Initial_Clock=1.0</code>
and <code>Final_Clock=10.0</code> and <code>Frame_Final=10</code> for a 10 frame animation.
</p>
<p>
For new scenes, we recommend you do not change the <code> Initial_Clock</code> or <code> Final_Clock</code> from
their default 0.0 to 1.0 values. If you want the clock to vary over a different range than the default 0.0 to 1.0, we
recommend you handle this inside your scene file as follows...
</p>
<pre>
#declare Start = 25.0;
#declare End = 75.0;
#declare My_Clock = Start+(End-Start)*clock;
</pre>
<p>
Then use <code>My_Clock</code> in the scene description. This keeps the critical values 25.0 and 75.0 in your .pov
file.
</p>
<p class="Note">
<strong>Note:</strong> more details concerning the inner workings of the animation loop are in the
section on shell-out operating system commands in section "<a href="s_95.html#s03_01_02_06">Shell-out to
Operating System</a>".
</p>
<h5><a name="s03_01_02_01_03">3.1.2.1.3 </a>Subsets of Animation Frames</h5>
<a name="s03_01_02_01_03_i1">
<table width="100%">
<tr>
<td width="30%">
<code>Subset_Start_Frame=</code>n<a name="s03_01_02_01_03_i2"><a name="Subset_Start_Frame"></a><a name="s03_01_02_01_03_i3"><a name="Subset_Start_Frame, ini-option"></a>
</td>
<td width="70%">
Set subset starting frame to n
</td>
</tr>
<tr>
<td>
<code>Subset_Start_Frame=</code>0.n
</td>
<td>
Set subset starting frame to n percent
</td>
</tr>
<tr>
<td>
<code>Subset_End_Frame=</code>n<a name="s03_01_02_01_03_i4"><a name="Subset_End_Frame"></a><a name="s03_01_02_01_03_i5"><a name="Subset_End_Frame, ini-option"></a>
</td>
<td>
Set subset ending frame to n
</td>
</tr>
<tr>
<td>
<code>Subset_End_Frame=</code>0.n
</td>
<td>
Set subset ending frame to n percent
</td>
</tr>
<tr>
<td>
<code>+SF</code>0.n<a name="s03_01_02_01_03_i6">
</td>
<td>
Same as <code>Subset_Start_Frame</code>
</td>
</tr>
<tr>
<td>
<code>+EF</code>0.n<a name="s03_01_02_01_03_i7">
</td>
<td>
Same as <code>Subset_End_Frame</code>
</td>
</tr>
</table>
<p>
When creating a long animation, it may be handy to render only a portion of the animation to see what it looks
like. Suppose you have 100 frames but only want to render frames 30 through 40. If you set <code>Initial_Frame=30</code>
and <code>Final_Frame=40</code> then the clock would vary from 0.0 to 1.0 from frames 30 through 40 rather than 0.30
through 0.40 as it should. Therefore you should leave <code> Initial_Frame=1</code> and <code>Final_Frame=100</code>
and use <code>Subset_Start_Frame=30</code> and <code>Subset_End_Frame=40</code> to selectively render part of the
scene. POV-Ray will then properly compute the clock values.
</p>
<p>
Usually you will specify the subset using the actual integer frame numbers however an alternate form of the subset
commands takes a float value in the range <em>0.0 <=n.nnn <=1.0</em> which is interpreted as a fraction of the
whole animation. For example, <code> Subset_Start_Frame=0.333</code> and <code>Subset_End_Frame=0.667</code> would
render the middle 1/3rd of a sequence regardless of the number of frames.
</p>
<h5><a name="s03_01_02_01_04">3.1.2.1.4 </a>Cyclic Animation</h5>
<a name="s03_01_02_01_04_i1">
<table width="100%">
<tr>
<td width="30%">
<code>Cyclic_Animation=</code>bool<a name="s03_01_02_01_04_i2"><a name="Cyclic_Animation"></a>
</td>
<td width="70%">
Turn cyclic animation on/off
</td>
</tr>
<tr>
<td>
<code>+KC</code><a name="s03_01_02_01_04_i3">
</td>
<td>
Turn cyclic animation on
</td>
</tr>
<tr>
<td>
<code>-KC</code><a name="s03_01_02_01_04_i4">
</td>
<td>
Turn cyclic animation off
</td>
</tr>
</table>
<p>
Many computer animation sequences are designed to be run in a continuous loop. Suppose you have an object that
rotates exactly 360 degrees over the course of your animation and you did <code>rotate 360*clock*y</code> to do so.
Both the first and last frames would be identical. Upon playback there would be a brief one frame jerkiness. To
eliminate this problem you need to adjust the clock so that the last frame does not match the first. For example a ten
frame cyclic animation should not use clock 0.0 to 1.0. It should run from 0.0 to 0.9 in 0.1 increments. However if
you change to 20 frames it should run from 0.0 to 0.95 in 0.05 increments. This complicates things because you would
have to change the final clock value every time you changed <code>Final_Frame</code>. Setting <code>Cyclic_Animation=on</code>
or using <code>+KC</code> will cause POV-Ray to automatically adjust the final clock value for cyclic animation
regardless of how many total frames. The default value for this setting is off.
</p>
<h5><a name="s03_01_02_01_05">3.1.2.1.5 </a>Field Rendering</h5>
<a name="s03_01_02_01_05_i1">
<table width="100%">
<tr>
<td width="30%">
<code>Field_Render=</code>bool<a name="s03_01_02_01_05_i2"><a name="Field_Render"></a>
</td>
<td width="70%">
Turn field rendering on/off
</td>
</tr>
<tr>
<td>
<code>Odd_Field=</code>bool<a name="s03_01_02_01_05_i3"><a name="Odd_Field"></a>
</td>
<td>
Set odd field flag
</td>
</tr>
<tr>
<td>
<code>+UF</code><a name="s03_01_02_01_05_i4">
</td>
<td>
Turn field rendering on
</td>
</tr>
<tr>
<td>
<code>-UF</code><a name="s03_01_02_01_05_i5">
</td>
<td>
Turn field rendering off
</td>
</tr>
<tr>
<td>
<code>+UO</code><a name="s03_01_02_01_05_i6">
</td>
<td>
Set odd field flag on
</td>
</tr>
<tr>
<td>
<code>-UO</code><a name="s03_01_02_01_05_i7">
</td>
<td>
Set odd field flag off
</td>
</tr>
</table>
<p>
Field rendering is sometimes used for animations when the animation is being output for television. TVs only
display alternate scan lines on each vertical refresh. When each frame is being displayed the fields are interlaced to
give the impression of a higher resolution image. The even scan lines make up the even field, and are drawn first
(i.e. scan lines 0, 2, 4, etc.), followed by the odd field, made up of the odd numbered scan lines are drawn
afterwards. If objects in an animation are moving quickly, their position can change noticeably from one field to the
next. As a result, it may be desirable in these cases to have POV-Ray render alternate fields at the actual field rate
(which is twice the frame rate), rather than rendering full frames at the normal frame rate. This would save a great
deal of time compared to rendering the entire animation at twice the frame rate, and then only using half of each
frame.
</p>
<p>
By default, field rendering is not used. Setting <code> Field_Render=on</code> or using <code> +UF</code> will
cause alternate frames in an animation to be only the even or odd fields of an animation. By default, the first frame
is the even field, followed by the odd field. You can have POV-Ray render the odd field first by specifying <code>
Odd_Field=on</code>, or by using the <code> +UO</code> switch.
</p>
<h4><a name="s03_01_02_02">3.1.2.2 </a>General Output Options</h4>
<a name="s03_01_02_02_i1">
<h5><a name="s03_01_02_02_01">3.1.2.2.1 </a>Height and Width of Output</h5>
<a name="s03_01_02_02_01_i1"><a name="s03_01_02_02_01_i2">
<table width="100%">
<tr>
<td width="30%">
<code>Height=</code>n<a name="s03_01_02_02_01_i3"><a name="Height, ini-option"></a>
</td>
<td width="70%">
Sets screen height to n pixels
</td>
</tr>
<tr>
<td>
<code>Width=</code>n<a name="s03_01_02_02_01_i4"><a name="Width, ini-option"></a>
</td>
<td>
Sets screen width to n pixels
</td>
</tr>
<tr>
<td>
<code>+H</code>n<a name="s03_01_02_02_01_i5">
</td>
<td>
Same as <code>Height=</code>n
</td>
</tr>
<tr>
<td>
<code>+W</code>n<a name="s03_01_02_02_01_i6">
</td>
<td>
Same as <code>Width=</code>n
</td>
</tr>
</table>
<p>
These switches set the height and width of the image in pixels. This specifies the image size for file output. The
preview display, if on, will generally attempt to pick a video mode to accommodate this size but the display settings
do not in any way affect the resulting file output.
</p>
<h5><a name="s03_01_02_02_02">3.1.2.2.2 </a>Partial Output Options</h5>
<a name="s03_01_02_02_02_i1">
<table width="100%">
<tr>
<td width="30%">
<code>Start_Column=</code>n<a name="s03_01_02_02_02_i2"><a name="Start_Column, ini-option"></a>
</td>
<td width="70%">
Set first column to n pixels
</td>
</tr>
<tr>
<td>
<code>Start_Column=</code>0.n
</td>
<td>
Set first column to n percent of width
</td>
</tr>
<tr>
<td>
<code>+SC</code>0.n<a name="s03_01_02_02_02_i3">
</td>
<td>
Same as <code>Start_Column</code>
</td>
</tr>
<tr>
<td>
<code>Start_Row=</code>n<a name="s03_01_02_02_02_i4"><a name="Start_Row, ini-option"></a>
</td>
<td>
Set first row to n pixels
</td>
</tr>
<tr>
<td>
<code>Start_Row=</code>0.n
</td>
<td>
Set first row to n percent of height
</td>
</tr>
<tr>
<td>
<code>+S</code>n<a name="s03_01_02_02_02_i5">
</td>
<td>
Same as <code>Start_Row=</code>n
</td>
</tr>
<tr>
<td>
<code>+SR</code>0.n or <code>+S</code>0.n
</td>
<td>
Same as <code>Start_Row=</code>0.n
</td>
</tr>
<tr>
<td>
<code>End_Column=</code>n<a name="s03_01_02_02_02_i6"><a name="End_Column, ini-option"></a>
</td>
<td>
Set last column to n pixels
</td>
</tr>
<tr>
<td>
<code>End_Column=</code>0.n
</td>
<td>
Set last column to n percent of width
</td>
</tr>
<tr>
<td>
<code>+EC</code>0.n<a name="s03_01_02_02_02_i7">
</td>
<td>
Same as <code>End_Column</code>
</td>
</tr>
<tr>
<td>
<code>End_Row=</code>n<a name="s03_01_02_02_02_i8"><a name="End_Row"></a><a name="s03_01_02_02_02_i9"><a name="End_Row, ini-option"></a>
</td>
<td>
Set last row to n pixels
</td>
</tr>
<tr>
<td>
<code>End_Row=</code>0.n
</td>
<td>
Set last row to n percent of height
</td>
</tr>
<tr>
<td>
<code>+E</code>n<a name="s03_01_02_02_02_i10">
</td>
<td>
Same as <code>End_Row=</code>n
</td>
</tr>
<tr>
<td>
<code>+ER</code>0.n or <code>+E</code>0.n
</td>
<td>
Same as <code>End_Row=</code>0.n
</td>
</tr>
</table>
<p>
When doing test rendering it is often convenient to define a small, rectangular sub-section of the whole screen so
you can quickly check out one area of the image. The <code>Start_Row</code>, <code>End_Row</code>, <code> Start_Column</code>
and <code>End_Column</code> options allow you to define the subset area to be rendered. The default values are the
full size of the image from (1,1) which is the upper left to (w,h) on the lower right where w and h are the <code>Width=</code><em>n</em>
and <code> Height=</code><em>n</em> values you have set.
</p>
<p class="Note">
<strong>Note:</strong> if the number specified is greater than 1 then it is interpreted as an absolute
row or column number in pixels. If it is a decimal value between 0.0 and 1.0 then it is interpreted as a percent of
the total width or height of the image.
</p>
<p>
For example: <code> Start_Row=0.75</code> and <code> Start_Column=0.75</code> starts on a row 75% down from the top
at a column 75% from the left. Thus it renders only the lower-right 25% of the image regardless of the specified width
and height.
</p>
<p>
The <code>+SR</code>, <code>+ER</code>, <code> +SC</code> and <code> +EC</code> switches work in the same way as
the corresponding INI-style settings for both absolute settings or percentages. Early versions of POV-Ray allowed only
start and end rows to be specified with <code> +S</code><em>n</em> and <code> +E</code><em>n</em> so they are still
supported in addition to <code> +SR</code> and <code>+ER</code>.
</p>
<p>
When rendering a subset of *columns* (<code>+sc/+ec</code>) POV-Ray generates a full width image and fills the not
rendered columns with black pixels. This should not be a problem for any image reading program no matter what file
format is used.
</p>
<p>
when rendering a subset of *rows* (<code>+sr/+er</code>) POV-Ray writes the full height into the image file header
and only writed those lines into the image that are rendered. This can cause problems with image reading programs that
are not checking the file while reading and just read over the end.
</p>
<p>
if POV-Ray wrote the actual height of the partial image into the image header there would be no way to continue the
trace in a later run.
</p>
<h5><a name="s03_01_02_02_03">3.1.2.2.3 </a>Interrupting Options</h5>
<a name="s03_01_02_02_03_i1">
<table width="100%">
<tr>
<td width="30%">
<code>Test_Abort=</code>bool<a name="s03_01_02_02_03_i2"><a name="Test_Abort, ini-option"></a>
</td>
<td width="70%">
Turn test for user abort on/off
</td>
</tr>
<tr>
<td>
<code>+X</code><a name="s03_01_02_02_03_i3">
</td>
<td>
Turn test abort on
</td>
</tr>
<tr>
<td>
<code>-X</code><a name="s03_01_02_02_03_i4">
</td>
<td>
Turn test abort off
</td>
</tr>
<tr>
<td>
<code>Test_Abort_Count=</code>n<a name="s03_01_02_02_03_i5"><a name="Test_Abort_Count, ini-option"></a>
</td>
<td>
Set to test for abort every n pixels
</td>
</tr>
<tr>
<td>
<code>+X</code>n
</td>
<td>
Set to test for abort every n pixels on
</td>
</tr>
<tr>
<td>
<code>-X</code>n
</td>
<td>
Set to test for abort off (in future test every n pixels)
</td>
</tr>
</table>
<p>
On some operating systems once you start a rendering you must let it finish. The <code>Test_Abort=on</code> option
or <code>+X</code> switch causes POV-Ray to test the keyboard for keypress. If you have pressed a key, it will
generate a controlled user abort. Files will be flushed and closed but only data through the last full row of pixels
is saved. POV-Ray exits with an error code 2 (normally POV-Ray returns 0 for a successful run or 1 for a fatal error).
</p>
<p>
When this option is on, the keyboard is polled on every line while parsing the scene file and on every pixel while
rendering. Because polling the keyboard can slow down a rendering, the <code> Test_Abort_Count=</code><em>n</em>
option or <code>+X</code><em>n</em> switch causes the test to be performed only every <em>n</em> pixels rendered or
scene lines parsed.
</p>
<h5><a name="s03_01_02_02_04">3.1.2.2.4 </a>Resuming Options</h5>
<a name="s03_01_02_02_04_i1">
<table width="100%">
<tr>
<td width="30%">
<code>Continue_Trace=</code>bool<a name="s03_01_02_02_04_i2"><a name="Continue_Trace, ini-option"></a>
</td>
<td width="70%">
Sets continued trace on/off
</td>
</tr>
<tr>
<td>
<code>+C</code><a name="s03_01_02_02_04_i3">
</td>
<td>
Sets continued trace on
</td>
</tr>
<tr>
<td>
<code>-C</code><a name="s03_01_02_02_04_i4">
</td>
<td>
Sets continued trace off
</td>
</tr>
<tr>
<td>
<code>Create_Ini=</code>file<a name="s03_01_02_02_04_i5"><a name="Create_Ini, ini-option"></a>
</td>
<td>
Generate an INI file to file
</td>
</tr>
<tr>
<td>
<code>Create_Ini=</code>true
</td>
<td>
Generate file.ini where file is scene name.
</td>
</tr>
<tr>
<td>
<code>Create_Ini=</code>false
</td>
<td>
Turn off generation of previously set file.ini
</td>
</tr>
<tr>
<td>
<code>+GI</code>file<a name="s03_01_02_02_04_i6">
</td>
<td>
Same as <code>Create_Ini=</code>file
</td>
</tr>
</table>
<p>
If you abort a render while it is in progress or if you used the <code><a href="s_95.html#s03_01_02_02_02">End_Row</a></code>
option to end the render prematurely, you can use <code>Continue_Trace=on</code> or <code>+C</code> option to continue
the render later at the point where you left off. This option reads in the previously generated output file, displays
the partial image rendered so far, then proceeds with the ray-tracing. This option cannot be used if file output is
disabled with <code><a href="s_95.html#s03_01_02_04">Output_to_file</a>=off</code> or <code>-F</code>.
</p>
<p>
The <code>Continue_Trace</code> option may not work if the <code>Start_Row</code> option has been set to anything
but the top of the file, depending on the output format being used. Also POV-Ray cannot continue the file once it has
been opened and saved again by any program
</p>
<p>
POV-Ray tries to figure out where to resume an interrupted trace by reading any previously generated data in the
specified output file. All file formats contain the image size, so this will override any image size settings
specified. Some file formats (namely TGA and PNG) also store information about where the file started (i. e. <code> +SC</code><em>n</em>
and <code> +SR</code><em>n</em> options), alpha output <code>+UA</code>, and bit-depth <code>+FN</code><em>n</em>,
which will override these settings. It is up to the user to make sure that all other options are set the same as the
original render.
</p>
<p>
The <code>Create_Ini</code> option or <code>+GI</code> switch provides an easy way to create an INI file with all
of the rendering options, so you can re-run files with the same options, or ensure you have all the same options when
resuming. This option creates an INI file with every option set at the value used for that rendering. This includes
default values which you have not specified. For example if you run POV-Ray with...
</p>
<pre>
POVRAY +Isimple.pov MYOPTS +GIrerun.ini MOREOPTS
</pre>
<p>
POV-Ray will create a file called <code>rerun.ini</code> with all of the options used to generate this scene. The
file is not written until all options have been processed. This means that in the above example, the file will include
options from both <code>myopts.ini</code> and <code> moreopts.ini</code> despite the fact that the <code>+GI</code>
switch is specified between them. You may now re-run the scene with...
</p>
<pre>
POVRAY RERUN
</pre>
<p>
or resume an interrupted trace with
</p>
<pre>
POVRAY RERUN +C
</pre>
<p>
If you add other switches with the <code>rerun.ini</code> reference, they will be included in future re-runs
because the file is re-written every time you use it.
</p>
<p>
The <code>Create_Ini</code> option is also useful for documenting how a scene was rendered. If you render <code>
waycool.pov</code> with <code> Create_Ini=on</code> then it will create a file <code>waycool.ini</code> that you could
distribute along with your scene file so other users can exactly re-create your image.
</p>
<h4><a name="s03_01_02_03">3.1.2.3 </a>Display Output Options</h4>
<a name="s03_01_02_03_i1">
<h5><a name="s03_01_02_03_01">3.1.2.3.1 </a>Display Hardware Settings</h5>
<a name="s03_01_02_03_01_i1">
<table width="100%">
<tr>
<td width="30%">
<code>Display=</code>bool<a name="s03_01_02_03_01_i2"><a name="Display, ini-option"></a>
</td>
<td width="70%">
Turns graphic display on/off
</td>
</tr>
<tr>
<td>
<code>+D</code><a name="s03_01_02_03_01_i3">
</td>
<td>
Turns graphic display on
</td>
</tr>
<tr>
<td>
<code>-D</code><a name="s03_01_02_03_01_i4">
</td>
<td>
Turns graphic display off
</td>
</tr>
<tr>
<td>
<code>Video_Mode=</code>x<a name="s03_01_02_03_01_i5"><a name="Video_Mode, ini-option"></a>
</td>
<td>
Set video mode to x; does not affect on/off
</td>
</tr>
<tr>
<td>
<code>+D</code>x
</td>
<td>
Set display on; Set mode to x
</td>
</tr>
<tr>
<td>
<code>-D</code>x
</td>
<td>
Set display off; but for future use mode x
</td>
</tr>
<tr>
<td>
<code>Palette=</code>y<a name="s03_01_02_03_01_i6"><a name="Palette, ini-option"></a>
</td>
<td>
Set display palette to y; does not affect on/off
</td>
</tr>
<tr>
<td>
<code>+D</code>xy
</td>
<td>
Set display on; Set mode x; Set palette y
</td>
</tr>
<tr>
<td>
<code>-D</code>xy
</td>
<td>
Set display off; use mode x, palette y in future
</td>
</tr>
<tr>
<td>
<code>Display_Gamma=</code>n.n<a name="s03_01_02_03_01_i7"><a name="Display_Gamma"></a><a name="s03_01_02_03_01_i8"><a name="Display_Gamma, ini-option"></a>
</td>
<td>
Sets the display gamma to n.n
</td>
</tr>
</table>
<p>
The <code>Display=on</code> or <code>+D</code> switch will turn on the graphics display of the image while it is
being rendered. Even on some non-graphics systems, POV-Ray may display an 80 by 24 character <em> "ASCII-Art"</em>
version of your image. Where available, the display may be full, 24-bit true color. Setting <code>Display=off</code>
or using the <code>-D</code> switch will turn off the graphics display which is the default.
</p>
<p>
On the Windows platform, the default is <code>Display=on</code>. Turning display off does not, of course, turn off
the actual video display. Instead, POV-Ray will not open the output window that it normally shows a render in.
</p>
<p>
The <code>Video_Mode=</code><em>x</em> option sets the display mode or hardware type chosen where <em>x</em> is a
single digit or letter that is machine dependent. Generally <code>Video_Mode=0</code> means the default or an
auto-detected setting should be used. When using switches, this character immediately follows the switch. For example
the <code>+D0</code> switch will turn on the graphics display in the default mode.
</p>
<p>
The <code> Palette=</code><em>y</em> option selects the palette to be used. Typically the single character
parameter <em>y</em> is a digit which selects one of several fixed palettes or a letter such <code>G</code> for gray
scale, <code> H</code> for 15-bit or 16-bit high color or <code> T</code> for 24-bit true color. When using switches,
this character is the 2nd character after the switch. For example the <code>+D0T</code> switch will turn on the
graphics display in the default mode with a true color palette. The <code> Display_Gamma=</code><em>n.n</em> setting
is not available as a command-line switch.
</p>
<p>
The <code> Display_Gamma</code> setting overcomes the problem of images (whether ray-traced or not) having
different brightness when being displayed on different monitors, different video cards, and under different operating
systems.
</p>
<p class="Note">
<strong>Note:</strong> the <code>Display_Gamma</code> is a setting based on your computer's display
hardware, and should be set correctly once and not changed.
</p>
<p>
The <code> Display_Gamma</code> INI setting works in conjunction with the new <code> assumed_gamma</code> global
setting to ensure that POV scenes and the images they create look the same on all systems. See section "<a href="s_102.html#s03_03_03_03">Assumed_Gamma</a>"
which describes the <code> assumed_gamma</code> global setting and describes gamma more thoroughly.
</p>
<p>
While the <code> Display_Gamma</code> can be different for each system, there are a few general rules that can be
used for setting <code> Display_Gamma</code> if you do not know it exactly. If the <code> Display_Gamma</code> keyword
does not appear in the INI file, POV-Ray assumes that the display gamma is 2.2. This is because most PC monitors have
a gamma value in the range 1.6 to 2.6 (newer models seem to have a lower gamma value). Mac has the ability to do gamma
correction inside the system software (based on a user setting in the gamma control panel). If the gamma control panel
is turned off, or is not available, the default Macintosh system gamma is 1.8. Many newer PC graphics cards can do
hardware gamma correction and should use the current Display_Gamma setting, usually 1.0.
</p>
<h5><a name="s03_01_02_03_02">3.1.2.3.2 </a>Setting your Display Gamma</h5>
<a name="s03_01_02_03_02_i1"><a name="s03_01_02_03_02_i2">
<p>
The following gamma test image can be used to help you set your <code>Display_Gamma</code> accurately.
</p>
<p>
Before viewing the gamma image darken the room and set the monitor brightness and contrast to maximum. While
viewing a black screen, lower the brightness gradually until the "background" is no longer noticeable (ie
when it just fades from view). This may be difficult on monitors that use overscanning, unless you change the viewable
area settings.<a name="s03_01_02_03_02_i3">
</p>
<p>
<br><center><img alt="Display gamma test image." src="images/reference/gamma.png"></center>
</p>
<p>
Now, lower the contrast until the alternating white and black bars on the left edge of each column are equal in
width. This is trying to get a 50% gray by using half white and half black. If this is not possible, choose a contrast
setting which is about in the middle. While viewing the image from a distance, or with squinted eyes, one of the
numbered "swatches" will best match the gray value approximated by the white and black bars. The number in
this "swatch" is your display's actual gamma value.
</p>
<p>
Normal display gamma values are in the range 2.0 to 2.6. If your monitor is usually used in a dim environment, we
often use a gamma value that is 15% - 25% lower than the actual display gamma to give the images more contrast. Some
systems, such as Macs and SGIs, already do gamma correction, so they may have display gammas of 1.0 or 1.8.
</p>
<p>
For scene files that do not contain an <code>assumed_gamma</code> global setting the INI file option <code>Display_Gamma</code>
will not have any affect on the preview output of POV-Ray or for most output file formats. However, the <code>Display_Gamma</code>
value is used when creating PNG format output files, and also when rendering the POV-Ray example files (because they
have an <code>assumed_gamma</code>), so it should still be correctly set for your system to ensure proper results.
</p>
<h5><a name="s03_01_02_03_03">3.1.2.3.3 </a>Display Related Settings</h5>
<table width="100%">
<tr>
<td width="30%">
<code>Pause_When_Done=</code>bool<a name="s03_01_02_03_03_i1"><a name="Pause_When_Done, ini-option"></a>
</td>
<td width="70%">
Sets pause when done on/off
</td>
</tr>
<tr>
<td>
<code>+P</code><a name="s03_01_02_03_03_i2">
</td>
<td>
Sets pause when done on
</td>
</tr>
<tr>
<td>
<code>-P</code><a name="s03_01_02_03_03_i3">
</td>
<td>
Sets pause when done off
</td>
</tr>
<tr>
<td>
<code>Verbose=</code>bool<a name="s03_01_02_03_03_i4"><a name="Verbose, ini-option"></a>
</td>
<td>
Set verbose messages on/off
</td>
</tr>
<tr>
<td>
<code>+V</code><a name="s03_01_02_03_03_i5">
</td>
<td>
Set verbose messages on
</td>
</tr>
<tr>
<td>
<code>-V</code><a name="s03_01_02_03_03_i6">
</td>
<td>
Set verbose messages off
</td>
</tr>
<tr>
<td>
<code>Draw_Vistas=</code>bool<a name="s03_01_02_03_03_i7"><a name="Draw_Vistas, ini-option"></a>
</td>
<td>
Turn draw vistas on/off
</td>
</tr>
<tr>
<td>
<code>+UD</code><a name="s03_01_02_03_03_i8">
</td>
<td>
Turn draw vistas on
</td>
</tr>
<tr>
<td>
<code>-UD</code><a name="s03_01_02_03_03_i9">
</td>
<td>
Turn draw vistas off
</td>
</tr>
</table>
<p>
On some systems, when the image is complete, the graphics display is cleared and POV-Ray switches back into text
mode to print the final statistics and to exit. Normally when the graphics display is on, you want to look at the
image awhile before continuing. Using <code>Pause_When_Done=on</code> or <code>+P</code> causes POV-Ray to pause in
graphics mode until you press a key to continue. The default is not to pause (<code>-P</code>).
</p>
<p>
When the graphics display is not used, it is often desirable to monitor progress of the rendering. Using <code>
Verbose=on</code> or <code>+V</code> turns on verbose reporting of your rendering progress. This reports the number of
the line currently being rendered, the elapsed time for the current frame and other information. On some systems, this
textual information can conflict with the graphics display. You may need to turn this off when the display is on. The
default setting is off (<code>-V</code>).
</p>
<p>
The option <code>Draw_Vistas=on</code> or <code>+UD</code> was originally a debugging help for POV-Ray's vista
buffer feature but it was such fun we decided to keep it. Vista buffering is a spatial sub-division method that
projects the 2-D extents of bounding boxes onto the viewing window. POV-Ray tests the 2-D x, y pixel location against
these rectangular areas to determine quickly which objects, if any, the viewing ray will hit. This option shows you
the 2-D rectangles used. The default setting is off (<code>-UD</code>) because the drawing of the rectangles can take
considerable time on complex scenes and it serves no critical purpose. See section "<a href="s_95.html#s03_01_02_08_02">Automatic
Bounding Control</a>" for more details.
</p>
<h5><a name="s03_01_02_03_04">3.1.2.3.4 </a>Mosaic Preview</h5>
<table width="100%">
<tr>
<td width="30%">
<code>Preview_Start_Size=</code>n<a name="s03_01_02_03_04_i1"><a name="Preview_Start_Size, ini-option"></a>
</td>
<td width="70%">
Set mosaic preview start size to n
</td>
</tr>
<tr>
<td>
<code>+SP</code>n<a name="s03_01_02_03_04_i2">
</td>
<td>
Same as Preview_Start_Size=n
</td>
</tr>
<tr>
<td>
<code>Preview_End_Size=</code>n<a name="s03_01_02_03_04_i3"><a name="Preview_End_Size, ini-option"></a>
</td>
<td>
Set mosaic preview end size to n
</td>
</tr>
<tr>
<td>
<code>+EP</code>n<a name="s03_01_02_03_04_i4">
</td>
<td>
Same as Preview_End_Size=n
</td>
</tr>
</table>
<p>
Typically, while you are developing a scene, you will do many low resolution test renders to see if objects are
placed properly. Often this low resolution version does not give you sufficient detail and you have to render the
scene again at a higher resolution. A feature called <em> "mosaic preview"</em> solves this problem by
automatically rendering your image in several passes.
</p>
<p>
The early passes paint a rough overview of the entire image using large blocks of pixels that look like mosaic
tiles. The image is then refined using higher resolutions on subsequent passes. This display method very quickly
displays the entire image at a low resolution, letting you look for any major problems with the scene. As it refines
the image, you can concentrate on more details, like shadows and textures. You do not have to wait for a full
resolution render to find problems, since you can interrupt the rendering early and fix the scene, or if things look
good, you can let it continue and render the scene at high quality and resolution.
</p>
<p>
To use this feature you should first select a <code> Width</code> and <code> Height</code> value that is the
highest resolution you will need. Mosaic preview is enabled by specifying how big the mosaic blocks will be on the
first pass using <code> Preview_Start_Size=</code><em>n</em> or <code> +SP</code><em>n</em>. The value n should be a
number greater than zero that is a power of two (1, 2, 4, 8, 16, 32, etc.) If it is not a power of two, the nearest
power of two less than n is substituted. This sets the size of the squares, measured in pixels. A value of 16 will
draw every 16th pixel as a 16*16 pixel square on the first pass. Subsequent passes will use half the previous value
(such as 8*8, 4*4 and so on.)
</p>
<p>
The process continues until it reaches 1*1 pixels or until it reaches the size you set with <code> Preview_End_Size=</code><em>n</em>
or <code> +EP</code><em>n</em>. Again the value n should be a number greater than zero that is a power of two and less
than or equal to <code> Preview_Start_Size</code>. If it is not a power of two, the nearest power of two less than n
is substituted. The default ending value is 1. If you set <code>Preview_End_Size</code> to a value greater than 1 the
mosaic passes will end before reaching 1*1, but POV-Ray will always finish with a 1*1. For example, if you want a
single 8*8 mosaic pass before rendering the final image, set <code> Preview_Start_Size=8</code> and <code>
Preview_End_Size=8</code>.
</p>
<p>
No file output is performed until the final 1*1 pass is reached. Although the preliminary passes render only as
many pixels as needed, the 1*1 pass re-renders every pixel so that anti-aliasing and file output streams work
properly. This makes the scene take up to 25% longer than the regular 1*1 pass to render, so it is suggested that
mosaic preview not be used for final rendering. Also, the lack of file output until the final pass means that
renderings which are interrupted before the 1*1 pass can not be resumed without starting over from the beginning.
</p>
<h4><a name="s03_01_02_04">3.1.2.4 </a>File Output Options</h4>
<table width="100%">
<tr>
<td width="30%">
<code>Output_to_File=</code>bool<a name="s03_01_02_04_i1"><a name="Output_to_File, ini-option"></a><a name="s03_01_02_04_i2"><a name="Output_to_File"></a>
</td>
<td width="70%">
Sets file output on/off
</td>
</tr>
<tr>
<td>
<code>+F</code>
</td>
<td>
Sets file output on (use default type)
</td>
</tr>
<tr>
<td>
<code>-F</code>
</td>
<td>
Sets file output off
</td>
</tr>
</table>
<p>
By default, POV-Ray writes an image file to disk. When you are developing a scene and doing test renders, the
graphic preview may be sufficient. To save time and disk activity you may turn file output off with <code>
Output_to_File=off</code> or <code>-F</code>.
</p>
<h5><a name="s03_01_02_04_01">3.1.2.4.1 </a>Output File Type</h5>
<table width="100%">
<tr>
<td width="30%">
<code>Output_File_Type=</code>x<a name="s03_01_02_04_01_i1"><a name="Output_File_Type, ini-option"></a>
</td>
<td width="70%">
Sets file output format to x
</td>
</tr>
<tr>
<td>
<code>+F</code>xn<a name="s03_01_02_04_01_i2">
</td>
<td>
Sets file output on; sets format x, depth n
</td>
</tr>
<tr>
<td>
<code>-F</code>xn<a name="s03_01_02_04_01_i3">
</td>
<td>
Sets file output off; but in future use format x, depth n
</td>
</tr>
<tr>
<td>
<code>Output_Alpha=</code>bool<a name="s03_01_02_04_01_i4"><a name="Output_Alpha, ini-option"></a>
</td>
<td>
Sets alpha output on/off
</td>
</tr>
<tr>
<td>
<code>+UA</code><a name="s03_01_02_04_01_i5">
</td>
<td>
Sets alpha output on
</td>
</tr>
<tr>
<td>
<code>-UA</code><a name="s03_01_02_04_01_i6">
</td>
<td>
Sets alpha output off
</td>
</tr>
<tr>
<td>
<code>Bits_Per_Color=</code>n<a name="s03_01_02_04_01_i7"><a name="Bits_Per_Color, ini-option"></a>
</td>
<td>
Sets file output bits/color to n
</td>
</tr>
</table>
<a name="s03_01_02_04_01_i8"><a name="output formats"></a>
<p>
The default type of image file depends on which platform you are using. MS-DOS and most others default to 24-bit
uncompressed Targa. Windows defaults to 'sys', which is 24-bit BMP. See your platform-specific documentation to see
what your default file type is. You may select one of several different file types using <code>Output_File_Type=</code><em>x</em>
or <code>+F</code><em>x</em> where <em>x</em> is one of the following...
</p>
<table width="100%">
<tr>
<td width="30%">
<code>.. C</code><a name="s03_01_02_04_01_i9"><a name="Targa output, compressed"></a><a name="s03_01_02_04_01_i10"><a name="Output, Targa, compressed"></a><a name="s03_01_02_04_01_i11">
</td>
<td width="70%">
<strong>C</strong>ompressed Targa-24 format (RLE, run length encoded)
</td>
</tr>
<tr>
<td>
<code>.. N</code><a name="s03_01_02_04_01_i12"><a name="PNG output"></a><a name="s03_01_02_04_01_i13"><a name="Output, PNG"></a><a name="s03_01_02_04_01_i14">
</td>
<td>
P<strong>N</strong>G (portable network graphics) format
</td>
</tr>
<tr>
<td>
<code>.. P</code><a name="s03_01_02_04_01_i15"><a name="PPM output"></a><a name="s03_01_02_04_01_i16"><a name="Output, PPM"></a><a name="s03_01_02_04_01_i17">
</td>
<td>
Unix <strong>P</strong>PM format
</td>
</tr>
<tr>
<td>
<code>.. S</code><a name="s03_01_02_04_01_i18"><a name="System-specific output"></a><a name="s03_01_02_04_01_i19"><a name="Output, system-specific"></a><a name="s03_01_02_04_01_i20"><a name="Output, BMP"></a><a name="s03_01_02_04_01_i21"><a name="BMP output"></a><a name="s03_01_02_04_01_i22">
</td>
<td>
<strong>S</strong>ystem-specific such as Mac Pict or Windows BMP
</td>
</tr>
<tr>
<td>
<code>.. T</code><a name="s03_01_02_04_01_i23"><a name="Targa output, uncompressed"></a><a name="s03_01_02_04_01_i24"><a name="Output, Targa, uncompressed"></a><a name="s03_01_02_04_01_i25">
</td>
<td>
Uncompressed <strong>T</strong>arga-24 format
</td>
</tr>
</table>
<p class="Note">
<strong>Note:</strong> the obsolete <code>+FD</code> dump format and <code>+FR</code> raw format have
been dropped because they were rarely used and no longer necessary. PPM, PNG, and system specific formats have been
added. PPM format images are uncompressed, and have a simple text header, which makes it a widely portable image
format. PNG is an image format designed not only to replace GIF, but to improve on its shortcomings. PNG offers the
highest compression available without loss for high quality applications, such as ray-tracing. The system specific
format depends on the platform used and is covered in the appropriate system specific documentation.
</p>
<p>
Most of these formats output 24 bits per pixel with 8 bits for each of red, green and blue data. PNG and PPM allow
you to optionally specify the output bit depth from 5 to 16 bits for each of the red, green, and blue colors, giving
from 15 to 48 bits of color information per pixel. The default output depth for all formats is 8 bits/color (16
million possible colors), but this may be changed for PNG and PPM format files by setting <code>Bits_Per_Color=</code><em>n</em>
or by specifying <code>+FN</code><em>n</em> or <code>+FP</code><em>n</em>, where n is the desired bit depth.
</p>
<p>
Specifying a smaller color depth like 5 bits/color (32768 colors) may be enough for people with 8- or 16-bit (256
or 65536 color) displays, and will improve compression of the PNG file. Higher bit depths like 10 or 12 may be useful
for video or publishing applications, and 16 bits/color is good for grayscale height field output (See section "<a href="s_105.html#s03_04_01_05">Height
Field</a>" for details on height fields).
</p>
<p>
Targa format also allows 8 bits of alpha transparency data to be output, while PNG format allows 5 to 16 bits of
alpha transparency data, depending on the color bit depth as specified above. You may turn this option on with <code>
Output_Alpha=on</code> or <code>+UA</code>. The default is off or <code> -UA</code>.
</p>
<p>
The alpha channel stores a transparency value for each pixel, just like there is also stored a value for red green
and blue light for each pixel. In POV-Ray, when the alpha channel is turned on, all areas of the image where the
background is partly or fully visible will be partly or fully transparent. Refractions of the background will also be
transparent, but not reflections. Also anti-aliasing is taken into account
</p>
<p>
The philosophy of the alpha channel feature in POV-Ray is that the background color should not be present in the
color of the image when the alpha channel is used. Instead, the amount of visible background is kept in the alpha and
*only* in the alpha channel. That ensures that images look correct when viewed with the alpha channel.
</p>
<p>
See section "<a href="s_115.html#s03_05_01_05_03">Using the Alpha Channel</a>" for further details on
using transparency in imagemaps in your scene.
</p>
<p>
In addition to support for variable bit-depths, alpha channel, and grayscale formats, PNG files also store the <code>
Display_Gamma</code> value so the image displays properly on all systems (see section "<a href="s_95.html#s03_01_02_03_01">Display
Hardware Settings</a>"). The <code>hf_gray_16</code> global setting, as described in section "<a href="s_102.html#s03_03_03_04">HF_Gray_16</a>"
will also affect the type of data written to the output file.
</p>
<h5><a name="s03_01_02_04_02">3.1.2.4.2 </a>Output File Name</h5>
<table width="100%">
<tr>
<td width="30%">
<code>Output_File_Name=</code>file<a name="s03_01_02_04_02_i1"><a name="Output_File_Name, ini-option"></a>
</td>
<td width="70%">
Sets output file to file
</td>
</tr>
<tr>
<td>
<code>+O</code>file<a name="s03_01_02_04_02_i2">
</td>
<td>
Same as <code>Output_File_Name=</code>file
</td>
</tr>
</table>
<p>
The default output filename is created from the scene name and need not be specified. The scene name is the input
name with all drive, path, and extension information stripped. For example if the input file name is <code>
c:\povray3\mystuff\myfile.pov</code> the scene name is <code> myfile</code>. The proper extension is appended to the
scene name based on the file type. For example <code>myfile.tga</code> or <code> myfile.png</code> might be used.
</p>
<p>
You may override the default output name using <code> Output_File_Name=</code><em>file</em> or <code> +O</code><em>file</em>.
For example:
</p>
<pre>
Input_File_Name=myinput.pov
Output_File_Name=myoutput.tga
</pre>
<p>
If an output file name of "-" is specified (a single minus sign), then the image will be written to
standard output, usually the screen. The output can then be piped into another program or to a GUI if desired.
</p>
<p>
<a name="s03_01_02_04_02_i3"><a name="Default Output Directory"></a><a name="s03_01_02_04_02_i4"><a name="Directory, default output"></a><a name="s03_01_02_04_02_i5"><a name="Output File, placing in a default directory"></a>
If the file specified is actually a path or directory or folder name and not a file name, then the default output name
is used but it is written to the specified directory. For example:
</p>
<pre>
Input_File_Name=myscene.pov
Output_File_Name=c:\povray3\myimages\
</pre>
<p>
This will create <code>c:\povray3\myimages\myscene.tga</code> as the output file.
</p>
<h5><a name="s03_01_02_04_03">3.1.2.4.3 </a>Output File Buffer</h5>
<a name="s03_01_02_04_03_i1"><a name="Buffer_Output"></a><a name="s03_01_02_04_03_i2"><a name="s03_01_02_04_03_i3"><a name="s03_01_02_04_03_i4"><a name="Buffer_Size"></a>
<p>
The output-file buffer options <code>Buffer_Output</code> and <code>Buffer_Size</code> are removed per POV-Ray 3.6
</p>
<p class="Note">
<strong>Note:</strong> the options are still accepted, but ignored, in order to be backward compatible
with old INI files.
</p>
<h5><a name="s03_01_02_04_04">3.1.2.4.4 </a>CPU Utilization Histogram</h5>
<p>
The CPU utilization histogram is a way of finding out where POV-Ray is spending its rendering time, as well as an
interesting way of generating heightfields. The histogram splits up the screen into a rectangular grid of blocks. As
POV-Ray renders the image, it calculates the amount of time it spends rendering each pixel and then adds this time to
the total rendering time for each grid block. When the rendering is complete, the histogram is a file which represents
how much time was spent computing the pixels in each grid block.
</p>
<p>
Not all versions of POV-Ray allow the creation of histograms. The histogram output is dependent on the file type
and the system that POV-Ray is being run on.
</p>
<h5><a name="s03_01_02_04_05">3.1.2.4.5 </a>File Type</h5>
<table width="100%">
<tr>
<td width="30%">
<code>Histogram_Type=</code>y<a name="s03_01_02_04_05_i1"><a name="Histogram_Type, ini-option"></a>
</td>
<td width="70%">
Set histogram type to y (Turn off if type is '<code>X</code>')
</td>
</tr>
<tr>
<td>
<code>+HT</code>y<a name="s03_01_02_04_05_i2">
</td>
<td>
Same as <code>Histogram_Type=</code>y
</td>
</tr>
</table>
<p>
The histogram output file type is nearly the same as that used for the image output file types in "Output File
Type". The available histogram file types are as follows.
</p>
<table width="100%">
<tr>
<td width="30%">
<code>+HTC</code><a name="s03_01_02_04_05_i3">
</td>
<td width="70%">
Comma separated values (CSV) often used in spreadsheets
</td>
</tr>
<tr>
<td>
<code>+HTN</code><a name="s03_01_02_04_05_i4">
</td>
<td>
PNG (portable network graphics) format grayscale
</td>
</tr>
<tr>
<td>
<code>+HTP</code><a name="s03_01_02_04_05_i5">
</td>
<td>
Unix PPM format
</td>
</tr>
<tr>
<td>
<code>+HTS</code><a name="s03_01_02_04_05_i6">
</td>
<td>
System-specific such as Mac Pict or Windows BMP
</td>
</tr>
<tr>
<td>
<code>+HTT</code><a name="s03_01_02_04_05_i7">
</td>
<td>
Uncompressed Targa-24 format (TGA)
</td>
</tr>
<tr>
<td>
<code>+HTX</code><a name="s03_01_02_04_05_i8">
</td>
<td>
No histogram file output is generated
</td>
</tr>
</table>
<p class="Note">
<strong>Note:</strong> <code>+HTC</code> does not generate a compressed Targa-24 format output file
but rather a text file with a comma-separated list of the time spent in each grid block, in left-to-right and top-to
bottom order. The units of time output to the CSV file are system dependent. See the system specific documentation for
further details on the time units in CSV files.
</p>
<p>
The Targa and PPM format files are in the POV heightfield format (see "<a href="s_105.html#s03_04_01_05">Height
Field</a>"), so the histogram information is stored in both the red and green parts of the image, which makes it
unsuitable for viewing. When used as a height field, lower values indicate less time spent calculating the pixels in
that block, while higher indicate more time spent in that block.
</p>
<p>
PNG format images are stored as grayscale images and are useful for both viewing the histogram data as well as for
use as a heightfield. In PNG files, the darker (lower) areas indicate less time spent in that grid block, while the
brighter (higher) areas indicate more time spent in that grid block.
</p>
<h5><a name="s03_01_02_04_06">3.1.2.4.6 </a>File Name</h5>
<table width="100%">
<tr>
<td width="30%">
<code>Histogram_Name=</code>file<a name="s03_01_02_04_06_i1"><a name="Histogram_Name, ini-option"></a>
</td>
<td width="70%">
Set histogram name to file
</td>
</tr>
<tr>
<td>
<code>+HN</code>file<a name="s03_01_02_04_06_i2">
</td>
<td>
Same as <code>Histogram_Name=</code>file
</td>
</tr>
</table>
<p>
The histogram file name is the name of the file in which to write the histogram data. If the file name is not
specified it will default to <code> histogram.ext</code>, where <code>ext</code> is based on the file type specified
previously.
</p>
<p class="Note">
<strong>Note:</strong> that if the histogram name is specified the file name extension should match
the file type.
</p>
<h5><a name="s03_01_02_04_07">3.1.2.4.7 </a>Grid Size</h5>
<table width="100%">
<tr>
<td width="30%">
<code>Histogram_Grid_Size=</code> nn.mm<a name="s03_01_02_04_07_i1"><a name="Histogram_Grid_Size, ini-option"></a>
</td>
<td width="70%">
Set histogram grid to nn by mm
</td>
</tr>
<tr>
<td>
<code>+HS</code>nn.mm<a name="s03_01_02_04_07_i2">
</td>
<td>
Same as <code>Histogram_Grid_Size=</code>nn.mm
</td>
</tr>
</table>
<p>
The histogram grid size gives the number of times the image is split up in both the horizontal and vertical
directions. For example
</p>
<pre>
povray +Isample +W640 +H480 +HTN +HS160.120 +HNhistogram.png
</pre>
<p>
will split the image into 160*120 grid blocks, each of size 4*4 pixels, and output a PNG file, suitable for viewing
or for use as a heightfield. Smaller numbers for the grid size mean more pixels are put into the same grid block. With
CSV output, the number of values output is the same as the number of grid blocks specified. For the other formats the
image size is identical to the rendered image rather than the specified grid size, to allow easy comparison between
the histogram and the rendered image. If the histogram grid size is not specified, it will default to the same size as
the image, so there will be one grid block per pixel.
</p>
<p class="Note">
<strong>Note:</strong> on systems that do task-switching or multi-tasking the histogram may not
exactly represent the amount of time POV-Ray spent in a given grid block since the histogram is based on real time
rather than CPU time. As a result, time may be spent for operating system overhead or on other tasks running at the
same time. This will cause the histogram to have speckling, noise or large spikes. This can be reduced by decreasing
the grid size so that more pixels are averaged into a given grid block.
</p>
<h4><a name="s03_01_02_05">3.1.2.5 </a>Scene Parsing Options</h4>
<a name="s03_01_02_05_i1">
<p>
POV-Ray reads in your scene file and processes it to create an internal model of your scene. The process is called <code>parsing</code>.
As your file is parsed other files may be read along the way. This section covers options concerning what to parse,
where to find it and what version specific assumptions it should make while parsing it.
</p>
<h5><a name="s03_01_02_05_01">3.1.2.5.1 </a>Constant</h5>
<a name="s03_01_02_05_01_i1"><a name="ini files, constant"></a><a name="s03_01_02_05_01_i2"><a name="Declare, ini-option"></a>
<table width="100%">
<tr>
<td width="30%">
<code>Declare=IDENTIFIER=FLOAT</code>
</td>
<td width="70%">
Declares an identifier with a float value
</td>
</tr>
</table>
<p>
You can now declare a constant in an INI file, and that constant will be available to the scene. Since INI file
statements may also be laced on the command-line, you can therefore also declare on the command-line (though there is
no switch for it).
</p>
<pre> Declare=MyValue=24 </pre>
<p>
This would be the same as a <code>#declare MyValue=24;</code> in a scene file. The value on the right-hand side
must be a constant float value.
</p>
<p>
A possible use could be switching off radiosity or photons from commandline:
</p>
<pre>
--in INI-file / on command-line
Declare=RAD=0
--in scenefile
global_settings {
#if (RAD)
radiosity {
...
}
#end
}
</pre>
<h5><a name="s03_01_02_05_02">3.1.2.5.2 </a>Input File Name</h5>
<table width="100%">
<tr>
<td width="30%">
<code>Input_File_Name=</code>file<a name="s03_01_02_05_02_i1"><a name="Input_File_Name, ini-option"></a>
</td>
<td width="70%">
Sets input file name to file
</td>
</tr>
<tr>
<td>
<code>+I</code>file<a name="s03_01_02_05_02_i2">
</td>
<td>
Same as <code>Input_File_Name=</code>file
</td>
</tr>
</table>
<p class="Note">
<strong>Note:</strong> there may be no space between <code>+I</code> and <code>file</code>.
</p>
<p>
You will probably always set this option but if you do not the default input filename is <code>object.pov</code>.
If you do not have an extension then <code>.pov</code> is assumed. On case-sensitive operating systems both <code>.pov</code>
and <code>.POV</code> are tried. A full path specification may be used (on MS-DOS systems <code>
+Ic:\povray3\mystuff\myfile.pov</code> is allowed for example). In addition to specifying the input file name this
also establishes the <em>scene name</em>.
</p>
<p>
The scene name is the input name with drive, path and extension stripped. In the above example the scene name is <code>myfile</code>.
This name is used to create a default output file name and it is referenced other places.
</p>
<p class="Note">
<strong>Note:</strong> as per version 3.5 you can now specify a POV file on the command-line without
the use of the +i switch (i.e. it works the same way as specifying an INI file without a switch), the POV file then
should be the last on the commandline.
</p>
<p>
If you use "-" as the input file name the input will be read from standard input. Thus you can pipe a
scene created by a program to POV-Ray and render it without having a scene file.
</p>
<p>
Under MS-DOS you can try this feature by typing.
</p>
<pre>
type ANYSCENE.POV | povray +I-
</pre>
<h5><a name="s03_01_02_05_03">3.1.2.5.3 </a>Include File Name</h5>
<table width="100%">
<tr>
<td width="30%">
<code>Include_Header=</code>file<a name="s03_01_02_05_03_i1"><a name="Include_Header, ini-option"></a>
</td>
<td width="70%">
Sets primary include file name to file
</td>
</tr>
<tr>
<td>
<code>+HI</code>file<a name="s03_01_02_05_03_i2">
</td>
<td>
Same as <code>Include_Header=</code>file
</td>
</tr>
</table>
<p>
This option allows you to include a file as the first include file of a scene file. You can for example use this
option to always include a specific set of default include files used by all your scenes.
</p>
<h5><a name="s03_01_02_05_04">3.1.2.5.4 </a>Library Paths</h5>
<a name="s03_01_02_05_04_i1"><a name="s03_01_02_05_04_i2"><a name="s03_01_02_05_04_i3"><a name="s03_01_02_05_04_i4"><a name="s03_01_02_05_04_i5">
<table width="100%">
<tr>
<td width="30%">
<code>Library_Path=</code>path<a name="s03_01_02_05_04_i6"><a name="Library_Path, ini-option"></a>
</td>
<td width="70%">
Add path to list of library paths
</td>
</tr>
<tr>
<td>
<code>+L</code>path<a name="s03_01_02_05_04_i7">
</td>
<td>
Same as <code>Library_Path=</code>path
</td>
</tr>
</table>
<p>
POV-Ray looks for files in the current directory. If it does not find a file it needs it looks in various other
library directories which you specify. POV-Ray does not search your operating system path. It only searches the
current directory and directories which you specify with this option. For example the standard include files are
usually kept in one special directory. You tell POV-Ray to look there with...
</p>
<pre>
Library_Path=c:\povray3\include
</pre>
<p>
You must not specify any final path separators ("\" or "/") at the end.
</p>
<p>
Multiple uses of this option switch do not override previous settings. Up to twenty unique paths may be specified.
If you specify the exact same path twice it is only counted once. The current directory will be searched first
followed by the indicated library directories in the order in which you specified them.
</p>
<h5><a name="s03_01_02_05_05">3.1.2.5.5 </a>Language Version</h5>
<table width="100%">
<tr>
<td width="30%">
<code>Version=</code>n.n<a name="s03_01_02_05_05_i1"><a name="Version, ini-option"></a>
</td>
<td width="70%">
Set initial language compatibility to version n.n
</td>
</tr>
<tr>
<td>
<code>+MV</code>n.n<a name="s03_01_02_05_05_i2">
</td>
<td>
Same as <code>Version=</code>n.n
</td>
</tr>
</table>
<p>
As POV-Ray has evolved from version 1.0 through to today we have made every effort to maintain some amount of
backwards compatibility with earlier versions. Some old or obsolete features can be handled directly without any
special consideration by the user. Some old or obsolete features can no longer be handled at all. However <em>some</em>
old features can still be used if you warn POV-Ray that this is an older scene. In the POV-Ray scene language you can
use the <code>#version</code> directive to switch version compatibility to different settings. See section "<a href="s_98.html#s03_02_02_05">The
#version Directive</a>" for more details about the language version directive. Additionally you may use the <code>Version=</code><em>n.n</em>
option or the <code>+MV</code><em>n.n</em> switch to establish the <em>initial</em> setting. For example one feature
introduced in 2.0 that was incompatible with any 1.0 scene files is the parsing of float expressions. Setting <code>
Version=1.0</code> or using <code>+MV1.0</code> turns off expression parsing as well as many warning messages so that
nearly all 1.0 files will still work. Naturally the default setting for this option is the current version number.
</p>
<p class="Note">
<strong>Note:</strong> some obsolete or re-designed features <em>are totally unavailable in the
current version of POV-Ray REGARDLES OF THE VERSION SETTING.</em> Details on these features are noted throughout this
documentation.
</p>
<h4><a name="s03_01_02_06">3.1.2.6 </a>Shell-out to Operating System</h4>
<table width="100%">
<tr>
<td width="30%">
<code>Pre_Scene_Command=</code>s<a name="s03_01_02_06_i1"><a name="Pre_Scene_Command, ini-option"></a>
</td>
<td width="70%">
Set command before entire scene
</td>
</tr>
<tr>
<td>
<code>Pre_Frame_Command=</code>s<a name="s03_01_02_06_i2"><a name="Pre_Frame_Command, ini-option"></a>
</td>
<td>
Set command before each frame
</td>
</tr>
<tr>
<td>
<code>Post_Scene_Command=</code>s<a name="s03_01_02_06_i3"><a name="Post_Scene_Command, ini-option"></a>
</td>
<td>
Set command after entire scene
</td>
</tr>
<tr>
<td>
<code>Post_Frame_Command=</code>s<a name="s03_01_02_06_i4"><a name="Post_Frame_Command, ini-option"></a>
</td>
<td>
Set command after each frame
</td>
</tr>
<tr>
<td>
<code>User_Abort_Command=</code>s<a name="s03_01_02_06_i5"><a name="User_Abort_Command, ini-option"></a>
</td>
<td>
Set command when user aborts POV-Ray
</td>
</tr>
<tr>
<td>
<code>Fatal_Error_Command=</code>s<a name="s03_01_02_06_i6"><a name="Fatal_Error_Command, ini-option"></a>
</td>
<td>
Set command when POV-Ray has fatal error
</td>
</tr>
</table>
<p class="Note">
<strong>Note:</strong> no <code>+</code> or <code>-</code> switches are available for these options.
They cannot be used from the command line. They may only be used from INI files.
</p>
<p>
POV-Ray offers you the opportunity to shell-out to the operating system at several key points to execute another
program or batch file. Usually this is used to manage files created by the internal animation loop however the shell
commands are available for any scene. The string <em>s</em> is a single line of text which is passed to the operating
system to execute a program. For example
</p>
<pre>
Post_Scene_Command=tga2gif -d -m myfile
</pre>
<p>
would use the utility <code>tga2gif</code> with the <code>-D</code> and <code>-M</code> parameters to convert <code>myfile.tga</code>
to <code> myfile.gif</code> after the scene had finished rendering.
</p>
<p class="Note">
<strong>Note:</strong> individual platforms may provide means of preventing shell-outs from occurring.
For example, the Windows version provides a menu command to turn shell-outs off (which is the default setting for that
platform). The reason for this (along with file I/O restrictions) is to attempt to prevent untrusted INI files from
doing harm to your system.
</p>
<h5><a name="s03_01_02_06_01">3.1.2.6.1 </a>String Substitution in Shell Commands</h5>
<p>
It could get cumbersome to change the <code>Post_Scene_Command</code> every time you changed scene names. POV-Ray
can substitute various values into a command string for you. For example:
</p>
<pre>
Post_Scene_Command=tga2gif -d -m %s
</pre>
<p>
POV-Ray will substitute the <code>%s</code> with the scene name in the command. The <em>scene name</em> is the <code>Input_File_Name</code>
or <code>+I</code> setting with any drive, directory and extension removed. For example:
</p>
<pre>
Input_File_Name=c:\povray3\scenes\waycool.pov
</pre>
<p>
is stripped down to the scene name <code>waycool</code> which results in...
</p>
<pre>
Post_Scene_Command=tga2gif -d -m waycool
</pre>
<p>
In an animation it may be necessary to have the exact output file name with the frame number included. The string <code>%o</code>
will substitute the output file name. Suppose you want to save your output files in a zip archive using the utility
program <code>pkzip</code>. You could do...
</p>
<pre>
Post_Frame_Command=pkzip -m %s %o
</pre>
<p>
After rendering frame 12 of <code>myscene.pov</code> POV-Ray would shell to the operating system with
</p>
<pre>
pkzip -m myscene mysce012.tga
</pre>
<p>
The <code>-M</code> switch in <code>pkzip</code> moves <code> mysce012.tga</code> to <code>myscene.zip</code> and
removes it from the directory. Note that <code>%o</code> includes frame numbers only when in an animation loop. During
the <code>Pre_Scene_Command</code> and <code> Post_Scene_Command</code> there is no frame number so the original,
unnumbered <code>Output_File_Name</code> is used. Any <code> User_Abort_Command</code> or <code>Fatal_Error_Command</code>
not inside the loop will similarly give an unnumbered <code>%o</code> substitution.
</p>
<p>
Here is the complete list of substitutions available for a command string.
</p>
<table width="100%">
<tr>
<td width="30%">
<code>%o</code>
</td>
<td width="70%">
Output file name with extension and embedded frame number if any
</td>
</tr>
<tr>
<td>
<code>%s</code>
</td>
<td>
Scene name derived by stripping path and ext from input name
</td>
</tr>
<tr>
<td>
<code>%n</code>
</td>
<td>
Frame number of this frame
</td>
</tr>
<tr>
<td>
<code>%k</code>
</td>
<td>
Clock value of this frame
</td>
</tr>
<tr>
<td>
<code>%h</code>
</td>
<td>
Height of image in pixels
</td>
</tr>
<tr>
<td>
<code>%w</code>
</td>
<td>
Width of image in pixels
</td>
</tr>
<tr>
<td>
<code>%%</code>
</td>
<td>
A single % sign.
</td>
</tr>
</table>
<h5><a name="s03_01_02_06_02">3.1.2.6.2 </a>Shell Command Sequencing</h5>
<p>
Here is the sequence of events in an animation loop. Non-animated scenes work the exact same way except there is no
loop.
</p>
<ol>
<li>
Process all INI file keywords and command line switches just once.
</li>
<li>
Open any text output streams and do Create_INI if any.
</li>
<li>
Execute Pre_Scene_Command if any.
</li>
<li>
Loop through frames (or just do once on non-animation).
<ol type="a">
<li>
Execute Pre_Frame_Command if any.
</li>
<li>
Parse entire scene file, open output file and read settings, turn on display, render the frame, destroy all
objects, textures etc., close output file, close display.
</li>
<li>
Execute Post_Frame_Command if any.
</li>
<li>
Repeat above steps until all frames are done.
</li>
</ol>
</li>
<li>
Execute Post_Scene_Command if any.
</li>
<li>
Finish
</li>
</ol>
<p>
If the user interrupts processing the <code>User_Abort_Command</code>, if any, is executed. User aborts can only
occur during the parsing and rendering parts of step (4b) above. If a fatal error occurs that POV-Ray notices the <code>Fatal_Error_Command</code>,
if any, is executed. Sometimes an unforeseen bug or memory error could cause a total crash of the program in which
case there is no chance to shell out. Fatal errors can occur just about anywhere including during the processing of
switches or INI files. If a fatal error occurs before POV-Ray has read the <code> Fatal_Error_Command</code> string
then obviously no shell can occur.
</p>
<p class="Note">
<strong>Note:</strong> the entire scene is re-parsed for every frame. Future versions of POV-Ray may
allow you to hold over parts of a scene from one frame to the next but for now it starts from scratch every time.
</p>
<p class="Note">
<strong>Note:</strong> that the <code>Pre_Frame_Command</code> occurs before the scene is parsed. You
might use this to call some custom scene generation utility before each frame. This utility could rewrite your <code>
.pov</code> or <code>.inc</code> files if needed. Perhaps you will want to generate new <code>.gif</code> or <code>.tga</code>
files for image maps or height fields on each frame.
</p>
<h5><a name="s03_01_02_06_03">3.1.2.6.3 </a>Shell Command Return Actions</h5>
<table width="100%">
<tr>
<td width="30%">
<code>Pre_Scene_Return=</code>s<a name="s03_01_02_06_03_i1"><a name="Pre_Scene_Return"></a>
</td>
<td width="70%">
Set pre scene return actions
</td>
</tr>
<tr>
<td>
<code>Pre_Frame_Return=</code>s<a name="s03_01_02_06_03_i2"><a name="Pre_Frame_Return"></a>
</td>
<td>
Set pre frame return actions
</td>
</tr>
<tr>
<td>
<code>Post_Scene_Return=</code>s<a name="s03_01_02_06_03_i3"><a name="Post_Scene_Return"></a>
</td>
<td>
Set post scene return actions
</td>
</tr>
<tr>
<td>
<code>Post_Frame_Return=</code>s<a name="s03_01_02_06_03_i4"><a name="Post_Frame_Return"></a>
</td>
<td>
Set post frame return actions
</td>
</tr>
<tr>
<td>
<code>User_Abort_Return=</code>s<a name="s03_01_02_06_03_i5"><a name="User_Abort_Return"></a>
</td>
<td>
Set user abort return actions
</td>
</tr>
<tr>
<td>
<code>Fatal_Error_Return=</code>s<a name="s03_01_02_06_03_i6"><a name="Fatal_Error_Return"></a>
</td>
<td>
Set fatal return actions
</td>
</tr>
</table>
<p class="Note">
<strong>Note:</strong> that no <code>+</code> or <code>-</code> switches are available for these
options. They cannot be used from the command line. They may only be used from INI files.
</p>
<p>
Most operating systems allow application programs to return an error code if something goes wrong. When POV-Ray
executes a shell command it can make use of this error code returned from the shell process and take some appropriate
action if the code is zero or non-zero. POV-Ray itself returns such codes. It returns 0 for success, 1 for fatal error
and 2 for user abort.
</p>
<p>
The actions are designated by a single letter in the different <code> ..._Return</code>=s options. The possible
actions are:
</p>
<table width="100%">
<tr>
<td width="30%">
<code>I</code>
</td>
<td width="70%">
ignore the code
</td>
</tr>
<tr>
<td>
<code>S</code>
</td>
<td>
skip one step
</td>
</tr>
<tr>
<td>
<code>A</code>
</td>
<td>
all steps skipped
</td>
</tr>
<tr>
<td>
<code>Q</code>
</td>
<td>
quit POV-Ray immediately
</td>
</tr>
<tr>
<td>
<code>U</code>
</td>
<td>
generate a user abort in POV-Ray
</td>
</tr>
<tr>
<td>
<code>F</code>
</td>
<td>
generate a fatal error in POV-Ray
</td>
</tr>
</table>
<p>
For example if your <code>Pre_Frame_Command</code> calls a program which generates your height field data and that
utility fails then it will return a non-zero code. We would probably want POV-Ray to abort as well. The option <code>Pre_Frame_Return=F</code>
will cause POV-Ray to do a fatal abort if the <code>Pre_Frame_Command</code> returns a non-zero code.
</p>
<p>
Sometimes a non-zero code from the external process is a good thing. Suppose you want to test if a frame has
already been rendered. You could use the <code>S</code> action to skip this frame if the file is already rendered.
Most utilities report an error if the file is not found. For example the command...
</p>
<pre>
pkzip -V myscene mysce012.tga
</pre>
<p>
tells pkzip you want to view the catalog of <code>myscene.zip</code> for the file <code>mysce012.tga</code>. If the
file is not in the archive <code>pkzip</code> returns a non-zero code.
</p>
<p>
However we want to skip if the file is found. Therefore we need to reverse the action so it skips on zero and does
not skip on non-zero. To reverse the zero vs. non-zero triggering of an action precede it with a "<code>-</code>"
sign (note a "<code>!</code>" will also work since it is used in many programming languages as a negate
operator).
</p>
<p>
<code> Pre_Frame_Return=S</code> will skip if the code shows error (non-zero) and will proceed normally on no error
(zero). <code> Pre_Frame_Return=-S</code> will skip if there is no error (zero) and will proceed normally if there is
an error (non-zero).
</p>
<p>
The default for all shells is <code>I</code> which means that the return action is ignored no matter what. POV-Ray
simply proceeds with whatever it was doing before the shell command. The other actions depend upon the context. You
may want to refer back to the animation loop sequence chart in the previous section "<a href="s_95.html#s03_01_02_06_02">Shell
Command Sequencing</a>". The action for each shell is as follows.
</p>
<p>
On return from any User_Abort_Command if there is an action triggered...
</p>
<table width="100%">
<tr>
<td width="30%">
...and you have specified...
</td>
<td width="70%">
...then POV-Ray will..
</td>
</tr>
<tr>
<td>
<code>F</code>
</td>
<td>
Then turn this user abort into a fatal error. Do the <code> Fatal_Error_Command</code>, if any. Exit POV-Ray
with error code 1.
</td>
</tr>
<tr>
<td>
<code>S</code>, <code>A</code>, <code>Q</code>, or <code> U</code>
</td>
<td>
Then proceed with the user abort. Exit POV-Ray with error code 2.
</td>
</tr>
</table>
<p>
On return from any <code>Fatal_Error_Command</code> then POV-Ray will proceed with the fatal error no matter what.
It will exit POV-Ray with error code 1.
</p>
<p>
On return from any <code>Pre_Scene_Command</code>, <code> Pre_Frame_Command</code>, <code>Post_Frame_Command</code>
or <code> Post_Scene_Commands</code> if there is an action triggered...
</p>
<table width="100%">
<tr>
<td width="30%">
...and you have specified...
</td>
<td width="70%">
...then POV-Ray will...
</td>
</tr>
<tr>
<td>
<code>F</code>
</td>
<td>
...turn this user abort into a fatal error. Do the <code> Fatal_Error_Command</code>, if any. Exit POV-Ray with
error code 1.
</td>
</tr>
<tr>
<td>
<code>U</code>
</td>
<td>
...generate a user abort. Do the <code>User_Abort_Command</code>, if any. Exit POV-Ray with an error code 2.
</td>
</tr>
<tr>
<td>
<code>Q</code>
</td>
<td>
..quit POV-Ray immediately. Acts as though POV-Ray never really ran. Do no further shells, (not even a <code>Post_Scene_Command</code>)
and exit POV-Ray with an error code 0.
</td>
</tr>
</table>
<p>
On return from a <code>Pre_Scene_Command</code> if there is an action triggered...
</p>
<table width="100%">
<tr>
<td width="30%">
...and you have specified...
</td>
<td width="70%">
...then POV-Ray will...
</td>
</tr>
<tr>
<td>
<code>S</code>
</td>
<td>
...skip rendering all frames. Acts as though the scene completed all frames normally. Do not do any <code>Pre_Frame_Command</code>
or <code> Post_Frame_Commands</code>. Do the <code> Post_Scene_Command</code>, if any. Exit POV-Ray with error code
0. On the earlier chart this means skip step #4.
</td>
</tr>
<tr>
<td>
<code>A</code>
</td>
<td>
...skip all scene activity. Works exactly like <code>Q</code> quit. On the earlier chart this means skip to step
#6. Acts as though POV-Ray never really ran. Do no further shells, (not even a <code> Post_Scene_Command</code>) and
exit POV-Ray with an error code 0.
</td>
</tr>
</table>
<p>
On return from a <code>Pre_Frame_Command</code> if there is an action triggered...
</p>
<table width="100%">
<tr>
<td width="30%">
...and you have specified...
</td>
<td width="70%">
...then POV-Ray will...
</td>
</tr>
<tr>
<td>
<code>S</code>
</td>
<td>
...skip only this frame. Acts as though this frame never existed. Do not do the <code>Post_Frame_Command</code>.
Proceed with the next frame. On the earlier chart this means skip steps (4b) and (4c) but loop back as needed in
(4d).
</td>
</tr>
<tr>
<td>
<code>A</code>
</td>
<td>
...skip rendering this frame and all remaining frames. Acts as though the scene completed all frames normally.
Do not do any further <code> Post_Frame_Commands</code>. Do the <code>Post_Scene_Command</code>, if any. Exit
POV-Ray with error code 0. On the earlier chart this means skip the rest of step (4) and proceed at step (5).
</td>
</tr>
</table>
<p>
On return from a <code>Post_Frame_Command</code> if there is an action triggered...
</p>
<table width="100%">
<tr>
<td width="30%">
...and you have specified...
</td>
<td width="70%">
...then POV-Ray will...
</td>
</tr>
<tr>
<td>
<code>S</code> or <code>A</code>
</td>
<td>
...skip all remaining frames. Acts as though the scene completed all frames normally. Do not do any further <code>
Post_Frame_Commands</code>. Do the <code>Post_Scene_Command</code>, if any. Exit POV-Ray with error code 0. On the
earlier chart this means skip the rest of step (4) and proceed at step (5).
</td>
</tr>
</table>
<p>
On return from any <code>Post_Scene_Command</code> if there is an action triggered and you have specified <code>S</code>
or <code>A</code> then no special action occurs. This is the same as <code>I</code> for this shell command.
</p>
<h4><a name="s03_01_02_07">3.1.2.7 </a>Text Output</h4>
<a name="s03_01_02_07_i1">
<p>
Text output is an important way that POV-Ray keeps you informed about what it is going to do, what it is doing and
what it did. The program splits its text messages into 7 separate streams. Some versions of POV-Ray color-codes the
various types of text. Some versions allow you to scroll back several pages of messages. All versions allow you to
turn some of these text streams off/on or to direct a copy of the text output to one or several files. This section
details the options which give you control over text output.
</p>
<h5><a name="s03_01_02_07_01">3.1.2.7.1 </a>Text Streams</h5>
<a name="s03_01_02_07_01_i1"><a name="s03_01_02_07_01_i2"><a name="s03_01_02_07_01_i3">
<p>
There are seven distinct text streams that POV-Ray uses for output. On some versions each stream is designated by a
particular color. Text from these streams are displayed whenever it is appropriate so there is often an intermixing of
the text. The distinction is only important if you choose to turn some of the streams off or to direct some of the
streams to text files. On some systems you may be able to review the streams separately in their own scroll-back
buffer.
</p>
<p>
Here is a description of each stream.
</p>
<p>
<strong> Banner:</strong> This stream displays the program's sign-on banner, copyright, contributor's list, and
some help screens. It cannot be turned off or directed to a file because most of this text is displayed before any
options or switches are read. Therefore you cannot use an option or switch to control it. There are switches which
display the help screens. They are covered in section "<a href="s_95.html#s03_01_02_07_05">Help Screen Switches</a>".
</p>
<p>
<strong> Debug:</strong> This stream displays debugging messages. It was primarily designed for developers but this
and other streams may also be used by the user to display messages from within their scene files. See section
"Text Message Streams" for details on this feature. This stream may be turned off and/or directed to a text
file.
</p>
<p>
<strong>Fatal:</strong> This stream displays fatal error messages. After displaying this text, POV-Ray will
terminate. When the error is a scene parsing error, you may be shown several lines of scene text that leads up to the
error. This stream may be turned off and/or directed to a text file.
</p>
<p>
<strong>Render:</strong> This stream displays information about what options you have specified to render the
scene. It includes feedback on all of the major options such as scene name, resolution, animation settings,
anti-aliasing and others. This stream may be turned off and/or directed to a text file.
</p>
<p>
<strong> Statistics:</strong> This stream displays statistics after a frame is rendered. It includes information
about the number of rays traced, the length of time of the processing and other information. This stream may be turned
off and/or directed to a text file.
</p>
<p>
<strong>Status:</strong> This stream displays one-line status messages that explain what POV-Ray is doing at the
moment. On some systems this stream is displayed on a status line at the bottom of the screen. This stream cannot be
directed to a file because there is generally no need to. The text displayed by the <code> Verbose</code> option or <code>+V</code>
switch is output to this stream so that part of the status stream may be turned off.
</p>
<p>
<strong> Warning:</strong> This stream displays warning messages during the parsing of scene files and other
warnings. Despite the warning, POV-Ray can continue to render the scene. You will be informed if POV-Ray has made any
assumptions about your scene so that it can proceed. In general any time you see a warning, you should also assume
that this means that future versions of POV-Ray will not allow the warned action. Therefore you should attempt to
eliminate warning messages so your scene will be able to run in future versions of POV-Ray. This stream may be turned
off and/or directed to a text file.
</p>
<h5><a name="s03_01_02_07_02">3.1.2.7.2 </a>Console Text Output</h5>
<table width="100%">
<tr>
<td width="30%">
<code>Debug_Console=</code>bool<a name="s03_01_02_07_02_i1"><a name="Debug_Console, ini-option"></a>
</td>
<td width="70%">
Turn console display of debug info text on/off
</td>
</tr>
<tr>
<td>
<code>+GD</code><a name="s03_01_02_07_02_i2">
</td>
<td>
Same as <code>Debug_Console=On</code>
</td>
</tr>
<tr>
<td>
<code>-GD</code><a name="s03_01_02_07_02_i3">
</td>
<td>
Same as <code>Debug_Console=Off</code>
</td>
</tr>
<tr>
<td>
<code>Fatal_Console=</code>bool<a name="s03_01_02_07_02_i4"><a name="Fatal_Console, ini-option"></a>
</td>
<td>
Turn console display of fatal error text on/off
</td>
</tr>
<tr>
<td>
<code>+GF</code><a name="s03_01_02_07_02_i5">
</td>
<td>
Same as <code>Fatal_Console=On</code>
</td>
</tr>
<tr>
<td>
<code>-GF</code><a name="s03_01_02_07_02_i6">
</td>
<td>
Same as <code>Fatal_Console=Off</code>
</td>
</tr>
<tr>
<td>
<code>Render_Console=</code>bool<a name="s03_01_02_07_02_i7"><a name="Render_Console, ini-option"></a>
</td>
<td>
Turn console display of render info text on/off
</td>
</tr>
<tr>
<td>
<code>+GR</code><a name="s03_01_02_07_02_i8">
</td>
<td>
Same as <code>Render_Console=On</code>
</td>
</tr>
<tr>
<td>
<code>-GR</code><a name="s03_01_02_07_02_i9">
</td>
<td>
Same as <code>Render_Console=Off</code>
</td>
</tr>
<tr>
<td>
<code>Statistic_Console=</code>bool<a name="s03_01_02_07_02_i10"><a name="Statistic_Console, ini-option"></a>
</td>
<td>
Turn console display of statistic text on/off
</td>
</tr>
<tr>
<td>
<code>+GS</code><a name="s03_01_02_07_02_i11">
</td>
<td>
Same as <code>Statistic_Console=On</code>
</td>
</tr>
<tr>
<td>
<code>-GS</code><a name="s03_01_02_07_02_i12">
</td>
<td>
Same as <code>Statistic_Console=Off</code>
</td>
</tr>
<tr>
<td>
<code>Warning_Console=</code>bool<a name="s03_01_02_07_02_i13"><a name="Warning_Console, ini-option"></a>
</td>
<td>
Turn console display of warning text on/off
</td>
</tr>
<tr>
<td>
<code>+GW</code><a name="s03_01_02_07_02_i14">
</td>
<td>
Same as <code>Warning_Console=On</code>
</td>
</tr>
<tr>
<td>
<code>-GW</code><a name="s03_01_02_07_02_i15">
</td>
<td>
Same as <code>Warning_Console=Off</code>
</td>
</tr>
<tr>
<td>
<code>All_Console=</code>bool<a name="s03_01_02_07_02_i16"><a name="All_Console, ini-option"></a>
</td>
<td>
Turn on/off all debug, fatal, render, statistic and warning text to console.
</td>
</tr>
<tr>
<td>
<code>+GA</code><a name="s03_01_02_07_02_i17">
</td>
<td>
Same as <code>All_Console=On</code>
</td>
</tr>
<tr>
<td>
<code>-GA</code><a name="s03_01_02_07_02_i18">
</td>
<td>
Same as <code>All_Console=Off</code>
</td>
</tr>
</table>
<p>
You may suppress the output to the console of the debug, fatal, render, statistic or warning text streams. For
example the <code> Statistic_Console=off</code> option or the <code>-GS</code> switch can turn off the statistic
stream. Using <code>on</code> or <code>+GS</code> you may turn it on again. You may also turn all five of these
streams on or off at once using the <code>All_Console</code> option or <code>+GA</code> switch.
</p>
<p class="Note">
<strong>Note:</strong> that these options take effect immediately when specified. Obviously any error
or warning messages that might occur before the option is read are not be affected.
</p>
<h5><a name="s03_01_02_07_03">3.1.2.7.3 </a>Directing Text Streams to Files</h5>
<a name="s03_01_02_07_03_i1"><a name="s03_01_02_07_03_i2">
<table width="100%">
<tr>
<td width="30%">
<code>Debug_File=true</code><a name="s03_01_02_07_03_i3"><a name="Debug_File, ini-option"></a>
</td>
<td width="70%">
Echo debug info text to DEBUG.OUT
</td>
</tr>
<tr>
<td>
<code>Debug_File=false</code>
</td>
<td>
Turn off file output of debug info
</td>
</tr>
<tr>
<td>
<code>Debug_File=file</code>
</td>
<td>
Echo debug info text to file
</td>
</tr>
<tr>
<td>
<code>+GDfile</code>
</td>
<td>
Both <code>Debug_Console=On, Debug_File=file</code>
</td>
</tr>
<tr>
<td>
<code>-GDfile</code>
</td>
<td>
Both <code>Debug_Console=Off, Debug_File=file</code>
</td>
</tr>
<tr>
<td>
<code>Fatal_File=true</code><a name="s03_01_02_07_03_i4"><a name="Fatal_File, ini-option"></a>
</td>
<td>
Echo fatal text to FATAL.OUT
</td>
</tr>
<tr>
<td>
<code>Fatal_File=false</code>
</td>
<td>
Turn off file output of fatal
</td>
</tr>
<tr>
<td>
<code>Fatal_File=file</code>
</td>
<td>
Echo fatal info text to file
</td>
</tr>
<tr>
<td>
<code>+GFfile</code>
</td>
<td>
Both <code>Fatal_Console=On, Fatal_File=file</code>
</td>
</tr>
<tr>
<td>
<code>-GFfile</code>
</td>
<td>
Both <code>Fatal_Console=Off, Fatal_File=file</code>
</td>
</tr>
<tr>
<td>
<code>Render_File=true</code><a name="s03_01_02_07_03_i5"><a name="Render_File, ini-option"></a>
</td>
<td>
Echo render info text to RENDER.OUT
</td>
</tr>
<tr>
<td>
<code>Render_File=false</code>
</td>
<td>
Turn off file output of render info
</td>
</tr>
<tr>
<td>
<code>Render_File=</code>file
</td>
<td>
Echo render info text to file
</td>
</tr>
<tr>
<td>
<code>+GR</code>file
</td>
<td>
Both <code>Render_Console=On, Render_File=file</code>
</td>
</tr>
<tr>
<td>
<code>-GRfile</code>
</td>
<td>
Both <code>Render_Console=Off, Render_File=file</code>
</td>
</tr>
<tr>
<td>
<code>Statistic_File=true</code><a name="s03_01_02_07_03_i6"><a name="Statistic_File, ini-option"></a>
</td>
<td>
Echo statistic text to STATS.OUT
</td>
</tr>
<tr>
<td>
<code>Statistic_File=false</code>
</td>
<td>
Turn off file output of statistics
</td>
</tr>
<tr>
<td>
<code>Statistic_File=file</code>
</td>
<td>
Echo statistic text to file
</td>
</tr>
<tr>
<td>
<code>+GS</code>file
</td>
<td>
Both <code>Statistic_Console=On, Statistic_File=file</code>
</td>
</tr>
<tr>
<td>
<code>-GS</code>file
</td>
<td>
Both <code>Statistic_Console=Off, Statistic_File=file</code>
</td>
</tr>
<tr>
<td>
<code>Warning_File=true</code><a name="s03_01_02_07_03_i7"><a name="Warning_File, ini-option"></a>
</td>
<td>
Echo warning info text to WARNING.OUT
</td>
</tr>
<tr>
<td>
<code>Warning_File=false</code>
</td>
<td>
Turn off file output of warning info
</td>
</tr>
<tr>
<td>
<code>Warning_File=file</code>
</td>
<td>
Echo warning info text to file
</td>
</tr>
<tr>
<td>
<code>+GWfile</code>
</td>
<td>
Both <code>Warning_Console=On, Warning_File=file</code>
</td>
</tr>
<tr>
<td>
<code>-GWfile</code>
</td>
<td>
Both <code>Warning_Console=Off, Warning_File=file</code>
</td>
</tr>
<tr>
<td>
<code>All_File=true</code><a name="s03_01_02_07_03_i8"><a name="All_File, ini-option"></a>
</td>
<td>
Echo all debug, fatal, render, statistic, and warning text to ALLTEXT.OUT
</td>
</tr>
<tr>
<td>
<code>All_File=false</code>
</td>
<td>
Turn off file output of all debug, fatal, render, statistic, and warning text.
</td>
</tr>
<tr>
<td>
<code>All_File=file</code>
</td>
<td>
Echo all debug, fatal, render, statistic, and warning text to file
</td>
</tr>
<tr>
<td>
<code>+GAfile</code>
</td>
<td>
Both <code>All_Console=On, All_File=file</code>
</td>
</tr>
<tr>
<td>
<code>-GAfile</code>
</td>
<td>
Both <code>All_Console=Off, All_File=file</code>
</td>
</tr>
</table>
<p>
You may direct a copy of the text streams to a text file for the debug, fatal, render, statistic, or warning text
streams. For example the <code> Statistic_File</code>=<em>s</em> option or the <code>+GS</code><em>s</em> switch. If
the string <em>s</em> is <code>true</code> or any of the other valid <code>true</code> strings then that stream is
redirected to a file with a default name. Valid <code>true</code> values are <code>true</code>, <code> yes</code>, <code>on</code>
or <code>1</code>. If the value is <code> false</code> the direction to a text file is turned off. Valid <code> false</code>
values are <code>false</code>, <code>no</code>, <code> off</code> or <code>0</code>. Any other string specified turns
on file output and the string is interpreted as the output file name.
</p>
<p>
Similarly you may specify such a true, false or file name string after a switch such as <code> +GS</code><em>file</em>.
You may also direct all five streams to the same file using the <code>All_File</code> option or <code> +GA</code>
switch. You may not specify the same file for two or more streams because POV-Ray will fail when it tries to open or
close the same file twice.
</p>
<p class="Note">
<strong>Note:</strong> that these options take effect immediately when specified. Obviously any error
or warning messages that might occur before the option is read will not be affected.
</p>
<h5><a name="s03_01_02_07_04">3.1.2.7.4 </a>Warning Level</h5>
<table width="100%">
<tr>
<td width="30%">
<code>Warning_Level=n</code><a name="s03_01_02_07_04_i1"><a name="Warning_Level, ini-option"></a>
</td>
<td width="70%">
Allows you to turn off classes of warnings.
</td>
</tr>
<tr>
<td>
<code>+WLn</code><a name="s03_01_02_07_04_i2">
</td>
<td>
Same as <code>Warning_Level=n</code>
</td>
</tr>
</table>
<p>
Level 0 turns off all warnings. Level 5 turns off all language version related warnings. The default is level 10
and it enables all warnings. All other levels are reserved and should not be specified.
</p>
<h5><a name="s03_01_02_07_05">3.1.2.7.5 </a>Help Screen Switches</h5>
<a name="s03_01_02_07_05_i1">
<table width="100%">
<tr>
<td width="30%">
<code>-?</code><a name="s03_01_02_07_05_i2">
</td>
<td width="70%">
Show help screen 0 if this is the only switch
</td>
</tr>
</table>
<p class="Note">
<strong>Note:</strong> there are no INI style equivalents to these options.
</p>
<p>
After displaying the help screens, POV-Ray terminates. Because some operating systems do not permit a question mark
as a command line switch you may also use the <code>+H</code> switch.
</p>
<p class="Note">
<strong>Note:</strong> this switch is also used to specify the height of the image in pixels.
Therefore the <code> +H</code> switch is only interpreted as a help switch if it is the only switch on the command
line.
</p>
<p>
Graphical interface versions of POV-Ray such as Mac or Windows have extensive online help.
</p>
<h4><a name="s03_01_02_08">3.1.2.8 </a>Tracing Options</h4>
<a name="s03_01_02_08_i1"><a name="s03_01_02_08_i2">
<p>
There is more than one way to trace a ray. Sometimes there is a trade-off between quality and speed. Sometimes
options designed to make tracing faster can slow things down. This section covers options that tell POV-Ray how to
trace rays with the appropriate speed and quality settings.
</p>
<h5><a name="s03_01_02_08_01">3.1.2.8.1 </a>Quality Settings</h5>
<table width="100%">
<tr>
<td width="30%">
<code>Quality=</code>n<a name="s03_01_02_08_01_i1"><a name="Quality, ini-option"></a>
</td>
<td width="70%">
Set quality value to n (0 <= n <= 11)
</td>
</tr>
<tr>
<td>
<code>+Q</code>n<a name="s03_01_02_08_01_i2">
</td>
<td>
Same as <code>Quality=</code>n
</td>
</tr>
</table>
<p>
The <code>Quality=</code><em>n</em> option or <code>+Q</code><em>n</em> switch allows you to specify the image
rendering quality. You may choose to lower the quality for test rendering and raise it for final renders. The quality
adjustments are made by eliminating some of the calculations that are normally performed. For example settings below 4
do not render shadows. Settings below 8 do not use reflection or refraction. The duplicate values allow for future
expansion. The values correspond to the following quality levels:
</p>
<table width="100%">
<tr>
<td width="30%">
<code>0, 1</code>
</td>
<td width="70%">
Just show quick colors. Use full ambient lighting only. Quick colors are used only at 5 or below.
</td>
</tr>
<tr>
<td>
<code>2, 3</code>
</td>
<td>
Show specified diffuse and ambient light.
</td>
</tr>
<tr>
<td>
<code>4</code>
</td>
<td>
Render shadows, but no extended lights.
</td>
</tr>
<tr>
<td>
<code>5</code>
</td>
<td>
Render shadows, including extended lights.
</td>
</tr>
<tr>
<td>
<code>6, 7</code>
</td>
<td>
Compute texture patterns, compute photons
</td>
</tr>
<tr>
<td>
<code>8</code>
</td>
<td>
Compute reflected, refracted, and transmitted rays.
</td>
</tr>
<tr>
<td>
<code>9, 10, 11</code>
</td>
<td>
Compute media and radiosity
</td>
</tr>
</table>
<p>
The default is 9 if not specified.
</p>
<h5><a name="s03_01_02_08_02">3.1.2.8.2 </a>Automatic Bounding Control</h5>
<a name="s03_01_02_08_02_i1">
<table width="100%">
<tr>
<td width="30%">
<code>Bounding=</code>bool<a name="s03_01_02_08_02_i2"><a name="Bounding, ini-option"></a>
</td>
<td width="70%">
Turn bounding on/off
</td>
</tr>
<tr>
<td>
<code>+MB</code><a name="s03_01_02_08_02_i3">
</td>
<td>
Turn bounding on; Set threshold to 25 or previous amount
</td>
</tr>
<tr>
<td>
<code>-MB</code><a name="s03_01_02_08_02_i4">
</td>
<td>
Turn bounding off
</td>
</tr>
<tr>
<td>
<code>Bounding_Threshold=</code>n<a name="s03_01_02_08_02_i5"><a name="Bounding_Threshold, ini-option"></a>
</td>
<td>
Set bound threshold to n
</td>
</tr>
<tr>
<td>
<code>+MB</code>n
</td>
<td>
Turn bounding on; bound threshold to n
</td>
</tr>
<tr>
<td>
<code>-MB</code>n
</td>
<td>
Turn bounding off; set future threshold to n
</td>
</tr>
<tr>
<td>
<code>Light_Buffer=</code>bool<a name="s03_01_02_08_02_i6"><a name="Light_Buffer, ini-option"></a>
</td>
<td>
Turn light buffer on/off
</td>
</tr>
<tr>
<td>
<code>+UL</code><a name="s03_01_02_08_02_i7">
</td>
<td>
Turn light buffer on
</td>
</tr>
<tr>
<td>
<code>-UL</code><a name="s03_01_02_08_02_i8">
</td>
<td>
Turn light buffer off
</td>
</tr>
<tr>
<td>
<code>Vista_Buffer=</code>bool<a name="s03_01_02_08_02_i9"><a name="Vista_Buffer, ini-option"></a>
</td>
<td>
Turn vista buffer on/off
</td>
</tr>
<tr>
<td>
<code>+UV</code><a name="s03_01_02_08_02_i10">
</td>
<td>
Turn vista buffer on
</td>
</tr>
<tr>
<td>
<code>-UV</code><a name="s03_01_02_08_02_i11">
</td>
<td>
Turn vista buffer off
</td>
</tr>
</table>
<p>
POV-Ray uses a variety of spatial sub-division systems to speed up ray-object intersection tests. The primary
system uses a hierarchy of nested bounding boxes. This system compartmentalizes all finite objects in a scene into
invisible rectangular boxes that are arranged in a tree-like hierarchy. Before testing the objects within the bounding
boxes the tree is descended and only those objects are tested whose bounds are hit by a ray. This can greatly improve
rendering speed. However for scenes with only a few objects the overhead of using a bounding system is not worth the
effort. The <code> Bounding=off</code> option or <code>-MB</code> switch allows you to force bounding off. The default
value is on.
</p>
<p>
The <code> Bounding_Threshold=</code><em>n</em> or <code> +MB</code><em>n</em> switch allows you to set the minimum
number of objects necessary before bounding is used. The default is <code>+MB25</code> which means that if your scene
has fewer than 25 objects POV-Ray will automatically turn bounding off because the overhead is not worth it. Generally
it is a good idea to use a much lower threshold like <code>+MB5</code>.
</p>
<p>
Additionally POV-Ray uses systems known as <em>vista buffers</em> and <em> light buffers</em> to further speed
things up. These systems only work when bounding is on and when there are a sufficient number of objects to meet the
bounding threshold. The vista buffer is created by projecting the bounding box hierarchy onto the screen and
determining the rectangular areas that are covered by each of the elements in the hierarchy. Only those objects whose
rectangles enclose a given pixel are tested by the primary viewing ray. The vista buffer can only be used with
perspective and orthographic cameras because they rely on a fixed viewpoint and a reasonable projection (i. e.
straight lines have to stay straight lines after the projection).
</p>
<p>
The light buffer is created by enclosing each light source in an imaginary box and projecting the bounding box
hierarchy onto each of its six sides. Since this relies on a fixed light source, light buffers will not be used for
area lights.
</p>
<p>
Reflected and transmitted rays do not take advantage of the light and vista buffer.
</p>
<p>
The default settings are <code> Vista_Buffer=on</code> or <code>+UV</code> and <code> Light_Buffer=on</code> or <code>+UL</code>.
The option to turn these features off is available to demonstrate their usefulness and as protection against
unforeseen bugs which might exist in any of these bounding systems.
</p>
<p>
In general, any finite object and many types of CSG of finite objects will properly respond to this bounding
system. In addition blobs and meshes use an additional internal bounding system. These systems are not affected by the
above switch. They can be switched off using the appropriate syntax in the scene file (see "<a href="s_105.html#s03_04_01_01">Blob</a>"
and "<a href="#l51">Mesh</a>" for details).
</p>
<p>
Text objects are split into individual letters that are bounded using the bounding box hierarchy. Some CSG
combinations of finite and infinite objects are also automatically bound. The end result is that you will rarely need
to add manual bounding objects as was necessary in earlier versions of POV-Ray unless you use many infinite objects.
</p>
<h5><a name="s03_01_02_08_03">3.1.2.8.3 </a>Removing User Bounding</h5>
<a name="s03_01_02_08_03_i1">
<table width="100%">
<tr>
<td width="30%">
<code>Remove_Bounds=</code>bool<a name="s03_01_02_08_03_i2"><a name="Remove_Bounds, ini-option"></a>
</td>
<td width="70%">
Turn unnecessary bounds removal on/off
</td>
</tr>
<tr>
<td>
<code>+UR</code><a name="s03_01_02_08_03_i3">
</td>
<td>
Turn unnecessary bounds removal on
</td>
</tr>
<tr>
<td>
<code>-UR</code><a name="s03_01_02_08_03_i4">
</td>
<td>
Turn unnecessary bounds removal off
</td>
</tr>
<tr>
<td>
<code>Split_Unions=</code>bool<a name="s03_01_02_08_03_i5"><a name="Split_Unions, ini-option"></a>
</td>
<td>
Turn split bounded unions on/off
</td>
</tr>
<tr>
<td>
<code>+SU</code><a name="s03_01_02_08_03_i6">
</td>
<td>
Turn split bounded unions on
</td>
</tr>
<tr>
<td>
<code>-SU</code><a name="s03_01_02_08_03_i7">
</td>
<td>
Turn split bounded unions off
</td>
</tr>
</table>
<p>
Early versions of POV-Ray had no system of automatic bounding or spatial sub-division to speed up ray-object
intersection tests. Users had to manually create bounding boxes to speed up the rendering. Since version 3.0, POV-Ray
has had more sophisticated automatic bounding than any previous version. In many cases the manual bounding on older
scenes is slower than the new automatic systems. Therefore POV-Ray removes manual bounding when it knows it will help.
In rare instances you may want to keep manual bounding. Some older scenes incorrectly used bounding when they should
have used clipping. If POV-Ray removes the bounds in these scenes the image will not look right. To turn off the
automatic removal of manual bounds you should specify <code> Remove_Bounds=off</code> or use <code> -UR</code>. The
default is <code> Remove_Bounds=on</code>.
</p>
<p>
One area where the jury is still out is the splitting of manually bounded unions. Unbounded unions are always split
into their component parts so that automatic bounding works better. Most users do not bound unions because they know
that doing so is usually slower. If you do manually bound a union we presume you really want it bound. For safety sake
we do not presume to remove such bounds. If you want to remove manual bounds from unions you should specify <code>Split_Unions=on</code>
or use <code> +SU</code>. The default is <code>Split_Unions=off</code>.
</p>
<h5><a name="s03_01_02_08_04">3.1.2.8.4 </a>Anti-Aliasing Options</h5>
<a name="s03_01_02_08_04_i1">
<table width="100%">
<tr>
<td width="30%">
<code>Antialias=</code>bool<a name="s03_01_02_08_04_i2"><a name="Antialias, ini-option"></a>
</td>
<td width="70%">
Turns anti-aliasing on/off
</td>
</tr>
<tr>
<td>
<code>+A</code><a name="s03_01_02_08_04_i3">
</td>
<td>
Turns aa on with threshold 0.3 or previous amount
</td>
</tr>
<tr>
<td>
<code>-A</code><a name="s03_01_02_08_04_i4">
</td>
<td>
Turns anti-aliasing off
</td>
</tr>
<tr>
<td>
<code>Sampling_Method=</code>n<a name="s03_01_02_08_04_i5"><a name="Sampling_Method, ini-option"></a>
</td>
<td>
Sets aa-sampling method (only <code>1</code> or <code>2</code> are valid)
</td>
</tr>
<tr>
<td>
<code>+AM</code>n<a name="s03_01_02_08_04_i6">
</td>
<td>
Same as <code>Sampling_Method=</code>n
</td>
</tr>
<tr>
<td>
<code>Antialias_Threshold=</code>n.n<a name="s03_01_02_08_04_i7"><a name="Antialias_Threshold, ini-option"></a>
</td>
<td>
Sets anti-aliasing threshold
</td>
</tr>
<tr>
<td>
<code>+A</code>n.n
</td>
<td>
Sets aa on with aa-threshold at n.n
</td>
</tr>
<tr>
<td>
<code>-A</code>n.n
</td>
<td>
Sets aa off (aa-threshold n.n in future)
</td>
</tr>
<tr>
<td>
<code>Jitter=</code>bool<a name="s03_01_02_08_04_i8"><a name="Jitter, ini-option"></a><a name="s03_01_02_08_04_i9">
</td>
<td>
Sets aa-jitter on/off
</td>
</tr>
<tr>
<td>
<code>+J</code><a name="s03_01_02_08_04_i10">
</td>
<td>
Sets aa-jitter on with 1.0 or previous amount
</td>
</tr>
<tr>
<td>
<code>-J</code><a name="s03_01_02_08_04_i11">
</td>
<td>
Sets aa-jitter off
</td>
</tr>
<tr>
<td>
<code>Jitter_Amount=</code>n.n<a name="s03_01_02_08_04_i12"><a name="Jitter_Amount, ini.option"></a>
</td>
<td>
Sets aa-jitter amount to n.n. If n.n <= 0 aa-jitter is set off
</td>
</tr>
<tr>
<td>
<code>+J</code>n.n
</td>
<td>
Sets aa-jitter on; jitter amount to n.n. If n.n <= 0 aa-jitter is set off
</td>
</tr>
<tr>
<td>
<code>-J</code>n.n
</td>
<td>
Sets aa-jitter off (jitter amount n.n in future)
</td>
</tr>
<tr>
<td>
<code>Antialias_Depth=</code>n<a name="s03_01_02_08_04_i13"><a name="Antialias_Depth, ini-option"></a>
</td>
<td>
Sets aa-depth (1 <= n <= 9)
</td>
</tr>
<tr>
<td>
<code>+R</code>n<a name="s03_01_02_08_04_i14">
</td>
<td>
Same as <code>Antialias_Depth=</code>n
</td>
</tr>
</table>
<p>
The ray-tracing process is in effect a discrete, digital sampling of the image with typically one sample per pixel.
Such sampling can introduce a variety of errors. This includes a jagged, stair-step appearance in sloping or curved
lines, a broken look for thin lines, moiré patterns of interference and lost detail or missing objects, which
are so small they reside between adjacent pixels. The effect that is responsible for those errors is called <em>aliasing</em>.
</p>
<p>
Anti-aliasing is any technique used to help eliminate such errors or to reduce the negative impact they have on the
image. In general, anti-aliasing makes the ray-traced image look <em> smoother</em>. The <code> Antialias=on</code>
option or <code>+A</code> switch turns on POV-Ray's anti-aliasing system.
</p>
<p>
When anti-aliasing is turned on, POV-Ray attempts to reduce the errors by shooting more than one viewing ray into
each pixel and averaging the results to determine the pixel's apparent color. This technique is called super-sampling
and can improve the appearance of the final image but it drastically increases the time required to render a scene
since many more calculations have to be done.
</p>
<p>
POV-Ray gives you the option to use one of two alternate super-sampling methods. The <code> Sampling_Method=</code><em>n</em>
option or <code> +AM</code><em>n</em> switch selects either type <code>1</code> or type <code> 2</code>. Selecting one
of those methods does not turn anti-aliasing on. This has to be done by using the <code>+A</code> command line switch
or <code> Antialias=on</code> option.
</p>
<p>
Type 1 is an adaptive, non-recursive, super-sampling method. It is <em> adaptive</em> because not every pixel is
super-sampled. Type 2 is an adaptive and recursive super-sampling method. It is <em>recursive</em> because the pixel
is sub-divided and sub-sub-divided recursively. The <em>adaptive</em> nature of type 2 is the variable depth of
recursion.
</p>
<p>
In the default, non-recursive method (<code>+AM1</code>), POV-Ray initially traces one ray per pixel. If the color
of a pixel differs from its neighbors (to the left or above) by at least the set threshold value then the pixel is
super-sampled by shooting a given, fixed number of additional rays. The default threshold is 0.3 but it may be changed
using the <code> Antialias_Threshold=</code><em>n.n</em> option. When the switches are used, the threshold may
optionally follow the <code>+A</code>. For example <code> +A0.1</code> turns anti-aliasing on and sets the threshold
to 0.1.
</p>
<p>
The threshold comparison is computed as follows. If r1, g1, b1 and r2, g2, b2 are the rgb components of two pixels
then the difference between pixels is computed by
</p>
<pre>
diff = abs(r1-r2) + abs(g1-g2) + abs(b1-b2)
</pre>
<p>
If this difference is greater than the threshold then both pixels are super-sampled. The rgb values are in the
range from 0.0 to 1.0 thus the most two pixels can differ is 3.0. If the anti-aliasing threshold is 0.0 then every
pixel is super-sampled. If the threshold is 3.0 then no anti-aliasing is done. Lower threshold means more
anti-aliasing and less speed. Use anti-aliasing for your final version of a picture, not the rough draft. The lower
the contrast, the lower the threshold should be. Higher contrast pictures can get away with higher tolerance values.
Good values seem to be around 0.2 to 0.4.
</p>
<p>
When using the non-recursive method, the default number of super-samples is nine per pixel, located on a 3*3 grid.
The <code> Antialias_Depth=</code><em>n</em> option or <code> +R</code><em>n</em> switch controls the number of rows
and columns of samples taken for a super-sampled pixel. For example <code>+R4</code> would give 4*4=16 samples per
pixel.
</p>
<p>
The second, adaptive, recursive super-sampling method starts by tracing four rays at the corners of each pixel. If
the resulting colors differ more than the threshold amount additional samples will be taken. This is done recursively,
i.e. the pixel is divided into four sub-pixels that are separately traced and tested for further subdivision. The
advantage of this method is the reduced number of rays that have to be traced. Samples that are common among adjacent
pixels and sub-pixels are stored and reused to avoid re-tracing of rays. The recursive character of this method makes
the super-sampling concentrate on those parts of the pixel that are more likely to need super-sampling (see figure
below).<br><center><img alt="Example of how the recursive super-sampling works." src="images/reference/recsuper.png"></center>
</p>
<p>
The maximum number of subdivisions is specified by the <code> Antialias_Depth=</code><em>n</em> option or <code>+R</code><em>n</em>
switch. This is different from the adaptive, non-recursive method where the total number of super-samples is
specified. A maximum number of <em>n</em> subdivisions results in a maximum number of samples per pixel that is given
by the following table.
</p>
<table width="100%">
<tr>
<td width="20%">
<code>+R</code>n
</td>
<td width="40%">
Number of additional samples per super-sampled pixel for the non-recursive method <code>+AM1</code>
</td>
<td width="40%">
Maximum number of samples per super-sampled pixel for the recursive method <code>+AM2</code>
</td>
</tr>
<tr>
<td>
<code>1</code>
</td>
<td>
1
</td>
<td>
9
</td>
</tr>
<tr>
<td>
<code>2</code>
</td>
<td>
4
</td>
<td>
25
</td>
</tr>
<tr>
<td>
<code>3</code>
</td>
<td>
9
</td>
<td>
81
</td>
</tr>
<tr>
<td>
<code>4</code>
</td>
<td>
16
</td>
<td>
289
</td>
</tr>
<tr>
<td>
<code>5</code>
</td>
<td>
25
</td>
<td>
1089
</td>
</tr>
<tr>
<td>
<code>6</code>
</td>
<td>
36
</td>
<td>
4225
</td>
</tr>
<tr>
<td>
<code>7</code>
</td>
<td>
49
</td>
<td>
16641
</td>
</tr>
<tr>
<td>
<code>8</code>
</td>
<td>
64
</td>
<td>
66049
</td>
</tr>
<tr>
<td>
<code>9</code>
</td>
<td>
81
</td>
<td>
263169
</td>
</tr>
</table>
<p class="Note">
<strong>Note:</strong> the maximum number of samples in the recursive case is hardly ever reached for
a given pixel. If the recursive method is used with no anti-aliasing each pixel will be the average of the rays traced
at its corners. In most cases a recursion level of three is sufficient.
</p>
<p>
Another way to reduce aliasing artefacts is to introduce noise into the sampling process. This is called <em>jittering</em>
and works because the human visual system is much more forgiving to noise than it is to regular patterns. The location
of the super-samples is jittered or wiggled a tiny amount when anti-aliasing is used. Jittering is used by default but
it may be turned off with the <code>Jitter=off</code> option or <code>-J</code> switch. The amount of jittering can be
set with the <code> Jitter_Amount=</code><em>n.n</em> option. When using switches the jitter scale may be specified
after the <code>+J</code><em>n.n</em> switch. For example <code>+J0.5</code> uses half the normal jitter. The default
amount of 1.0 is the maximum jitter which will insure that all super-samples remain inside the original pixel.
</p>
<p class="Note">
<strong>Note:</strong> the jittering noise is random and non-repeatable so you should avoid using
jitter in animation sequences as the anti-aliased pixels will vary and flicker annoyingly from frame to frame.
</p>
<p>
If anti-aliasing is not used one sample per pixel is taken regardless of the super-sampling method specified.
</p>
<p>
<a name="l51">
<small><strong>More about "Mesh"</strong></small>
</a>
<ul>
<li><small>
<a href="s_106.html#s03_04_02_03">3.4.2.3 Mesh</a> in 3.4.2 Finite Patch Primitives
</small>
<li><small>
<a href="s_106.html#s03_04_02_04">3.4.2.4 Mesh2</a> in 3.4.2 Finite Patch Primitives
</small>
</ul>
</p>
<br>
<table class="NavBar" width="100%">
<tr>
<td align="left" nowrap="" valign="middle" width="32">
<a href="s_94.html"><img alt="previous" border="0" src="prev.png"></a>
</td>
<td align="left" valign="middle" width="30%">
<a href="s_94.html">3.1.1 Notation and Basic Assumptions</a>
</td>
<td align="center" valign="middle">
<strong>3.1.2 Command-line Options</strong>
</td>
<td align="right" valign="middle" width="30%">
<a href="s_96.html">3.2 Scene Description Language</a>
</td>
<td align="right" nowrap="" valign="middle" width="32">
<a href="s_96.html"><img alt="next" border="0" src="next.png"></a>
</td>
</tr>
</table>
</body> </html>
|
