-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lag on 4k display #149
Comments
I'm not super experienced with this repo as of yet nor do I have a 4k display,
Test with you settings in init.vim set to:
Is there still lag? |
@dseeni I got around to doing what you suggested right now, and I must say it is a big improvement over the previous state (lag is gone 90%). still get it while scrolling through files, but not at first. if I keep 'j' pressed to scroll down, it starts just fine (nice and smooth while on the first page), then gradually becomes slower when it scrolls into the next page of text. |
Nice, glad that helped.
For the nvui config
Using frameless set through the .ini file and turning off vsync seems to help for me. The rest of the stuff is just me trying to reduce latency as much as possible. I seem to get the most performance when I set those things.. (older OS though). In terms of nvim performance |
Hello devs,
I have just tried this amazing frontend for neovim and I must say, I am impressed with the quality.
That being said, the only downside is that it is extremely laggy on a 4k display. I cand easily reproduce this by shrinking down the nvui window and it works as expected and is fast, so I know for syre the resolution is the problem.
I have encountered this problem when trying neovide as well (see: neovide/neovide#1299) and initially thought it was a problem related to their implementation, but now I am not so sure, because it might be something deeper than the UI. The only frontend that has fast performance for me on a 4k display up until now is nvim-qt.
Could we maybe somehow coordinate between these three (your project, neovide and nvim-qt) to try and find a solution to this?
The text was updated successfully, but these errors were encountered: