Render Pass Compatibility Issue

Based on the information available, I can provide some insights about your render pass chain issue, though the specific interaction between SSRPass and SSAARenderPass isn't directly covered in the provided documentation.

The issue you're experiencing where SSRPass stops working when replacing SMAAPass with SSAARenderPass likely relates to how these different anti-aliasing techniques interact with your rendering pipeline.

Possible causes:

1. Render target compatibility: SSAARenderPass might be using or modifying render targets in a way that conflicts with what SSRPass expects.

2. Rendering order: SSAARenderPass (Supersample Anti-Aliasing) works differently from SMAAPass (Subpixel Morphological Anti-Aliasing). SSAA renders the scene multiple times at higher resolution, which might interfere with the screen space reflection calculations.

3. Buffer formats: The two passes might be using incompatible buffer formats or color spaces.

Potential solutions:

1. Try adjusting the order of your passes - perhaps SSAARenderPass needs to come after SSRPass.

2. Check if SSAARenderPass has configuration options that might make it more compatible with SSRPass.

3. Consider using a different anti-aliasing technique that's more compatible with screen space reflections.

The Three.js documentation lists several renderer options including CSS2DRenderer, CSS3DRenderer, and SVGRenderer, but for your specific issue with post-processing passes, you might need to consult the Three.js examples or forums for more detailed information about pass compatibility.