Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Having problems running some games on macbook chrome and safari, M1 Max chip

A topic by i_like_snacks created 77 days ago Views: 222 Replies: 12
Viewing posts 1 to 6
Submitted (4 edits)

Triple-edit: A chrome update broke some games for macOS. An upcoming chrome update should fix it, or use the current chrome dev build.

Thanks graphific for identifying and flagging the new issue on github, as it goes beyond the old macOS HTML5 WebGL2 incompatability problems. 

Sorry that I can't play some of y'all's games :(

A game I made last month used a simple shader to blur the background when the pause menu is up. Now it breaks when you hit pause, on macOS Chrome, and on Safari it ran the first time but with no sound (?), and I can't get it to start running a second time no matter how many times I refresh, even restarting the browser. However, I did not test it on safari last month. This is an issue that probably affects lots of games. I'm about to push an update to mine to simply remove the shader. 


Double-edit: mystery solved, apparently Godot 4's web exports are not macOS compatible. I did not know that. I thought Godot could export for the web in general, and I wish I understood how to avoid the problems that break games for mac, because I've made 6 games in Godot 4 in the past month and all have run fine on the web on my macbook, and most other Godot games seem to as well, and I am confused. So any insight into that would be appreciated.

Original Edit: actually, I'm starting to wonder if there's some sort of memory leak with certain ways lighting is rendered in these lighting-heavy games, that the macbook gpu is particularly susceptible to. Can someone else with a macbook with an M1 Max chip report on whether the games linked below are playable?

(As this is a Godot-specific jam, I figure that if there's a very specific memory leak issue with lighting, it might either be a known issue or useful to hunt it down? Or maybe this really is just a Me problem.)


Original post:

I'm starting to think this is a Me problem because I've come across three games in this jam that don't work for me on my macbook.

Most games work fine, and I've never had any of these problems running games embedded in itch pages before. Updating and restarting my browsers didn't help, restarting my computer didn't help, my computer seems to have plenty of space, but browser stuff can be inscrutable so I'd appreciate any other suggestions.

Web search suggests it could have to do with a memory leak, but is that a me problem that I can fix by doing anything? The games work for others and no one else is reporting having the same problems.

Here are examples!

https://ziblo.itch.io/ducks-at-dawn

This beautiful game loads on chrome with fireflies flying around. However, the lights don't follow the fireflies like they're supposed to, making the game unplayable.

On safari, the lights move correctly, but taking many seconds per frame.

https://ratracestudio.itch.io/light-the-night

In chrome I get a random alternation between these errors, when I reload.


On safari it will load and run, but at a dizzying ~4fps.

https://ccadori.itch.io/sailing-in-the-dark

In chrome the game will load the main game art and animations but never load the UI.

In safari it takes a bit and then crashes saying "this page was reloaded because a problem occurred."

Submitted

This sometimes happens to me but I use Opera GX so idk. I usually refresh until it works lmao

Submitted

I am apparently behind on my Opera, hadn't heard of the GX. Are you using it on MacOS?

Submitted

These 3 games work and load for me in Chrome on Windows.

image.png image.png image.png

Submitted(+1)

Alas, it's apparently a Mac issue. I appreciate you taking the time to be thorough with screenshots.

Submitted

I use a mac m1 and have had this issue with some games. For myself I just have kept testing if things work when developing my jam game and one issue I found is for instance requesting raw texture data in a shader gives exactly that webgl error.

This is my game and does work, but very hacky experimental js bridge stuff going on there, so was tricky to get it to work well: https://graphific.itch.io/spirit-hands

The sailing in the dark game doesnt work for me on chrome, but it does work in Safari on my mac.

Submitted

Oh no, I really wanted to experiment with writing shaders in Godot. I just started using Godot a month ago and I feel like no one one warned me about these things... but that's what jams are for, I suppose! I am learning things here.

Thank you for taking the time to give me some insight.

Submitted

Its a recent issue I think with the newest chrome release, as I'm pretty sure this kind of stuff used to work. heres a jam game that used to work on chrome but also just now found out it doesnt anymore https://graphific.itch.io/bird-ruckus

Submitted (1 edit)

Just submitted an issue as this actually means that newest chrome on mac broke _a lot_ of games:
https://github.com/godotengine/godot/issues/95832

Submitted

Ooh look at you being all responsible and submitting official github issues. Thanks for doing that.

I was so happy that the Godot engine runs so well on my macbook (and without eating battery life, as I discovered while game jamming during a power outage last week), that it really was a downer to think that MacOS is simply not supported for web. In the game you linked I get the WebGL2 error, but a lot of games in the jam are broken in more subtle ways that make it hard to tell. And in the three games I first linked, only one threw that error on Chrome, but all were broken in different ways on both Chrome and Safari, and some were just framerate issues where it's hard to tell who's at fault.

For another example, this game: https://physiiic.itch.io/duck-and-light

In Chrome, for the opening part of the game it runs and I can move around just fine in the lab. But in the next level when I pick up a light, I get a light for a tiny radius on top of my head, seen below. That's the duck's head there near the center. So, is this the developer's bug/design issue, or is it that Godot and Chrome no longer cooperate on rendering lighting graphics? 

The same game, in Safari, it runs fine through the splash screen and opening credits, the menu UI is fine, and then in the first gameplay scene each frame starts to take several seconds.

So for this game, I'm pretty sure it's an incompatibility issue. But it's definitely making it more difficult to play and rate games when this stuff pops up randomly and without giving an error.

Submitted (1 edit)

FYI fix for mac users by updating chrome to newest v128 from the dev channel:
https://www.chromium.org/getting-involved/dev-channel/

see also chrome issue at https://issues.chromium.org/issues/359912067

Submitted

Yay! I can confirm that the above games all run fine in the current chrome dev build.

Am I right in understanding that normal users should have the fix in the next 6 weeks or so?

Submitted

Google's official doc states "updated every 2-3 weeks for minor releases, and every 4 weeks for major releases", so hopefully 3 weeks or so.