Simon Harris

``` geometry.set({ instanceOffsets: [] // divisor is assumed as this is instanced attribute and defaults to 1 }) ``` Seems more user friendly and feels nice with the other properties

- why `geometry` and `surface` ? is this additional jargon that might just add confusion? - are you going to be be able to change these on the fly? -...

I tried randomising the up vector every frame and it still happens 😆 ``` const up = [Math.random(), Math.random(), Math.random(), Math.random()] ```

yeah, doesnt help

I suppose Im suggesting an extension to the transform component: https://docs.unity3d.com/ScriptReference/Transform.html This is unity’s see methods such as rotateAround and lookAt and properties such as up.

Marcin's response: ```javascript rot = quat.fromEuler(quat.create(), [Math.PI/2, 0, 0]) //beta [email protected] rot = quat.setAxisAngle(q, axis, angle) rot = quat.fromDir(q, fromDir, toDir) Entity.transform.rotation = rot Etc ``` One missing thing is...

What you suggested above is using maths functions **and a knowledge of relatively complex geometry** to modify values. I suggesting that by adding these as methods of the transform component...

there is a mentality shift between x.transform.rotation.set(maths) and x.transform.rotate([0,0,1]) as well as a higher level of knowledge