AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
![]() Open-source KVM software (client and server CLI binaries)Īpplication that allows streaming with Inochi2D puppets Kyocera Printing Package for many Kyocera printers (stripped of kdialog9).Ī modern load testing tool, using Go and JavaScript X11 extention protocol library for the VNC extension Reference implementation of the ZIM specification by the openZIM project. ![]() Maps are drawn from an isometric perspective. X-cursor theme inspired by macOS and based on capitaine-cursors My GPU is a dated Kepler-based Nvidia Quadro, with drivers that Nvidia no longer keeps current.« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 . Since Firefox 109 doesn’t have the same issue, it means primarily that they have been able to figure out the right combination of settings for certain thus affected GPUs, just like Google did with Chrome. When it comes to Firefox/Waterfox, I’ve just recently installed Firefox 109, for reference and comparison, and I’m not going to install 102 ESR along with it…īut there is no blur for me in Firefox 109 with ‘performance defaults’ enabled, while in Waterfox 5.1.2, I had to uncheck ‘performance defaults’ and uncheck ‘use hardware acceleration’. Interestingly enough, Microsoft has not gone through the same diligence with Edge, and I had to uncheck their ‘Use hardware acceleration’ option. While I’ve never observed this issue in any stable release of Google Chrome, it was well obvious to me from their detailed GPU-related settings that they have carefully disabled certain parts of GPU-accelerated rendering for certain GPU/drivers. I’m new to Waterfox, but I’ve known this blur for years from… Microsoft Edge!įrom what I’ve known, this has nothing to do with Windows dpi scaling and everything to do with the browser’s accelerated rendering incompatibility with certain GPUs and their drivers.
0 Comments
Read More
Leave a Reply. |