The Blend4Web team has compared the performance of their engine against Unity WebGL.
The developers of the Unity engine announced “official support” of WebGL in December 2015. From this point, Unity can be considered a competitive player in the field of 3D Web. Thus, it can be interesting to compare the functionality, the maturity and the efficiency of both Blend4Web and Unity.
I’ve created three test applications of varying complexity as benchmarks. These benchmarks were created for both engines at the same time and are completely symmetrical. Their scenes, objects, textures and even material settings are almost identical. No handicaps and no specific optimizations were made for any of the engines. Whatever was offered “out-of-the-box” was used by default.
3 Comments
Gorgeous info, thank you!)
Ok, run some of the tests on the page and ther results were OPPOSITE :) not always, but UNITY won on my computer. of course, I didn't test on mobile...
Unfortunately this has nothing to do with a fair comparison, at least the performance measurements.
The out of the box settings have tremendous differences. E.g. Blend4Web doesn't use environment lighting while Unity does. Besides that, Blend4Web seems to use a very computationally cheap shader by default, while the one from Unity is far more expensive. The Unity shader is physically based, which e.g. means that it uses Fresnel, energy conservation and reflections by default. All those computations don't seem to be calculated at all in the Blend4Web case.
Out of the box comparisons are only useful, if the default settings are pretty much identical. That's unfortunately not the case here and as such the performance comparison is completely useless.