fix(renderer): Only apply barriers on drawGoup boundaries (#12347) 31aa875e47

csmartdalton · csmartdalton · commit 2a78c966fbd7 · 2026-04-30T02:14:47.000Z
We caught a bug where draws with multiple subpasses were being
interleaved together like this:

  - drawA, subpass0
  - dstBlendBarrier (because drawB has a dstBlend)
  - drawB, subpass0
  - drawA, subpass1
  - drawB, subpass1

This was a problem because drawA was geting a dstBlend barrier between
subpasses. When dstBlend is implemented as a texture copy, it interrupts
the render pass and resolves MSAA, causing the MSAA data to be lost for
the next subpass.

Since drawA and drawB don't overlap, the correct solution to only apply
barriers on the first batch of a drawGroup:

  - dstBlendBarrier (because drawB has a dstBlend)
  - drawA, subpass0
  - drawB, subpass0
  - drawA, subpass1
  - drawB, subpass1
diff --git a/.rive_head b/.rive_head
@@ -1 +1 @@
-d2cf8f885bfcfa10bba902959788c4e6d36ab974
+31aa875e47991b346f031fdef5bafd76f19e04f2
diff --git a/submodules/rive-runtime b/submodules/rive-runtime
@@ -1 +1 @@
-Subproject commit 3e00fa5e232a45ca42b32b0bba887c1965bad214
+Subproject commit 69130e2970a3b37cf09b59d97ec036cb7acd0888

Original file line number	Diff line number	Diff line change
`@@ -1 +1 @@`
`1`		`-d2cf8f885bfcfa10bba902959788c4e6d36ab974`
	`1`	`+31aa875e47991b346f031fdef5bafd76f19e04f2`