Le 01/10/2017 à 01:09, clipka a écrit :

> I'm with Alain on this one: My guess is that there's nothing wrong with
> the macro per se, but rather with its invocation, and that you're
> accidently passing a 2D point or scalar as the 3rd or 4th parameter. The
> `.x` works fine for either of those (you can interpret a scalar as a 1D
> vector if you will), but `.y` requires at least a 2D vector, and `.z`
> requires at least a 3D vector.
> 

Bingo ! You're right.

Somewhere in the code, i pass a bad vector.


Sorry.


-- 
Kurtz le pirate
Compagnie de la Banquise

Post a reply to this message