I do not have this problem on version 1.3.1
On versions 1.4.2 and 1.4.3, this problem is always present.
Enabling Anti-Aliasing helped.
The same problem is described in this topic:
And this:
I do not have this problem on version 1.3.1
On versions 1.4.2 and 1.4.3, this problem is always present.
Enabling Anti-Aliasing helped.
The same problem is described in this topic:
And this:
I do not have this problem on version 1.3.1
On versions 1.4.2 and 1.4.3, this problem is always present.
Enabling Anti-Aliasing helped.
The same problem is described in this topic:
And this: