Lerp | Linear interpolation microlibrary | iOS library

I had the same problem too. I researched a lot of documents about that and finally, I solved this problem. The problem is not about your codes or events or smth else. The problem is related to Unity. I don't know the exact reason for the problem but you can solve it this way: First, go Edit > Project Settings and select Input System Package from the Left tab. And then, change the Update Method with Process Events In Dynamic Update. And that's all! Dynamic update means the usual Update method that you see in the scripts void Update().

The bounds object doesn't appear to be properly created. The purple p5 vertices you're rendering may be giving you a false sense of confidence, since those aren't necessarily related to what MJS sees.

It's actually a pretty simple fix, passing an array of vertices instead of individual arguments:

Your items are overlapping because you're not allowing any lerping diffing when the items should switch positions.

The current value should never equal the target value. If the values match, than the current value needs to catch up the target — giving that erratic movement and wrong calculations, additionally aggravated for the two sibling elements which should be perfectly in sync to give that immediate snap-back, perceived as a fluid continuous motion.

• Instead of animating two (or more) children independently,
  animate only the parent .loop-container.
• The container should be as wide as one child element exactly.
• "Push" one child element to the far left using position: absolute; left: -100%
• To allow the target value to be always greater than the current value:
  when the target value is greater than 100 — set current to the negative difference of the two values, and target to 0

_{Demo time:}

The problem is that you do not limit the zRotation values between your desired values. In the current state of your code you only rely on your computer being fast and having little Time.deltaTime values (the time elapsed since the last frame). If you have any kind of hiccup (which happens often in the first couple of frames after starting up), the Time.deltaTime value is going to be relatively large, resulting in a zRotation that is so large that it takes longer to return into the [-45...45] range. You can check this by adding a line of

Debug.Log($"Time: {Time.deltaTime} - Rotation: {zRotation}");

to your update method.

This way the following scenario can occur (each line is the log of a frame):

1. Time: 0 - Rotation: 360
2. Time: 0,02 - Rotation: 380
3. Time: 0,02 - Rotation: 420
4. Time: 0,333 - Rotation: 733,33

In the last step there was a deltaTime value that was so big that caused the zRotation to get loose and go really far from your desired range. If you limit the rotation values with

zRotation = Mathf.Min(Mathf.Max(zRotation, 315), 405);

You would not go out of the desired range. (Of course you have to update your if statements from < to <= or you could leave some kind of threshold in the Min(Max()) part.

I would also advise you use the modulo operator (%) and initialize the value of zRotation to 0 so that you don't have to constantly keep track of the 360-minAngle, 360+minAngle values, you could just use the angles in a much easier way and the modulo operator helps you stay in the [-360...360] range.

I updated your code:

Keep in mind that FixedUpdate() can happen a few times within a single frame. Check if _spacePressed == true in the beginning of your Process_Jumping().

UHM I fixed it... in the weirdest possible way? I'm not sure at all what caused the issue, but if anybody knows it, please share. Some people could find it interesting.

Anyways, here is the fix:

You can animate a mesh along a path with plain three.js by defining a curve based on your sequence of points and then using this curve for animation.

There are a lot of ways you could do this, but I personally in this case would create new coroutines FadeIn and FadeOut, instead of directly calling the following:

fadeCoroutine = StartCoroutine(FadeTo(objectsToFadeMaterials[i], 0, duration));

Then, at the end of your FadeOut coroutine you can take some additional step(s) to trigger a teleport or whatever else you need to trigger. It looks like you don't want your Fading to hold a reference to your Teleporting, which is smart, so you could choose to fire an event instead that your Teleporting component can subscribe to.

change Tween(begin: 0, end: 1) to Tween(begin: 0.0, end: 1.0)