Open CompSciFutures opened 9 years ago
Will look into this. This seems rather suspicious to me, since
That being said, I'm going to look into this, but would ask you to double check if there is something else in your code that mutates the states directly, e.g. the returned offset arrays shouldn't be mutated directly.
Hi alex, I checked it very closely hence the minmal working example. I'm pretty sure it's real.
NB, I built a wrapper around it to fix that problem but now it appears that the z axis is in the range [-0.5, +0.5] rather than [0, 1]. I have not investigated that too deeply but just started working with that coordinate system instead.
Why I mention it is that this bug might be caused by an attempt to band-aid over a bigger z-axis problem?
Description
Node#setMountPoint() and Node#setAlign() decrements their respective Z-components by 0.5 every time they are called.
Isolation
Example
Relevant Code Section
Working Example Code
Ouptut
Actual Console Ouptut
(note component "2" decrements by 0.5 each time)
Expected Console Output