Issue with Render/Arctic display mode in Rhino 8

Rhino
,
1

Hi! I just updated to Rhino 8 and suddenly, when I enter Rendered and Arctic display modes, the mesh I’m modeling has this weird contour effect, rather than showing up as a smooth object. I converted the mesh to a polysurface and a subD and still had this issue, so I think it’s an issue with my settings, not with the object itself. Any ideas how this happened? I’m not a Rhino expert so I’m having issues knowing how to troubleshoot this. Online research suggests that isocurve settings might be the issue, but I went into Options>General and Options>View>DisplayModes>Rendered/Arctic and turned isocurves on there, but no luck. And in the properties panel, under Properties: Object, the Isocurve Density settings are greyed out.

image
image2420×1100 780 KB

2

Are you using default Render/Arctic working display mode settings?
There is really anything else to comment on on without your SystemInfo and the 3dm file.

3

I was using the default display mode settings, but then went in and selected Show Isocurves at the recommendation of a thread I saw here. When you say “SystemInfo,” what do you need to see exactly? I’m pretty junior so I don’t know all the terminology very well yet. Unfortunately, I can’t share any files since there’s an NDA on this project.

4

“SystemInfo” is a command in Rhino since V6, that reports the computer resources Rhino is seeing.
Like any other command, you can just type it.

What happens to the display if you click the “Restore Defaults” button in the working display mode settings?

5

Here’s the systeminfo. And I restored defaults for the display mode settings, but nothing changed.

image
image1345×1542 159 KB

6

Thanks
Your SystemInfo looks reasonable.
Your Intel GPU drivers are very old, and your Nvidia drivers a a little old but not terrible. You have enough VRAM to run a single monitor and it looks like that’s what you’re doing.

I don’t see an obvious problem.
The next step will be to get a file from you that is not under NDA, but exhibits the same problem.

7

I’ll try to create a cleaned-up duplicate file, just showing the part I had in the first image, and share it in a bit. Thanks for helping!

8

I encountered the same issue. In my case, using the new push-pull from gumble triggered this bug. Looks like it’s affecting the modes with Ambient Occlusion and scene Lighting. This is how it looks like in my case:

image
image1920×1353 104 KB

Here are my system info:

image
image1004×1471 55.8 KB

I am also attaching the file to test (I emptied it due to NDA but the issue is still there in my case):
Display_Mode_BUG.3dm (599.4 KB)

I restarted both Rhino and the computer. Only solution was to create a new file and copy the contents. (the issue was present just in this rhino file).

Thanks!

9

Hi Cosmin -

When I open your file, the maximized viewport has its camera set somewhere 644 402 km away from the target.

image

Simply resetting the viewports clears this up.
-wim

1 Like