Blurry Text (Edge, Vision, 8.1.42)

I have a Vision client running on my Linux (Debian) system.
I noticed that there is some blurry font on certain objects.

Here is an example:
screenshot

The alarm status table rows are configured identically (Noto Sans 10), but the only difference is that the blurry rows are on a main window and the "clear" text resides in a docked window.

Interestingly when the window loads, or other scripts / actions execute, or briefly changing to another window, the blurry text will very very briefly be clear only to blur again.

This issue only happens on this client - no issues running a client in Windows. I suspect this is a rendering issue with java swing on Linux but not sure if there is anything I can do about it. I've tried playing with font size and type but that doesn't seem to help too much.

Is there an "easy" tweak on the java / vision side? It's possible it could be an issue with the rendering on the graphical desktop environment I am using, so just trying to eliminate potential causes.

Upon investigation this appears to be unrelated to Ignition and everything to do with the system and how different desktop environments render text.

1 Like

If you're talking about the bottom screenshot, the text there is actually too sharp - it hasn't had any anti aliasing applied to it either at the component level (I remember there used to be an option in v7 to anti-alias text) or at the OS level. In Windows this is called Clear Type, but I'm sure there's something similar in Linux. There might also be a jvm option for it

2 Likes

Yeah, there was definitely some AA that needed to be applied. I'm still learning a bit about Linux and how the desktop environments work.

The issue was I was a using a Windows Manager only (Openbox), as opposed to a full GUI desktop package (like LXDE), on it's own as a desktop environment in order to keep everything locked down. Unfortunately this doesn't appear to use AA, where LXDE does.

I ended up using LXSession to load Openbox only, but not all the other bells and whistles that normally loads with LXDE proper (LXpanels and such). This has the benefit of loading whatever handles the AA.

A bit of a pain, there are like a dozen different settings and config files that need to be referenced and it is hard to do it piece meal without having a complete understanding of how these desktop environments work. It took a bit of trail and error.

1 Like

You could try setting these arguments in your client launcher config, as JVM overrides:

-Dawt.useSystemAAFontSettings=on
-Dswing.aatext=true

Thanks, I will give this a shot too.

Edit:
Sorry, where would these arguments be set? Is this in a config file, or directly as arguments in the Vision Client Launcher?

In the "JVM Arguments" section in the details of the configuration.

1 Like