Pan & Orbit suddenly slow, jerky, unresponsive
-
Just yesterday pan and orbit has gone from smooth to jerky and unresponsive to the mouse.
Sketchup Pro 8
This behavior occurs in all files even a simple file containing one rectangle.
No changes were made on hardware, drivers, or the OS (Win7) prior to this behavior starting.
This is not a middle mouse button problem. It occurs even when I select the orbit or pan tool and use the left mouse button.
This behavior occurs with 2-different new mice (Logitech and MS, all drivers updated) as well as the touchpad. It happens with the non-mouse specific, HID-standard default driver as well as proprietary drivers.
This occurs no matter how I set the OpenGL settings.
There is no problem with zooming. It seems to work normally scrolling with the middle wheel.I'm using an older laptop with the built-in Mobile Intel 4-series express chipset display adapter with up to date drivers. I know this is not the preferred setup, but it has worked fine for years without any pan or orbit issues.
Specifically, in a simple file with one object, no matter the pointing device, starting the pan/orbit with the cursor on the object, the pan/orbit works reasonably well if the pointing device motion is very slowly. The faster the movement, the more unresponsive it becomes. I'm talking about normal mouse movements here, not abrupt fast movements. The object freezes, then sort of catches up to the mouse in a large jump. I can move the cursor, at a modest speed, across the entire screen without the object rotating until I stop, at which point it it rotates with one big jerk.
This is a real pain. Thoughts?
-
so you're sure that no other software is running? taking up a lot of system resources?
-
Kristoff's question is good. Did you just recently update the graphics drivers? It isn't unheard of that an update to the graphics drivers causes problems. What have you changed on the computer recently? Did you install any new plugins? If SketchUp 8 has been working fine for years it isn't likely to be a problem with the program but rather something else causing the problem.
Advertisement