11–20 of 122 posts
I'm curious to know how networking behaves in a webgl build. Will my tcp sockets just work straight out of the box? That would be seriously impressive!
They won't, but changing your server to accept websocket instead shouldn't be too bad.
Article does not address licensing terms; what's in it for Unity?
Each platform for Unity has another license associated with it (eg: $1500 for Android Pro, another $1500 for iOS Pro). Another web target would be another $1500 license for folks to buy annually, I imagine.
Earlier quoted context omitted.
They have already proved (Lego Starwars demo IIRC) that they can target the NaCL runtime for Chrome (and ARM Chromebooks). But I'm not sure when/if they plan to release that publicly.
I think it makes more sense for them to aim towards some sort of unified platform. NaCL is cool and all, but it's very Google specific. WebGL is now even supported in the latest versions of IE.
Earlier quoted context omitted.
They have already proved (Lego Starwars demo IIRC) that they can target the NaCL runtime for Chrome (and ARM Chromebooks). But I'm not sure when/if they plan to release that publicly.
I think it makes more sense for them to aim towards some sort of unified platform. NaCL is cool and all, but it's very Google specific. WebGL is now even supported in the latest versions of IE.
Earlier quoted context omitted.
I think it makes more sense for them to aim towards some sort of unified platform. NaCL is cool and all, but it's very Google specific. WebGL is now even supported in the latest versions of IE.
Yeah. Target asm.js and WebGL and you'll get Internet Explorer 11, Chrome, Firefox, IE and probably eventually Safari. With NaCl you get Chrome only. The choice is simple.
Slightly off-topic: I wonder if we're going to see more games being written to run in Web Browsers, or more games being written using web technologies like JS + WebGL but for desktop/mobile devices using things like phonegap/node-webkit [0] and then sold through various app stores such as Steam, iOS & Android.
The infrastructure for monetising web games in the same way that Steam and the App Stores has done isn't there yet, but maybe it will be soon?
[0]: Like A Wizard's Lizard http://steamcommunity.com/sharedfiles/filedetails/?id=205801...
Earlier quoted context omitted.
I think it makes more sense for them to aim towards some sort of unified platform. NaCL is cool and all, but it's very Google specific. WebGL is now even supported in the latest versions of IE.
As a company they surely do not care if something is Google specific or not. They only care if they can sell enough licenses for it to make the development costs make sense. In light of chrome's adoption curve it seems to be a not terrible idea to target nacl.
It would be cool if the engine could figure out what assets to download on-the-fly, but I have a feeling that's not the case so game makers would still have to do a bit of work before making the games web-ready (instead of ideally just hitting an "export to webgl" button).
"This is a big day for evolving the Web as a platform for gaming and we are very excited to see what experiences developers will bring to the Web using this powerful technology." Slightly off-topic: I wonder if we're going to see more games being written to run in Web Browsers, or more games being written using web technologies like JS + WebGL but for desktop/mobile devices using things like phonegap/node-webkit [0]…
But with Unity you can have one codebase and export to Win/OSX/Linux/iOS/Android/HTML5 and even consoles while some HTML5 engines offer an acceleration wrapper for iOS but thats basically it.