I was also unlucky enough to run into the fwupd bug related to some Logitech keyboards, so had to change my keyboard to even get 17. Using journalctl to look at the logs, I see a lot of gnome-shell related errors and warnings.Īll pretty disappointing. I've now installed MATE and seeing if that works better as the gnome-shell gets sluggish enough to be almost unusable unless I reboot every few hours. I did not have these problems with 17.04 and the gnome ubuntu remix. Shutting down the single applications doesnt work consistently. I'm using the default oss graphics drivers (I have a nvidia gforce card, but not using the nvidia driver as it is not compatible with wayland). The only solution I know is to shut down the computer and restart everything fresh. on a couple of occasions 15 seconds before the lockscreen wallpaper is cleared and the password prompt appears. Now go to the Pointers tab and disable Pointer shadow. Click on Hardware and Sound and select Hardware and Devices and click on Next to run the troubleshooter. Type troubleshooting and select Troubleshooting. Under Motion, set appropriate pointer speed and enable Enhance pointer precision Under Visibility, disable Hide pointer while typing and Display pointer trail. Press the Windows + X, and click on Search. When the lock screen kicks in, after hitting a key to bring up the password prompt, there is a definite lag i.e. Type main.cpl to open Mouse Properties Go to Pointer Options. In my case, after a reboot, all is good for a while, but things slowly degrade and after a few hours, switching between virtual desktops or moving windows gets slower and slower. It does seem to be a little worse under Wayland. After I upgraded from 17.04, I've found lag/sluggish response with gnome-shell under both Wayland and Xorg. In other versions of Minecraft like Java Edition every input update arrives at the very next frame.Unfortunately, I don't think this is a Wayland only issue. This problem therefore is clearly an ingame issue that must be fixed for reducing input delays. Using the ingame framerate limiter and setting it to 10, a similar delay will be noticed between native limit and RivaTuner limit. Now it will be made easily visible that every input you do, will be delayed by 4 frames / 4 seconds. To confirm this, I used RivaTuner to set the framerate to 1 FPS. Notes: This seems to be an issue related to Vsync.Īdditional information from MCPE-169538 to aid in reproducing:Īs already mentioned in a comment of this bug, the engine for Minecraft Bedrock Edition has a fixed frame delay set which leads to noticeable input delay, more prominent the less frames are rendered. Please do fix this issue in the next beta so Windows 10 getting Render Dragon won't cause issues. I have reinstalled and updated all drivers multiple times, and tried various mice and keyboard set ups. Try swinging your view around with a mouse and you will see that your input is delayed even more than it was before this beta. Since upgrading to Windows 10, my mouse and keyboard are extremely laggy and glitchy, sometimes to the point where its almost unbearable to be able to do anything on the computer. Simply put, input lag appears to be much much worse in this new beta. This comment also provides a potential workaround for players by adjusting the V-Sync setting manually, which you might find useful. We will keep you updated as soon as we have some more news in the changelogs which are published with each update. Please be assured that we have not forgotten about this bug, and hope to have a solution that will resolve the issue for you without the need for workarounds. Update 16 June 2023: Thank you for your patience while we continue to work on a solution for this ongoing issue.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |