I just downloaded the latest BETA today and immediately figured out that the Zzoom button of my 3d mouse no longer works properly with it. When I select one or more objects, pressing the Zoom button of my 3d mouse does nothing. My Windows 10 plays the “reject” sound or whatever it’s called. This action also switches the state of the “Grid snap” for some reason.
However, when I deselect the object and select it again, followed by pressing the Zoom button of my 3d mouse twice (the initial press turns off the “Grid snap”), Rhino 9 BETA finally zooms the selection.
It’s really strange that this is happening, especially the bug with the “Grid snap”.
I also noticed that the grid settings were changed to snap to every 10 mm instead of every 1 mm. I haven’t made any changes to my settings since the previous version of the BETA from one week ago.
I think you have the same Spacemouse as I have here, the old SpaceExplorer?
I have Rhino.Options.SpaceBall.UseLegacy = True
And these shortcuts in 3Dconnection Buttons:
It’s sad that the cause of the bug is untraceable so far. I can’t fix it on my end. I see no obvious connection between the “Zoom” button of my 3d mouse and the “Grid snap” toggle.
Actually, the button on my 3d mouse is called “Fit”, but its purpose is to zoom.
Note that I don’t use the default command of my 3d mouse which is “Zoom extents”. I use a custom macro to “Zoom selected”. The macro itself is written this way and it worked perfectly fine with the previous version of the BETA:
It seems that the keys are firing an enter automatically. S is the shortcut for GridSnap, you can actually see that happening in your video.
Why not simply use the actual macros? !_ZoomSelected or (without canceling any running command) '_Zoom _Selected?
I’m unable to navigate up and down with the arrow keys inside the Command line to see the previous commands. However, I can do that in Rhino 7. Is that a new bug introduced in the latest BETA?
My 3d mouse will not give me an option for “Zoom selected”, this is why I’m using a custom macro for it. The default option is “Application Use”, which is “Zoom Extents”. For some reason, the latest Rhino 9 BETA does not recognize the “ZS” combination of my custom macro. It only reads the “Z” key or the “S” key individually, instead of waiting for both keys to be executed before the “Enter” which is also part of the macro.
Perhaps there is some setting for adding an automatic “Enter” after pressing a single key? Is that related to the newly introduced single-key commands (instant aliases) in Rhino 9 BETA?
I just made an experiment and made the “ZS” (Zoom selected) an instant alias. It works the first time I use it by typing “ZS” with the keyboard. However, when I deselect the object and select it again, typing quickly “ZS” actually disables the “Grid snap”. Typing “ZS” again zooms the selected object. This behaviour is the same as if I press the “Fit” button on my 3d mouse which triggers the “ZS” macro.
When I disable the 3d mouse and the driver, and then I run Rhino 9 BETA, the bug is still present. This means that the bug is not caused by the 3d mouse.
This is a copy of my Command line list of used commands
Command: ZS
Command: '_Zoom
Drag a window to zoom ( All Dynamic Extents Factor In Out Selected Target 1To1 ): _Selected
Command: ZS
Command: '_Zoom
Drag a window to zoom ( All Dynamic Extents Factor In Out Selected Target 1To1 ): _Selected
Command: ZS
Command: '_Zoom
Drag a window to zoom ( All Dynamic Extents Factor In Out Selected Target 1To1 ): _Selected
Command: ZS
Command: '_Zoom
Drag a window to zoom ( All Dynamic Extents Factor In Out Selected Target 1To1 ): _Selected
1 closed polysurface added to selection.
1 closed polysurface added to selection.
Command: S
Command: '_Snap
GridSnap is Off
Command: ZS
Command: '_Zoom
Drag a window to zoom ( All Dynamic Extents Factor In Out Selected Target 1To1 ): _Selected
1 closed polysurface added to selection.
1 closed polysurface added to selection.
Command: S
Command: '_Snap
GridSnap is On
Command: ZS
Command: '_Zoom
Drag a window to zoom ( All Dynamic Extents Factor In Out Selected Target 1To1 ): _Selected
NOTE: I just edited my post and added more text to it.
What are your CommandMode options set to?
To see the history in the command history, you need to use the scrollwheel on the mouse or the scrollbar in that history window. I see that the spinner in the actual command line part of this is redundant.
→ RH-97628 CommandPrompt (Eto): Redundant Spinner
-wim
I don’t remember the exact version of the last good BETA, but I downloaded it last week, about 10 days ago, so perhaps it’s either Rhino 9 BETA (9.0.26209) or Rhino 9 BETA (9.0.26202). I’m 99% sure that it was the first one, because it was released exactly 10 days ago.
The version that makes issues now is Rhino 9 BETA (9.0.26216) , which I downloaded on August 5th.
Hi @wim , I use a 100% default Rhino 9 BETA, which I also reset earlier today just in case. But both bugs mentioned by me (inability to zoom with the 3d mouse’s “Fit” button and inability to navigate the Command line with the arrow keys) are still there.
This is what I saw when I opened the stock BETA after pasting the command you wrote:
As far as I remember, I had to change two settings of the Rhino 9 BETA recently, because I didn’t liked the defaults:
I use “Large objects - Millimeters” as a template. For some reason, the “SnapSpacing” of the Grid was set to every 10 mm instead of every 1 mm after the update. The “MinorLineSpacing” was set to 10, too. I changed it to 1, too;
I prefer to use a solid grid instead of the new style whose border blends with the background.
After I ran the _TestEtoCommandUI command and closed the latest Rhino 9 BETA, I copied the 3d mouse plug in from Rhino 6.3 into the “Plug ins” folder to enable my discontinued 3d mouse. Then I ran the BETA again and the bug is gone. The “Zoom selected” macro works as expected now.
I also can navigate with the arrow keys in the Command line history. Seems like the _TestEtoCommandUI command is the fix I needed.
However, when I ran the same command again to enable the new buttons style of the Command line, both bugs are back again.
I enabled the old style again and everything is flawless.
