I had 1607 all the time and all was running smooth also i didn’t had issue with thea ir.
I made update to 1703 and then to 1709 and issue occures on both updates. I tried to reinstall rhino / no luck || ddu + clean instal of nvidia drivers / no luck || in my case plugins aren’t related to this issue as far as i see now ill try to roll back intel hd 530 display driver but as i see this is the same driver i had earlier (it’s date is 11/11/2016) so this is rather rhinos internal gpu handling stuff
Edit: i tried on dektop xeon / quadro / gtx / 1709 and there’s no issue - viewports are ok no fuzzynes and thea ir is on its place overlaying normal viewport
Edit2: Very intereting finding is that when i pluged in hdmi and turned off hd 530 rhino behaved on different screen as it should.
It only happens with dual GPU systems and started happening after Windows 10 Creators Update. It has to do with the changes introduced in the way accelerated surfaces are transferred from DGPU to IGPU framebuffer. It has nothing to do with Rhino itself.
A possible fix in the Rhino 5 viewport rendering pipeline would be to run a viewport refresh in every viewport each time viewports are maximized/restored.
Rhino 6 is not affected by this maybe due to changes introduced in viewport rendering pipeline.
It is up to McNeel to develop a hotfix for Rhino 5.
It also affects previous versions of Illustrator CC when the viewport is changed from GPU mode to CPU mode.
Oh indeed? It happens not only for dual gpus cause if i turn off hd 530 problem remains… Also there are different issues with gpu discovery for eg. on sys with has gtx and quadro rhino discovers half of first and half of second. Not to mention tripple gpu setup but as i see theres also no issues - cause thers no intel integrated graphics - so mainly systems which will be affected will be those with integrated intels pseudo gpus and compute devices behind them.
Turn off the DGPU and the problem will go away. It is not even a workarround but a way to confirm the bug. When you disable the IGPU you can still render OGL accelerated surfaces and those are also copied to the IGPU in VESA mode. So that is why the problem continues when you disable the IGPU.
You do not actually disable it you just move into VESA mode.
In my case a laptop with Intel (IGPU) + NVIDA (DGPU).
If I disable the NVIDIA GPU via Windows Device Manager the problem goes away.
In my case I cannot completely disable the IGPU because both LVDS and HDMI are hardwired to the IGPU.
Sadly, with most Intel laptops you are stuck with their integrated GPUs as both the internal panel (LVDS/eDP) and connectors (HDMI/DP/VGA) are hardwired to it. That means that whatever is rendered by the DGPU is always channelled through the IGPU causing this kind of trouble.
In some laptops the HDMI port is hardwired to DGPU instead of IGPU.
Also, some gaming/professional laptops offer the possibility to bypass the Intel GPU completely.