Can you give me more information on how the web version doesn't work? What system specs, browser, etc? What did you do, what did you expect to happen, and what actually happened? There used to be a bug with invisible blocks far down but it was fixed... I looked and couldn't see it happen. Did you see a 2nd enemy type down there at all? If not then it might be some issue preventing them from spawning properly or something like that. I appreciate your patience trying to play despite the technical issues you faced!
I had friends test in libra wolf, edge and chrome. Seemingly only chrome had no issues but the same bug still happened on the installed game so it might not even be a browser issue. As for what actually happens, the screen starts shaking slightly and then increases quickly until the shaking is so violent the game becomes unplayable. It pretty much just throws your camera off screen so you cant actually see whats happening.
One of my friends did see the second enemy type but this was on the dirtpay.exe as this was the only version of the game where the previous bug did not happen to him. Although im not sure if that bug is actually present in that version or not. He was also the same one who ran into the invisible blocks.
16 hours ago(+1)
Ah I didn't realize I had that old exe still being zipped up, oops. That is quite old (hence the old temp name for the game). Very interesting, I primarily use firefox and I only was able to reproduce similar problems in Chrome previously, so it's funny that's the browser you didn't have problems with... but I don't think it's browser-related either. I speed-ran the game in browser to see if I could reproduce it but alas nothing yet. The invisible blocks bug would be in the old dirtpay version, but shouldn't be in the recent builds. The shaking... I have no idea anymore.
Heres a gif of the bug from a friend of mine
"my guess as a gamedev is the framerate is low due to the web build so the camera is moving towards the player in big stuttery steps, overshooting the player and then moving back again and overshooting further" is what they think the problem is. Hopefully that helps.
1 hour ago(+1)
I figured out the cause is related to the camera smoothing and extremely low FPS (<10). Make sure hardware acceleration is turned on in your browser, or pull a Todd Howard and try on a better PC? I was able to reproduce it exactly as you get it by throttling CPU in chrome, and removing the throttle fixes it, so it's directly tied to fps.