Skip to content
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 dual monitor setups #2

Open
boof-fo opened this issue Mar 3, 2022 · 8 comments
Open

lag on dual monitor setups #2

boof-fo opened this issue Mar 3, 2022 · 8 comments

Comments

@boof-fo
Copy link

boof-fo commented Mar 3, 2022

First of all, thanks for making this, I love it.
But when I use this screen saver on my dual monitor setup it works as expected on the primary screen, but it doesn't on the secondary one.
What happens is that toasts and toasters get stuck on the top-right side of the screen and they don't move at all. Sometimes they move but they stutter a lot (it looks like it's running at 0,5 FPS).

Device: baseline Macbook Pro 16" M1 Pro
OS: MacOS Monterey 12.2.1

@boof-fo boof-fo changed the title bug on dual monitor setups lag on dual monitor setups Mar 3, 2022
@robertventurini
Copy link
Owner

Interesting; thanks for reporting this. I will try to reproduce this when I have access to a second display to test layout on. I'm currently running on a single ultra wide monitor so I haven't been able to make this issue occur yet.

@shannonpasto
Copy link

shannonpasto commented Dec 22, 2022

Love this...lot's a good memories. I'd love to see a Simpsons or Star Trek version!!

I can report that on a Samsung 34" Ultra wide (curved) monitor (connected via USB-C) the screen saver is not smooth when compared to the in-built MBP13" (M1) display. I don't have any issues with a HP 27" (HDMI)

@robertventurini
Copy link
Owner

robertventurini commented Dec 23, 2022

Shannon, thanks for reporting. That's really curious about the Samsung 34" ultra wide monitor-- I'm running an LG 38" curved ultra wide on USB-C and haven't observed any lag issue however my machine is a 2018 intel mac. I used this screensaver as a jumping in point to start to learn SpriteKit, its entirely possible that something is not optimized with my usage, and may be manifesting on the M1 specifically at certain resolutions. Unfortunately I don't have an M1 here that I can test that hypothesis on and debug/profile in instruments right now.

boof-fo's original issue above is also surfacing on M1 hardware, that is (at least) a coincidence 🤔

@shannonpasto
Copy link

Thanks for the response. It wouldn't surprise me this is an M1 issue, we had nothing but issues (kernel panics) with those monitors and the MBP 14" M1 in Monterey when waking from sleep. The issue is mostly gone in Ventura though. Those monitors aren't the best either.

@johnrpenner
Copy link

johnrpenner commented Dec 25, 2022 via email

@dotsam
Copy link

dotsam commented Apr 25, 2023

I hadn't previously been seeing this on an M1 Air (3 displays, one native and 2 DisplayLink), but have been since installing macOS 13.3 a few weeks ago.

@boof-fo
Copy link
Author

boof-fo commented Jul 14, 2023

UPDATE: after updating to Sonoma the bug appears in a different way. The screen saver will sometimes either not render at all or it will render at the wrong monitor’s resolution (shows up in a smaller 1080p rectangle on a 1440p monitor while both are connected).

@douglaswhitaker
Copy link

I'm experiencing this issue, too. I have an M1 MBP with Ventura 13.5.1 and two external displays (two ASUS VP249 connected via HDMI to USB-C adapters). The external displays have resolution 1920x1080. The screen saver works as expected on both external displays, but on the MBP built-in display it freezes/lags substantially. Essentially a single frame is displayed (and zoomed) for a while, then it switches. Most of the time it is a black screen because there is so much empty space, but sometimes there will be static toasters/toast.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants