• Building
  • HTML5: "unreachable" and "table index is out of bounds"

Hello everyone I making games for social network and and recently, two errors began to occur in my games after the loading screen: "unreachable" and "table index is out of bounds"

I use Godot version 3.3.2 and standard export templates for HTML5, the games are on a cloud server What can cause these errors and how can I fix it?

Sorry for my bad English, I'm from Russia and understand English better than I speak it

6 days later

Must be a bug in 3.3.2, My game shows function signature mismatch on debug and table index is out of bounds on release export. This happens only when I attempt to open the game for the second time on my smartphone. First load works fine, then when I refresh the page, the bug is reproduced. Opened same project in godot 3.2, export, no problems, it works

@lugdt said: Must be a bug in 3.3.2, My game shows function signature mismatch on debug and table index is out of bounds on release export. This happens only when I attempt to open the game for the second time on my smartphone. First load works fine, then when I refresh the page, the bug is reproduced. Opened same project in godot 3.2, export, no problems, it works

It helps but godot 3.2 make it really worse in game loading and perfomance. Hope to find a solution that works with version 3.3.2 or 3.3

@lugdt said: First load works fine, then when I refresh the page, the bug is reproduced.

Hmm, does clearing cookies help?

@Megalomaniak said:

@lugdt said: First load works fine, then when I refresh the page, the bug is reproduced.

Hmm, does clearing cookies help?

only sometimes. Trying to build from source 3.3.2 both godot and the export templates at the moment but without much luck, it works on desktop but on mobile now it takes very long to load the game and I'm getting "Directional shadow framebuffer status invalid" as well as "table index is out of bounds". If anyone knows a way to get any godot version to run fine on mobile web, I'd very much appreciate the help.

I'm thinking leaving it as it and handling it in html to reload the wasm if not loaded propertly...

If clearing cookies can and does help then that indicates the issue is to do with them. There could be a bug in there perhaps, not sure. But if you can't find anything else then perhaps it is worth opening an issue on the tracker.

@lugdt said: I'm thinking leaving it as it and handling it in html to reload the wasm if not loaded propertly...

If you find a way to do it - share it, please!

@Mdch Is it you who cross-posted this issue to GitHub?

Remember to always cross-reference posts when posting on multiple communities, so that people can find solutions to their problems more easily :)

@Calinou said: @Mdch Is it you who cross-posted this issue to GitHub?

Remember to always cross-reference posts when posting on multiple communities, so that people can find solutions to their problems more easily :)

it was me. You beat me to it :)

@Mdch said:

@lugdt said: I'm thinking leaving it as it and handling it in html to reload the wasm if not loaded propertly...

If you find a way to do it - share it, please!

try using 3.2.stable

@lugdt said: try using 3.2.stable

This helps for 6 out of 7 of my games (the seventh shows an error "memory access out of bounds"), but after loading, a black screen appears for a few seconds. I am looking for a solution to how I can replace this black screen with the game loading screen so as not to scare away potential players.

Sorry, just catching up on this. Have you looked in the web browser developer console? There may be additional errors there that can help pinpoint the problem. Also, I've been testing in WebGL from Godot and it generally works decent (at least on desktop, on mobile there can be issues depending on how far you are pushing it).