Custom fonts render with glitches on certain Windows devices
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 35/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- javascript
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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
- 主要语言
- JavaScript
- 星标
- 1.4k
- 派生
- 485
- 平均合并
- 1 天 2 小时
- 30 天内合并 PR
- 9
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
phaserjs/phaser-ce 的其他 Issue
-
Web audio stops playing in iOS 17 and 18 after refocusing可能重新可做 @samme 于 633 天前认领,目前没有进行中的 PR。 未关闭
phaserjs/phaser-ce#748 · 2 个 reaction · 已指派 1 人 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 25/100
phaserjs/phaser-ce#724 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 25/100
phaserjs/phaser-ce#711 · 1 条评论 ·
维护者通常 1 天内回复
-
bug
难度 4/5 3-5 天 新手友好度 25/100
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 20/100
phaserjs/phaser-ce#690 · 1 条评论 ·
维护者通常 1 天内回复
查看 phaserjs/phaser-ce 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 65/100
-
needs:triage
难度 1/5 1 小时以内 新手友好度 92/100
维护者通常 1 天内回复
-
fix(readme): skills.sh badge says 'resource not found' and the skills.sh link is a 404; skills.sh still lists the old name tdk-skills可能已有人在做 @bfs2021 今天认领。 未关闭area: ci area: docs badge bug chore cleanup consistency developer-experience difficulty: easy docs documentation good first issue hygiene journey: first-visit links priority: P3 skills user-journey
难度 2/5 1-3 小时 新手友好度 65/100
flisk-sh/flisk-skills#39 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
-
Bug
难度 2/5 1-3 小时 新手友好度 82/100
Ionaru/easy-markdown-editor#656 ·