Eliminate redundant work in raycaster component

[mqp]

THREE.Object3D.getWorldPosition already internally calls updateMatrixWorld in order to always produce an up-to-date position, so we don't want to call it ourselves first -- that's just doing the work twice.

[mqp]

By the way, I would be interested to understand why raycaster.checkIntersections calls setTimeout(updateLine) at the end. Why can't it just call updateLine directly? Alternatively, can drawLine happen in the next tick, instead of in a separate timeout? I ask because the raycaster code is fairly performance-sensitive for our team and setTimeout is relatively slow.

[ngokevin]

Not sure, should have left a comment back then. You can try removing it or moving to a tock.