Fonts appear blurry on macOS Big Sur.
on the right side is iTerm2, on the left is Neovide

I noticed this too. Its bit hard to work with this blur.
Same on me. Also the icon not working.

I have the same issue. It looks like there's more discussion here: https://github.com/Kethku/neovide/issues/455
Wait, is that the same issue? The screen caps above look like a font hinting/subpixel rendering issue rather than a resolution problem.
Ah sorry, it's my mistake then! I had the resolution issue (solved by switching to the OpenGL branch) not the font rendering issue.
no problem :)
Same issue here, Windows 10, Version 10.0.19042 Build 19042.
The top is neovim in Windows Terminal, bottom is Neovide

I have exactly the same thing as @JSchrtke, 100% identical problem. However it appears only on some files while on others it's fine. Markdown files with a lot of text do it while something like init.vim does not.
I have Neovide 0.7.0 (built 6 days ago) on Windows 10 (20H2) build 19042.
This is from the openGL build for macOS, I built it just a few minutes back

(neovide on the left)
According to this issue: https://github.com/Kethku/neovide/pull/502, sub pixel was merged into openGL a while back but it still looks as it did earlier. Proper subpixel rendering (with thin strokes enabled) is on the right, theres a big difference
@shaunsingh I've been fighting trying to fix this using the subpixel settings for a while now I believe subpixel font rendering is at least somewhat working, but the positioning of the rendered surface and or the thin stroke settings for the skia font rendering is still not quite there yet.
I'm planning on looking into this further after opengl and possibly font fallback solutions are merged.
In fact, once opengl merges, I'm going to pin this issue as its probably one of my next top priorities
Nice to see! Font fallback is definitely higher priority, but its good to know the openGL branch is stable enough to replace the Vulkan build.
Or at least it will be stable enough ;)
@Kethku why was this unpinned?
It was unpinned in favor of more urgent fixes. Don't worry I haven't forgotten
@Kethku - just FYI, I want to switch to neovide as an attempt to ditch VSCode, but this issue has been keeping me from using this.
That's super helpful to know. Like I said though, I believe the current pinned issues are blocking more people. But I will come back to this
Same here, this issue is preventing me from using neovide.
Most helpful comment
Same here, this issue is preventing me from using neovide.