I’ve been testing my new ‘corded’ usb SpaceNavigator today, with the latest driver and I’m not seeing any of my previous ‘wireless’ SpaceMouse issues, so far…
I’m not getting the memory run-away even with template startup or the Ruby Console errors that I had previously, but it’s early days…
the plugin still installs to the System Library, much to my annoyance, and I miss my muscle memory shortcuts hand availability…
how’s it going at your end of the pond, steve…
I’m still on El Capitan which may well make a difference…
I’m running macOS 10.12.5 (no SketchUp issues from that, so far as I have seen). I noticed during the driver install that it asked whether I wanted it to be for all users. I wonder if that causes it to install in the system library’s app support (a mistake, I think. The device hardware driver needs to go into an appropriate system folder, but the SketchUp extension should be in a user’s app support).
On my Mac the runaway memory issue is 100% repeatable if I don’t promptly close the default blank model window, but has not happened if I do close it. So, I suppose there could be either a hardware-specific issue (mine is a MacBook Pro Retina mid-2012) or a macOS version issue.
Otherwise I’ve been practicing to develop the muscle memory. For me, at least, it took a while to get single-function motion, especially pan and zoom, which take some care to avoid mixing in a tilt or rotation.
I noticed during the driver install that it asked whether I wanted it to be for all users.
It asks you that, but then doesn’t give you the choice of installing it in your user (home) Library — that choice is always greyed out (at least for me on El Capitan). So it always and only gets installed in the system level library.
The distinction you’ve made between the location of the hardware drivers and the plugin is an important one I suspect. Maybe they force the System Library location to avoid multiple instances running at the same time on different versions of SketchUp? (as that seems to have been one of the proximate cause of the race conditions I described in an earlier post.)
Otherwise I’ve been practicing to develop the muscle memory. For me, at least, it took a while to get single-function motion, especially pan and zoom, which take some care to avoid mixing in a tilt or rotation.
Their driver installs as a kernel extension. Since the space navigator can be used with other apps, not just SketchUp, it can’t depend on the SketchUp extension to make it work. For example, right now SketchUp is not running on my Mac, but kextstat shows the space navigator driver kernel extension loaded.
I suspect more likely they just didn’t consider the possibility of more than one version of SketchUp running at the same time. Most other apps don’t install multiple simultaneous versions. And each version of SketchUp gets a separate subfolder in /Library/Application Support, just like it does in ~/Library/Application Support. So, they’d have the same issue detecting simultaneous versions regardless.
I tried the “Dominant” setting briefly. At that time I didn’t like it - seemed too restrictive. Once I get more comfortable with the regular interface, I may try that setting again to better understand what it does.
I dislike the Dominant setting. The main reason I use a 3D Mouse is to allow me to move in full 3 dimension, at all times. Not along one axis at a time. Just my $0.02, though.
