Custom fonts render with glitches on certain Windows devices
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 35/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Ferma
- Stack tecnologico
- javascript
- Ambito
- computer-graphics, frontend
Direzione di ricerca
Start by comparing the Phaser-CE JSFiddle with the Phaser 3, PixiJS 3, and vanilla JS examples on an affected Windows device in Chrome. The issue suspects BaseTexture in updateTexture and notes that calling text.updateText() avoids the glitch; investigate how Phaser-CE handles custom font text rendering and compare its behavior with the working examples. Done means identifying and fixing the cause so the text renders without missing fill chunks under the reported conditions.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Summary
- Issue: Text with custom fonts appear with artifacts/glitches on certain Windows machines.
- Phaser version(s): Phaser-CE v2.20.0
- Live example:
- Phaser-CE: https://jsfiddle.net/Akurn/u3xb4rs2/ (the only one that shows the font glitch)
- Phaser 3: https://jsfiddle.net/Akurn/58wbe6n7/
- PixiJS 3: https://jsfiddle.net/Akurn/13u602wb/
- Vanilla JS: https://jsfiddle.net/Akurn/2evyskft/
- (I need to do a test on PixiJS v2 in case its also reproducible)
- What steps produce the bug:
- View the JSFiddle on affected machines in the Chrome browser
- So far we've replicated on Dell i7 laptops with Intel Xe integrated graphics chips running either Windows 10 or 11
- Text between 10-29 px without a Stroke, seem to be affected more
- What should happen: Text should render cleanly
- What happens instead: Text renders with random chunks missing from the fill
- Screenshot:
Description
Hi all, we've been experiencing this strange text glitch when using custom fonts in Phaser-CE on some Windows machines (it's similar to these posted Chrome issues, caused by hardware rendering. And is also addressed when hardware rendering is turned off).
Even though this does appear to be a Chrome/Windows issue, the reason I'm posting it here is that I've tested this with various other Canvas 2D frameworks, and they all seem to circumvent the issue, as I only see it in Phaser-CE (yet to test PixiJS v2, but v3 is fine). Links to each version are listed above.
I plan to further investigate this issue myself when I get more time, but thought to post it here in case others have also experienced the issue, or have ideas of what it could be. Or maybe we need to replicate what other frameworks do, and patch Phaser-CE to address it.
The glitch only appears in Chrome on some Windows machines (i7 laptops with integrated Intel Xe graphics). Our company supplies these to some non-dev employees, and most or all are seeing this glitch. It does not appear on MacOS or Desktop Windows (with dedicated graphics chips). On the affected machines it doesn't matter the display drivers versions, Windows updates or Windows versions 10 or 11, all show the glitch. I suspect it's related to type of hardware, since our tested Desktops don't reproduce the issue.
The bug has been seen for over a year (since 2022). Haven't tested with other Phaser-CE or Pixi versions other than listed above.
More Symptoms
- The location of the missing chunks is inconsistent, refreshing or reloading the text object, can change the glitch locations, or even not show it
- Doesn't matter on the particular font (tested over 20 different custom fonts, both Google Fonts and custom loaded ttf)
- Larger text sizes (above 30px) don't seem to show it
- In certain conditions, the first text object doesn't have the glitch, but additional text objects can
- Changing font sizes also removes the glitch but only if the next font size is drastically different (within a few pixels, 1-4px difference, they can still be visible)
- Adding a text stroke (even very tiny like
0.0001) or rendering the text without fill, also avoids the issue - The text possibly also needs word wrapping and a new line char (
\n)
Current Workarounds
- Turning Off Hardware Rendering in Chrome prevents the issue: https://support.google.com/chrome/thread/2331445/chrome-displaying-font-problem?hl=en
- Calling
text.updateText()after instantiation, also seems to prevent the glitches (our current workaround)
Suspected issues
It could be some memory issue related to BaseTexture in updateTexture method?
I plan to investigate this more, but thought to post it here first to gather some helpful clues or additional things to check or test
- Lingua principale
- JavaScript
- Stelle
- 1.4k
- Fork
- 485
- Merge medio
- 1g 2h
- PR unite (30g)
- 9
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di phaserjs/phaser-ce
-
Web audio stops playing in iOS 17 and 18 after refocusingForse di nuovo libera @samme l’ha presa 633 giorni fa e non c’è nessuna pull request aperta. Aperta
phaserjs/phaser-ce#748 · 2 reazioni · 1 assegnatario ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 25/100
phaserjs/phaser-ce#724 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 25/100
phaserjs/phaser-ce#711 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 4/5 3-5 giorni Idoneità per principianti 25/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 20/100
phaserjs/phaser-ce#690 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di phaserjs/phaser-ce
Issue simili
-
enhancement ready
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
-
enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
DCGM/semant-demo#708 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
-
agents area: runtime automation chore cli consistency dependencies developer-experience difficulty: easy documentation enhancement good first issue help wanted hygiene json-output priority: P3 starters tests
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
I maintainer di solito rispondono entro 1 giorno
-
Client codegen: an import repeated in an impl file is emitted twice, and the browser rejects the moduleForse già presa @MalithaPrabhashana l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 64/100
jaseci-labs/jac#10756 ·
I maintainer di solito rispondono entro 1 giorno