There are three locations in the built-in documentation (as of 3.61a) where
"insure" is incorrectly used instead of "ensure":
[184.108.40.206.4 - immediately before the second yellow box]
The default amount of 1.0 is the maximum jitter which will insure that all
super-samples remain inside the original pixel.
[220.127.116.11.3 - at the end of the paragraph following the first blue box]
Type checking is performed to insure that the proper type data is read into
[18.104.22.168.4 - at the end of second yellow box]
It is up to the user to insure that something inside the loop changes so
that it eventually terminates.
Post a reply to this message