protonscr

Vertex explosions (spike artifacts) in Assassin's Creed Syndicate (DXVK) on Intel Iris Xe

dxvkopen intel anv
doitsujin/dxvk#5625 · opened 2026-05-09 by grm2ngo · updated 2026-05-09 · 1 comments · github
Ggrm2ngo 2026-05-09 github

System Information

  • OS: CachyOS (Arch Linux based)
  • Kernel: 7.0.3-1-cachyos
  • GPU: Intel Iris Xe Graphics (Tiger Lake GT2) [8086:9a49]
  • Desktop Environment: KDE Plasma 6.6.4 (Wayland / kwin_wayland)
  • DXVK Version: dxvk-gplasync-v2.7.1-1
    • Also reproduced on upstream DXVK v2.7.1, v2.6.2,v2.3.1
  • Wine Version: Wine 11.8 (Lutris)

Describe the Issue

When running Assassin's Creed Syndicate (DirectX 11) through DXVK on Intel Iris Xe, all human character models exhibit severe vertex corruption.

The issue appears as large colorful spikes or stretched triangles protruding from character bodies.

Observed Behavior

  • The corruption appears immediately after loading into the game world.
  • The issue is 100% reproducible.
  • The spikes flicker and shift with camera movement or character animation.
  • Environment geometry, textures, lighting, and UI render correctly.
  • Only character models appear affected.

Attempted Workarounds

The following had no effect:

  • Switching between xe and i915 kernel drivers
  • Disabling GuC (i915.enable_guc=0)
  • Clearing DXVK state cache
  • Clearing Mesa shader cache
  • Lowering all in-game graphics settings
  • Using both GPLAsync and upstream DXVK builds

Regression

Unknown.

The issue has been reproduced across multiple recent Linux distributions:

  • Fedora
  • Bazzite
  • CachyOS

Older Mesa versions have not been tested.


Additional Notes

  • The issue seems isolated to skinned/animated character meshes.
  • Static world geometry renders normally.
  • Artifact behavior resembles invalid vertex/index data or broken skinning transformations.

Attachments

dxvk.log

Image Image
Ddoitsujin maintainer 2026-05-09 github

Game is being regularly tested and generally works fine on AMD and Nvidia, good chance there's some sort of driver issue here.

Nothing extracted yet.