I’m not sure you ran the test as I described it but rather your own permutation which is much different.
If you’ve deactivated any percentage of the navigation behavior of either the 3D mouse or the 2D mouse, then said test isn’t the same test.
First and foremost, it’s merely a comparison of the navigation fluency of CATIA to the lack of navigation fluency of Rhino – relative to the usage of peripheral devices of the last few decades that have been available to all users of all GUI’s associated to 3D modeling programs that have existed – so far.
Secondly, if you really think about it you’ll realize there are indeed advantages to having both your left hand and your right hand to control the GUI space that’s right in front of your face, when you’re interacting with the digital content you’re creating in the evermore evolving 3D space that this world is continuing to focus energies on.
If we don’t break through the shackles of 3D navigation limitations, then we will just stagnate our developments throughout every aspect of traversing the verses of 3D/4D etc.
Even Rhino’s 2D mouse isn’t exactly comparable to CATIA’s 2D mouse. But imagine a scenario where both a 3D mouse and a 2D mouse in Rhino have the ability to control pan, rotate, zoom simultaneously and fluently without jerks, obstructions, or incompatibilities – (depending on button combinations of course, and user comprehensions).
Now imagine, the 2D mouse has a trick up it’s sleeve whereby it can smoothly alter the position of rotation both in depth and in direction, depending on how it’s aimed/directed/positioned on screen.
My intent isn’t so much to describe the navigation capabilities of CATIA, but merely to describe possibilities of the future of all CAD’s, including Rhino.
My first encounter to it was back in the yrs 2004-2008 when I became very well verse in CATIA using a spaceball5000 navigation device. It was like a dream being able to control 3D space so smoothly and fluently.
It wasn’t until the year 2009ish when I started taking on the endeavor of learning Rhino, that I hit a major wall in this jerky navigation behavior I’ve described.
Back then I was so used to moving both the 3D mouse and 2D mouse all the time (together), no matter how ever so slightly, it would cause Rhino to jerk. I was so used to it never being a problem until I started using Rhino.
Not to mention the rotation position problems, I probably shouldn’t even mention that here – I’ve mention that in other threads. I did mention it slightly here already, but that’s not my focus.
And sorry if I hijacked this thread lol.
I just figured this thread was being driven into the belief that something associated with 3D navigation is somehow “solved”, and it is most certainly not “solved”. There’s inherently something still broken in Rhino’s navigation behavior/compatibility with 3D/2D mice.
The key to part of the solution is the ( camera frustum entity ) control or lack thereof – fwiw.
sorry i didnt understand what you meant at first 