Why is CFrame.new ( Vector3 pos, Vector3 lookAt ) deprecated?

[MysteryOfHyper]

I’m probably late to this but I just found out that CFrame.new ( Vector3 pos, Vector3 lookAt ) is deprecated.
I don’t really care about switching to :fromMatrix() but I just want to know the reason why.

[idkhowtocode]

The lookat constructor for CFrame still works (for now). The same functionality can be achieved with :fromMatrix() and more, so there is no reason to spend engineering resources maintaining the old constructor.

[MysteryOfHyper]

Ok, that’s cool! Thanks for responding.

[spliceosome (Shardwielder)]

There is a forum post that discusses how other alternatives do not provide the same functionality, especially with some fringe cases. I’d look it up.

I choose not to waste my time, and use the built in constructor which works perfectly and conveniently. I don’t think anybody knows why it’s deprecated, or if that’s just a wiki mistake. There’s a huge amount of significant games which rely on this constructor, there’s effectively 0% chance of something happening to it.

[Anaminus]

My conclusion is that it is not deprecated.

Is CFrame.new(Vector3 position, Vector3 lookAt) actually deprecated?

I think the claim that it’s deprecated is dubious. I vaguely remember some years ago how the lookAt constructor (lookAt) was disfavored because it didn’t let you specify the longitudinal axis (or “roll”). That is, the resulting CFrame is always oriented upright. With the addition of fromMatrix, it became possible to specify other axes more easily. I think that whoever wrote the documentation interpreted this as lookAt becoming obsolete, and therefore “deprecated”. However, as the given example s…