Route San Bernardino Line: Los Angeles - San Bernardino - Feedback

I'm sure this got covered a quite a while ago but the access to the highway still seems very narrow.

 

how do shadows work in this game. i'm at pomona station and looking at the lamp shadow you see the post shadow but when walking closer the lamp shadow appears. it like the lamp is two different object or maybe uv bug or something,

 

Unfortunately, I still can't get there, I just tried it on PS5...

 

Metrolink 335 gets into LA Union Station around 20-25 minutes late due to not meeting an eastbound Metrolink at El Monte Station as well as not meeting another eastbound Metrolink at the small siding in the middle of I-10 like it seems to have been intended to (I still went through the siding, delyaing me further).

 

I mentioned this on the previous page.

I'd like to remind you that this is no longer a core route, which means it's unlikely that they'll patch it.

 

Did you check that the random signal delays are turned off in your settings? It is a new "feature" that could cause this.

 

Same situation was in TSW5, which doesn't have any signal delays. The problem is that the wrong train have a higher priority.

 

This seems to be a core issue where the dispatcher can’t prioritize which train should be going first. It’s especially noticeable on routes like this where there are single track sections… but also routes like Boston Providence where Acelas are late because the dispatch pits slow commuter train in front.

 

Came across this issue at the level crossing just after leaving Fontana Metrolink Station.

 

This route has many level crossings where cars never stop. There is one near the east end of Kaiser yard where the spawn point for the cars in on one of the tracks, so if you're doing a switching service the cars spawn in your train and drive out of it over and over.

DW

 

Just another example of sloppy route building and QA which will never be fixed, as DTG conveniently forget these "old" routes.

 

It would be interesting if DTG could implement the system Metrolink uses in IRL especially at Fontana IRL they often have to cancel the crossing due to boarding than request it again but I’m not sure if DTG could simulate canceling & re-requesting crossings.

 

That is really bad as well as Pomona Crossing ..
Some of crossing look like it belongs on a Roblox server due to how low they are to the ground …

 

At the moment of departure from LA, all passengers simply fell out of the train and were left standing on the tracks.
I was asked not to be rude, so come up with your own epithets.

 

Claremont platform 1: passengers are walking along the tracks. It's not just one dude who got pushed on tracks, there's a whole pack of them. While I was choosing a nice angle for the screenshot, they all climbed back onto the platform and pretended as if nothing had happened.

 

DLC still unplayable in 2026,

Cars crossing closed railroad crossings, or railroad crossings that close while a train is passing.
A map riddled with visual glitches.

But the worst part is the performance—probably the worst DLC on the Shutters.
It’s the only DLC where a 1-hour service takes 2 hours because the game freezes for a full minute for every 20–30 seconds of normal operation.
It’s like watching a slideshow.

The updates do absolutely nothing, and the DLC seems to have been swept under the rug.
It’s not cool of Metrolink, who granted their license, to allow such a lack of respect for their virtual representation by leaving this DLC in such a state.
I hadn’t touched the DLC in a while because of this, and I see that absolutely nothing has changed and that it’s still being sold in this state.

 

Which platform? Works fine for me on PS5.

 

Yes, the first drive along the route is really tough. Many freezes, and they come one after another in some areas.
But even after two full services, the route is full of small stutters, and the sound suffers especially. This is sad because the overall performance is fine, the only problems are with the stutters.

 

Works fine for me on xbox series x

 

STEAM - PC

 

Personally, those 1-minute freezes drive me crazy, especially when I'm maneuvering the locomotive—or even worse, when the horn is activated during the freeze, turning that 1-minute freeze into a noisy nightmare.

 

There's something seriously the matter with your PC if you're getting freezes for a minute.

 

Only this DLC does that to me
Some Steam reviews seem to say the same thing

 

What is your CPU? Also HDD or SSD? Or maybe you using some heavy engine.ini tweaks?
Like 4-5 seconds freezes on the first run in some areas for me. But mostly around 1 second. I updated my GPU drivers so now I'm having shader compilation gala.

 

NVME SSD
I5 12450H
RTX4060
16GB RAM
Game set to 30 FPS Max in settings
My PC isn't a beast, but it meets the game's requirements.
Jetwash .INI with no custom modification

 

So it's a laptop. But nothing criminal. It should work well with this hardware. There shouldn't be such long freezes. Are the temperatures okay? No overheating, no throttling? Either the problem is in the engine.ini, or somewhere deeper in the hardware.

 

I don't understand why this is the only DLC that do that; on the others, my shutters last 2 seconds at most, even on the most modern ones.
I regularly dust off my fans, and the PC is placed on a ventilated laptop stand.
My GPU driver is last to date.

 

Are you using godmode? It's possible there's a problem with the config for this particular route.
The thing is that if you remove edited engine.ini now and switch back to the default DX11, the shader compilation will start over.
But you can try it and see what happens. There will be freezes when the shaders are compiled again, but then it will be possible to check whether a third-party file is to blame, or whether the vanilla game behaves the same way.

 

I'm going to try it without the .ini files tomorrow (UTC+2) and without god mode to see if it makes a difference. thanks for suggestions ^^.