Why NASA Switched from Unity to Blend4Web
gamedev.net
Why NASA Switched from Unity to Blend4Web
1–10 of 47 posts
Re: Why NASA Switched from Unity to Blend4Web
#2Long story short: if WebGL is your primary target platform, Unity is not exactly the first place you should look.
Re: Why NASA Switched from Unity to Blend4Web
#3Re: Why NASA Switched from Unity to Blend4Web
#4It's very simple: Unity was never designed with a target platform as radical as HTML5/JS/WebGL in mind. It's stuck with an older version of the Mono runtime for its scripting language, and they've pulled off some crazy tricks to get it to work on WebGL: Mono IL code is cross-compiled to C++, which then gets cross-compiled again to JS/WebGL using Emscripten. That it works at all is nothing short of a miracle. However,…
If one main goal is WebGL then the best option is to adopt a WebGL native engine, instead of trying to cram a native experience into the browser.
Re: Why NASA Switched from Unity to Blend4Web
#5Re: Why NASA Switched from Unity to Blend4Web
#6What about Unreal 4? I read that they support HTML5 pretty decently by using Emscripten. I really do not know what is their current status on that subject.
Re: Why NASA Switched from Unity to Blend4Web
#7It's very simple: Unity was never designed with a target platform as radical as HTML5/JS/WebGL in mind. It's stuck with an older version of the Mono runtime for its scripting language, and they've pulled off some crazy tricks to get it to work on WebGL: Mono IL code is cross-compiled to C++, which then gets cross-compiled again to JS/WebGL using Emscripten. That it works at all is nothing short of a miracle. However,…
Re: Why NASA Switched from Unity to Blend4Web
#8What about Unreal 4? I read that they support HTML5 pretty decently by using Emscripten. I really do not know what is their current status on that subject.
The problem with taking a engine like Unity or Unreal and compiling to javascript is that 1) they end up with very large blobs of javascript (Unity is around 5MB of JS for the webplayer alone) 2) It is impossible to optimize, debug or inspect any of that code in the target setting. Neither of these engines have ever demonstrated code running on mobile browsers for good reasons, they can't.
Meanwhile, engines designed specifically for the web, for example, PlayCanvas [https://playcanvas.com] let you create content that works on every device, down to the likes of the iPhone 4S and comes in much smaller download sizes. e.g.
http://tanx.playcanvas.com (~1MB)
http://mmx.playcanvas.com (~3MB)
http://swooop.playcanvas.com (~10MB)
All of which work on mobile browsers. The future of Web 3D is not compilation of desktop game engines. It's engine's designed to be web (and mobile) first.
Re: Why NASA Switched from Unity to Blend4Web
#9Re: Why NASA Switched from Unity to Blend4Web
#10What about Unreal 4? I read that they support HTML5 pretty decently by using Emscripten. I really do not know what is their current status on that subject.
Dont bother. Its lightyears worse than unity, and thats saying something.