Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: DropShadow with WebGPU and parent Mask is blurry #10506

Open
nerumo opened this issue May 3, 2024 · 1 comment
Open

Bug: DropShadow with WebGPU and parent Mask is blurry #10506

nerumo opened this issue May 3, 2024 · 1 comment
Assignees
Labels
🕷 Bug Verified that it’s actually a legit bug that exists in the current release.

Comments

@nerumo
Copy link

nerumo commented May 3, 2024

Current Behavior

I'm having a specific object tree structure. If I use the DropShadow and the webgpu in combination, all the rendering gets blurry. If I do the same on webgl, it works as expected.

Expected Behavior

DropShadow should render the same in webgpu as in webgl

Steps to Reproduce

Add a mask to the parent container and everything within the container gets blurry as soon as dropshadow is used (with webgpu activated).

Here's a sandbox to reproduce

https://codesandbox.io/p/sandbox/pixijs-dropshadow-tcgh2j?file=%2Fsrc%2Findex.ts%3A8%2C30

You can toggle the 'preference' in and out and see the result

Environment

  • pixi.js version: 8.1.0
  • pixi-filters version: 6.0.3
  • Browser & Version: Chrome 124
  • OS & Version: Ubuntu 24.04, Windows 11
  • Running Example: e.g. https://pixiplayground.com/

Possible Solution

No response

Additional Information

No response

@GoodBoyDigital
Copy link
Member

thanks for sharing, looks like dropshadow filter needs updating! its not actually rendering the content - just the shadow bit!

@Zyie Zyie added the 🕷 Bug Verified that it’s actually a legit bug that exists in the current release. label May 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🕷 Bug Verified that it’s actually a legit bug that exists in the current release.
Projects
None yet
Development

No branches or pull requests

4 participants