The video explains it all. None of the other overlays in the game are affected by this glitch.
~ 〉 pacman -Q | grep -iE '(nvidia|mesa|intel)' intel-gmmlib 22.8.1-1.1 intel-media-driver 25.3.4-1.1 intel-ucode 20250812-1 lib32-mesa 1:25.2.3-3 lib32-mesa-utils 9.0.0-4 lib32-nvidia-utils 580.95.05-2 lib32-opencl-nvidia 580.95.05-2 lib32-vulkan-intel 1:25.2.3-3 lib32-vulkan-mesa-device-select 1:25.2.3-3 lib32-vulkan-mesa-layers 1:25.2.3-3 libva-nvidia-driver 0.0.14-1.1 linux-cachyos-bore-nvidia-open 6.17.1-1 linux-firmware-intel 1:20250917-2 linux-firmware-nvidia 1:20250917-2 mesa 1:25.2.4-2 mesa-utils 9.0.0-7.1 nvidia-prime 1.0-5 nvidia-settings 580.82.09-2 nvidia-utils 580.95.05-2 opencl-nvidia 580.95.05-2 vulkan-intel 1:25.2.4-2 vulkan-mesa-device-select 1:25.2.4-2 vulkan-mesa-layers 1:25.2.4-2
~ 〉 lspci | grep -iE '(vga|3d)' 00:02.0 VGA compatible controller: Intel Corporation TigerLake-H GT1 [UHD Graphics] (rev 01) 01:00.0 VGA compatible controller: NVIDIA Corporation GA107M [GeForce RTX 3050 Mobile] (rev a1)
Steps to Reproduce
.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now