I am aware this is a beta OS (unsupported by Zwift) but Zwift is unlike most of the games I have in that this mode won’t work, and there haven’t been updates to those apps specifically to enable it. As part of the changes are to enhance Bluetooth, I think it would be worth someone taking a look at it who is currently working on forthcoming updates, to see why this does work for most game apps and not Zwift.
Umm, no. After 3 years of waiting I think most of us just got tired of asking. Great that they finally got here, but kind of anticlimactic at this point. I use a lot of software and Zwift was (by a long shot) the only Intel app I had running until today.
Yeah, I’m wondering about this also. Zwift has never, from what I can tell, actually run in true full screen mode. I also use IndieVelo and as soon as I updated to Sonoma, it also started giving me the full screen notifications on start. In true full screen mode, when you move the cursor to the top of the screen, you don’t get the notification bar popping down, which seems to be a tell-tale sign that Zwift is not actually running full screen.
UPDATE SEPTEMBER 12
Rollout of this feature is complete.
If you’re using a Mac with M1+ processor, please make sure you’re using the latest version of the Zwift launcher app. One of the launcher’s functions is to detect if your Mac runs on an Intel or Apple processor, and kick off the version of the main game app your machine will support. If you’re using an outdated launcher, it will kick off the Intel build.
This. It’s been way too long. And now after all this time, native support comes, and there’s not even a bump in visual quality. That’s really the bummer. Yay shadows! Shadows should not have taken 3 YEARS!!!
The whole “no shadows” thing was a red herring. They could have turned this on a long time ago, Rosetta or not. The Apple Silicon carrot was just used as a convenient excuse to not turn on shadows for M1/M2 in High profile… Anyway, I guess it’s all water under the bridge now. In terms of visual improvements, it’s not unexpected that the native support had no improvements. The change to “Metal API” that happened months ago was where any visual improvements would have happened.
Definitely great to see MacOS running native - well done Zwift!
I’m hoping the iOS and iPadOS apps could get some attention next. I understand they’re already native, they just don’t seem to have access to the same level of detail and framerates their M-series Mac equivalents do.
The new iPhones run the latest console games from Resident Evil and Assassin’s Creed, and the iPad is getting M3 next year. Wish Zwift could support more than Basic at 30fps soon!
Definitely seeing significant improvement running Zwift on a Mac Mini M2 Pro. 4K resolution, high profile, pinned at 60fps (max screen resolution), also running OBS with a 4K webcam on the same machine.
Folks, I’m running a MacAir with M1 chip and the 8core GPU. I believe this update is now supposed to support M1 natively, if so I have an issue and am wondering if anyone else is experiencing this… The issue occurs when the system is on plugged in and not on battery power. Within 4 min of riding the thermals shoot through the roof turning the laptop into a cooktop, the only way to fix this is to dummy down the laptop by changing the battery setting while connected to conserve power, essentially cutting its legs off. However if I do this the CPU and GPU run around 59 degrees C , instead of 100!! This occurs whether I’m in Ultra or 4k and 30 or 60 fps. It makes no difference ( I output to 4k capable TV through HDMI ) . SO QUESTION FOR ZWIFT HQ , Do you know why this is occurring if Zwift is now native??
Do you see the running application name as “ZwiftAppSilicon”? (If not, update the launcher) I’m running on a 10-core M1 Pro in a MacBook Pro and not seeing a problem, but my system has a cooling fan while yours does not…
Yes it does say ZwiftAppSilicon. And yes mo fan , but you would figure that if native it should not require treating it like it was unplugged in power save mode. Obviously this has game smoothness implications. Out of curiosity what are your thermals, plugged and unplugged in power save mode. Would be interested in the delta value… THANKS FOR YOUR RESPONSE!!
I tried this a while back before native support was finally rolled out, and certain worlds (Makuri and France especially) were getting some very weird freezes and glitches. What settings are you using? I may try again now that native support is real.
These are the only available settings for me so if plugged in I must choose “low power mode” otherwise the laptop cooks. I.e. If I choose “never” the laptop cpu/gpu rises to around 100 and turns orange meaning running way to hot. As an aside this the behaviour prior to the port to native so for me I really don’t see the improvement…