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
I assume it's intended to be used like catmullRom, however given the same parameters it shows unexpected(?) results.
example for cubic, running code glm::cubic(prevHexPos, currHexPos, nextHexPos, nextNextHexPos, ii)
example for catmullRom, running code glm::catmullRom(prevHexPos, currHexPos, nextHexPos, nextNextHexPos, ii)
they are both passed the exact same valid positional vectors. The lines drawn seem to point from the correct origin, however the target seems to be off in the distance somewhere away from the world origin (seems to be complete opposite direction of origin, so maybe the resulting vector is scaled somehow?)
I don't remember exact version of glm but I think its 1.0.1.
The text was updated successfully, but these errors were encountered:
From gtx splines
I assume it's intended to be used like catmullRom, however given the same parameters it shows unexpected(?) results.
example for cubic, running code
glm::cubic(prevHexPos, currHexPos, nextHexPos, nextNextHexPos, ii)
example for catmullRom, running code
glm::catmullRom(prevHexPos, currHexPos, nextHexPos, nextNextHexPos, ii)
they are both passed the exact same valid positional vectors. The lines drawn seem to point from the correct origin, however the target seems to be off in the distance somewhere away from the world origin (seems to be complete opposite direction of origin, so maybe the resulting vector is scaled somehow?)
I don't remember exact version of glm but I think its 1.0.1.
The text was updated successfully, but these errors were encountered: