Running latest release of 8. I have Surface Edges set to 1 in both wireframe and shaded mode. When I’m in a command and it’s time to start selecting items such as surfaces, the surface and solid edges switch to 2 or even 3, then stay like that until I’ve canceled out of the command and then move the camera. Then it goes back to 1.
Any suggestions on this? Not a huge deal overall but little annoying.
Windows 11 (10.0.26100 SR0.0) or greater (Physical RAM: 64GB)
.NET 7.0.0
Computer platform: DESKTOP
Standard graphics configuration.
Primary display and OpenGL: NVIDIA Quadro P2000 (NVidia) Memory: 5GB, Driver date: 9-10-2024 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 556.39
> Accelerated graphics device with 4 adapter port(s)
- Windows Main Display attached to adapter port #0
- Secondary monitor attached to adapter port #1
- Secondary monitor attached to adapter port #2
OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
GPU Tessellation is: 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: 9-10-2024
Driver Version: 32.0.15.5639
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 5 GB
Bump. Can someone please help with this? It’s really hurting my workflow because when the edges change to super bold while in the middle of a command, it’s extremely difficult to select things.
Can you upload a simple model that exhibits this behaviour? It is much easier to explore a problem than to attempt an accurate guess at the root cause.
Hi Jeremy, thanks for looking into this. So it seems to happen with any of my files, in wireframe and in shaded mode. As you can see in video, everything starts out fine with the polysurface edges showing up as ‘1’ thickness. As soon as I select a command, in this case DupEdge, the thickness bumps up to 2 or 3. It only reverts back after I cancel out the command and readjust the camera.
Unfortunately, without a model from you exhibiting the behaviour (as requested), there is little chance of anyone being able to spot the cause. A video shows us the problem and may clarify your explanation but gives us nothing to investigate.
With a model we can at least say whether we see the same problem, in which case it is probably a Rhino issue, or we don’t, in which case it is probably something to do with your setup.
If I’m reading this correctly, you have 3 monitors hooked up to your desktop?
Which monitor are you using for Rhino - assuming you don’t have viewports on all 3 screens?
At which resolution are you running that device and what is the recommended resolution?
-wim
Interesting. So I’m using my main display, a 42" 4K dell ultrasharp, set to 3840 x 2160 (recommended) and 150%. The next monitor is a 32" version of the 4K ultrasharp set to same resolution. Rhino exhibits the same issue on both screens.
I have the same settings (for use on a 32" 4K monitor), except for the Surface Edge Scale which I have set to 2.00 - on my system that is the default value.
Changing it to 1 doesn’t make your problem appear on my system.