Anyone seen this before or know what might this be about? Started today, yesterday all was fine. Tried flatpak update after it started, no change. The glitch depends on what is on screen.
I am on linux flatpak version (Manjaro) with AMD Radeon RX 7700 XT.
#graphics glitch (map extension bug for linux + AMD graphics) [FIXED]
1 messages · Page 1 of 1 (latest)
try to disable map edge extension
it helped Viglory just now, had the same issue you did
@stark flower is this effect what you saw?
having the same problem. fixed it by turning of map edge extension in the advanced settings
can confirm, turning off map edge extension does help. (But I'd like to have that on)
would love to too but hey its better than nothing. when i get a chance ill maybe check if a issues has been logged and if not log it
welp, @dire hemlock
graphics glitch (map extension bug)
git revert eada8b6a07c1307a4e55d24f55f4f8c6be63a0ac?
Confirmed issue on Fedora 44 [Linux kernel 7.0.8] as well
that did indeed work for now
hopefully I can turn it back on soon
@frank musk @glad stag @solemn violet @stark flower so you're all on linux, and are you perchance all on AMD?
I'm also on linux but on nvidia and had no such issue
he uses arch btw
fastfetch
steamc@cachyos-SteamConsole
OS: CachyOS x86_64
Kernel: Linux 7.0.8-1-cachyos
Uptime: 13 hours, 5 mins
Packages: 1494 (pacman)
Shell: fish 4.7.1
Display (VA3209-QHD): 2560x1440 in 32", 7]
DE: KDE Plasma 6.6.5
WM: KWin (Wayland)
WM Theme: Breeze
Theme: Breeze (Dark) [Qt], Breeze-Dark [G]
Icons: breeze-dark [Qt], breeze-dark [GTK]
Font: Noto Sans (10pt) [Qt], Noto Sans (1]
Cursor: capitaine (24px)
Terminal: alacritty 0.17.0
Terminal Font: monospace (12pt, Regular)
CPU: AMD Ryzen 5 3600 (12) @ 4.21 GHz
GPU: AMD Radeon RX 6700 XT [Discrete]
Memory: 12.56 GiB / 31.24 GiB (40%)
Disk (/): 75.41 GiB / 118.74 GiB (64%) - s
Disk (/mnt/disk2): 846.50 GiB / 915.82 Gi4
Disk (/mnt/disk3): 1.06 TiB / 1.83 TiB (54
Local IP (enp4s0): 192.168.1.197/24
Locale: cs_CZ.UTF-8

please try installign this version as custom widget
better, but not ok
and this version?
"Attempt to use invalid shader object in Finalize. Did you call :Compile() or :Initialize()"
btw did map edge extension used to work at all before this?
anyway this should be it
yes, always
Yes, the 3rd version seems to be working as expected
graphics glitch (map extension bug for linux + AMD graphics)
yes
this is wild that this is a sticker lol
it used to work perfectly for a year and a half up until yesterday lol
does this mean we can update and re-enable?
Yes, update the game and it should be good to go.