fredizzimo
fredizzimo
@ldelossa Just as a clarification, which of the montitors have good performance, and which has bad?
Just some quick updates on this. I think I have identified the problems, but I won't promise any time estimates for the fixes. There are rougly 4 different problems 1....
I optimized the rendering a bit to not call `save_layer` and the blurring functionality unless there's a transparent floating window that needs it and blurring is not disabled. Standard transparency...
I just want to say, that I'm still working on this, I didn't have that much time until now, but last weekend I did some more updates. I'm working in...
No, I'm talking about the `settings` part. If I set `compiler=clang` and `compiler.version=12` I think it should pass `COMPILER_CXX_COMPILER=clang++-12` and `COMPILER_C_COMPILER=clang-12` automatically without having to define any custom environment variables....
Yes, that makes sense, and that was basically what I assumed could be the only possible reason as well. I think the current behaviour is fine and that it's mostly...
It should still start with even when that error message is shown. I have it in Linux myself since I set `timedatectl set-local-rtc 1` to make Windows and Linux use...
Closing this, as the startup issue should be fixed. And the logger issue is just a warning with the logger, but works perfectly otherwise.
Fixed by * #2123 And some earlier fixes.
This might be fixed by https://github.com/neovide/neovide/pull/1786, but I'm not sure