also my "formula" lib is much faster as the hscript expressions!

off-topic of WHAT ????

limescript

I only worry when it gets wild

and it's starting to 🙂

what is going wild .. that you break your code and talk together with others about

coding

?

or do you mean we should swith into the ->

causual

bar ?

does semmi want to be blocked from lime as well? 😄

yes -> DO

-> BURN books ALSO

🔥

🙈

NotBilly, i am still miss your

code

- sample for you last asset-

commit

here:

(what is a new

graphic-snipped

without the

code

who is using it ?)

Well im completing it

To some degree at least

I've made a whole lot of additions to it

Getters and setters for example

Or a protype of fully customizable flxstates and substates, which will probably go unused once I finish the softcoded class implementation

Hell I made an entire sheet just for setting up inheritance

does anyone anyone have implementations of normalize and lookAt functions?

they don't exist in lime math

no wait its just the lookAt, I found the normalize

hx
public static function lookAt(target:Vector3, position:Vector3, up:Vector3):Matrix4 {
    var forward:Vector3 = target.subtract(position).normalize();
    var right:Vector3 = up.cross(forward).normalize();
    var newUp:Vector3 = forward.cross(right).normalize();
    
    var lookAt:Matrix4 = new Matrix4();
    
    lookAt.set(right.x, newUp.x, -forward.x, 0,
                right.y, newUp.y, -forward.y, 0,
                right.z, newUp.z, -forward.z, 0,
                -right.dot(position), -newUp.dot(position), forward.dot(position), 1);
    
    return lookAt;
}

does that look right?

||@hallowed-ocean-84954 || (sorry for the ping), I looked into your rubiks cube repo, and fortunately found the lookat function, but I can't adjust it to lime instead of openfl 🥶

I haven't look into conversion of the matrices and vectors to lime yet but my guess would be that you'll need to use Vector4's in place of my Vector3D's. The problem is what then to do with w. Technically I think for a direction vector you can just set w to 0.0.

Actually there is a simpler way - the Matrix4 class has a method which takes the camera pos, up and at vectors directly. And all as Vector4's.

If I'm right pointAt should just be lookAt under another name.

@tall-teacher-57409 ^