Pulsing Border shader glitch on Nvidia

[fredm00n]

Hi there!

I noticed the pulsing shader renders a different output on macOS and Windows/Nvidia

Attaching a screenshot of the same shader under both environments. Seems to be related to the Scale setting only, the others are fine!

Hope this helps
fred

Windows with Nvidia 3060 Ti

macOS

[uuuulala]

Suuuper helpful, thank you!
I don’t have any device where it reproduces, unfortunately, so I’ll need to try fixing it blindly. If you have time to help with testing, that would be awesome

Could you let me know:
a) if you see the same issue if you open https://shaders.paper.design/pulsing-border on Windows?
b) if that colored cross responds to the roundness parameter?

Thanks again for reporting!

[fredm00n]

Happy to help! This is what I see on the URL you shared:

Roundness does not affect the glitch:

However, Scale + Rotation + Offset settings are the only one affecting it:

Here is a quick video recording too:
https://github.com/user-attachments/assets/7cf531ae-d8c1-4deb-a49e-ff797f4c15ab

Please note my Nvidia drivers are up to date 😊

Anything else you want me to try feel free to let me know.

[uuuulala]

Alright, that narrows it down!

We need to check if that shapes still appear with default parameters and low scale.

• test1 - I guess it's still there but let's test anyway
• test2 - this should work as I'm applying the circular mask on top of everything
• if test2 looks good: test3 - does it look good on other ratio? And if you resize the window? Do you see any cuts if you set smoke=1?

[fredm00n]

test1 - yes still there

test2 - looks great!

test3 - looks great too, even when resizing the window and adjusting smoke or other settings.

Well done! Seems entirely fixed on my end.

[uuuulala]

Great! Thanks for checking, I just merged the fix.
Closing the issue but we have another update coming for PulsingBorder (better control over the shape border shape, improved antialiasing, etc) - stay tuned!

[fredm00n]

Hi @uuuulala – apologies for reopening this but, is the fix now pushed to the main branch and npm package? I'm importing @paper-design/shaders-react and a client of mine is still noticing an issue with it.

Thanks again for your help!

[uuuulala]

Let's see, I merged it to main Aug 29th and published the new version on npm Sept 1st (log)

Can you please double-check if you're using the version 0.0.47? Another good test is to check how it looks for you on shaders.paper.design/pulsing-border

[fredm00n]

Thanks @uuuulala - I see the issue now: a new glitch appeared which is why I was confused.

See a new video recording attached. Happens only on my Windows/Nvidia setup. Not on macOS!

As you can see, when the component is stretched in width, a new artifact appears in the middle. That's exactly where the previous glitch would sometimes be located too.

Recording.2025-09-10.110459.mp4

Anything you need me to help with, let me know!

Many thanks for your help with this
fred

[uuuulala]

Hey Fred!

I can't figure what it can be tbh. We're going to release a big update for this specific effect soon anyway, I'm wondering if it's better to publish the update first and check if this bug is still there.

Hope it's not too much of a problem on your end, let's get back to it in a bit

[fredm00n]

No problem, thanks for letting me know. Looking forward to the new release!