{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreieecz7kvq43pzeaf4qh2eplyzfs7gz4o7btl2s2g5lvcqp3tece24",
    "uri": "at://did:plc:yrn4rbgwenb6lfhhzjegbtnc/app.bsky.feed.post/3mj2ggoyo22t2"
  },
  "path": "/t/request-support-for-the-vulkan-amd-anti-lag-extension-in-flatpak-mesa-runtime/11974#post_1",
  "publishedAt": "2026-04-08T18:35:28.000Z",
  "site": "https://discourse.flathub.org",
  "tags": [
    "AMD Anti-Lag",
    "other Vulkan layers",
    "Reddit"
  ],
  "textContent": "AMD Anti-Lag support was introduced in Mesa 25.3 via the `VK_AMD_anti_lag` extension (Vulkan layer). While this can be enabled with the `ENABLE_LAYER_MESA_ANTI_LAG=1` environment variable, it doesn’t seem to work within the Flatpak sandbox, even though the current Flatpak Mesa runtime (v25.3.5) should technically support it.\n\nIt’s possible that this specific Vulkan layer isn’t being exported or included in the Flatpak Mesa build. Could this be added or exposed similarly to how other Vulkan layers are handled in the runtime? I’ve seen a discussion on Reddit suggesting this might be the case.\n\nMany modern titles that run on Linux—such as Counter-Strike 2, Dota 2, Marvel Rivals, Arc Riders, Horizon Zero Dawn Remastered and others—support this technology. Enabling it could improve input latency for AMD users running these games via Flatpak.",
  "title": "[Request] Support for the Vulkan AMD anti-lag extension in Flatpak Mesa runtime"
}