I know this bug in drivers above version 10.3.0, it probably concerned the 3dxware driver itself in combination with the Rhino plugin and it appeared for all users I had the opportunity to meet and unfortunately it was not solved by 3DConnexion. That is why I always used the “Hard” entry in the Rhino.xml configuration file for the driver which prevented the 3D mouse from switching to a new application and kept the driver’s “focus” constantly on Rhino as long as it was running.