Created attachment 138681 [details]
With Vulkan renderer I see strange artefacts in Dota 2. Did not happen with mesa 17.
Have a look at attachment.
➜ ~ phoronix-test-suite system-info
Phoronix Test Suite v7.6.0
PROCESSOR: Intel Core i5-4570 @ 3.60GHz
Core Count: 4
Extensions: SSE 4.2 + AVX2 + AVX + RDRAND + FSGSBASE
Cache Size: 6144 KB
Scaling Driver: intel_pstate powersave
GRAPHICS: MSI AMD Radeon RX 470/480/570/580 8192MB
Display Driver: modesetting 1.19.1
Monitor: BenQ xl2411t
MOTHERBOARD: ASUS B85-PLUS
Chipset: Intel 4th Gen Core DRAM
Network: Realtek RTL8111/8168/8411
DISK: 128GB Samsung SSD 840 + 1000GB Seagate ST1000DM010-2DM1 + 1000GB Seagate ST1000DM003-1CH1
Mount Options: relatime rw space_cache ssd subvol=/ subvolid=5
Disk Scheduler: CFQ
OPERATING SYSTEM: Arch rolling
Kernel: 4.15.15-1-ARCH (x86_64)
Desktop: GNOME Shell 3.28.0
Compiler: GCC 7.3.1 20180312
What GPU do you have?
Also how do you get to the screen shown in the artifact screenshot?
An RX 480. The screen appears after queuing for a game in dota. Once the matchmaking system finds a suitable game for you, such pop-up will appear in the game for you so you can decide to either join or cancel.
Here are repro instructions on how to get to that screen in Dota without having to join a public match:
1. Go to Arcade -> Overthrow
2. Create Custom Lobby
3. Set lobby password
5. Click Start Game
Bisected it to
commit ad11fc3571e025b22d9feed80a7f499665f7a255 (refs/bisect/bad)
Author: Dave Airlie <email@example.com>
Date: Thu Jan 11 08:02:52 2018 +1000
radv: don't emit unneeded vertex state.
If the number of instances hasn't changed and we've already
emitted it, don't emit it again.
If the vertex shader is the same and the first_instance, vertex_offset
haven't changed don't emit them again.
This increases the fps in GL_vs_VK -t 1 -m -api vk from around 40
to around 60 here, it may not impact anything else.
Dieter also reported smoketest going from 1060->1200 fps.
Reviewed-by: Bas Nieuwenhuizen <firstname.lastname@example.org>
Reviewed-by: Samuel Pitoiset <email@example.com>
Tested-by: Dieter Nützel <Dieter@nuetzel-hh.de>
Signed-off-by: Dave Airlie <firstname.lastname@example.org>
(with LLVM 5)
Should be fixed with https://cgit.freedesktop.org/mesa/mesa/commit/?id=74b0b869ddd4dbd36482aa9bec3403d45396af2d
I my self probably don't have the know-how to compile & replace your patched mesa with my system's mesa to verify the fix.
Since you use Arch, it may be worth building/running
Can confirm that since mesa 18.0.1-1 the issue has been fixed for me.
Thank you for the work!