I haven't purchased the new LIRR Comuntter map. But, I've heard other comments, about the core dispatcher problem. Not able to delete the problem train in journey scenario mode. AND paying the amount of money for an Add-on map V2.0 isn't satisfying to us, who loves this new LIRR route. So, Thank-You. I do NOW plan to email DTG about this concern. And why should we have to wait for a sale, until this problem is fixed. AND HOPE OTHERS DO THE SAME TOO.!!
I recommend you don't, because if you do, and if your angry and show them how angry you are, they'll report you to the Police, and threaten you with the Police, show “evidence” and even ban you permanently... Don't do it.
I once got stuck at San Jose after a long run from San Francisco, which I can tell you is very annoying and wastes lots of time. Thank you for your honest words on this situation.
Unless they rewrite the dispatcher from scratch I can’t see this ever being addressed. When it comes up on live streams Matt just shakes his head, shrugs his shoulders and says “Yeah, it sucks”. I don’t think DTG fully understands the problem it needs to fix. I’m now getting stuck in Scenarios on old routes, like the 353 DLC on Ruhr Sieg Nord.
I noticed these timetable issues really really bad in the Metro North Harlem Line scenarios since that DLC initially launched during TSW2. I reported the issues several times to Dovetail and they only fixed it fairly recently, like well after TSW3 was launched. Sadly it’s not a new problem 😢
You reminded me of this when you mentioned the Boston route toward the end of the video. Another dispatching issue is how it routes an MBTA commuter train ahead of most northbound Acelas at Attleboro, forcing the Acela to crawl behind restricting signals all the way into Boston. This would definitely not happen IRL and it's why the passing tracks at Attleboro are there.
I'm hoping the next patch we should get a proper fix! Still have hope it's a great route unfortunately myself cannot play either my game is crashing after every service SMH
There is still something wrong about london underground tube stocks But why is it cannot move when it's spawned in? And that's been a minor issues about Class 700 and class 377. And why they are not forgotten to fix this bug?! And so It must Have a passenger system While the train was spawned in. But why?
@@ShawnLamont1997 Exactly, what I hate even more about the ATC and ACES on the LIRR, the setting doesn’t even give you a clear warning it’s going to reduce to a lower authorized speed limit. For example a player is going at 60mph on the LIRR, when out of nowhere the ATC reduces the speed limit to 30mph, leaving the train in an emergency brake system not controlled by the player. I hate how MTA did this, it just not fun.
@@mtanycftrain3812 exactly… sometimes it shuts down the whole train and I have to completely reset it .. its a lot more fun when it’s truly a train simulator and not a simulation of how to work for the mta
For me on my PS4 everytime i play LIRR 2 , It crashed twice both with the M7 and M9 the second time was when I was at a read light before reaching Jamaica and had to wait till the signal cleared and as soon as I started to approach Jamaica station. It immediately crashed
This happend to me in southeastern high speed i just got thameslink class 700 and i tried trainspotting at gillingham and swanscombe and a train always after like 10 minutes just stopped at a red signal when nothing happened in front so after a while it delayed every other train im starting to think in that case that it was a signal failiure but tsw would never do a signal failiure simulation
Noticed aome issues with this game. The pacers(class 142)you cant open the doors sometimes or sometimes on free roam you cant seem to go without "service failure" when nothing has gone wrong and no signalls being passed at danger. Its a good chilled game but some things are really stupid on this game
The 142 doors need to be unlocked and opened via the guards panel above the door if you're inside, on the outside there's a hatch you need to unlock and push the open/close button. That other bug is usually because an ai service went through a red signal, at least it is in my experience.
