You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the usage is bad, and it causes math to be more confusing now that mul ordering was fixed a couple years ago. this would be a breaking change and probably prevent an enormous amount of confusing bugs from this legacy bit of the api
it's not really a bug so much as a legacy misfeature that should just go away. a long time ago it made using it easier.
signed, me who just explained the math to someone backwards for the last hour before realizing the logical inconsistency.
The text was updated successfully, but these errors were encountered:
clarification: functions such as mat4.scale take an a argument which is a base matrix to multiply with, which gets post-multiplied with the new matrix. this was helpful for making things act liked they seemed like they should a long time ago (before #33) was fixed, and is now just plain confusing, and wasteful when the sensible thing to do is to pass identity all the time.
the replacement will be to call mul yourself and not have to deal with this oddball behavior.
the usage is bad, and it causes math to be more confusing now that mul ordering was fixed a couple years ago. this would be a breaking change and probably prevent an enormous amount of confusing bugs from this legacy bit of the api
it's not really a bug so much as a legacy misfeature that should just go away. a long time ago it made using it easier.
signed, me who just explained the math to someone backwards for the last hour before realizing the logical inconsistency.
The text was updated successfully, but these errors were encountered: