--- ray/doc/man/man1/rtpict.1	2022/03/16 00:06:08	1.9
+++ ray/doc/man/man1/rtpict.1	2023/01/05 19:25:21	1.12
@@ -1,4 +1,4 @@
-.\" RCSid "$Id: rtpict.1,v 1.9 2022/03/16 00:06:08 greg Exp $"
+.\" RCSid "$Id: rtpict.1,v 1.12 2023/01/05 19:25:21 greg Exp $"
 .TH RTPICT 1 3/19/2018 RADIANCE
 .SH NAME
 rtpict - generate a RADIANCE picture or layered image using rtrace
@@ -88,7 +88,7 @@ option should be used to assign the reference (median)
 units, which applies to the overall scene.
 Surface normals (from the 'n' and 'N' types) will be converted
 to a 32-bit representation by
-.I rcode_normal(1).
+.I rcode_norm(1).
 Finally, identifiers (from the 's', 'm', and 'M' types) will be
 converted to a 16-bit index format by
 .I rcode_ident(1).
@@ -109,28 +109,9 @@ rtpict -n 4 -vf mypers.vf -ab 1 -af scene.amb scene.oc
 To render radiance, first surface distance, and normals in a layered image:
 .IP "" .2i
 rtpict -n 8 -vf fish.vf @render.opt -ovLn fisholay scene.oct
-.SH NOTES
-Users should seriously consider using
-.I rpiece(1)
-when irradiance caching is employed with a shared ambient file.
-If
-.I rtpict
-is used in multiprocessing mode with a shared irradiance cache,
-it is trying to compute almost
-the same part of the same scanline in different processes, which
-results in many redundant calculations.
-The
-.I rpiece
-program avoids this by working on separate tiles in each
-process, with less overlap in the indirect irradiance calculation.
-Either program will benefit from an "overture" run of a
-single-process rpict to create the ambient file using a low-resolution
-rendering that is discarded, but this will not completely solve the
-problem for
-.I rtpict.
 .SH AUTHOR
 Greg Ward
 .SH "SEE ALSO"
 getinfo(1), mkpmap(1), oconv(1), pfilt(1), 
-pvalue(1), rad(1), rcode_depth(1), rcode_normal(1), rcode_ident(1),
+pvalue(1), rad(1), rcode_depth(1), rcode_norm(1), rcode_ident(1),
 rcrop(1), rpiece(1), rpict(1), rsplit(1), rtrace(1), rvu(1), vwrays(1)