Hello Again, we have a fairly large system that would be difficult to put on github for you to test. However I was able to at least identify the culprit. After further analysis, I dont think this has anything to do with how we are loading and assigning textures as originally thought. Also this issue seems to be something with the pointer event handling under the hood and only occurs in chrome. I have tested on safari and seems to work fine. What is going on is we see a RAF Violation and a noticeable hitch in the framerate on that initial pointerdown click AS LONG AS that click happens to be on top of some geometry… like its trying to pick the geo . If we click-drag anywhere outside of the object, we do not see a frame-rate hitch and everything happens as normal. This violation warning happens even if we dont register our own pointer event. I have also tested this with the babylon default camera and same behaviour.
We are getting some warnings:
“[Violation] Added non-passive event listener to a scroll-blocking ‘wheel’ event.”
Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
[Violation] Added non-passive event listener to a scroll-blocking ‘touchstart’ event. Consider marking event handler as ‘passive’ to make the page more responsive
I saw that there was a PR for the non-passive event listener warning, but even without that fix it the warning can be ignored.
still not sure if these warnings are related to the issue.