Thought I wasn't going crazy thinking back to TSW5 and not remembering it having issues with duplicate locos, so I reinstalled it and compared to TSW6 with exactly the same DLC installed on both. And yes, it looks like showing locos in a non-broken way is now lost technology
I would love to hear an explanation for why this has happened as even if it doesn't impact performance, it is still annoying to shuffle through so many duplicate locos. I remember back to the Salzburg-Rosenheim stream when I first noticed something like this and asked Matt why there were three identical 111's, but he didn't know at the time. Hopefully someone knows why this happens by now.
I’m not sure why locomotives can’t simply be included as part of the core game, with DLC purchases effectively unlocking them for use where appropriate. The current system, where the same locomotive can be loaded multiple times because it appears across three, four, or sometimes even more DLC packs, seems completely unnecessary. I can’t imagine repeatedly loading duplicate versions of the same loco has any positive impact on performance. It also makes the menus increasingly messy, confusing and cluttered. Seeing multiple versions of essentially the same locomotive is unsightly and, honestly, becoming quite irritating. A more streamlined system where locomotives are managed centrally and DLC simply unlocks the relevant content would make the whole experience much cleaner and easier to navigate.
I think that including all locomotives in the base game would massively increase the minimum download size of the game regardless of which DLCs you owned. Instead, the locomotives and routes could be seperate DLCs where if a new route included the same loco as a previous route, the same loco DLC can be bundled in the store pack. If the route brings an update to the train, then update that loco DLC. There are a couple of reasons I can think of for why they didn't do this though. It may require a lot more testing to update locos, and there are many subtle differences between the same locomotives from different packs. For example the new Nuremberg talent 2 vs Dresden talent 2.
I would like to see an extra layer of UI, where you pick Intercity or BR Blue (as one example) first and then you get all of just them, that would clean it up a lot. But the main problem is all the duplicates of exactly the same locomotive, rather than essentially the same locomotive.
Yup, pointed this out in another discussion. Several irritating factors with this; the obvious having to actually pick one of these, then that the issue has persisted since 2 weeks after launch of TSW6 & completely ignored by DTG, then that we have a massive optimisation problem ongoing & nonsense like this is still getting into the game, then finally it compounds & highlights the issue of re-including the same loco from another DLC, but as a separate, duplicated asset. Ultimately it’s a laughably irritating aspect of DTG thinking a new menu makes a new game, but they ignore the issues with it & just add things that are sidegrades & downgrades. If DTG insists on tasking people to the menu, then they need to be tasked with fixes & improvements, not playing with colour pallets & coming up with new examples of hostile UI.
I understand that but any increase in the core game size would be offset against reductions in the DLC’s download size. Surely this would be better for both the state of the game and also individual players who are using storage space for the same loco if they own multiple packs. I appreciate that there’s often subtle differences but then these would feature correctly labelled. Maybe someone with some more technical expertise can shine a light on this. However, from a players perspective the current setup is counterproductive. At the very least the game should allow players to hide duplicate locos on the menu screen if there is no real desire from the games creators to address this longstanding issue which will only get worse the more DLC’s are released.
That is a huge number. It must be quite a hassle for users aiming to complete that route to track them all down. The service frequency counter is also behaving erratically.
