Cousin Ricky <ric### [at] yahoocom> wrote:
>
> My results are the same with versions 3.5, 3.6.1, 3.7.0.10, and
> 3.8.0-beta.2, all on GNU/Linux.
>

So at this late date, the bigger questions are:

1) What should be done about the documentation concerning the defaults?

Given that the behavior is a complicated situation, it seems to me that the most
expedient 'fix' would be to issue a warning (of *some* kind)-- in both the docs
and during a render.  Something like:

"Due to a long-standing quirk in the photons code, be aware that these default
values may be overridden and cause unexpected results. Best practice would be to
use explicit photon blocks and on/off keywords in your scenes."

2) Should an attempt even be made to correct the underlying code, to bring it
into strict compliance with the stated defaults (given that these quirks have
been around 'since the beginning of time')? Doing so might alter the outcome of
*many* older scenes. However, there are precedents for such a large change: for
example, the 'emission' keyword (and its message warning about a too-high
ambient value); and radiosity now automatically turning off 'ambient' light.
These two changes also required older scenes to be edited.

-----------
BTW:
I think that the docs'  'target' default of 1.0 also needs a small
clarification, since a numerical value is only meant to apply when 'spacing' is
used in the global photos block.  Of course, the 1.0 value  also works when
'count' is used instead-- but as just a Boolean operator in that case(?)-- and
incrementally changing the float value has no effect.

However, a simple 'on' can also be used, again in either case... but the docs
don't mention it.

Would these be more appropriate for the docs' default?:
target 1.0     When 'spacing' is used in the global photons block
target on     When 'count' is used in the global photons block

Post a reply to this message