-
Notifications
You must be signed in to change notification settings - Fork 421
Workaround for macOS bug mirrored virtual screens have laggy or sometimes unresponsive mouse cursor #807
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
Comments
This is interesting. Are you using dummy mirroring? |
Yes I am, setting the monitor to mirror the dummy Also I don't know if it's because of me updating to macOS 12.5 late last week. Before that update I was running BetterDummy v1.2.2 and it was fine FYI this is a 2021 14-inch MacBook Pro with M1 Pro chip |
Seems like it's not just during text editing, the cursor would sometimes disappear on its own: https://youtu.be/wARDNJSep6A Appreciate you looking into this :) |
There was no change in this regard from 1.2.2 to 1.2.7 I think. The issue might be with macOS 12.5, but I am on Ventura beta 3 and I am not sure I can reproduce the issue the issue (sometimes it feels like I can pinpoint occasions when the mouse seems to appear a bit late if I move it super slowly but other times not, I would not have noticed any issue if I was not super aware that there might be an effect like this). I'll see if the issue is present in Ventura beta 4 or not. |
I am also having the same issue. |
I did some investigation. I am afraid I can't fix this issue as this is not something BetterDummy does but seems to be an issue related to virtual screens being mirrored. If you have an iPad, you could try if you connect it to the Mac as a Sidecar display and mirror the iPad to your main screen (not the other way around!), the same behavior should occur, even without BetterDummy running. If this is not the case, please let me know! |
Hello I have exactly same issue. Could you have a look please? Thanks! |
Yes, the issue seems to be present in Ventura beta4 as well (was not in beta3). The mouse cursor tends to disappear when entering text and takes its time to reappear. A probably related issue is that mouse shake or an increased cursor size makes the cursor icon cut into half. This seems to be a macOS bug, I am not sure if it is fixable on BetterDisplay's end. Probably the best we can do is to report it to Apple, hoping for a fix. |
Hello, I'm facing the same issue when mirroring two monitors. It started to happen after upgrading to 12.5. Any news on any potential fix for this? It's a shame because until this doesn't come I need to disable BetterDisplay. Thanks! |
Hi @pabloibanezcom - I am still investigating this. However the issue happens only with dummy mirroring. For most users native smooth scaling is a much better option (or creating specific custom HiDPI resolutions for those who do not want to purchase Pro as that functionality is available for free). |
Hi, |
Yes, of course. You should follow these instructions to set up native smooth scaling on you Apple Silicon mac: https://github.com/waydabber/BetterDisplay#how-to-unlock-scaling-and-hidpi-for-my-display Let me know if you have any issues! |
@waydabber This looks amazing! Thank you very much! |
I meant the section under |
Yes, I did that and now everything is perfectly working. This is even better than before as it has higher quality. |
Thank you @waydabber. I was in the same situation as @megasoft1978 and by enabling native smooth scaling everything looks better and without the mirroring issues. |
Yes, I confirm that the solution with native smooth scaling works like a charm! Thank you! |
Same problem here on two M1 MBPs after upgrading to macOS 12.5. I can’t use a workaround because “Allow smooth resolution scale“ is disabled in BetterDisplay settings. (it remained disabled after a reboot)
The latter is the most annoying 🤔 |
Hi @kachkaev - yes, native smooth scaling is a Pro feature so it will be disabled if the Trial expires and you don't purchase Pro. If you don't want to purchase Pro but you are using some specific resolutions and don't need too much flexibility, you can create custom resolutions for completely free by enabling Please note that the custom resolutions should have the same aspect ratio as the display and should be lower than the native resolution. |
Ah right, how could I miss that part of the text? 🤦 😅 I followed your suggestion and it did the job – big thanks for your reply and support! Looks like I don’t need a pro license but I should probably still buy one. BetterDisplay is a top-quality software, I love your attention to detail! ✨ UPD: license bought 🤩 💸 |
Oh you mean this issue is caused by the updated version of macOS, not by BetterDisplay. |
Yes, by all means, you can report it. But don't keep your hopes high - so far Apple did not exactly rush fixing any of the issues reported by the community regarding virtual screens/dummies. :) |
@waydabber do you think any of the locking stuff with screen savers could also be related here? |
You mean the inability to put the screen to sleep properly when a virtual screen is mirrored? I think that is an unrelated issue to the mouse problems. The mouse issue with us since a specific Monterey version (it was 12.5 if I remember correctly) but the screen locking issue predated that, it was always a problem on Apple Silicon. |
Yes, I almost think that it is happening but the screen hasn't refreshed similar to how the screen has not refreshed with the mouse under certain circumstances where the flipped pixel forces the screen to draw again. |
Not sure. It might be a power management issue. The mirror target display might be waiting for the mirror source display to go to sleep but the virtual screen probably does not that like expected so the target screen is not entering sleep mode either. But it's just a guess. |
Ok, I added a solution to this. Will be in the next internal pre-release. Hopefully works fine. |
|
There is a similar bug with a somewhat related solution: #3931 |
@dave-fl - this should be available in the latest internal pre-release (enable under Settings/Applications/Update). Please let me know if this works. Thanks! :) |
@waydabber So far so good. Thank you! |
@dave-fl - saw your comment about CPU use - it was removed so I guess wasn't relevant after all. Just want to note the solution should not add any serious CPU overhead (will add some of course but it shouldn't be significant). |
@waydabber I removed it because it's not relevant and yes I agree it's definitely minimal. It has to be there because the mouse has to be tracked at all times as it can lock up at any area and any time on the virtual screen. Things are working really well. I think people will be happy with this (I know I am). |
Thanks @dave-fl for the feedback! I released a proper v3.3.1 pre-release with this now. If things turn out ok with some of the other changes as well, I'll do a stable v3.3.2 release. |
Thanks @waydabber, thanks @dave-fl I downloaded the internal and now also the pre-release and everything is working smoothly. No more mouse stuck or disappearing 🙏 |
Looking forward to trying this when I get home. My workaround was to have a video playing in the corner of the screen. Thanks @waydabber! |
Uh oh!
There was an error while loading. Please reload this page.
Hi! I'm currently using BetterDisplay with a Dell S3220DGF, and had this curious problem where the mouse cursor doesn't show up immediately after mouse movement after it normally disappears during typing.
Illustration here: https://youtu.be/-mJYMJAfsEo. I immediately started moving the mouse after typing a few letters but the cursor only shows up after a small delay, meaning I couldn't find the cursor for a brief moment.
However, when I try to do screen recording using shift+command+5, the recording did not pick up this issue and the cursor appeared immediately, despite the fact that I'm seeing the delay on the screen.
Comparing to directly connecting without using BetterDisplay, the mouse cursor appears immediately when I move the mouse: https://youtu.be/pnAjhbmxhF0
The text was updated successfully, but these errors were encountered: