#1
|
|||
|
|||
Bug of setPosition
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 (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.. |
Tags |
relative coordinates, setposition |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
setPosition() and collision | mape2k | Vizard | 2 | 02-18-2015 06:07 AM |
Bug in setPosition | sleiN13 | Vizard | 2 | 10-18-2013 02:25 AM |
about setPosition | xingxing | Vizard | 2 | 02-20-2008 10:32 AM |