Without a license, developers are not free to reuse code. 👎

This is a very cool program. Currently I am using three.js to develop a large scene display effect, which contains a lot of static models. I tried LOD, clone and other related technologies and finally did not have any significant acceleration. My goal It can be rendered as efficiently as your current demo version. If three.js can do it, please give me some inspiration, thank you very much.

Hi, I noticed you have a few branches in progress, including one to use ammo.js and three.js for physics and rendering, so maybe this is a moot point (not sure what state of completion that branch is in?) but I noticed that for all surfaces that are curved, perhaps because they are made from the Q3 patches, are not processed by the collision mesh generating script perhaps? So the player character clips & falls through curved walls quite readily.

I guess this post doubles as a question somewhat: If you are aware of this issue, do you remember by any chance if it's an issue with collision detection by the character, or like I mentioned above, the collision surface generation process? And, is it worth exploring a fix in the "main" branch, or working with the "exporter" branch?

I am using Chrome 18 on a mac and the pointer lock is not working. I am running the game on localhost and I have enabled the pointer lock functionality in about:flags. I also tested chrome canary with same result.

I tried updating to version 0.5 of the game shim and then my keyboard stopped working (W, A, S, D) and still no pointer lock.

When I start the game the following error appears in the console (both locally and on your server).

Uncaught Line: 71, Uncaught Error: INVALID_STATE_ERR: DOM Exception 11 ------ q3bsp.js:55
Uncaught Error: INVALID_STATE_ERR: DOM Exception 11 ------- /q3bsp/js/q3bsp_worker.js:71

However the pointer lock described on this webpage works.
http://updates.html5rocks.com/2012/02/Pointer-Lock-API-Brings-FPS-Games-to-the-Browser

Well, it's quite not an issue, but you could update some code for performance.

in
https://github.com/toji/webgl-quake3/blob/master/js/main.js#L325
document.getElementById('viewport') in drawFrame is maybe not the best thing to do.

in
https://github.com/toji/webgl-quake3/blob/master/js/main.js#L455
Should also try to put code like 'W'.charCodeAt(0) in a more global object like

const CharCode = {
    'W': 'W'.charCodeAt(0),
    ...
};

CharCode.W

in
https://github.com/toji/webgl-quake3/blob/master/js/main.js#L283
You could put vrPosition.position in a variable too?

But your general code is easy to read and I found nice answer.

Hi there,

i tried to run this code base locally but it says "Incompatible BSP version.".

Is there anything i should add before running the code?

https://github.com/toji/webgl-quake3/blob/master/js/util/game-shim.js

Hi, just saw this in VS:Code since I am converting this to TypeScript currently (and this is marked as an error).

"writeable" needs to be "writable", it has five occurrences in that file

Hi @toji,
I have tried to do my best to document and report a bug on the webxr polyfill that causes iOS not to be able to use WebXR on this demo (Im trying to make a working q3 cardboard gameplay 😬)

I have seen you had previously contributed to both the examples and the polyfill repos, so maybe this is something you could be able to fix or point me in the right direction to make the view to attach to the device movement:

I made a workaround adding the above on main.js->initEvents():

window.addEventListener('deviceorientation', (event) => {
  const yPos = isXRPresenting() ? event.gamma : event.beta;
  moveLook(-event.alpha * 10, -yPos * 10);
});

which initially "works more or less", but need to figure out how properly transform event's alpha, beta, gamma values to moveLook parameters.

Thanks in advance.
Best.

running this locally, it fails to load because of two 404's. http://localhost:9000/demo_baseq3/scripts/web_demo.shader and http://localhost:9000/demo_baseq3/maps/q3tourney2.bsp.