According to the profiler, it’s one of the most expensive things, frequently taking over 5ms. I’ve removed all inputs from the camera, so scene.activeCamera.inputs.attached is {}. There is only one camera. Maybe the virtual joystick? But it’s running even when I’m not touching the joystick.
I tried adding breakpoints in the constructor and attach methods, but alas, it seems my .map file is not working properly, so they never get hit.
This is used to scale meshes with gizmos. I am not sure why you would have it except if you instantiated it in your code ?
Like @sebavan is saying, it’s specifically related to gizmos. Without knowing what your code looks like, it’d be difficult to determine why it’s appearing there.
@sebavan, @PolygonalSun, I’m not using any gizmos. I’ll try setting scene.skipPointerMovePicking to see if it makes a difference.
This class is a utility not used internally in Babylon so your code is probably creating it in some ways. It would be great to see a repro.
