Bug: Hex Tower Defense - Blurry text in menus and gameplay #171

Closed
opened 2026-05-22 17:57:15 +00:00 by Zhekrom · 1 comment
Title: C# Bug: Hex Tower Defense - Blurry text in menus and gameplay
Severity: Low
Mode: Hex Tower Defense
Lesson ID / File: Hex Tower Defense (C# course game)
Environment: Browser (specify version), OS (specify version)
Date/Time: 2026-05-22

Source Code

(Not applicable � rendering/UI issue)

Steps to Reproduce

1. Launch the Hex Tower Defense game.
2. Look at the mode selection menu text.
3. Observe the text in the gameplay screen.

Expected Output

Text should be sharp, clear, and easily readable as expected in a web-based game.

Actual Output

Text appears blurry both in the mode selection menu and during gameplay, making reading somewhat difficult.

Suggested Priority

Low � Does not block gameplay, but impacts readability and overall polish.

Additional Notes

Since this is a web-based game, text rendering should be crisp. This may be a resolution, canvas scaling, or font rendering issue.


Suggestion (not part of the bug): Consider adding a tutorial or instructions explaining how to play the game. The gameplay mechanics are not intuitive, and improving the onboarding experience would make the game more enjoyable for users.

Title: C# Bug: Hex Tower Defense - Blurry text in menus and gameplay Severity: Low Mode: Hex Tower Defense Lesson ID / File: Hex Tower Defense (C# course game) Environment: Browser (specify version), OS (specify version) Date/Time: 2026-05-22 Source Code (Not applicable � rendering/UI issue) Steps to Reproduce 1. Launch the Hex Tower Defense game. 2. Look at the mode selection menu text. 3. Observe the text in the gameplay screen. Expected Output Text should be sharp, clear, and easily readable as expected in a web-based game. Actual Output Text appears blurry both in the mode selection menu and during gameplay, making reading somewhat difficult. Suggested Priority Low � Does not block gameplay, but impacts readability and overall polish. Additional Notes Since this is a web-based game, text rendering should be crisp. This may be a resolution, canvas scaling, or font rendering issue. --- **Suggestion (not part of the bug):** Consider adding a tutorial or instructions explaining how to play the game. The gameplay mechanics are not intuitive, and improving the onboarding experience would make the game more enjoyable for users.
Zhekrom changed title from C# Bug: Hex Tower Defense - Blurry text in menus and gameplay to Bug: Hex Tower Defense - Blurry text in menus and gameplay 2026-05-22 18:09:28 +00:00
Owner

Root cause identified and fixed in spikerj/spikersoft-angular#12 (auto-merge scheduled once CI passes).

Cause: The game's WebGL renderer was created without setPixelRatio, so its drawing buffer rendered at CSS-pixel resolution and the browser upscaled it to the physical (e.g. 2x) display — blurring all WebGL-rendered text. Since the whole game (mode-selection menu, HUD, and in-game labels) is drawn through this one scene, text looked soft everywhere.

Fix: The renderer now matches the device pixel ratio (capped at 2x) at creation and on resize, so the buffer is drawn at native resolution and text is crisp.

Note on the in-bug suggestion (tutorial / how-to-play onboarding): that's a worthwhile enhancement but out of scope for this rendering fix — worth tracking as a separate feature request.

Root cause identified and fixed in spikerj/spikersoft-angular#12 (auto-merge scheduled once CI passes). **Cause:** The game's WebGL renderer was created without `setPixelRatio`, so its drawing buffer rendered at CSS-pixel resolution and the browser upscaled it to the physical (e.g. 2x) display — blurring all WebGL-rendered text. Since the whole game (mode-selection menu, HUD, and in-game labels) is drawn through this one scene, text looked soft everywhere. **Fix:** The renderer now matches the device pixel ratio (capped at 2x) at creation and on resize, so the buffer is drawn at native resolution and text is crisp. Note on the in-bug suggestion (tutorial / how-to-play onboarding): that's a worthwhile enhancement but out of scope for this rendering fix — worth tracking as a separate feature request.
Sign in to join this conversation.