Using these settings, The Nudge (arrow keys) move the selected object only one move, and the action is not repeated if the arrow key is hit again.
Nudge keys work properly for me. V8 Work In Progress (8.0.22347.14305, 2022-12-13)
Run Rhino command SystemInfo and post the results here.
Nudge working here correctly as well…
After restarting Rhino WIP it Now works as expected.
Rhino 8 SR0 2022-12-13 (Rhino WIP, 8.0.22347.14305, Git hash:master @ 70d310a6547f69edd926830eeb2cea39ff1dbf1b)
License type: Commercial, build 2022-12-13
License details: Cloud Zoo
Expires on: 2023-01-27
Windows 10 (10.0.19044 SR0.0) or greater (Physical RAM: 64Gb)
Computer platform: DESKTOP
Standard graphics configuration.
Primary display and OpenGL: NVIDIA Quadro K5000 (NVidia) Memory: 4GB, Driver date: 4-27-2022 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 473.47
> Accelerated graphics device with 4 adapter port(s)
- Windows Main Display attached to adapter port #0
- Secondary monitor attached to adapter port #1
Secondary graphics devices.
NVIDIA Quadro K600 (NVidia) Memory: 1GB, Driver date: 4-27-2022 (M-D-Y).
> Accelerated graphics device with 2 adapter port(s)
- Secondary monitor attached to adapter port #0
OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On
Graphics level being used: OpenGL 4.6 (primary GPU's maximum)
Anti-alias mode: 4x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High
Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 4-27-2022
Driver Version: 30.0.14.7347
Maximum Texture size: 16384 x 16384
Z-Buffer depth: 24 bits
Maximum Viewport size: 16384 x 16384
Total Video Memory: 4 GB
Rhino plugins that do not ship with Rhino
Rhino plugins that ship with Rhino
C:\Program Files\Rhino 8 WIP\Plug-ins\Commands.rhp "Commands" 8.0.22347.14305
C:\Program Files\Rhino 8 WIP\Plug-ins\rdk.rhp "Renderer Development Kit"
C:\Program Files\Rhino 8 WIP\Plug-ins\RhinoRenderCycles.rhp "Rhino Render" 8.0.22347.14305
C:\Program Files\Rhino 8 WIP\Plug-ins\rdk_etoui.rhp "RDK_EtoUI" 8.0.22347.14305
C:\Program Files\Rhino 8 WIP\Plug-ins\rdk_ui.rhp "Renderer Development Kit UI"
C:\Program Files\Rhino 8 WIP\Plug-ins\NamedSnapshots.rhp "Snapshots"
C:\Program Files\Rhino 8 WIP\Plug-ins\RhinoCycles.rhp "RhinoCycles" 8.0.22347.14305
C:\Program Files\Rhino 8 WIP\Plug-ins\RhinoCode\RhinoRoslyn.rhp "RhinoRoslyn" 8.0.22347.14305
C:\Program Files\Rhino 8 WIP\Plug-ins\RhinoCode\RhinoCodePlugin.rhp "RhinoCodePlugin" 8.0.22347.14305
C:\Program Files\Rhino 8 WIP\Plug-ins\RhinoCode\RhinoCPython.rhp "RhinoCPython" 8.0.22347.14305
C:\Program Files\Rhino 8 WIP\Plug-ins\Toolbars\Toolbars.rhp "Toolbars" 8.0.22347.14305
C:\Program Files\Rhino 8 WIP\Plug-ins\3dxrhino.rhp "3Dconnexion 3D Mouse"
C:\Program Files\Rhino 8 WIP\Plug-ins\Displacement.rhp "Displacement"
C:\Program Files\Rhino 8 WIP\Plug-ins\ConstraintsUI.rhp "Constraints UI" 8.0.22347.14305
C:\Program Files\Rhino 8 WIP\Plug-ins\SectionTools.rhp "SectionTools"
C:\Program Files\Rhino 8 WIP\Plug-ins\NamedPositions.rhp "Named Position"
Here is the repeatable error or bug.
-
Open WIP and create a New Rhino file (Small Objects - Inches.3dm)
-
With 4 viewports visible, select the top view, and construct a box using your mouse and the front viewport to finish the extrusion.
-
Select the cube/box with Gumball active and use the Nudge (arrow keys) to confirm that it works… And it should work as expected.
-
Now create a simple corner to corner rectangle next to the cube.
-
Select the Rectangle and in the layers panel, Right click on Layer 1, and “Change Object Layer”
-
On Layer 1, click on the Lock icon to lock Layer 1. You may need to ckick a few times as its target is small.
-
Go back to the top view and select the Cube/box… Now try the Nudge keys It should only move once. If I deselect it, then reselect it will move once again then stop.
Note: my nudge key setting does not include “Alt”
Hi Gregory -
I’m afraid this is not reproducible with those steps on my system.
I see that you are running 3 monitors. Our recommendation is that you have at least 12 GB of VRAM for doing that - your system has 5 GB and so I’m wondering if that might have something to do with this. What happens when you only have a single monitor that is connected to the K5000 GPU?
-wim
I can’t repeat this here either.
Well, there are two video cards. If @MrPelican is not running 4K monitors, the 4Gb should be largely sufficient for running 2 HD (1920 x 1080) monitors and the 1Gb card should also probably run one HD monitor sufficiently well for not-too-complex stuff.
I doubt this is the problem, but I would first disconnect the single monitor connected to the 1Gb card and just try running the two monitors (if not 4K) on the 4Gb card. If it still happens, then I suspect the problem is elsewhere.
I only have this issue when running WIP, I do not have this issue in Rhino 7 running the same monitor setup.
Also 2 the monitors are Samsung SyncMaster SA8500 and the third is a Wacom Cintiq 24HD. I will disconnect the Wacom and test again.
The monitor change made no difference.
I believe that the problem lies within the Option Setting for Nudge. When I have Nudge set to include the “Alt” key, I have no issue. When I have Nudge set to move when only the Arrow Keys are pressed I have the problem.
When I select the red surface then go to the layers panel (layer 1) to lock it. It leaves the focus of the application in the layers panel, because when I return to the top viewport to select the white surface to apply the Nudge to … Use of the nudge keys (arrow keys) move the white surface once, then it stops, but continues to move the highlighted selection (blue) in the Layers Panel.
Best regards, Gregory McCambley.
I don’t mind you having a different opinion on this, and I’ll stay clear from making up system requirements myself, but every time this comes up internally, the recommendation is 4 GB per “standard resolution” screen:
Well, yes, that makes all the difference. Thanks for that screenshot, Gregory!
RH-72275 Keyboard: Viewport focus is lost with floating Layers panel
-wim
Well, I don’t mind McNeel having a different opinion either, but when these recommendations are posted, I always put up my “second opinion” - based on years of use and also some simple math.
First, the simple math - a 4K monitor has 4x the number of pixels as a “standard resolution” monitor; all other things being equal, if 4Gb are necessary to run one standard monitor, it would then mean that one would need 16Gb VRAM to run one 4K monitor. Currently I am running two 4K monitors with one 12Gb card with no problems, so this is clearly not the case of a minimum or even average requirement.
Second, practical experience: I have a laptop with a 4K screen and a 4Gb video card and it runs fine. I also have some very old laptops with only 2Gb video cards and HD screens and they run Rhino without any video glitches.
But let’s say that OK, one should have at least 8Gb to run one 4K monitor and that my 12Gb two 4K monitor setup is “underpowered”. That still means that for a single “standard” monitor - at 1/4 the pixels of a 4K monitor, one would only need 2Gb.
1 Like
I wonder if McNeel’s “4 GB per “standard resolution” screen” occurred because that much video memory in a GPU is generally associated with sufficient processing power, rather than the amount of actual memory required.
Also it should be noted that the 4 GB is a recommendation, not a requirement as is sometime stated by McNeel representatives. A user who does not do much rendering does not need as much video memory or processing power as users who have a rendering intensive workflow.