Using the new Navigation2DServer and exporting the game to windows & html5 leads to different behaviors in the game

0 votes

The different behavior means, navigation works in the Windows build but does not in in the HTML5 build.

This happened in my own project as well as the Navigation2DServerTest sample project from the asset library.

Do I have to make certain setting to make this work or is this simply a bug in den export templates?

Edit
After researching and bothering people in discord I found the situation is like this:
2DNavigation requires the Threads option in exporting. Threads require SharedArrrayBuffers in the browser and the browsers require the correct Cross-Origin headers which are set in the server configuration.

I theory I should be able to run the game in the browser now, but it stops after the title screen and the browser freezes, probably another issue.

Godot version 3.5.stable
in Engine by (16 points)
edited by

Please log in or register to answer this question.

Welcome to Godot Engine Q&A, where you can ask questions and receive answers from other members of the community.

Please make sure to read Frequently asked questions and How to use this Q&A? before posting your first questions.
Social login is currently unavailable. If you've previously logged in with a Facebook or GitHub account, use the I forgot my password link in the login box to set a password for your account. If you still can't access your account, send an email to [email protected] with your username.