Why does a DLC sometimes take 18 months? The answer is much more complicated than many think!

Quite honestly: This is exactly where the actual misunderstanding begins. Many people imagine a DLC like a small extra portion. A bit of new content, a few models, maybe a new map, done. But this is almost never how development works in reality. Especially in simulations, a DLC is often not a small attachment, but a highly complex project that touches many individual areas at the same time. If, for example, you get a new bus, a new tram, a new route, or a new map, then it is not simply “something new” that is thrown into the game. Instead, this new element must be cleanly planned, built, tested, adjusted, and in the end connected with everything that already exists in the game.

You can picture it vividly like a house extension. From the outside, the new room may not even look huge. But before it stands, it must be planned how it connects to the old house, whether electricity, water, structure, and transitions work, and whether everything really fits together in the end. DLCs are exactly the same. A new route does not only need rails or roads. It needs signals, AI traffic, soundscapes, objects, lighting, performance optimization, timetables, logic, triggers, stops, interactions, and often also new systems in the background. A new vehicle does not only need a pretty 3D model. It needs sounds, physics, textures, animations, cab logic, displays, lights, doors, braking behavior, controls, error handling, and compatibility with existing content. And that is only the visible part.

In many cases, development begins long before players see anything of it at all. First there is often the question of what should even be built. That sounds simple, but it is not. Developers have to check what is technically feasible, what makes economic sense, which licenses are required, which reference data is available, and how large the project is even allowed to become. Especially with real vehicles, brands, or real routes, there are often also discussions with manufacturers, transport operators, or rights holders. This early phase alone can take weeks or months, without there already being a finished image visible to the outside.

After that, the actual production process begins. Artists build models, environment teams create maps and surroundings, sound designers work on audio, programmers implement systems, designers build gameplay structures, QA testers check for errors. And now comes the decisive point: These tasks may run in parallel, but never completely independently from one another. If something changes in the vehicle model, that may affect animations, sounds, or camera perspectives. If something shifts on a map, it may influence timetables, AI routes, or performance. Development is therefore rarely a straight line. It is much more like constant readjustment.

That is exactly why DLCs often take longer than people expect from the outside. Because it is not only about creating content, but also about making it work. Ideally, a DLC must not only run on one developer PC, but stably on thousands of different systems, often also on several platforms. What looks perfect on one strong test machine can suddenly cause performance drops on weaker hardware. Then begins the phase that many players barely see, but which often consumes an enormous amount of time: optimization. Objects are simplified, textures adjusted, lighting reworked, sounds remixed, scripts revised, loading times improved. This is exactly where weeks sometimes disappear, without the player later being able to immediately say: “Ah, so that is what those two months were for.” But that is often exactly what they were for.

In addition, DLCs are almost never created in isolation. While one team works on an expansion, the main game often also has to be supported at the same time. There are patches, support requests, hotfixes, console adjustments, certifications, maybe even other studio projects. That means: During the full 18 months, it is not always the case that twenty people are working exclusively only on this one DLC. Priorities often shift, teams are reorganized, tasks change. This also extends development time, without automatically meaning that people are “working slowly.”

Especially in simulations, there is another factor that many underestimate: credibility is created through details. A player notices immediately if a door closes incorrectly, a sound feels wrong, the brake reacts strangely, a display shows wrong values, or a switch does not function cleanly. The problem is: such details feel completely natural in the final product, but in development they are often one of the biggest time consumers. Because the closer a DLC is supposed to be to reality, the more detailed work is inside it. A single vehicle can have dozens of switches, displays, states, and special cases. A single route can contain hundreds of objects, signals, triggers, and sequences. From the outside, it often looks “like just a DLC.” From the inside, it quickly becomes a huge mountain of individual problems.

And then there is still the final phase. Many people believe that when a DLC is “basically finished,” the work is almost over. In reality, that is often exactly when it becomes really exhausting again. Now the final bugs are fixed, texts are localized, store pages are prepared, trailers are created, builds are submitted, certifications are passed, and release versions are secured. Especially on consoles, this can take additional time because approval processes are not completed at the press of a button. So even if the content itself is already finished, that still does not mean it can be released immediately.

If you put all of this together, 18 months suddenly no longer seem absurd at all. Instead, it becomes clear: A DLC is often not a “mini-project,” but a condensed form of real game development. The only difference is that players do not see a completely new game at the end, but “only” a new train, a bus, a map, or a route. But behind exactly this “only,” there is often an enormous amount of work.

Quite honestly: That is why the better question may no longer even be why a DLC takes 18 months. The more exciting question is rather how studios sometimes manage to finish such content within that time at all.

Would you have thought that a DLC is this complex? Were you aware of the many development steps? Do 18 months now seem more understandable to you? What surprises you the most?