Custom fonts render with glitches on certain Windows devices

Abierto
#740 9 comentarios 2 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
javascript

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Summary

  • Issue: Text with custom fonts appear with artifacts/glitches on certain Windows machines.
  • Phaser version(s): Phaser-CE v2.20.0
  • Live example:
  • 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:
    phaser-ce-windows

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

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

Lenguaje dominante
JavaScript
Estrellas
1.4k
Forks
485
Merge medio
1 d 2 h
PR fusionados (30 d)
9

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de phaserjs/phaser-ce

Todos los issues de phaserjs/phaser-ce

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.