View Full Version : Bug of setPosition

08-08-2018, 11:12 PM
I've made a tunnel node, and set it parent as another node
below scripts got different results:
tunnel.setPosition([1,1,1],mode = viz.ABS_GLOBAL)# it won't change the global coordinates but change the parent-relative coordinates; in other words,
it ignores the input variable "mode"
tunnel.setPosition(1,1,1,mode = viz.ABS_GLOBAL)# works fine

setEuler seems to have similar problem:)

I want this bug to be fixed since I and my colleague just computed the coordinate and euler transforming function for two whole work days:mad:
(we just try the [1,1,1] one and thought this was a deep bug so we didn't try to use other way until I happened to find it just now)

Although our math skills were improved, this shouldn't have happened..

08-09-2018, 10:32 PM
Thanks for the bug report. I will bring this to the attention of our developers.