The @pointer-move function experiences noticeable lag

[hawk86104]

Describe the bug

The @pointer-move function experiences noticeable lag when the [widthSegments | heightSegments] of PlaneGeometry exceeds 100.

Reproduction

https://stackblitz.com/edit/tresjs-basic-bxhf8j?file=src%2Fcomponents%2FTheExperience.vue

Steps to reproduce

<TresMesh @pointer-move="onPointerMove">
  <TresPlaneGeometry :args="[50, 50, 200, 200]" />
  <MeshBasicMaterial />
</TresMesh>

System Info

No response

Used Package Manager

yarn

Code of Conduct

• [X] I agree to follow this project's Code of Conduct
• [X] Read the Contributing Guidelines.
• [X] Read the docs.
• [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• [X] The provided reproduction is a minimal reproducible example of the bug.

[CptJJ]

@alvarosabu this is probably related to what I was talking about on discord, i only see the lag come up when i bind any of the events (even onClick) to a mesh that has several hundred triangles:

[alvarosabu]

Thnx both for raising this @hawk86104 @CptJJ

[Sea-DH1]

I have encountered this problem before. I checked the code and finally found that if three-mesh-bvh is used, this problem no longer exists.

[alvarosabu]

@Tinoooo @garrlker maybe this would be fixed by the changes you guys are doing on events?

[hawk86104]

Thank you, it has indeed solved the problem

	hawk

@.*** |

---- Replied Message ---- | From | Alvaro @.> | | Date | 12/13/2023 16:53 | | To | @.> | | Cc | @.> , @.> | | Subject | Re: [Tresjs/tres] The @pointer-move function experiences noticeable lag (Issue #436) |

@@.*** maybe this would be fixed by the changes you guys are doing on events?

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

[CptJJ]

Amazing Fixed It!

Is there a downside to making this the default when rendering meshes in tres?

[alvarosabu]

Glad to hear it has been solved, @CptJJ what do you mean on making it default?

[garrlker]

@alvarosabu @hawk86104

It looks like the Tres V4 RC fixes the issues in the original stackblitz

Here's a fork that updates to the V4 RC and does not show the same performance issues

If you don't mind @hawk86104, could you temporarily disable the three-mesh-bvh code and try out the V4 RC in your project and let us know if the issue is fixed?

yarn i @tresjs/core@4.0.0-rc.0

[hawk86104]

@alvarosabu @hawk86104

It looks like the Tres V4 RC fixes the issues in the original stackblitz

Here's a fork that updates to the V4 RC and does not show the same performance issues

If you don't mind @hawk86104, could you temporarily disable the three-mesh-bvh code and try out the V4 RC in your project and let us know if the issue is fixed?

yarn i @tresjs/core@4.0.0-rc.0

@garrlker You're very welcome! That's great to hear. I'm not sure when it will be merged into the main branch.

[Rain20199]

@tresjs/core@4.0.0-rc.0 pointer events trigger multiple times

[garrlker]

@Rain20199 They do?

That's strange, we do check for duplicate events and ignore a handler if we've already called it

Any chance you could make a reproduction so I can look into it?

[alvarosabu]

@Rain20199 since it is a different issue can you open a new ticket with a minimal reproduction? Thanks