When nesting active framebuffers, previous framebuffers appear empty when antialiasing is turned on

[davepagurek]

Most appropriate sub-area of p5.js?

• Accessibility
• Color
• Core/Environment/Rendering
• Data
• DOM
• Events
• Image
• IO
• Math
• Typography
• Utilities
• WebGL
• Build Process
• Unit Testing
• Internalization
• Friendly Errors
• Other (specify if possible)

p5.js version

1.7.0

Web browser and version

Firefox 114

Operating System

MacOS 12.5.1

Steps to reproduce this

Steps:

1. Create two framebuffers with antialiasing turned on
2. Call begin() on the first one to activate it
3. Draw something to it
4. Call begin() on the second one to activate it without deactivating the original
5. Draw the first one to the second with image()
6. Call end() on both
7. Draw the second framebuffer to the screen

The image() call does nothing when antialiasing is turned on due to the fact that we only draw the antialiased renderbuffer to the framebuffer texture when end() is called.

Snippet:

createCanvas(200, 200, WEBGL);
setAttributes({ antialias: true })
const fbo1 = createFramebuffer()
const fbo2 = createFramebuffer()

imageMode(CENTER)
noStroke()
fill(0)

fbo1.begin()
circle(0, 0, 40)

fbo2.begin()
image(fbo1, 0, 0)
fbo2.end()

image(fbo2, 30, 30)
fbo1.end()

image(fbo1, 0, 0)

With antialiasing turned on:

With antialiasing turned off (expected):

Live: https://editor.p5js.org/davepagurek/sketches/LAmO0RZ5m