8000 LOD position is not based on camera position (PointerLockControls) and lacks support for TresInstancedMesh · Issue #630 · Tresjs/cientos · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
LOD position is not based on camera position (PointerLockControls) and lacks support for TresInstancedMesh #630
Open
@Dekier

Description

@Dekier

Describe the bug

I am using LOD in a scene with PointerLockControls, and currently the LOD system switches levels based on the distance from the center of the scene, not the actual camera position.

Expected behavior:
LOD should take the current camera position into account when using PointerLockControls, as the player moves through the scene and expects objects to update accordingly.

Actual behavior:
LOD uses the scene origin (or a fixed point) for distance calculation, so level switching does not reflect the player's movement accurately.

Additionally, there is no support for TresInstancedMesh. Right now, it replaces the entire instanced mesh instead of updating individual instances based on their distance to the camera.

Reproduction

lack

Steps to reproduce

Steps to reproduce

Set up a TresCanvas scene with LOD components and PointerLockControls.

Move the camera/player through the scene.

Observe that LOD transitions are not based on camera position.

Try using LOD with TresInstancedMesh and notice that all instances change at once.

System Info

Used Package Manager

npm

Code of Conduct

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0