btw. the flicker also shows in the Rhino render interface.
To me it seems as if the redraw of the backgound color does somehow not match the custom interface color.
Windows 10.0.19042 SR0.0 or greater (Physical RAM: 32Gb)
Computer platform: LAPTOP - Plugged in [84% battery remaining]
Hybrid graphics configuration.
Primary display: Intel(R) UHD Graphics (Intel) Memory: 1GB, Driver date: 11-3-2021 (M-D-Y).
> Integrated graphics device with 4 adapter port(s)
- Windows Main Display is laptop’s integrated screen or built-in port
Primary OpenGL: NVIDIA GeForce RTX 3080 Laptop GPU (NVidia) Memory: 16GB, Driver date: 7-12-2021 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 471.41
> Integrated accelerated graphics device with 4 adapter port(s)
- Secondary monitor is laptop’s integrated screen or built-in port
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: 7-12-2021
Driver Version: 30.0.14.7141
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 16 GB
Rhino plugins that do not ship with Rhino
C:\Program Files\Next Limit\Maxwell for Rhino\maxwell_rhino.rhp “Maxwell for Rhino” 5.2.6.1
C:\Program Files\Common Files\McNeel\Rhinoceros\7.0\Plug-ins\Bella (813de3fb-18eb-405f-bfcd-b0b4d3da91fb)\21.4.1.0\bella_rhino.rhp “Bella” 21.4.1.0
I don’t think that’s the problem, I have seen this flickering with non-native rhino UI for awhile. It occurs more frequently than the screen recorder is capturing (meaning, maybe higher frame rate would catch it, but this is good enough to show the issue) here:
This was recorded on a freshly-updated rhino, with current drivers, in safe mode:
Rhino 7 SR16 2022-3-8 (Rhino 7, 7.16.22067.13001, Git hash:master @ aa7902c94c5aa33511e60d30f82b636be43bc85f)
License type: Not For Resale Lab, build 2022-03-08
License details: Cloud Zoo
Windows 10.0.22000 SR0.0 or greater (Physical RAM: 64Gb)
Computer platform: DESKTOP
Standard graphics configuration.
Primary display and OpenGL: NVIDIA Quadro P620 (NVidia) Memory: 2GB, Driver date: 2-10-2022 (M-D-Y). OpenGL Ver: (null)
> Accelerated graphics device with 4 adapter port(s)
- Windows Main Display attached to adapter port #0
OpenGL Settings
Safe mode: On
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On
Graphics level being used: OpenGL (null) (primary GPU's maximum)
Anti-alias mode: 4x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High
Vendor Name: Unknown
Render version: (null)
Shading Language: (null)
Driver Date: 2-10-2022
Driver Version: 30.0.15.1179
Maximum Texture size: n/a
Z-Buffer depth: n/a
Maximum Viewport size: n/a
Total Video Memory: 2 GB
Rhino plugins that do not ship with Rhino
Rhino plugins that ship with Rhino
C:\Program Files\Rhino 7\Plug-ins\Commands.rhp "Commands" 7.16.22067.13001
C:\Program Files\Rhino 7\Plug-ins\rdk.rhp "Renderer Development Kit"
C:\Program Files\Rhino 7\Plug-ins\RhinoRenderCycles.rhp "Rhino Render" 7.16.22067.13001
C:\Program Files\Rhino 7\Plug-ins\RhinoRender.rhp "Legacy Rhino Render"
C:\Program Files\Rhino 7\Plug-ins\rdk_ui.rhp "Renderer Development Kit UI"
C:\Program Files\Rhino 7\Plug-ins\Toolbars\Toolbars.rhp "Toolbars" 7.16.22067.13001
In order to record this:
I deleted AppData\Roaming\McNeel\Rhinoceros\7.0
started rhino in safe mode
imported a stripped down options .ini with only appearance & UI paint colors in it
cycles params are not properly shown at the bottom of the panel, so switched to legacy rhino render, in order to be able to switch back (this loads RhinoRender.rhp)
switched back to rhino render, cycles params are now shown at the bottom (this loads RhinoRenderCycles.rhp)
(and fwiw, this occurs about the same on two different machines of mine, this one, and a laptop, and also when using remote desktop with the machine in the vid)
This flickering that is described by @jdhill is due to Eto-based UI being hosted in MFC. Probably good to compare with v8 as well, since there more of the surrounding GUI is Eto-based, and most likely will no longer exhibit the flickering.
The flickering of the OP looks like MFC or Windows components hosted in Eto holder, which is in turn hosted in MFC.
For v7 it is probably something for @johnc to look into at some point, but I think he’s been quite busy lately with other tasks.
I do not know how the hosting goes in the Maxwell case, but technically on Windows the hosting is between MFC, Forms and ETO which in this case is WPF. These three components (MFC, Forms and WPF) can host each other in nested combinations.
The case shown by @jdhill is as Nathan says an Eto based UI hosted by MFC and in v8 the whole content editor is implemented in Eto so this problem should not be in v8.