Skip to content

Remove damage number outline for Linux clients#651

Open
Tiagoquix wants to merge 1 commit into
rbjaxter:masterfrom
Tiagoquix:outline-linux
Open

Remove damage number outline for Linux clients#651
Tiagoquix wants to merge 1 commit into
rbjaxter:masterfrom
Tiagoquix:outline-linux

Conversation

@Tiagoquix

Copy link
Copy Markdown
Contributor

Due to the multitude of issues that apply to fonts on Linux (see SolarLightTF2/solarlighthud-redux#10 (comment)), especially in regards to outlines and (drop) shadows, the font used for damage numbers always looks a bit off because they are not properly rendered, in comparison with its Windows counterpart. It is the same font, but something in the Linux port makes it render bad. This is especially noticeable if you zoom-in more closely, and is noticeable during gameplay where you always feel something is wrong, even by a tiny bit.

This is also the reason as to why custom crosshairs with outlines or shadows do not work as good on Linux as they do on Windows, since font shadow/outline being rendered incorrectly (since custom crosshairs are a font hack into the HUD) makes them look bad.

This PR makes it so the damage numbers do not have any shadows or outlines, but only on Linux. Looks better to the eyes, since you stop noticing the jankiness of font outlines being rendered incorrectly. A FIXME comment is also added, in order to remove it in the future.

This is nothing to do with budhud itself, but rather due to how fonts are rendered.

Other parts of the HUD do not have such perceptible jankiness, since the HUD outlines/shadows render correctly in such parts. This is one of the most jarring ones, in my opinion.

Coincidentally, the default HUD is not affect, because damage numbers in the default HUD do not have any outlines or shadows.

Default combat text (with outline) on Linux. Zoom-in to notice the jarriness.

image-8 image-9 image-10

Drop shadow variant (a test, but it got even worse, IMO)

image-11

Variant without outline or shadow (this PR)

image-5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant