Epic’s ex-‘Unreal evangelist’ is making his own engine 🔨

#epicgames #unrealengine #unity #gamedev #news #pcgaming #pcgamer

https://www.pcgamer.com

X: https://x.com/pcgamer TikTok: https://www.tiktok.com/@pcgamer_mag Instagram: https://www.instagram.com/pcgamer_mag/ Facebook: https://www.facebook.com/pcgamermagazine/ Forum: https://forums.pcgamer.com/

To subscribe to the magazine in the US, UK, or elsewhere, visit magazines direct.

PC Gamer is the global authority on PC games. For over 30 years, we’ve been at the forefront of covering PC gaming with worldwide print editions, around-the-clock news, features, esports coverage, hardware testing, and game reviews, as well as our popular PC Gaming Shows.

Epic’s ex-‘Unreal evangelist’ is making his own engine 🔨

In the fast-evolving landscape of game development, a familiar name from the Unreal ecosystem is stepping onto a new stage. An industry veteran once celebrated for championing Unreal Engine has embarked on a bold venture: creating his own game engine. The move signals a broader shift in how developers approach tooling, performance, and the delivery of next-generation experiences.

The decision tothread the needle from evangelism to engineering is not taken lightly. It requires balancing the lessons learned from years of advocating a single platform with the pragmatism needed to design a system that stands on its own merits. At the core of this pursuit are several guiding principles: performance, modularity, and developer empowerment. The engineer-turned-creator seeks to offer a toolset that emphasizes speed without sacrificing flexibility, a feature set that scales from indies to AAA teams, and a philosophy that prioritizes clean architecture and long-term maintainability.

Performance as a first-class concern remains the north star. The engine under development aims to leverage modern hardware trends: multicore parallelism, advanced rendering techniques, and efficient memory management. By focusing on a lean runtime with a leaner abstraction layer, the project aspires to minimize overhead while delivering predictable pipelines for content creators. The result should be a platform that enables high-fidelity visuals, responsive iteration, and robust tooling that keeps pace with rapid iteration cycles.

Modularity and extensibility follow closely behind. Rather than building a monolithic stack, the engine is conceived as a composable ecosystem where core systems interact through well-defined interfaces. This approach invites collaboration from a diverse community of contributors and gives studios the freedom to replace or augment components—renderers, physics, toolchains, or asset pipelines—without lock-in. In practice, this means clean API boundaries, thoughtful documentation, and an emphasis on backwards compatibility where it makes sense.

Developer empowerment is the throughline that ties engineering discipline to creative agency. Beyond raw performance, the engine aims to streamline common workflows, reduce boilerplate, and provide expressive tooling for artists and engineers alike. Integrated profiling, readable debugging experiences, and comprehensive automation paths are expected to lower the friction of iteration. By designing with users in mind, the project strives to accelerate discovery, enabling teams to prototype, test, and refine ideas with confidence.

The origin story of this endeavor adds a layer of narrative resilience to the project. The founder’s experience evangelizing a leading engine brings a unique perspective on what developers need to succeed: clear communication from core developers, transparent roadmaps, and a community that thrives on feedback. This background informs an open development ethos—public roadmaps, early-access builds, and channels for external contributors to shape the engine’s trajectory while maintaining a coherent vision.

As with any ambitious engine project, there are challenges to anticipate. Compatibility with established tools, the onboarding curve for new users, and the long arc of platform support are critical considerations. Addressing these early with well-documented migration paths, comprehensive tutorials, and a modular design will be essential to building trust and momentum within the community.

Looking ahead, the community will be watching for tangible milestones: first public beta, a robust set of core systems demonstrated through a playable prototype, and a clear strategy for ecosystem growth—plugins, middleware integrations, and sample projects that illustrate real-world value. If the execution aligns with the principles outlined—the emphasis on performance, modularity, and developer empowerment—the project has the potential to become a compelling alternative in a crowded field.

Ultimately, the journey from evangelist to engine architect reflects a broader industry truth: creative software evolves when passionate practitioners invest in tools that empower others to create. Whether this new engine becomes a dominant platform or a niche but influential option, its emergence will contribute to ongoing conversations about performance, openness, and the future of game development tooling.