Direct3D glitches on rendered mode

Serengeti (Rhino BETA)
,
1

Direct3D rendered viewport is creating some squares. (8x8 pixels)


Those are Rhino glitches , not video compression artifacts. When I change the object color to green, the top/above glitches are still red.
Once a geometry pass through the square, the square then behave differently, remembering the color of the geometry… :sweat_smile:

This is not a new bug here, I’ve seen this since the first time I tried Direct3D on Rhino WIP… I hoped this was going to disappear on more mature releases.

Oh, during a command prompt, or if there is something selected (even a curve/point) those glitches disappear.
More specifically, even with gumball off, if I can see the selection (yellow highlighted) on the rendered viewport the glitches disappear, as soon as the selected object is fully outside the viewport, the glitches appears again.

Edit: this seems related to Antialiasing. If set to “None” the problem disappears.

Summary

Rhino 9 SR0 2026-6-30 (Rhino 9 BETA, 9.0.26181.12303, Git hash:master @ 63db21acdecff631b4b3c30057580aaff9bf8c35)
License type: Commercial, build 2026-06-30
License details: Cloud Zoo
Expires on: 2026-08-14

Windows 10 (10.0.19045 SR0.0) or greater (Physical RAM: 32GB)
.NET 10.0.2

Computer platform: DESKTOP

Standard graphics configuration using DirectX
Primary display: AMD Radeon RX 6700 XT (AMD) Memory: 12GB, Driver date: 6-19-2026 (M-D-Y). DirectX(11)
> Accelerated graphics device with 7 adapter port(s)
- Windows Main Display attached to adapter port 0
- Secondary monitor attached to adapter port 1

Secondary graphics devices.
None found.

DirectX Settings
Safe mode: Off

OpenBLAS: OpenBLAS 0.3.30 DYNAMIC_ARCH NO_AFFINITY Zen MAX_THREADS=64.

Rhino plugins that do not ship with Rhino

Rhino plugins that ship with Rhino
C:\Program Files\Rhino 9 WIP\Plug-ins\Commands.rhp “Commands” 9.0.26181.12303
C:\Program Files\Rhino 9 WIP\Plug-ins\WebBrowser.rhp “WebBrowser”
C:\Program Files\Rhino 9 WIP\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 9 WIP\Plug-ins\RhinoScript.rhp “RhinoScript”
C:\Program Files\Rhino 9 WIP\Plug-ins\3dxRhino.9.rhp “3DxRhino.9”
C:\Program Files\Rhino 9 WIP\Plug-ins\IdleProcessor.rhp “IdleProcessor”
C:\Program Files\Rhino 9 WIP\Plug-ins\UpdatesAndStatistics\UpdatesAndStatistics.rhp “UpdatesAndStatistics” 9.0.26181.12303
C:\Program Files\Rhino 9 WIP\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 9.0.26181.12303
C:\Program Files\Rhino 9 WIP\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 9.0.26181.12303
C:\Program Files\Rhino 9 WIP\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 9 WIP\Plug-ins\MeshCommands.rhp “MeshCommands” 9.0.26181.12303
C:\Program Files\Rhino 9 WIP\Plug-ins\RhinoCycles.rhp “RhinoCycles” 9.0.26181.12303
C:\Program Files\Rhino 9 WIP\Plug-ins\Displacement.rhp “Displacement”
C:\Program Files\Rhino 9 WIP\Plug-ins\SectionTools.rhp “SectionTools”

@jeff

2

First, please test with latest Beta since there has been some churn in the area.
9.0.26195.12303 | July 14, 2026 | 700.5 MB

Can we get your Rhino SystemInfo.
Open Rhino, Type the command SystemInfo. Copy and paste the text results into your reply.

First, Get the glitches to show up again: turn on Antialiasing.

  1. Turn off shadows - Do the glitches go away?
  2. Turn off the ground plane - do the glitches go away?
  3. Set the ground plane to use a material (ie. Turn OFF shadows only option). Do the glitches go away?

Lastly, have you changed any other settings in Rendered mode settings?
Please send screen capture of your Render panel.

3

I installed the latest WIP and also done full _Reset of everything.

  1. Turn off shadows - Do the glitches go away? — no
  2. Turn off the ground plane - do the glitches go away? — no
  3. Set the ground plane to use a material (ie. Turn OFF shadows only option). Do the glitches go away? — no
  4. Lastly, have you changed any other settings in Rendered mode settings? — no

Glitches seems to pop more if the rendered viewport is 1/4 (after _4View), if perspective viewport is enlarged to full, they almost all go away.
Turning off antialiasing remove the glitches.
Antialiasing 4x have the most glitches, instead at 2x or 8x almost none.

SystemInfo

Rhino 9 SR0 2026-7-14 (Rhino 9 BETA, 9.0.26195.12303, Git hash:master @ e65c4e97d90a610a755e1fa38d13856483719a8c)
License type: Commercial, build 2026-07-14
License details: Cloud Zoo
Expires on: 2026-08-28

Windows 10 (10.0.19045 SR0.0) or greater (Physical RAM: 32GB)
.NET 10.0.2

Computer platform: DESKTOP

Standard graphics configuration using DirectX
Primary display: AMD Radeon RX 6700 XT (AMD) Memory: 12GB, Driver date: 6-19-2026 (M-D-Y). DirectX(11)
> Accelerated graphics device with 7 adapter port(s)
- Secondary monitor attached to adapter port #0
- Windows Main Display attached to adapter port #1

Secondary graphics devices.
None found.

DirectX Settings
Safe mode: Off

OpenBLAS: OpenBLAS 0.3.30 DYNAMIC_ARCH NO_AFFINITY Zen MAX_THREADS=64.

Rhino plugins that do not ship with Rhino

Rhino plugins that ship with Rhino
C:\Program Files\Rhino 9 WIP\Plug-ins\Commands.rhp “Commands” 9.0.26195.12303
C:\Program Files\Rhino 9 WIP\Plug-ins\WebBrowser.rhp “WebBrowser”
C:\Program Files\Rhino 9 WIP\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 9 WIP\Plug-ins\RhinoScript.rhp “RhinoScript”
C:\Program Files\Rhino 9 WIP\Plug-ins\3dxRhino.9.rhp “3DxRhino.9”
C:\Program Files\Rhino 9 WIP\Plug-ins\IdleProcessor.rhp “IdleProcessor”
C:\Program Files\Rhino 9 WIP\Plug-ins\UpdatesAndStatistics\UpdatesAndStatistics.rhp “UpdatesAndStatistics” 9.0.26195.12303
C:\Program Files\Rhino 9 WIP\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 9.0.26195.12303
C:\Program Files\Rhino 9 WIP\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 9.0.26195.12303
C:\Program Files\Rhino 9 WIP\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 9 WIP\Plug-ins\MeshCommands.rhp “MeshCommands” 9.0.26195.12303
C:\Program Files\Rhino 9 WIP\Plug-ins\RhinoCycles.rhp “RhinoCycles” 9.0.26195.12303
C:\Program Files\Rhino 9 WIP\Plug-ins\Displacement.rhp “Displacement”
C:\Program Files\Rhino 9 WIP\Plug-ins\SectionTools.rhp “SectionTools”

Thanks for the support!

4

Thanks @maje90

It’s odd that we’re unable to reproduce this here using any of our AMD configs… It’s also odd that this is only happening in Rendered mode…which is why Mary had you try disabling the settings above…

Digging into the code for frame buffer resolves (which is what happens when AA is on), there’s another path I’d like to eliminate as a possible cause… and that’s Gamma correction… Can you please disable all gamma correction and linear workflow settings and set gamma to 1.0 in your Rendered mode. You can do this all from the Rendering tab panel.

If you still see the artifacts, it means they’re occurring in a very specific code path, and unfortunately it also means that it’s a hardware only code path, which might require me to write my own resolve for this specific case…just to see if it “fixes” it…but it also would explain why this only happens in Rendered mode…I guess something really easy to try is to see if Arctic mode shows the same artifacts…it also uses gamma correction… I believe Rendered and Arctic modes are the only ones that use gamma correction out of the box.

If you no longer see the artifacts when gamma = 1.0, then there are 2 other code paths we need to try to isolate…which will require me to add some test/toggle commands for you to run… I will start typing on those while you check the former gamma = 1.0 path.

Thanks,

-Jeff

5

And just to clarify … You do not see these artifacts when using OpenGL, correct?

Thanks,

-J

6

Let me first say: Thank you!!
I know I’m using W10 while Rhino 9/WIP is expected to run only on W11.
Also, I’m using and AMD card, which should be supported, but I understand how the whole market is unbalanced towards Nvidia, so thanks for supporting even this lone case!

Yes, we are talking about Direct3D. (no problems on OpenGL mode)
If I set Gamma to 1.0 (or disable Gamma) the artifacts are gone! (Shadow on/off, ground plane on/off, no difference)

Arctic mode, even with Gamma 1.0, still have the artifacts.

Rendered mode, even a Gamma of 0.98 or 1.02 make the arctifacts very visible:

Rendered + Shadows + Ground plane, Direct3D AA 2x:
direct3d gamma artifacts AA 2x

Rendered + Shadows + Ground plane, Direct3D AA 4x:
direct3d gamma artifacts AA 4x

Rendered + Shadows + Ground plane, Direct3D AA 8x:
direct3d gamma artifacts AA 8x

Strange how, the bigger the viewport, the less amount of artifacts:


During the refresh of _4View I can see all the past viewport borders, this will cleanup when Rhino is minimized…

Passing a geometry in the artifacts, make them “remember” the color…
direct3dgammaartifactsmemory-ezgif.com-optimize

Operations that make the artifacts temporarly disappear:

  • during windows selection
  • during mouse panning or rotating (moving the camera)
  • during 3dmouse movement
  • selecting or sub-selecting anything visible on-viewport
    (note, the selected isocurve have to be visible)
  • the sub-selection pink preview while holding CTRL+SHIFT and mouse hovering geometries

Operations that do not make the artifact disappear:

  • selecting a curve (instead sub-selecting a segment, do make them disappear)

mixed

7

What happens if you keep the Ground Plane, but flip the camera view (camera view upside down in perspective)? Do the artefacts move to the lower half of viewport?

8

No, they always appear mostly on top of the viewport, regardless of the 3d world orientation.

9

I’m pretty sure this is a resolve issue… I just need to narrow down where. The residual artifacts are just that…residual goo that’s not getting flushed from internal buffers prior to resolving…and most likely due to something I’m doing wrong, or the drivers making wrong assumptions.

There’s one more thing I’d like you to try:

  1. Get the artifacts to appear
  2. Run the TestDynamicRange command and set Quality to HDR_FP16 and/or HDR_FP32
  3. Do the artifacts remain or disappear?

Thanks,

-Jeff

10

They remain.
(They disappear only once when the option is changed, but as soon as I move the camera, they re-appear…)

Do I have to enable/disable HDR in my Windows setting?
I usually have it disabled, I enabled it and there is no difference.

11

No, this is purely a Rhino setting that forces the use of floating point (HDR) frame buffers…doing so causes a specific code path during resolve…but since you still see the artifacts, it means it’s probably hardware/driver related on the final frame presentation pass… I’ll try to come up with some more diagnostics as soon as I can to see if we can narrow this down further…

Thanks,

-J

12

Ok I have a theory on what’s probably happening…although I’m not much of a fan of it…since it means there’s a bug in the drivers, and I hate blaming drivers.

The theory is this:

  • when AA is on, Rhino needs to “resolve” the frame buffer from multiple samples down to 1 sample, and then present it (show it on the screen).
  • If/when gamma correction is needed, Rhino then takes the resolved results and passes it through a gamma correction pass.

So when both are in play, it means Rhino is trying to read and write from the just-resolved results, and my thinking is that AMD’s color compression is getting lost in transition, and that the resolved results that are being read and written by the gamma correction are bogus… it’s why I think the results you’re getting also look like compression artifacts. There are a few articles on Navi 2.x GPUs/drivers that talk about similar problems (but none clearly discussed how or why, so I’m making a WAG here).

Given that, rather than come up with several diagnostic trial and errors options for you, I’ve written my own resolve, that also applies gamma correction in-place. Not only does this completely eliminate AMD’s resolve/read/write issue, it also makes things a bit more efficient in Rhino’s pipeline.

Once this lands in an upcoming Beta (probably early Saturday), I’d like you to download and install it… It’s not on by default, so you’ll need to run “TestMyResolve” (no pun intended :slight_smile: )

If that command does not exist, then it means you’ve downloaded too early of an installer, so grab the next one.

The command acts as a toggle, so pay attention to the command line if/when running it multiple times. When using my version of resolve, the command line will say “Using custom render target resolve…”, when using the driver’s it will say “Using hardware/driver resolve…”. My hope is that when it says “Using custom render target resolve”, you will no longer see the artifacts.

Note: This setting is not remembered across Rhino sessions…it’s just a test. If it works, I will make it a permanent (default) path for multisample resolution.

Let me know how it goes.

Thanks,

-Jeff

13

@maje90 Have you had a chance to check out the above addition in the latest Beta?

Anticipation is killing me. :slight_smile:

Thanks,

-J

14

RH-97195 is fixed in Rhino BETA

15

Sorry Jeff!
With your “next Saturday” I expected it was a week later, instead it was just the day after…
… my english sucks, sorry.

On 9.0.26209.12553, 2026-07-28.
Direct3D AA 4x , Rendered mode, shadows on, ground plane on, gamma at 2.2.

Before TestMyResolve , glitches appear with “any” viewport redraw.

After TestMyResolve, glitches does NOT appear when using Rotate (drag right click) or Pan…
…but still appear when using scroll wheel, 3dconnexion movementor or when redrawing the viewport with _4View or similar.
TestMyResolve

So… it’s a success?

Thanks!

16

Bummer… unfortunately this is still a failure… :frowning:

So what happens when the artifacts are visible and all you do is drag a selection rectangle in the view? Do not select anything, just drag out a rectangle somewhere geometry does not exist… What I’m testing for here is to see if just a simple frame update (no selection, no projection change, no camera change, etc…) clears the artifacts.

So I guess the sequence would now be:

  1. Rotate the view to clear the artifacts.
  2. Mouse wheel one click to zoom in/out slightly… I’m assuming this now will produce the artifacts.
  3. Drag out selection rectangle in a blank area in the scene (i.e. don’t actually selecting anything)

Do the artifacts disappear on step 3?

Thanks,

-Jeff

17

Also, I’m curious what happens if you completely disable/unplug your 3dConnexion device… Close Rhino, unplug the device, restart Rhino.

-J

18

Also, try to eliminate other factors… turn shadows off, turn skylight off… I just want plain rendered mode with gamma correction on… The more we can eliminate as possible causes, the closer we can get to the actual culprit.

Thanks,

-J

19

@maje90 Another thing… do you see the artifacts in a blank scene in Rendered mode? No geometry, just a plain blank scene… can you get the artifacts to appear?

-J

20

I didn’t like being the only one reporting this, so I tried to setup another machine.
I bought some week ago a 2nd hand pc for 350 bucks: i7 8700K + RX 5700XT 8GB.
I tried with a clean fresh install of both Windows 11 and Windows 10, and they both have no glitches on Rendered Viewport.
I did fast installation with Windows default GPU drivers, I’ll make more tests but it’s not worth to have you waste time on this.
I’m really sorry Jeff, it seems this specific problem only occurs on my main pc.
Thank you for the support!

What I notice today with Rhino WIP is that once I switch to rendered mode, Rhino will gradually take up ram indifinitively, the CPU with high load even when doing nothing at all:

2026-07-30 16_21_16-Untitled - Rhino BETA
2026-07-30 16_21_16-Untitled - Rhino BETA1088×661 112 KB

22GB … same behavior in my other pc…

I’ll update here if glitches happens also on the other pc or I manage to remove them on my main pc , maybe a clean Windows re-install is due…

I can reply to your last questions, tell me if you want to pursue this road… but maybe it’s not relevant anymore?