Min/max waveform artefact on 2K display

[AloyseTech]

Joulescope model

JS220

UI version

1.2.2

What OS are you seeing the problem on?

Windows 11

What happened?

Waveform min/max traces have artefacts and some lines of the drawn polygon seem to converge on the waveform window center.

What was expected?

Normal min/max waveform

How to reproduce?

1. Open UI window on a 2K display
2. Start acquisition with show_min_max setting on fill1 or fill2

Extra information

If I resize the window while the acquisition is running, the artefacts only appear above a certain width. If the window is resized below ~2300px they disappear.

[mliberty1]

Can you share your monitor resolution and graphics card?

My normal machine is 3840 x 2160. However, this is always less than 2300 px.

[AloyseTech]

Monitor resolution : 2560x1440p
Graphic card : Intel Iris Xe

[mliberty1]

We have the same monitors!

I usually run at full res 3840 x 2160 with no issues.

I am guessing that this is an Intel graphics OpenGL bug. Is that the most recent Intel graphics driver for your machine?

[mliberty1]

Hopefully updating the graphics drivers helped.

If not, I have a few things to try. The first is to disable OpenGL rendering for the Waveform widget. The frame rate will definitely decrease, but it may at least render correctly. Right-click on the Waveform widget, selected Settings and then uncheck opengl like this:

This change should take effect immediately.

If this helps, the next thing is to try the software opengl renderer. Turn back on the Waveform widget opengl setting, undoing what you did previous. Then, click on Settings → Common and select software for the opengl backend, like this:

Close and restart the UI for this change to take effect.

Does this help?

[AloyseTech]

All drivers are up to date. I will try this and report back.

[mliberty1]

Also note that you have to close and restart the UI after changing the backend UI renderer.

[AloyseTech]

Disabling opengl in the settings solves the issue (but slows down the UI a lot obviously).

Re-enabling opengl and setting the rendered to software does not solve the problem. Setting it to desktop do solve the problem though. For some reason I think it was on software by default. When setting it to desktop I had the popup about #216 but no problem so far. And the UI is much more responsive.

[mliberty1]

Great to hear you have a working solution!

The dodgy Intel integrated graphics support for OpenGL has been an issue. We added those workarounds a while ago. Maybe Intel has actually fixed things? If you do run into #216, please post again!