Skip to main content

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

well, f me!

was playing the game for literally hours in one go, (web build)
had like 7 of 8 herald bells and whatnot.
after killing the weaver spider bos and going upstairs to the next area upwards, screen first lagged and then started fliggering, as if I was switching between areas repeatedly or something.

did reload page, first it showed some "loading game for the first time" nonsense and when that was gone and the normal play button was there, i click it and get "

Error

The following features required to run Godot projects on the Web are missing:

WebGL2 - Check web browser configuration and hardware support"

now, no matte rhow often i reload the page and press the play button, that is all I see now >:-(

guess that's that for the game for me, game broke and save likely gone, if it ever made a save in the first place (I literally played from start till nowfor hours, never reloaded page or closed browser).

Anyways cant play it anymore anyways, so that's that for me.
And even if it were to work again, I wont replay like 5 hours of content again!

So sorry about that, and thank you for playing that long! Your report found a real bug: right above the Weaver, between the Cocoon hall and the Dovecote, holding a direction could bounce you between the two rooms forever. Each bounce reloaded the room until the browser's graphics gave up, and that's what the "WebGL2 is missing" error means. It's fixed in 1.1.1, which is up now.

Your progress should still be there: the game autosaves every time you enter a room, and the web version keeps the save in your browser.
To get the game running again:

  1. Fully close the browser (all windows) and open it again. In Chrome you can type chrome://restart in the address bar. A page reload isn't enough: the browser keeps WebGL off until it restarts.
  2. Open the game page in the same browser and press Continue. You should be back near the Weaver.

If the WebGL error is still there after a restart, check that hardware acceleration is on (Chrome: Settings → System → "Use graphics acceleration when available"). If the save really is gone, tell me and I'll see what I can do. Thanks again, this saves the next player from the same trap.

(1 edit)

while this happened as I explained, it kind of happened a few times again.

Basically each time the game had a short freeze (maybe cause computer's cpu maxed I dont know. my ntoebook is like 10 years old).
the gam freezes for say 1-2 seconds, say during an attack.
then visually it apparently is hung up in an attack loop, like replaying the same attack animation on screenover and over again.
howeverI can still use the keyboard and going by the audio the game does seem in fact to pay normally in the background as I can hear music, even voices and stuff, so it's like playing the game then blindly while on screen it jsut hangs at that forever looping freeze moment animation, like watching a 1 second gif.

of course I then reload the page as anyone would do.
and THEN the error is here,page reloading doesnt remove it.

have to clsoe and reopen browser full each time for it to be gone and game open normally again.

so basically something happens where the engine hangs up, freezes for whatever reason for a bit being unresponsive.
and then the visuals just repeat the last movement in a 1 second loop on screen, never advancing past that.
while in background the game, going by sound, plays normally.
jsut the visuals dont fit it at all anymore.
I assume that congruency between whats on screen and what is actually happening game wise then fu cks the whole game, making a browser reboot necessary.

no clue how this happens but I had this happen in oher godot games too before, though rarely.
back then didnt know that browser reboot would fix it though.

no clue how this happens, where the visuals jsut basically crash, stuck in the last thing they were showing.

might jsut be my old ntoebook, but testing on website shows that webgl2 is supported by it, so that i basically a nosnense erorr theree likely unrelated to whatever happens.
likely the graphics engine crashing jsut fs the whole godot and needs a reboot basically.

not sure if this is related by this topics only hppens and starts happening basically only when I am in the spider area, namely the rooms with the mega bell and the one above it.
fate really doesnt lik me being there.

Also, more actual game question, there is an obvious to be found room in the spider area to the east but with no visible entrance on any side.
I already had the women in the workshop open the apider areas door for me but that didnt seem to change anything, sitl no entrance to the room.
how does one get there?

I mean I got all important thigns,relics, etc by now but still wanna 100% everything for reasons before going to the final boss himself. :-)

(+1)

Update 1.1.3 is live, and a lot of it is thanks to your reports!

What you described (a 1–2 second freeze, then the picture looping the same second while sound and controls keep going) is the browser losing its WebGL graphics context. Old or busy graphics chips are more prone to it. Godot can't recover from it inside the page, and the browser then keeps WebGL off until it's fully restarted. That's why a reload showed "WebGL2 missing".

What's new to help with that:

  • Settings → Light graphics. Draws the game at 1280×720, 30 fps, lamps without dynamic light, fewer particles. It looks almost the same and is much easier on old hardware. I'd suggest turning it on.
  • If the graphics do crash anyway, the game now pauses on the spot (no more playing blind) and tells you what to do. Your progress up to the last room you entered is kept.
  • Settings → Save file → Export / Import. Export your save as a small file, keep it as a backup, or load it into the downloadable Windows version, which doesn't depend on WebGL and is far more stable on older laptops. I'd recommend exporting once now, just in case.

If it happens again: close the browser completely (all windows; in Chrome you can type chrome://restart) and open the game. Closing other tabs and checking that hardware acceleration is on in the browser settings also helps.

And the sealed room in the east of the attics is the Nest of the Shroud Mother. It has no entrance on purpose: it opens only after the true ending. At the Heart-Bell choose to call the choir (all 4 notes and at least 20 rescued citizens), and you'll be taken there. A forge inside lets you return. It no longer shows on the map before then. Good luck with the 100%!