games_fps Example: Collision detection anomaly

[Jinxishihenian]

Description

In the games_fps example, when the player is stationary, the collision detection fails almost every six seconds.

Reproduction steps

In 'https://threejs.org/examples/?q=gam#games_fps' the player stands still and the octree outputs the result of the collision.

Code

	function playerCollisions() {

		const result = worldOctree.capsuleIntersect(playerCollider);
		// When the player is stationary on the ground, it triggers almost every six seconds or so
		if (!result) {
			console.log('fail');
		}
	 
		playerOnFloor = false;

		if (result) {
	 
			playerOnFloor = result.normal.y >= 0;

			if (!playerOnFloor) {

				playerVelocity.addScaledVector(result.normal, -result.normal.dot(playerVelocity));

			}

			playerCollider.translate(result.normal.multiplyScalar(result.depth));

		}
 
	}

Live example

Screenshots

No response

Version

0.165.0

Device

Desktop

Browser

Chrome

OS

Windows

[Mugen87]

I'm unable to reproduce the issue with Chrome on macOS. fail is only logged at the very beginning of the app when player is still in the air. But as soon as the player is on the ground, there are no additional logs (unless you jump or fall down a platform).

Do you mind recording a short video that shows how the messages are logged in your browser?

[ycw]

It's reproducible when player idles on ramp for a while

[Mugen87]

Oh, now I can reproduce as well.

[Jinxishihenian]

Very efficient efficiency, thank you very much