[1.18] Certain fonts will cause a renderer error (MesloLGM NF, Cascadia Code Nerd Font)

[ffes]

Windows Terminal version

1.18.1421.0

Windows build number

10.0.19045.2965

Other Software

oh-my-posh v16.8.0
Ubuntu 22.04.02 LTS

Steps to reproduce

• Make sure oh-my-posh is started automatically on startup
• Open a new tab
• Notice the render problems
• Press enters, type text
• Notice even more render problems
• Wait a while and see the renderer catch up

It seems impossible to create a screenshot with the snipping tool because when the focus on WT is lost, the renderer catches up immediately.

Tearing of a tab created an error the very first time, but couldn't reproduce it anymore.

Expected Behavior

No response

Actual Behavior

Various rendering issues

[zadjii-msft]

Could you share your settings.json file/?

This might be partially the font thing from #15403

[lhecker]

I'm sorry for causing the issue - We only noticed it mere hours before publishing 1.18 and I already opened a PR to fix it: #15403. If you can and don't mind, it'd be great if you could use an alternative font just for a week, because it would help us find other potential bugs you might encounter. I personally for instance like using Delugia. Otherwise, I hope we'll be able to ship a fix soon!

[zadjii-msft]

Collected notes from other threads:

Fixes:

• AtlasEngine: Fix Present() of out of bounds glyphs #15403
• AtlasEngine: Fix cursor invalidation for BackendD2D #15427
• AtlasEngine: Improve scroll and swap chain invalidation #15425

If you're experiencing this, you can

• Switch to another font temporarily. Delugia Code is apparently a bit better.
• Manually disable the Atlas engine. You can do that in the settings.json like so:

    "profiles":
    {
        "defaults":
        {
            "useAtlasEngine": false
            

  Or in the Settings UI:
  
  You need to create new tabs after making this change, or restart the application. Existing tabs will retain the text renderer they were created with.

---

@lhecker also built a Windows Terminal Preview version that integrates the previous 3 AtlasEngine bug fixes, 2 of which might be relevant here: #15403 and #15425. You can download it here: blob.hecker.io/sharex/Microsoft.WindowsTerminalPreview_1.18.1443.0_8wekyb3d8bbwe.msixbundle I'm using my own personal domain because I don't want to expose my internal work addresses. However the file is properly cryptographically signed by Microsoft.

[DennisGaida]

Confirming that the version you posted does not have the reported problems.

[withinboredom]

We only noticed it mere hours before publishing 1.18

I'm not going to lie, I didn't even have the non-preview version installed and didn't even realize I was running the preview version. This thing is so rock solid for me, I wish I had it on my Linux machine.

Keep up the excellent work!

[ryan-ambit]

I can confirm the rendering error with Nerd Font v3 (Cascadia Cove Nerd Font Mono) when using neovim with nerd font v3 symbols.

After turning off Atlas Engine, the rendering is now normal!

Nerd Font v3 was released in late April this year. So there might be more undiscovered bugs with the new utf8 characters introduced in Nerd Font v3 specs.

[ffes]

Just tried v1.18.1462.0 and indeed the problem is fixed. Thanks a lot for fixing this so quickly.

[withinboredom]

@zadjii-msft -- still seeing some differences in rendering. This is original:

This is 1.18.1462.0

I can't figure out how to give you a simple reproduction, but the easiest would be to install oh-my-zsh and go through the powerlevel10k installation wizard which does a whole bunch of interesting things to the terminal.

[zadjii-msft]

@withinboredom Mind filing a new issue? That looks like a much more minor graphical error, vs the pretty substantial issue this thread was originally tracking. Thanks!

[withinboredom]

Will do, thanks for the fast response @zadjii-msft !