Well, it keeps printing the same error in the console, over and over again for all eternity:
Tried to switch to same state, this should not happen. MV_GL.framework.js.gz:3:35236
"The error message "Tried to switch to the same state, this should not happen" typically occurs in Unity when you are trying to change to a state that the object is already in, such as in a Finite State Machine (FSM) or when handling animation transitions. Unity is letting you know that this transition is unnecessary because you're already in the target state."
is what chatgpt says about this error
well, i literally jsut start the game, be it via website or program, choose classic mode new game.
do the jumper and get up to the left side, active checkpoint by walking past, collect cheese by walking past, touch the blueish shining thing oon the left.
and thats it, the splitsecond I touch the screen, all movement freezes, no controls do anything anymore (only esc shortly opens the menu but autocloses directly) and the light reduces to that light circle, so no full illuminated room anymore.
no idea, seems like some games jsut dont like my computer :-)
I also, unrelated, sometimes have trouble with godot games, where i get error messag that the vulcan driver thing doesnt work or soemthing.
so I have to run the game via console command, explicitly telling it to use the opengl3 driver isntead of the normal vulcan driver, then it works.
unrelated to this, jsut saying that my computer has issues with a bunch of games, not jsut this.
even tzhough the freezing thing here is a first to me.
oh and by the way, fancy mode doesnt work at all for me.
like I choose fancy mode new game, see the screen with characters standing there.
and thats it, no controls do anything. (no, i didnt check javascript console, but it is likely the same thing)
likely related to the same issue, jsut that in classic mode it happens slightly later.