G2 Execution Stalls UCCNC Display Updating

[rv255]

I've been testing some routines after purchasing UCCNC. I found that loading code for drilling holes stalled the display update and mouse input.
I'm running a pretty new I3 with Win 10 64 bit Pro and a new UC100. An air test seems to run ok but the display has a 5-6 second delay.
It continues stalling and is very slow even when the code is not executing.
I made this simple drill of two holes using the G2 command generated in CAMBAM 1.0.
I've changed around with CV parameters with no effect.
Mach4 with the UC100 on the same machine runs this with no problems.

Any help. Thank you.

( Made using CamBam - http://www.cambam.co.uk )
( G CODE TEST CIRCLE DRILL WITH BIT CHANGES 4/14/2017 9:00:26 AM )
( T1 : 1.0 )
( T2 : 2.0 )
G21 G90 G64 G40
G0 Z3.0
( T1 : 1.0 )
T1 M6
( Drill1 )
G17
M3 S1000
G0 X-31.0 Y-11.0
G0 Z3.0
G0 X-21.5 Y-11.0
G0 Z1.0
G1 F500.0 Z0.0
G2 F1000.0 X-35.75 Y-19.2272 Z-0.3333 I-9.5 J0.0
G2 Y-2.7728 Z-0.6667 I4.75 J8.2272
G2 X-21.5 Y-11.0 Z-1.0 I4.75 J-8.2272
G2 X-35.75 Y-19.2272 Z-1.3333 I-9.5 J0.0
G2 Y-2.7728 Z-1.6667 I4.75 J8.2272
G2 X-21.5 Y-11.0 Z-2.0 I4.75 J-8.2272
G2 X-35.75 Y-19.2272 Z-2.3333 I-9.5 J0.0
G2 Y-2.7728 Z-2.6667 I4.75 J8.2272
G2 X-21.5 Y-11.0 Z-3.0 I4.75 J-8.2272
G2 X-35.75 Y-19.2272 I-9.5 J0.0
G2 Y-2.7728 I4.75 J8.2272
G2 X-21.5 Y-11.0 I4.75 J-8.2272
( Drill2 )
G0 Z3.0
( T2 : 2.0 )
T2 M6
M3 S1000
G0 X3.0 Y-12.0
G0 Z3.0
G0 X12.198 Y-12.0
G0 Z1.0
G1 F500.0 Z0.0
G2 F1000.0 X-1.599 Y-19.9657 Z-0.3333 I-9.198 J0.0
G2 Y-4.0343 Z-0.6667 I4.599 J7.9657
G2 X12.198 Y-12.0 Z-1.0 I4.599 J-7.9657
G2 X-1.599 Y-19.9657 Z-1.3333 I-9.198 J0.0
G2 Y-4.0343 Z-1.6667 I4.599 J7.9657
G2 X12.198 Y-12.0 Z-2.0 I4.599 J-7.9657
G2 X-1.599 Y-19.9657 Z-2.3333 I-9.198 J0.0
G2 Y-4.0343 Z-2.6667 I4.599 J7.9657
G2 X12.198 Y-12.0 Z-3.0 I4.599 J-7.9657
G2 X-1.599 Y-19.9657 I-9.198 J0.0
G2 Y-4.0343 I4.599 J7.9657
G2 X12.198 Y-12.0 I4.599 J-7.9657
G0 Z3.0
M5
M30

[cncdrive]

I ran your code on 2 of my computers here, one is Win 7 and the other is Win 10 and I see no problem.

You probably have the same issue (Windows updates bug) which I described in this thread:

viewtopic.php?f=4&t=509&p=3550&hilit=KB4013429#p3550

I also copy the text of interest and the solution here:

Yes, unfortunately Windows 10 Cumulative Update KB4013429 which was released a few weeks ago in March 2017 is buggy and makes some Intel HD graphics cards (So far HD 4000 is known by us to have problems with this update) to not work properly with OpenGL.
If you search the update number you can find forum posts with the same problem, e.g. on the Google Sketchup site and on other software sites which using OpenGL.
The exact problem is that the OpenGL drawing slows down the application to an unusable level.

Currently as far as we know there is no real workaround to resolve this other than to uninstall and disable the KB4013429 update.
Some instructions about how to do it is here: https://www.howtogeek.com/223864/how-to ... indows-10/

[rv255]

I'll check into your suggestions.
What is strange is that pocketing, profiling and engraving tests all worked super fine.
My Win10 just did an update a few days ago before I installed UCCNC.
Many thanks.

[cncdrive]

We do not exactly know yet how the KB4013429 Windows 10 update bug exactly effects the different systems and a few people reported a total slowdown of the UCCNC and other OpenGL applications while some others reported similar issues to yours that when lots of line segments are loaded into the OpenGL framebuffer is when they having the issue.
Arcs on the screen are built from lots of line segments because there is no arc object in OpenGL, only lines and triangles.
So, when an arc is shown then it is drawn from many small line segments.

The only thing we surely know yet is that there is a bug like this in the mentioned update which effects Intel Graphics HD drivers and OpenGL, we currently know about HD4000 cards, but maybe it effects others too, however so far we did not receive reports from users of other card models.
And the other thing we surely know is that when this issue happens is that removing the KB4013429 Windows update resolves the problem.

We have planned to look deeper into the issue and to investigate it if Microsoft will not resolve this problem, because maybe we will find a workaround to this OpenGL bug, we will see if Microsoft will not release a fix soon.

[rv255]

Hi,
Success. I uninstalled Win10 update KB4015217. Now at KB4013418 and everything is back to normal and running fine.
By the way my graphics are HD 2000 1600x900.
The computer is now in the garage and not hooked to the internet. So no more pesky updates.
Thanks very much for your help.