I can work with that. Thanks for the info!
@PolygonalSun I’m happy to help or run tests If I can! I created a quick playground to check for maxTouchPoints aswell as the touchstart event on the canvas. When using my wacom, the callback does not get triggered for the touchstart event though. So it might be a different problem then?
Playground: Babylon.js Playground
This is the console output:
Just adding another observation: When opening this Playground: https://playground.babylonjs.com/#2JKA91#6 in Chrome, when I do a drag operation while holding the right mouse button on my pen tablet pen babylon does a rotate operation. In Firefox the same operation is doing a translate operation. That’s kind of weird. Again this is happening only in v5, in v4 everything behaves normal.
Thanks for the PG. I’m almost done with the fix that should resolve the clearing of events when all controls are detached (using scene.detachControl) and I managed to get my hands on a tablet so (pending no random weirdness), I should be able to verify a fix for tablets.
PR with event changes is live: DeviceInputSystem: Add configure/removeEvents to be called by DeviceSourceManager by PolygonalSun · Pull Request #11959 · BabylonJS/Babylon.js (github.com)
2 Likes
PR is merged
1 Like
Just following up here because I think there still might be some lingering issues around this @PolygonalSun ! and @RaananW might be interested because there’s some VR involved.
We updated from beta 2 to beta 8 recently, and now when in the Oculus Quest, before entering VR mode but while trying to use the Quest Controller to interact with the scene, I also get “logger.js?0c56:70 BJS - [17:25:35]: Max number of touches exceeded. Ignoring touches in excess of 0” and I can’t interact with any clickable buttons in my scene.
Once I enter VR mode, I am then able to click on the buttons. Any ideas?
1 Like
I took a look back at the commits and it looks like my changes made it into beta 9 (just missed beta 8). Would you be able to try updating to 9 and let me know what behavior you see?
1 Like
Hi @PolygonalSun , it does indeed look like this is fixed in beta 9!
2 Likes