Skip to content

render --aov fails after 2 frames with MSAA: msaa_for_3d turns MSAA back on under the AOV prepasses ("expects multisampled = false") #159

Open

Description

@lizTheDeveloper

raea 0.1.4, Linux x86_64 (vast.ai RTX 3090, driver 580). raea render X.tsx --at A,...,B --aov fails on the third frame:

REFUSED  frame 2402: the 3D: the GPU stopped the render (Validation error): Validation Error Caused by:
In Device::create_bind_group, label = 'aov' Texture binding 0 expects multisampled = false, but given a view with samples = 4

The first two frames come out with depth/ and motion/. The composition is a single Canvas3D with a perspective
Camera3d, Bloom, Shadows and ToneMapping, and no <AntiAliasing>.

Likely cause (from reading main).

  • engine/render/src/engine/aov.rs aov_prepasses inserts (DepthPrepass, MotionVectorPrepass, Msaa::Off) once, on
    cameras Without<MotionVectorPrepass>.
  • systems/post/src/lib.rs msaa_for_3d then sets Msaa::default() again on any non-single, non-deferred camera
    whose Msaa is Off.

So after a frame or two the prepass is multisampled, and the AOV compute's texture_depth_2d binding rejects it.
Either msaa_for_3d should leave a camera with the AOV prepasses alone, or aov_prepasses should re-assert Msaa::Off
every update.

Workaround. Put <AntiAliasing mode="fxaa" /> in the Canvas3D. Then aa is in the camera's rows, msaa_for_3d
treats the camera as single-sample, and 60 frames of --aov render.

Found while compositing render layers by depth (the layers rendered --alpha --aov, composited per frame by reverse-Z
depth).

A smaller note from the same work: a page-only layer rendered with --alpha (a semi-transparent full-frame gradient
over nothing) comes back premultiplied. Compositing it "over" as straight alpha gave 18.6 dB against the single-pass
render; as premultiplied it gave 39 dB. If the PNGs are meant to be straight, that's a second, small bug. If they're
meant to be premultiplied, the docs could say so.

Activity

  1. added 3 commits that reference this issue on Nov 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions