Babylon.js

We investigated this many years ago: https://github.com/BabylonJS/Babylon.js/ 1. It works just fine for basic 3D functionality, but has limited support for tricks like fog FX etc. WebGL is actually quite capable when combined with simplified physics engines, and animated mesh packing formats. 2. In a business context it fails to check all the boxes, as people are not going to invest in a platform with near zero IP protection. 3. Steam + Unreal has all the advantages, and none of the problems/overhead of a Browser. i.e. peoples game pads, spacial audio, and shader cache buffers will work properly. WebGL is just hitting the same VRML market that failed decades ago for the same reasons. =3

You can see a cross-Browser WebGL Game Engine here: https://github.com/BabylonJS/Babylon.js In general, the tradeoffs are: * WebGL is not always available and enabled in all browsers * Spacial Audio effects and formats are inconsistent across platforms * mouse/keyboard/game-pad support is tricky (browser security is messy) * Rigging a mesh for animation gets computationally expensive * Basic collision detection and snapping to surfaces is always computationally expensive, so to make it performant people use 90's style sphere/cube assumptions * mutable textures are supported, but basic animated effects still bloat into video memory * all game assets and runtime code are exposed to end users Thus, most conclude JS+WebGL are incompatible with most commercial settings, and basic anti-cheat enforcement. Note, WebAssembly+webGL is marginally i

If you want to learn more about 3d engines (game or rendering), I would recommend BabylonJS: https://github.com/BabylonJS/Babylon.js It has fairly good docs: http://doc.babylonjs.com/ as well as an active forum for developers and users: http://www.html5gamedevs.com/forum/16-babylonjs/ Other options mentioned are also good - the Typescript compiler (https://github.com/Microsoft/TypeScript) is good to get started with especially if you read this Gitbook: https://basarat.gitbooks.io/typescript/content/docs/compiler... You could also search popular typescript github projects that are more closely related to what you work on, but the Typescript compiler and Babylonjs 3d engine are both well written projects with fairly good documentation in my opinion.

Latest. Here's the string concatenation to set the active texture unit. (By the way the fastest way to do it is "gl.TEXTURE0 + channel" instead of creating the string to index in the proper constant). https://github.com/BabylonJS/Babylon.js/blob/master/src/baby... As for the broken cache, I think it was Engine._activeTexturesCache; sometimes its indexed by texture channel other times by GL enum values (this makes the cache array explode to 30k elements and causes cache misses in half the code paths.) From what I remember, lots of caches are needlessly trashed many times per frame. There's also noticeable overhead to all of those "private static <constant> = value;" with public getters.

Its on GitHub https://github.com/BabylonJS/Babylon.js

> Microsoft I don't see anything that says that this is a Microsoft product. It looks like a side project by a Microsoft employee. (full disclosure: I work at MS.) > Not open source Looks like the source code is available at https://github.com/BabylonJS/Babylon.js under the "Microsoft Public License" which has been certified by the Open Source Initiative as an open source license.

It is open sourced under Microsoft Public License: https://github.com/BabylonJS/Babylon.js According to the Free Software Foundation, it is a free software license but not compatible with the GNU GPL.