Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

hittest cpu #4

Open
gushenjie opened this issue Sep 3, 2022 · 4 comments
Open

hittest cpu #4

gushenjie opened this issue Sep 3, 2022 · 4 comments

Comments

@gushenjie
Copy link

After the collision detection is turned on, the FPS on the PC side is only about 30 frames, and on the mobile side, it is only about 6 frames. Is there any suggestion for optimization?

@mese79
Copy link
Owner

mese79 commented Sep 3, 2022

Do you run the provided example or your own one?
For me, this example works about 60 fps on my laptop and mobile.

@gushenjie
Copy link
Author

I directly access the example address you sent, and it is a black screen after clicking to open through WeChat

@gushenjie
Copy link
Author

It may be that the number of objects detected by the raycaster is large. I printed the timestamp log on the mobile terminal and found that it took 60ms.

@mese79
Copy link
Owner

mese79 commented Sep 7, 2022

If you have numerous objects in the scene, then yes, that might slow down the collision detection.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants