Since recent releases, I have been having issues when using my Wacom Intuos Pro (5) with Rhino. So today I decided to update my OS (I’m on Windows 10.0.19044) and to also update Rhino to SR20 (7.20.22193.9001, 2022-07-12). Unfortunately, the buttons of my pen are still improperly recognised. When I put down my pen on the tablet’s surface, it doesn’t click, but rather initiate a pan when I have one viewport maximised.
With multiple viewports, editing in one viewport ends up navigating in another (first it did this in the top left, but while recording it happened in the bottom left.
E: Wacom Driver is 6.3.46-1, which is the most recent one.
Solution
I managed to resolve the issue by disabling Windows ink. In the past, I have never used a profile that is specific to Rhino, so something must have changed with regards to Windows ink, either on Windows end or in Rhino.
Keep in mind that wacoms software has its rough edges too.
From time to time I have to reload my wacom profiles from backup to force the driver to restart or it wouldn’t recognise my cintiq screen.
Also the windows ink option that magically switches itself on happened to me a couple of times in the past.
Yeah, I need to restart the service (Wacom driver) quite often as well. I don’t actually remember whether this error emerged by updating the Wacom driver, from 6.3.45-1 to 6.3.46-1, all I do know is that it happened recently. In case there is an issue, McNeel could take a look. If there isn’t, I let users know to disable Windows ink for Rhino.
Hi, I’m new to Rhino and would like to use my Wacom Cintiq touch. I’m finding the pen does not map correctly on the viewport very similar to what is described here. I’m using Rhino 7 on windows 11 and was wondering if this is a know issue. All other programs are working fine with the pen and touch screen (Shapr3D, ZBrush, Blender, etc…) I should note that the touch navigation works fine and all other touch functionality. It’s just the Pens (slim, pro and 3D pens all have issues). I disabled windows Ink and I still have the same issue. Thanks.