Thanks,
This was the only thing that came up with my searching for the issue. Glad to know that it is actually a known issue just with that compilation of the software.
Is the rendering issue considered fixed now? The page linked above at https://kicad.org/help/known-system-related-issues/ still mentions the need to use gtk2 though the launchpad bug https://bugs.launchpad.net/kicad/+bug/1339539 seems to be closed now.
I’m not sure if this is exactly the same issue since I observe this on eeschema and not pcbnew but using the archlinux package, which is now built with gtk3 and comparing it to one built with gtk2, the rendering are very different. The two screenshots below are taken at the same zoom level, both with an autodetected zoom level of 2, no antialias.
gtk2:
The page is out of date. We’ll update. Thanks for the reminder
But it seems that the rendering with gtk3 is still worse than that with gtk2. Is that a known issue?
can you check the different antialiasing options? I assume this is with accelerated graphics?
Enabling antialiasing helps for the gtk3 version but it is still not as sharp as the unantialiased gtk2 version. This is on a 4k screen and there should have been enough pixels to show the text clearly without turning on antialiasing.
And yes, I should have drivers for running opengl on the iGPU. I assume it’s using it.
… But What are your settings? I think you want to disable anti aliasing in eeschema. Or maybe it is the supersampling.
I tried to apply the antialiasing settings again to see which one improved things and noticed that nothing in the accelerated setting make any difference. It appears that I’m using fallback and I have no idea why. Switching to accelerated gives a rendering as good as what it was on gtk2.
What could be causing the fallback to be used?
The screenshot kind of looked like pixel doubling to me. Since you mention that this is 4k screen this makes me wonder if you are using 200% scale in your window manager settings.