Bug: [v8] arctifact when rendering big polygon with offscreen coordinates in Firefox and Safari

[erikdubbelboer]

Current Behavior

The two red areas left and right are rendered using Graphics.poly/fill. With 8.0.5 the line thought though the middle wasn't there but now with 8.1.0 it is there.

Expected Behavior

The line across the screen shouldn't be there.

Steps to Reproduce

I haven't had the time to create a small reproducible case. But seeing as other polygons that are small and fully in screen work well I think it has to do with the coordinates being outside of the canvas.

Environment

• pixi.js version: 8.1.0
• Browser & Version: Firefox and Safari (line is not there in Chrome)
• OS & Version: Mac
• Running Example: https://dubbelboer.com/sillysky.html go to the Mountain Valley level

Possible Solution

No response

Additional Information

No response

[erikdubbelboer]

Firefox and Safari is because it only happens in webgl and this game has preference: 'webgpu'. Now that I removed the preference it also happens in Chrome with webgl.

[GoodBoyDigital]

thanks for clarifying @erikdubbelboer !

[GoodBoyDigital]

this looks like an artefact caused by the blur filter - would yo mind removing the blur to see if it disappears? Thank!!

[erikdubbelboer]

Yes, removing the blur filter fixes it. I'm just doing:

        const filter = new BlurFilter({
            strength: 2,
            quality: 4,
        });
        this.filters = [filter];

Where this is a Container with the Graphics in it. I also have this in other places, but there the graphics don't go out of the screen, so that seems to have something to do with it.

[GoodBoyDigital]

heya, this should be fixed in the current release - i had set the texture wrap modes to repeat in the last version. This was not a smart move - as it resulted in bleeding on filter textures. The next release, this should be back to clamp-to-edge and the issue will be resolved! Let me know! thanks!

[erikdubbelboer]

@GoodBoyDigital what do you mean with the "current release", cause v8.1.0 is 3 weeks old and still has this issue?

[erikdubbelboer]

@GoodBoyDigital the issue is still present in v8.1.1.