Hi again :)

Why does str() always return zeroes even for values that aren't zero?

Example:


#include "metals.inc"

#debug "A_GoldD = "
#debug concat(str(A_GoldD.x,5,0), ", ")
#debug concat(str(A_GoldD.y,5,0), ", ")
#debug concat(str(A_GoldD.z,5,0), "\n")

#debug concat("D_GoldD = ", str(D_GoldD, 5, 0), "\n")


This outputs all zeroes, but if I replace "diffuse D_GoldD" and "ambient 
A_GoldD" in the definition of T_Chrome_2D with "diffuse 0" and "ambient 
0", I get a very different material. Therefore I assume the values 
aren't actually zero.

How do I output the correct values?

Thanks
Timwi

Post a reply to this message

Timwi <tim### [at] gmxnet> wrote:
> Why does str() always return zeroes even for values that aren't zero?

  Because you told it to print 0 decimals (which causes it to round the
value appropriately)?

-- 
                                                          - Warp

Post a reply to this message

Timwi <tim### [at] gmxnet> wrote:
> Why does str() always return zeroes even for values that aren't zero?

Well, simple - because you're using it wrong ;)

The 3rd parameter controls the display precision of the fractional part in
powers of 0.1 (i.e. the number of digits to display after the decimal point);
setting it to zero therefore gives you only the integer part of the value. As
the numbers you intend to display are all quite small, POV will consequently
round them to zero.

Set the 3rd parameter to -1 to have POV automatically pick a (more or less)
suitable precision, or to e.g. 3 to have POV display the numbers to a precision
of 0.001.

Post a reply to this message

clipka wrote:
> Timwi <tim### [at] gmxnet> wrote:
>> Why does str() always return zeroes even for values that aren't
>> zero?
> 
> The 3rd parameter controls the display precision of the fractional
> part in powers of 0.1 (i.e. the number of digits to display after the
> decimal point); setting it to zero therefore gives you only the
> integer part of the value. [...] Set the 3rd parameter to -1 to have
> POV automatically pick a (more or less) suitable precision

Thanks a lot! :)

Post a reply to this message