*On 09/08/2011 at 19:43, xxxxxxxx wrote:*

User Information:

Cinema 4D Version: R12

Platform: Windows ; Mac ; Mac OSX ;

Language(s) : XPRESSO ;

---------

Howdy,

I just upgraded to R12 and there is a serious math bug with the formula node and using the ^ operator.

It is a mathematical law that n ^ 0 = 1:

But in R12's formula node if you type in $1 ^ $2 for the formula and leave the second value at 0, the result of the calculation is whatever the value is of the first value, when it should always be 1.

Also, if you set both values to the same number then the result is 0, for example setting both values at 2 will give you a result of 0, when it should be giving a result of 4. (2 ^ 2 = 4)

It was working fine in R10, R10.5(demo), R11(demo), but I just checked R11.5(demo) and that seems to be when it was broken.

Adios,

Cactus Dan

*On 09/08/2011 at 19:43, xxxxxxxx wrote:*

User Information:

Cinema 4D Version: R12

Platform: Windows ; Mac ; Mac OSX ;

Language(s) : XPRESSO ;

---------

Howdy,

I just upgraded to R12 and there is a serious math bug with the formula node and using the ^ operator.

It is a mathematical law that n ^ 0 = 1:

But in R12's formula node if you type in $1 ^ $2 for the formula and leave the second value at 0, the result of the calculation is whatever the value is of the first value, when it should always be 1.

Also, if you set both values to the same number then the result is 0, for example setting both values at 2 will give you a result of 0, when it should be giving a result of 4. (2 ^ 2 = 4)

It was working fine in R10, R10.5(demo), R11(demo), but I just checked R11.5(demo) and that seems to be when it was broken.

Adios,

Cactus Dan

*On 10/08/2011 at 00:49, xxxxxxxx wrote:*

Originally posted by xxxxxxxxHowdy,

I just upgraded to R12 and there is a serious math bug with the formula node and using the ^ operator.

It is a mathematical law that n ^ 0 = 1:

But in R12's formula node if you type in $1 ^ $2 for the formula and leave the second value at 0, the result of the calculation is whatever the value is of the first value, when it should always be 1.

Also, if you set both values to the same number then the result is 0, for example setting both values at 2 will give you a result of 0, when it should be giving a result of 4. (2 ^ 2 = 4)

It was working fine in R10, R10.5(demo), R11(demo), but I just checked R11.5(demo) and that seems to be when it was broken.

Adios,

Cactus Dan

You're using the bitwise XOR, not the pow() functions - see "Formula" section in the appendix of the manual/help system. Therefore the result is as expected.

Best regards,

Wilfried

]]>*On 10/08/2011 at 04:58, xxxxxxxx wrote:*

Howdy,

Ah, OK, I see that was changed.

The problem, though, was the rig was built in R10 and handed to a client who's using R12. But, I see that in R10 I can replace it with a coffee node with the formula:

```
Output1 = pow(Input1, input2);
```

... and it will stay compatible when loaded into R12.

Sorry, for the panicky post.

Adios,

Cactus Dan