iScreensaver has been updated to version 6.8.4.1356
iScreensaver version 6.8.4 has a number of bug-fixes and improvements, including several bugs that could cause playback failure on multi-monitor macOS Apple Silicon / M1 systems or the macOS Ventura 13.0 beta. Authors who are building screensavers that may be encountering any of these issues should update, re-build, and re-distribute their screensavers.
Release Notes
iScreensaver version 6.8.4 has a number of bug-fixes and improvements, including several bugs that could cause playback failure on multi-monitor macOS Apple Silicon / M1 systems or the macOS Ventura 13.0 beta. Authors who are building screensavers that may be encountering any of these issues should update, re-build, and re-distribute their screensavers.
Release Notes
We are pleased to announce the release of iScreensaver version 6 which supports macOS 10.11 (El Capitan) through 11 (Big Sur) and Windows 7 through 10. Read about Version 6
macOS Catalina Security Update 2021-007 iScreensaver and WebGL
It appears that the recent update to macOS 10.15.7 Catalina (Security Update 2021-007, released on 25 October 2021) causes WebGL to fail on certain Macintosh models. This affects all websites that use WebGL. as well as applications that use WebKit.
See for example:
- It appears that Mid-2012 Macbook Pros running Catalina have ...https://www.reddit.com › apple › comments › it_appear...
- 2021-007 Security Update Catalina causes - Apple Support ...https://discussions.apple.com › ... › MacBook Pro
Since iScreensaver uses WebKit and WebGL internally, this also affects iScreensaver.
We are following the issues and will report back here if there is an update to fix the problem.
Comments
Update: we are seeing this issue on a 2012 MacBook Pro. The problem exists with Safari 14.1 as well as Safari 15.1.
The last time a software update broke functions like this ( see https://iscreensaver.com/forum/discussion/541/solved-security-update-2020-005-breaks-swift-based-screensavers#latest ) Apple released another update to fix the problem, and they had the fix ready in about one week.
We hope and expect something similar will happen soon, and will update this thread once we know more.