Issues while upgrading from PIXI 6.5.5 to 7.3.2.

[pongstylin]

First of all, yes, I completely uninstalled PIXI before installing the newer version. I also looked at the v7 migration guide and all the release changes between here and there. I fixed many issues, but this is one that I'm struggling the most with. Here's a screenshot of a before (top) and after (bottom). What you are seeing is the results of using PIXI / WebGL to create some images / avatars and then extract them so that they can be displayed in IMG elements on a web page. Each avatar is composed of multiple layers and semi-transparency. I make use of ColorMatrixFilter and tinting. So far, I've noticed that if I omit a ColorMatrixFilter that applied "brightness" to the whole avatar, then those pastel red circles under each avatar is fixed.

Any suggestions on what I should try or look at?

[pongstylin]

Simplified the problem down to a single sprite without tint that gets extracted into an image. With a brightness ColorMatrixFilter, it looks like the left, and looks like the right without. Still haven't figured out why.

const lightFilter = new PIXI.filters.ColorMatrixFilter();
lightFilter.brightness(1.25);
sprite.filters = [ lightFilter ];
const imageSource = renderer.extract.canvas(sprite).toDataURL('image/png');

P.S. I can now confirm that the issue does not exist in 6.5.10, but does in 7.0.0 (as well as 7.3.2). Perhaps it is a bug?

[pongstylin]

More certain than ever that it is a bug. Here's another screenshot where we see the Poison Wisp in both WebGL and Canvas contexts (there are 2 canvas HTML elements on the page). It has similar effects to that white circle we were looking at before. That is, it has a gradient sprites layered behind and in front of it (granting the creature a "glow"). These gradient sprites are just as distorted as the white circle. But notice that the WebGL context (right) looks clean while the Canvas context (left) looks distorted. And the avatar extraction examples above was using canvas to perform the extraction. So the bug may be specific to the canvas context.