ProjectSpeed ProjectSpeed
ProjectSpeed ProjectSpeed
  • Home
  • FAQ
  • Videos
  • Contact
  • Devblog

 

 

Custom Game Engine Development: Building the Technology Behind the Game

 

Developing a game with a custom engine is a completely different experience from working with an established engine. Every feature presents a new challenge, from rendering and resource management to world streaming and performance optimization.

 

Recently, my focus has been on improving the core technology behind my engine, built around DirectX 12. The goal is to create a flexible foundation for an open-world racing game, with enough control over the rendering pipeline and development tools to shape the experience exactly as needed.

 

One of the most interesting parts of this process is that improvements rarely happen in isolation. A change to resource management can affect rendering performance, while a small improvement in the terrain pipeline can make a huge difference when working with large environments.

 

I'm also focusing on the tools themselves. A custom engine is only as useful as the workflow built around it. Terrain editing, procedural road generation, vegetation placement, and world-building systems all need to work together efficiently. Spending time improving these tools now can save countless hours later.

 

Of course, building everything from scratch means constantly balancing flexibility, performance, and development time. Not every system needs to be reinvented, but understanding how the pieces work together makes it easier to identify bottlenecks and make informed decisions.

 

The engine is still evolving, and there's plenty left to improve. For me, the most rewarding part is seeing individual systems gradually come together into something capable of supporting a much larger world.

 

More engine improvements and development progress to come.

 

October 21, 2026

 

 

 

 

Engine Development Update – Building the Foundations

 

Another month of engine development, and this one has been mostly about the things you don't immediately notice when playing the game.

 

I've been working on improving the core systems that everything else depends on. Rendering, resource management, world streaming, and tooling have all received smaller improvements that add up to a much better foundation.

 

One of the main areas of work has been the rendering pipeline. I'm continuing to reduce unnecessary CPU work and improve how the engine handles large numbers of objects. The goal is to make the renderer scale better as the open world becomes more detailed.

 

I've also been spending time on the editor and world-building tools. A good tool can save hours of repetitive work, so I'm trying to make common tasks faster and easier to iterate on. Being able to quickly modify terrain, roads, vegetation, and other world elements makes a noticeable difference during development.

 

World streaming is another area getting attention. An open-world racing game puts a lot of pressure on memory and loading systems, especially when the player can travel through the environment at high speed. I'm working toward a system that can continuously stream the world without interrupting the driving experience.

 

There have also been plenty of smaller fixes and optimizations along the way. None of them are particularly exciting on their own, but together they're making the engine feel more mature.

 

The interesting part about engine development is that progress isn't always visible in screenshots. Sometimes the biggest improvements are simply being able to build a larger world, iterate faster, or run the same scene with less overhead.

 

Still a lot to do, but the foundation is getting stronger.

 

 

September 19, 2026

 

 

 

 

I’ve been spending a lot of time lately working on the less glamorous side of game development: the engine itself.

 

There’s something satisfying about building systems from scratch.

 

Rendering, resource management, shaders, world streaming, tools, debugging — every feature tends to uncover another problem underneath it.

 

The nice thing about a custom engine is that you can shape everything around the game you’re actually making.

 

The downside is that you also own every bug.

 

A seemingly small change in the renderer can turn into a few days of profiling and debugging. A new world system can expose problems in memory management. Even a simple editor feature can require changes across several engine systems.

 

But that’s also what makes it interesting. The goal isn’t to build the biggest or most technically impressive engine. It’s to build the systems that make the game easier to create. Right now, a lot of the work is happening behind the scenes. It may not look like much from the outside, but these foundations are what will eventually make the open world racing game possible. Slow progress is still progress.

 

 

August 19, 2026

 

 

 

 

Building an Open World Racing Game with a Custom Engine

 

 

There are moments during development when it's easy to focus only on features, frame rates, and bug lists. This week was a reminder that building a game engine isn't just about technology—it's about creating the foundation that lets the game grow for years.

 

One of the biggest advantages of using a custom engine is that every system is designed around the needs of an open world racing game. Instead of adapting gameplay to fit an existing engine, I can optimize streaming, rendering, physics, and world management to work together from the start.

 

A significant part of development has been dedicated to world streaming. The goal is for players to drive across large environments without noticing where one section ends and another begins. Roads, terrain, vegetation, buildings, and props are loaded and unloaded seamlessly in the background, allowing the world to feel continuous while keeping memory usage under control.

 

Rendering also continues to evolve. Every optimization matters in an open world where thousands of objects can be visible at once. Recent work focused on reducing CPU overhead, improving GPU workload distribution, and making better use of modern DirectX 12 features. Small improvements in individual systems often combine into meaningful gains when viewed across an entire frame.

 

The world itself is becoming more believable with each iteration. Terrain generation, vegetation placement, and environmental details are constantly being refined to make every road feel unique. Long highways, mountain passes, forests, rural roads, and urban districts should each have their own identity rather than feeling procedurally repeated.

 

Another area receiving attention is the development workflow. Internal tools are just as important as the engine itself. Faster terrain editing, improved asset management, and better debugging tools mean less time waiting and more time creating. Every minute saved during development translates into more time spent improving the game.

 

There's still a long road ahead, but that's part of the journey. Building both the engine and the game simultaneously is challenging, yet it gives me complete control over every system. Each milestone brings me closer to the experience I've envisioned from the beginning: a seamless open world where driving feels natural, exploration is rewarding, and every kilometer tells its own story.

 

Thanks for following the project. More technical deep dives and development updates will be coming soon.

 

 

July 19, 2026

 

 

 

 

Development Update – Engine Improvements

 

 

Hello everyone,

 

It's time for another development update.
Over the past few weeks, work has continued on both the game engine and the open-world racing game built on top of it.
While much of the progress has happened behind the scenes, these improvements are laying the foundation for a larger, more detailed world and a smoother gameplay experience.

 

Engine Development

 

A major focus has been performance and scalability.

 

Terrain System

 

The terrain pipeline has received several improvements aimed at supporting larger environments while maintaining stable frame rates.
Terrain streaming is now more efficient, reducing memory usage and minimizing loading stalls as players move through the world.
Work also continues on terrain generation tools, allowing faster iteration when creating roads, hills, valleys, and large-scale landscapes.

 

Rendering Improvements

 

The renderer has undergone optimization passes to improve overall performance. Recent work includes:
* Reduced draw-call overhead.
* Improved culling systems.
* Better management of large numbers of world objects.
* More efficient vegetation rendering.

 

These changes are particularly important for open-world environments where thousands of objects may be visible at once.

 

Asset Pipeline
The asset import pipeline has become more automated, making it easier to bring new content into the project.
This reduces development time and allows faster testing of vehicles, environment assets, and world-building experiments.

 

What's Next?
The next phase of development will focus on two key areas:
1. Further engine optimization for large open worlds.
2. Expansion of the road network and playable regions.

 

As always, many of the most important tasks are not immediately visible, but they provide the technical foundation required for future gameplay systems and content.

 

Thank you for following development. More updates, and technical breakdowns will be shared as progress continues.

 

 

June 18, 2026

 

 

More Articles …

  1. Post43
  2. Post42
  3. Post41
  4. Post40
  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10

Page 1 of 10

We use cookies

This website uses first- and third-party cookies to analyse and improve your browsing experience.

Cookie Policy
Information on the use of cookies

Cookies are small pieces of information that are sent to and stored on the user's computer hard drive through the browser when connecting to a website. Cookies can be used to collect and store user data while connected in order to provide the requested services, and are sometimes not retained. Cookies may be first- or third-party.

There are several types of cookies:

  • Technical cookies that facilitate user navigation and the use of the different options or services offered by the website, such as identifying the session, allowing access to certain areas, facilitating orders, purchases, form completion, registrations, security, and enabling functionalities (videos, social networks, etc.).
  • Personalisation cookies that allow the user to access services according to their preferences (language, browser, configuration, etc.).
  • Analytics cookies that allow anonymous analysis of the behaviour of website users and enable measurement of user activity and the development of browsing profiles with the aim of improving websites.

Therefore, when accessing our website, in compliance with Article 22 of Law 34/2002 on Information Society Services, for analytics cookies we have requested your consent for their use. This is to improve our services. We use Google Analytics to collect anonymous statistical information, such as the number of visitors to our site. Cookies added by Google Analytics are governed by the Google Analytics privacy policies. If you wish, you can disable Google Analytics cookies.

In any case, you can enable or disable these cookies by following the instructions of your Internet browser.

Cookie preferences
Necessary cookies

Essential for basic site functions and cannot be disabled.

3 cookies detected.

  • jbcookies (JoomBall!)
    Stores the consent given by the user on the website.
  • joomla_user_state (Joomla!)
    Preserves the user's authentication state.
  • joomla_remember_me_* (Joomla!)
    Keeps the session remembered for the authenticated user.
Analytics cookies

They help us understand usage and improve performance.

No cookies have been detected in this category yet.

Marketing cookies

They personalise advertising and measure the effectiveness of campaigns.

No cookies have been detected in this category yet.

Unclassified cookies

Cookies pending review or automatic classification.

No cookies have been detected in this category yet.