Same applies to physx supposedly being unable to generate convex hulls.' Wouldn't call it a clickbait, because texture arrays are a very solid argument. Did you know that they have clauses in EULA that forbid posting more than 30 lines of code anywhere? That's not 'Open'. When you hit this low point, you begin to seriously question your career 'Proprietary engine with limited source code access they can revoke at any moment. This raises a whole hell of issues, like having to pick mip levels yourself and wasting precious memory in padding textures to avoid bleeding.

When an engine lacks texture array support, you must use 2D atlasing. Texture arrays make a big difference if you need complex materials where many different types of surfaces need to be splatted in a single draw call. That is a dealbreaker if your middleware is to be used as a plugin like it is our case. However, this is not possible with the out-of-the-box Unreal distribution. Unreal almost supports them, in fact, we managed to make them work in a custom branch of UE4 with little effort. Unity has one crucial advantage over Unreal, which is it natively supports texture arrays. This has likely been the lion's share of their R&D for years now. Both are also able to render at very high frame rates, even for fairly complex content. Both Unity and Unreal are capable of rendering beautiful scenes.

Unreal engine 4 procedural generation