NET to use different than default drivers (or Rendering Engine). Either width should be 1.01 (instead 1), or LineStyle.AntiAliasing= LineAntialias.None (instead of ‘Normal’).įourth: set LightningChart.

PolygonSeries.Border): no antialiased 1px line. Third: change each ‘problematic’ object (e.g. Second: disable anti-aliasing in the chart, =0. There are 4 workarounds available: Solutionsįirst: set different anti-aliasing rules to be used, 2D = LineAntiAliasingType.QLAA (in WindowsForms RenderOptions). NET users, who don’t want or could not updated graphic drivers, could mitigate the above rendering problem with a few simple steps. It is usually recomended to get drivers update from computer manufacture page/channel, but everybody could install beta drivers from here. Issue offically resolved and closed by Intel, and we could confirm that in our test starting from drivers version 31.0.101.4091 problem is not manifesting anymore. Latest update (March 31st, 2023). Intel® confirmed bug for 11th and 12th Gen. This type of line could be set for PolygonSeries.Border, Annotation.BorderLineStyle, SampleDataSeries.LineStyle, PointLineSeries.LineStyle, FreeformPointLineSeries.LineStyle etc. Whenever LightningChart is asked to render antialiased Line width=1px, the application will freeze, if it is using Iris® Xe graphic DirectX11 drivers. We detected one type of setting, which led to the above chart behavior.

Particularly, when the default Rendering Engine is used (which is based on DirectX 11), the chart could freeze, be very slow and even crash. NET users have reported us experiencing technical issues with rendering when using Intel® Arc™ or Iris® Xe Graphics.

Iris xe graphics