Tag Info

Hot answers tagged


Emscripten can be used to port C++ applications to javascript. It was able to succesfully make the Unreal 3 engine run in a web browser. It works best in browsers which support asm.js, an optimization-friendly subset of the Javascript language which can reach performance comparable to native code.


pepper.js allows you to write C++ code and then deploy directly as: Machine code via PNaCl for higher performance, currently only supported by Chrome. Javascript via Emscripten for maximum reach. From the project page: pepper.js is a JavaScript library that enables the compilation of native Pepper applications into JavaScript using Emscripten. ...


No, Corona does not build for web platforms.


Unity Web Player, as you probably know, is a browser plugin so it is allowed to run anyway it likes. Unity 5 will export to WebGL, and the article you linked says they worked with Mozilla to bring that technology, so they are most likely using Emscripten which is a LLVM to Javascript compiler. Several languages can be compiled to LLVM (including C# and ...


WASD is viable because for the best player experience the client (the browser) should be simulating actions based on inputs at the same time the server is verifying inputs as valid and sends you appropriate data back. To put it in perspective, if you are playing a game and we figure on average it takes 100ms (arbitrarily picked this number - no real ...


When you are OK with excluding Internet Explorer 9 and below, you might consider to use WebSockets instead of AJAX. It is much more suitable for real-time games. You do not need to notify the server every tick which key the user is holding down. It's enough to tell the server when the user starts pressing it and when the user is releasing it. The ...


Found a solution so to use the same code for both Windows and Web Player deployment (disclamer: I'm just reading these XML files): you can put the XMLs in the Resources located into the Project Assets folder. This basically tells to Unity to keep these files into the final build and you can load them at runtime using (in case of xmls for example): ...

Only top voted, non community-wiki answers of a minimum length are eligible