Do not use getElapsedTime on the main state clock, it messes up the delta

[AlaricBaraou]

A very simple PR

Just used the Cloud component and I noticed it messed up 'the time'

I then saw that many components call clock.gelapsedTime() on the main clock instead of reading the .elapsedTime property

Calling getElapsedTime() update the delta of the clock and then returns .elapsedTime

Clock source in three.js
https://github.com/mrdoob/three.js/blob/master/src/core/Clock.js

Edit: In case you want the elapsed time precisely at the moment of the method call, use a separate clock for that.
I'd add that in 99% of case, you want the same elapsed time for all object in the current frame, making reading .elapsedTime even better than clock.gelapsedTime() to fully sync everything.

This could be added to the gotcha section of the doc because I come across this issue in most projects I review.

[vercel]

@AlaricBaraou is attempting to deploy a commit to the Poimandres Team on Vercel.

A member of the Team first needs to authorize it.

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.