Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
CurvePath getPointAt, missing optionalTarget
See original GitHub issueFrom the documentation and typescript definition, curvePath.getPointAt() has 2 params, with the second being optionalTarget, but in reality this isn’t implemented.
https://github.com/mrdoob/three.js/blob/master/src/extras/core/CurvePath.js#L58
Issue Analytics
- State:
- Created 4 years ago
- Comments:12 (4 by maintainers)
Top Results From Across the Web
Curve#getPointAt – three.js docs
An abstract base class for creating a Curve object that contains methods for interpolation. For an array of Curves see CurvePath.
Read more >ThreeJS Curve - TAE - Tutorial
Returns a vector for a given position on the curve. .getPointAt ( u : Float, optionalTarget : Vector ) : Vector. u -...
Read more >three.js - Apple Open Source
1 : + x; }; } if ( 'name' in Function.prototype === false ) { // Missing in IE ... Matrix4: the constructor...
Read more >Three.JS Object following a spline path - rotation / tanget ...
To maintain a constant speed, you use .getPointAt( t ) instead of .getPoint( t ) . To get the box to remain tangent...
Read more >Why is the object not moving along the curve path?
I tried rotating the tube and change the axis, but it still didn't work. Could anyone please point out what I missed in...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I do not think anyone would want their bug report to be assigned that label.
There is no point in adding that label and fixing the bug right away.
Exactly. That is an excellent way to give new users the opportunity to contribute.
Perhaps it was implied, but I would also support unifying “Feature Request” and “Feature Request (easy)”.