Degeneration of Display Pipeline?

[erik6 (erik)]

Dimension numbers have disappeared (some remain):

After restart (and closing three other Rhinos):

This has happened before. Not sure what is going on.

SystemInfo (after restart):

Rhino 8 SR8 2024-6-11 (Rhino 8, 8.8.24163.12481, Git hash:master @ ded4d86ca901dbeaf13ee84f79b3e91b22da4880)
License type: Commercial, build 2024-06-11
License details: Cloud Zoo

Windows 11 (10.0.22631 SR0.0) or greater (Physical RAM: 96GB)
.NET 7.0.0

Computer platform: DESKTOP

Standard graphics configuration.
Primary display and OpenGL: NVIDIA GeForce RTX 4090 (NVidia) Memory: 24GB, Driver date: 5-13-2024 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 555.85
> Accelerated graphics device with 4 adapter port(s)
- Secondary monitor attached to adapter port 0
- Windows Main Display attached to adapter port 1

Secondary graphics devices.
Intel(R) UHD Graphics 770 (Intel) Memory: 128MB, Driver date: 1-18-2024 (M-D-Y).
> Integrated graphics device with 4 adapter port(s)
- There are no monitors attached to this device!

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: 5-13-2024
Driver Version: 32.0.15.5585
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 24564 MB

Rhino plugins that do not ship with Rhino
C:\Program Files\RhinoTerrain_7\Bin\RhinoDB.rhp “RhinoDB”
C:\Users\Erik\AppData\Roaming\McNeel\Rhinoceros\7.0\Plug-ins\D5Conv (e0d5e210-02f6-4ee9-a2b0-1675e225d958)\0.10.1.0001\Rhino 7\D5Conv.rhp “D5Converter for Rhino”

Rhino plugins that ship with Rhino
C:\Program Files\Rhino 8\Plug-ins\Commands.rhp “Commands” 8.8.24163.12481
C:\Program Files\Rhino 8\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 8\Plug-ins\RhinoScript.rhp “RhinoScript”
C:\Program Files\Rhino 8\Plug-ins\RhinoBonusTools.rhp “Rhino Bonus Tools”
C:\Program Files\Rhino 8\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 8.8.24163.12481
C:\Program Files\Rhino 8\Plug-ins\RhinoRender.rhp “Legacy Rhino Render”
C:\Program Files\Rhino 8\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 8.8.24163.12481
C:\Program Files\Rhino 8\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 8\Plug-ins\MeshCommands.rhp “MeshCommands” 8.8.24163.12481
C:\Program Files\Rhino 8\Plug-ins\RhinoCycles.rhp “RhinoCycles” 8.8.24163.12481
C:\Program Files\Rhino 8\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 8.8.24163.12481
C:\Program Files\Rhino 8\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 8\Plug-ins\Displacement.rhp “Displacement”
C:\Program Files\Rhino 8\Plug-ins\SectionTools.rhp “SectionTools”

[bigpiper246 (John Brock)]

• If you Zoom in and out do they show up?
• Are you Zoomed in closely on a file that covers a large area?
• Does this happen on all files or mostly this one?
• Do both good and bad dimensions belong to the same name annotation style?

[erik6 (erik)]

Nothing changed if you zoom in/out.

Or switch layout back and forth.

I can’t zoom in to find a very small dimension text. It seems to be completely gone.

They are the same Style.

Only thing that works is a restart of Rhino.

[pascal (Pascal Golay)]

Hi Erik - when this happens, please look in Properties, with no selection, and check the camera coordinates and the distance to target - are the numbers reasonable/expected?

-Pascal

[erik6 (erik)]

I think this was in the Layout. With an Active/Passive Detail. Does the Camera question apply there as well ? If Active yes, but if Passive ?

[erik6 (erik)]

Here is something similar. When I zoom in/out. The section hatch pattern somehow fails.

Why does the hatch suddenly turn red ?

I can see that the Layer colour is red.

But the section style is like in the dialog.

So it should not turn red.

tech@mcneel.com already has this file as it is behaving weirdly in many other aspects.

All the best
/Erik

[nathanletwory (Nathan 'jesterKing' Letwory)]

I’m going out on a limb here and say it is due to duplicate geometry with different settings. Like the other thread I answered in.

Materials getting mixed up

@erik6 the issue you are seeing is duplicate geometry in the same place but with different materials. Zooming in and out or looking from specific angles will change which object “wins” to be drawn “on top”. For instance in the file you shared window marked W-3.1 FK-205, which is a group. Select that and run _Isolate. Then _Ungroup. Select the window pane, you’ll see that Rhino asks you which of the two objects to select: [image] Select either and move it away so you can see the other object. …

[wim (Wim Dekeyser)]

Hi Erik -

@erik6

Why does the hatch suddenly turn red ?

It appears to only do that here when I have the viewport in the Arctic display mode and a Picture object is visible in the scene. When you hide that picture, it displays correctly here.

I’ve put this on the list as RH-82893 Display: Section Color is Wrong in Arctic
Thanks,
-wim

[erik6 (erik)]

Not that simple I think.

In this version there is only one polysurface. It still changes into red when zooming out. And as far as I know there is no red hatch or anything that can appear as solid red when zooming out.

See updated movie here:

/Erik

[nathanletwory (Nathan 'jesterKing' Letwory)]

I think you meant to post this in your other thread to my other reply Degeneration of Display Pipeline? - #7 by nathanletwory ?

[erik6 (erik)]

Sorry, you’re right.

Is it possible to move the post ?

/Erik

[nathanletwory (Nathan 'jesterKing' Letwory)]

moved

[erik6 (erik)]

Here is another one with the same behaviour:

From the same file. No duplicate materials.

/Erik

[BrianJ (Brian James)]

That looks like duplicate or coincident objects with differing materials to me. Select what’s there > use Export to save it as it’s own 3dm file > open that 3dm file and test if you still see this issue. If not, the coincident object was probably on a locked layer or locked globally.

[erik6 (erik)]

Hello Brian,

I’m 100% positive this is not caused by duplicate geometry. I opened the same file today and I can’t reproduce the problem. But I’ve checked the objects and there are no duplicates. I’m quite sure that this is caused by some kind degeneration of the OpenGL (or similar) database or something of the kind.

/Erik

[BrianJ (Brian James)]

Okay, if you see it again, please do as I explained so I can try and reproduce it. I have not seen this issue myself.

[brian (Brian Gillespie)]

RH-82893 is fixed in Rhino 8 Service Release 10