Arctic render problem in details

Rhino Rhino for Windows
1

Hi! Our office is having problems with some ambient occlusion details. Its creating this weird layered effect on the models on various parts and not others. The two angled parts in this view should look the same (one is flat on to the camera and one is at an angle if that means anything). Its happening sporadically, if I make a new detail of the same view it does not seem to be there, but I’m not sure what’s causing it.

Its a big problem, as it makes arctic mode unusable for my draftings at the moment.
Any ideas how I could fix this? Thanks!

image
image1672×597 65.7 KB

2

Maybe let’s start with your Rhino SystemInfo details?

Do all files have this problem?
Have you modified the Arctic working display mode settings?

Thanks

3

Hello!

This is in default arctic mode, and the issue also carried over into 2 other custom view modes that use ambient occlusion. No issues on render views without ambient occlusion. Attached is a file with the issue you can see in paper space.

I tried the file on a couple other peoples computers and had the same issue.

I deleted the detail and made a new one which did not have the problem, but it seems to crop up randomly.

AO_RenderProblem.3dm (6.4 MB)

Here’s my info:

Rhino 7 SR8 2021-6-30 (Rhino 7, 7.8.21181.05001, Git hash:master @ dd41d5edfa591ef81b3f34039b4e3ae5cfe59fd1)
License type: Commercial, build 2021-06-30
License details: Cloud Zoo

Windows 10.0.19042 SR0.0 or greater (Physical RAM: 64Gb)

Computer platform: DESKTOP

Standard graphics configuration.
Primary display and OpenGL: NVIDIA GeForce RTX 2070 SUPER (NVidia) Memory: 8GB, Driver date: 9-30-2020 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 456.71
> Accelerated graphics device with 4 adapter port(s)
- Windows Main Display attached to adapter port #0
- Secondary monitor attached to adapter port #1

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: 8x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High

Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 9-30-2020
Driver Version: 27.21.14.5671
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 8 GB

Rhino plugins that do not ship with Rhino
C:\Program Files\Badger 1.0 (64-bit)\Badger.10.v60.x64.rhp “Badger”
C:\Users\Nick_Work\AppData\Roaming\McNeel\Rhinoceros\packages\7.0\EleFront\4.2.2\ElefrontProperties.rhp “ElefrontProperties” 1.0.0.0

Rhino plugins that ship with Rhino
C:\Program Files\Rhino 7\Plug-ins\SolidTools.rhp “SolidTools”
C:\Program Files\Rhino 7\Plug-ins\Commands.rhp “Commands” 7.8.21181.5001
C:\Program Files\Rhino 7\Plug-ins\WebBrowser.rhp “WebBrowser”
C:\Program Files\Rhino 7\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 7\Plug-ins\RhinoScript.rhp “RhinoScript”
C:\Program Files\Rhino 7\Plug-ins\RPC.rhp “RPC”
C:\Program Files\Rhino 7\Plug-ins\RhinoBonusTools.rhp “Rhino Bonus Tools”
C:\Program Files\Rhino 7\Plug-ins\RhinoLabsTools.rhp “Rhino Labs Tools”
C:\Program Files\Rhino 7\Plug-ins\IdleProcessor.rhp “IdleProcessor”
C:\Program Files\Rhino 7\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 7.8.21181.5001
C:\Program Files\Rhino 7\Plug-ins\RhinoRender.rhp “Legacy Rhino Render”
C:\Program Files\Rhino 7\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 7.8.21181.5001
C:\Program Files\Rhino 7\Plug-ins\rdk_ui.rhp “Renderer Development Kit UI”
C:\Program Files\Rhino 7\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 7\Plug-ins\Alerter.rhp “Alerter”
C:\Program Files\Rhino 7\Plug-ins\IronPython\RhinoDLR_Python.rhp “IronPython” 7.8.21181.5001
C:\Program Files\Rhino 7\Plug-ins\RhinoCycles.rhp “RhinoCycles” 7.8.21181.5001
C:\Program Files\Rhino 7\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 7.8.21181.5001
C:\Program Files\Rhino 7\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 7\Plug-ins\BlockEdit.rhp “BlockEdit” 7.8.21181.5001
C:\Program Files\Rhino 7\Plug-ins\Displacement.rhp “Displacement”
C:\Program Files\Rhino 7\Plug-ins\NamedPositions.rhp “Named Position”

4

Your SystemInfo looks fine to me.
I have no idea what the “Badger” plugin is.
If it’s a display related tool, maybe try temporarily disabling it to see if that helps.

Is the geometry shown these Details a long way from the 0,0 World coordinate origin?

5

Nope, its close to the origin. the 3 other computers I tried it on did not have badger installed so I dont think thats it. Did you try the file on your end?

6

Hello- I see this as well, I do not yet see why it is happening…

-Pascal

7

I did notice the ones on the left that display correctly are Groups, and the goofy one is a Block instance. I don’t understand why that would matter.

This will probably need a developer like @stevebaer or @jeff to understand it.

8

Ya, I assumed the blocks might be an issue, but it did not seem to resolve after exploding the blocks like some issues in the past did. Also, the grouped ones that rendered properly are the same block, grouped. The ones that looked ok were parallel to the camera if that makes a difference.

9

My guess is this is a resolution thing - not the screen but the available steps in the arctic shading. The camera frustum is very very long in this view:

image

Making those numbers more ‘normal’ cleans up the display:

image
image491×518 6.61 KB

I turned the camera on for that detail (F6), unlocked the detail and moved the camera closer to the target in the Top view… question is, how did it get this way?

-Pascal

2 Likes
10

Interesting! Im not sure how that could have happened to the camera, all I did with that detail was create a detail, add a clipping plane and pan around a bit, it was never in a perspective view. Im not sure how the camera would have moved in the x direction away from the object.

So it seems like a quick work around would be to just set the crazy camera value down to 0 in the camera properties. At least that seemed to fix it, that wouldn’t mess with any of the parallel projection right? It should still be an accurate orthographic view?

Thanks Pascal!

11

As long as the change does not affect the camera direction, I think setting the number directly is probably fine.

-Pascal

12

Hello

I have a similar display problem. When I change the value in my camera settings this sorts out the problem. But as soon as I pan around my drawing layout the problem reappears

13

Hi -

Please post the result of the Rhino SystemInfo command and a simple 3dm file that shows this behavior on your system.
-wim

14

Hi, I am having the same issue. Same as many of us Rhino users in the office.
Viewport camera keeps moving to an absurd location and giving me these face errors like the ones sent here. I re-installed Rhino 7 and still have the same issue.
I had to gave up on it, so now I’m using Rhino 6 again.
Do we know what’s going on?
Thanks

15

@shirahockman and @contato3 - If you can find a way to reproduce this issue it would be very helpful.

@shirahockman From what you wrote, it looks like you can reproduce the issue by panning. Can you send us the model and give us exact instructions for how to reproduce?