You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
In the current implementation, the check for intersecting objects happens on every single render cycle (see here).
Describe the solution you'd like
We could change the code in a way that the intersections are only calculated when the pointer moves or when the canvas is being clicked. Maybe there is even a possibility to only check meshes in which the respective directives (@click, ...) are used. These changes would lead to performance improvements.
Suggested solution
See above.
The text was updated successfully, but these errors were encountered:
Tinoooo
changed the title
raycaster: only check for intersections when pointer moves or on click events
Raycaster: Only check for intersections when pointer moves or on click events
Mar 3, 2023
Is your feature request related to a problem? Please describe.
In the current implementation, the check for intersecting objects happens on every single render cycle (see here).
Describe the solution you'd like
We could change the code in a way that the intersections are only calculated when the pointer moves or when the canvas is being clicked. Maybe there is even a possibility to only check meshes in which the respective directives (
@click
, ...) are used. These changes would lead to performance improvements.Suggested solution
See above.
The text was updated successfully, but these errors were encountered: