I am giving Rhino 8 a try, but this function or bug is making it unworkable.
Running a default shortcut like ctrl+alt+e starts typing a command starting with an E in the command prompt. Running another shortcut, for instance ctrl+alt+r while keeping ctrl and alt pressed continues to type in the command prompt but doens’t run the shortcut.
Changing the shortcut to start with ! _ doesn’t change the behaviour.
Although if it would that is still not ideal, as you wouldn’t want to cancel a command you are working on while changing, for instance, render modes with a shortcut.
Hi Niels - so, in a new file, if you make a box and Ctrl-Alt-e, you get an e on the command line, is that correct? Can you press F2 and copy/paste the last few lines from that Command History here?
Command: _Box
First corner of base ( Diagonal 3Point Vertical Center )
Other corner of base or length ( 3Point )
Height. Press Enter to use width
1 closed extrusion added to selection.
Command: '_Zoom
Drag a window to zoom ( All Dynamic Extents Factor In Out Selected Target 1To1 ): _Selected
Command: _CommandHistory
Before being able to enter CommandHistory with F2 I had to delete the E from the commandpromt, see screenshot.
Your example Ctrl-Shift-e followed by Ctrl-Shift-r zooms extents in all and then sets the current vp to rendered. I hate to fall back on suggesting a re-boot but I can’t think of what else might help, at the moment.
Hi Niels - a colleague suggests running Reset and doing a full reset - last check box. This will reset everything. If you have made customizations at all that you care about, push the button to save the settings first.
Do you have any news on this? Is it still just me experiencing this?
I made a video with a keyboard input overlay, just to show you it’s real, and well I am afraid to say, but also kind of really annoying.
It means everytime I use a shortcut I need to clear the command input field before I can type a command. Also it will occasionally continue typing in there without registering the shortcut.
I hope there might be any news on this. I am running the latest service release candidate.
I thought maybe it’s the keyboard or the drivers so I have tested those on my laptop, but I see no problems there.
Would there be anyway to best diagnose this?
It makes it very frustrating to work in Rhino 8 together with a lot of other small issues and a general sluggishness of menu’s, panels, materials, etc. Unfortunately it makes R8 unworkable for me and I will be forced to revert back to R6 where I don’t have these problems.