Node.position.set() doesn't have affect

Horchynskyi · June 30, 2020, 12:33pm

Hi all. I noticed when I am trying set position by node.position.set() it doesn’t have any affect.
Just node.setPosition() works.

StudioAMK · June 30, 2020, 9:52pm

Do you mind sharing the codes?

Position is Vec3 and, if I’m not wrong, you can directly assign a Vec3 value.

And also, did you correctly pass the parameters when you called set() method? Check that method’s signature here

Horchynskyi · July 1, 2020, 12:41am

Hi, thanks for replay.
I am trying to use not static “set” method:

so as you can see node isn’t moving on the screen, also in console this vector still in zero values.

StudioAMK · July 1, 2020, 9:46am

I think, it’s a static method of Vec3.
So we can call it from any Vec3 instance.

Try this.

let newPos = new Vec3(100, 100, 0);
this.node.position.set(this.node.position, newPos);

Horchynskyi · July 1, 2020, 10:48am

No, there is also not static method as I see:
console.log(this.node.position.set.toString());

and if I try to set one of axis like here:
this.node.position.x = 100;

it also doesn’t work.

github.com

cocos/cocos-engine/blob/f495398f4307775f0f733162e3d128d81e063063/cocos2d/core/value-types/vec3.ts#L1082

      
        
            }
            
            
/**
             * !#en Set the current vector value with the given vector.
             * !#zh 用另一个向量设置当前的向量对象值。
             * @method set
             * @param {Vec3} newValue - !#en new value to set. !#zh 要设置的新值
             * @return {Vec3} returns this
             * @chainable
             */
            set (newValue: Vec3): Vec3 {
                this.x = newValue.x;
                this.y = newValue.y;
                this.z = newValue.z;
                return this;
            }
            
            
/**
             * !#en Check whether the vector equals another one
             * !#zh 当前的向量是否与指定的向量相等。
             * @method equals

StudioAMK · July 1, 2020, 3:10pm

I see. Can you try with the latest 2.4.0?

Horchynskyi · July 1, 2020, 4:54pm

Same behavior with 2.4.0