Topic
Every article about Unreal Engine 5 on the COLONIZED blog, newest first.
7 articlesRSS feed
RenderOne day of work on COLONIZED, read from the commit history: how dune fields will come from each world's wind, why the ground now weathers by real data, what the terrain costs and how we will make it cheaper, and why our public roadmap looked frozen until that night.
8 min read
RenderMegaLights became production-ready in Unreal Engine 5.8. What it actually does, why its cost barely grows with the number of lights, what hardware it expects, what it cannot light yet, how it differs from Lumen, and why the COLONIZED development build does not use it.
5 min read
RenderMost procedural planets start from a random seed. COLONIZED starts from a canon: radius, density, air, rock, places and rules written as data. How that data becomes fifteen worlds, why the terrain comes from real elevation and physics, and what is still under review.
4 min read
RenderThe first devlog on the new site does one job: sort every system of COLONIZED into done, in development or designed, with the numbers behind it, plus two things we got wrong and how we fixed them.
5 min read
RenderNanite and Lumen without the marketing: how virtualised geometry and dynamic global illumination work, what Virtual Shadow Maps, MegaLights and TSR add, the budgets and limits Epic documents, and two lessons from using them on a whole planet.
6 min read
RenderWhy a planet-sized world breaks a game engine, the three tricks that fix it (floating origin, double precision, compressed distances), how orbits and spheres of influence work, and how COLONIZED builds the Aurin system: real radii, Kepler orbits and one server zone per body.
5 min read
RenderA practical guide to performance in UE5 games on PC: the settings with the biggest impact, what eats video memory, how to read minimum and recommended requirements, and the measured story of how we cut a planet's VRAM by 58 % and its cloud cost from 15.5 to 3.5 ms.
6 min read
LUMBRE