Hi!
@Michael_Todd and @Anonymous
I nailed it down to where this error happens inside xgmCopyGuides.
In the end this happens, when copying 1 guide to an other:
vector $source_normal = <<0,1,0>>;
vector $destination_normal = <<0,1,0>>;
vector $test_axis = cross($source_normal, $destination_normal);
float $test_ang = angle ($source_normal, $destination_normal);
vector $t=<<1,1,1>>;
vector $test_tmp = rot ($t, $test_axis , $test_ang);
which results in NaN here.
Please test the script above.
The problem is $test_axis ( or axis in original script) becoming "0 0 0" and then rot will lead to NaN.
Can this be reproduced, should there be an other result, or should source and destination normal be different?
I could send a scene-file with the manipulated script (just to print values) alongside with the output i get, but maybe the forum is not the right place for this.
Output looks like this:
selectMode -object; xgmCopyGuides("paste");
cvs_0: 0.373428911 7.847722537e-17 -0.3534300029 cvs_1: 0.xxx-xxxxxxxx 0.333 0.xxx-xxxxxxxx cvs_2: -0.1115397051 0.667 -0.1331127027 cvs_3: 0.xxx-xxxxxxxx 1 0.1159008552
srcN: 0 1 0
dstN: 0 1 0
axis: 0 0 0
axis unit: 0 0 0
base: -0.3578279912 -4.022870817e-17 0.1811739951
vector tmp: 0.078359 0.333 0.093514
rot
tmp: 0.xxx-xxxxxxxx 0.333 0.xxx-xxxxxxxx
axis: 0 0 0
ang: 0
tmp result = -nan(ind) -nan(ind) -nan(ind)
vec -nan(ind) -nan(ind) -nan(ind)
vector tmp: -0.11154 0.667 -0.133113
...
Edit: Those xxx-xxxxxxxx should be numbers, maybe website tries to hide personal information!?