Page 1 of 1

HUD Overlay glitch

Posted: Thu Feb 12, 2026 8:40 pm
by New_Vicious
Action
Action Version: 4.45.0 to 4.75.1
Recording Resolution: Original
Recording Mode: Game

Windows and Hardware
OS: Windows 11 25H2
Video Card: NVIDIA RTX 3060Ti
Video Driver Version: 591.86
CPU brand and model: Intel Core i5 11600K
Motherboard brand and model: Gigabyte Z590 Gaming X
Memory: 64 GB
Monitor Resolution: 2560x1440

Problem Description
Game/App Problem: World of Tanks, World of Warships and World of Warplanes
Error Type: HUD Bug
Video Editor: Vegas 23
Description: In the recorded video, there is a shadow from the HUD that is sometimes noticeable and sometimes not. It's not annoying, it only happens in those three games. So far, I haven't seen anything similar in others, and the affected versions are from 4.45.0 to 4.47.1, so right now I'm using 4.44.1 to record.

Attached screenshots

Image
Image

Re: HUD Overlay glitch

Posted: Tue Mar 03, 2026 8:19 am
by idrufous
Interesting that it only appears in the three Wargaming titles and not in other games. That makes me think the issue is engine-specific rather than hardware-related — especially on a 3060 Ti with 64GB RAM.

Re: HUD Overlay glitch

Posted: Mon Mar 09, 2026 4:37 am
by PhyllisBarlow
The "shadow" often comes from how the HUD transparency or background is rendered, try to check if the shadow persists when the HUD is hidden. And try switching to Active Desktop (Screen) recording mode. While less efficient, it captures the frame buffer differently and often bypasses HUD hooking bugs.

Re: HUD Overlay glitch

Posted: Thu Mar 19, 2026 2:17 am
by karlsinner
Likely a HUD capture conflict in World of Tanks, World of Warships, and World of Warplanes introduced in newer Action versions. Try switching capture mode or rolling back to 4.44.1 since it works correctly.

Re: HUD Overlay glitch

Posted: Tue Mar 24, 2026 1:04 am
by ernestcrosby
Thanks for the detailed report! It does sound like a version-specific HUD rendering issue with those games. Sticking with 4.44.1 for now is a good workaround—hopefully the devs can reproduce and fix it in a future update.