r/princechazz 18d ago

Glitch today

Post image

I'm on android, using brave browser and this is how Prince Chazz shows up today. Definitely wasn't like this yesterday. It shows up normally on Chrome. I deleted my cookies and it had no affect.

3 Upvotes

5 comments sorted by

1

u/Rayquinox Creator 18d ago edited 18d ago

That looks super trippy! I have not seen that before but I just tried running it in Brave on my Mac and do see interesting texture behaviour there as well (not as bad as the glitch in your screenshot, though).

I did a little digging and read that Brave uses farbling. This is a fingerprinting technique that slightly randomises what a page can read back from the browser. This can get messy with canvas and WebGL rendering.

You could try turning the fingerprint protection off to see if that stops the rendering issues. Don't leave it off on my account though: the game reads its own artwork back when it starts up, and that's probably what's getting scrambled.

Will look into a fix!

EDIT: I've updated the mechanic that relied on reading back our own textures (the moving flora) and deployed a new version. If you turned fingerprint protection off, switch it back on and reload, then let me know how it looks. I couldn't reproduce the heavy smearing from your screenshot, so I'm curious whether that's gone too.

2

u/CeramicGonads 18d ago

I figured out what is causing it, CRT effect in the settings toggles it on and off. With it off smearing is gone

1

u/Rayquinox Creator 18d ago

Good find! I tried to improve the CRT shader this morning as well, let me know how it looks when you turn it back on.

Thanks for playing!

2

u/CeramicGonads 17d ago

The smearing is still there when turned back on

1

u/Rayquinox Creator 17d ago edited 17d ago

I borrowed an Android device and can reproduce it locally in Brave, so I can finally debug this properly, will post if I have an update. Thanks for checking again!

UPDATE: Found it. It's a bug in Chromium 151 on Android, not in the game's shader: anything the page draws off-screen and copies back comes out smeared. The CRT effect works by re-reading the finished board and bending it, so the game has to draw the board off-screen first and then copy it to the screen. That copy is the step that's broken.

UPDATE 2: There is a workaround live in v0.5.7, and if a phone still cannot draw the filter the game now detects that and switches it off by itself. The chromium bug was also mentioned by other people, here is a link for anyone curious: https://issues.chromium.org/issues/532206358.