Yeah, the performance issue is well known, I think I just put too much shaders and geometry in.

Though the binaries (if you are not on a mac) for windows or linux should work much better.
Inititially I had even more complex geo and shaders in it.

In the last few hours before submitting, I already discovered some issues when testing, after which I did already some quick optimisations. So I guess the original version would have been worse. The version running in the browser is basically the same as the fallback binaries
In the web and fallback version for example I am using entirely the low poly version seen on the right, the original uses the left model for the close area where you can walk on, and the low poly for objects in the environment

I checked it, the verson I uploaded has thread support enabled and only runs with this experimental shared array buffers option.

So this doesn't seem to be the issue. I got even weirder, when I tried it on different machines in the browser, a laptop running linux where it runs smoothly, and a windows pc, encountering these performance issues.

I wonder, if I just went too high with shader complexity / geometry (polycount), particle effects and / or post processing.

Yeah, I think I had something like this once when developing too, I thought it froze, but after a minute or so it worked.

And for the issue with inside the platforms, I had initially the issue that was able to get stuck inside if you are in there, so I had to do it so that the collision activates when the player is out of the collision zone. I really wanted to make them activatable if inside, by making the mesh already visible, so that the player knows it is activated.

Otherwise not beeing able to activate if inside felt even more strange and unwanted for me, resulting in more trial and error.

It is more or less the downside, that it is sometimes hard to activate. What I usually do is doing small jumps, not too far away from the platform I am standing, landing back on the platform, until I see that the platform was revealed. Basically controlled jumps back and forth trying not to fall down. And then I can safely jump on.

As I wrote somewhere before, I guess the crashes are caused by the high number of label3d elements to create the depth effect.
It seems to be a known issue too,  I found a similar bug report: https://github.com/godotengine/godot/issues/66566

If you haven't done it already, download the fallback version, where I reduced the number of label elements used for the effect.

And if you want, try to play the tutorial level in both versions as many times you want as a benchmark, or compare it to other levels (the turorial level has by far the largest amount of 3D labels)

Yeah, I focused a lot on polishing graphics (which was also my aim to experiment here with the visuals, like what I can do with shaders or particle effects)

Additionally I have a strong computer / GPU, so I didn't have the lag / crash issues that much (except for the tutorial level, which even my computer wasn't able to handle in a few cases).

Also, I must say, especially the last 2-3 levels are really difficult. The very last even still for me.

I had this too sometimes, but only with the tutorial level. Maybe it is caused by the many text elements I have in there, I wasn't able to figure it out.

Just try to restart it a few times and check if it works. Basically trial and error until it works

totally true, only the idea with playing a farting cow came after I had the idea with invisible platforms.

It was born from random thoughts I had before the theme was announced, and I had other ideas related to cows because of the theme suggestion cow. I was heavily brainstorming days before, so I got the idea pretty quickly when the theme was announced.