PC Boston - Providence After Update - Bugs, Glitches Etc.

The reason not every DB box is ticked is because then the dispatcher has to be calculating paths for every train all the time, which can overload it.

 

Appreciate that. So the use of "dispatch beyond" is kinda a lazy way of making trains do what you want so the timetable has a better chance of compiling. It has its places, but you have to know when and where.

 

Even after all the updates, why are trains STILL getting stuck on this route? It's cursed at this point I feel like lol
It's always in this Readville / hyde park area... They all just sit here at reds and eventually the trains on the mainline from Boston - Prov start getting stuck too... This is after about 15-20 minutes into free roam, after completing one MBTA service from Boston to Stoughton successfully.

 

we got a floating beans poster at hyde park haha

 

Cuz it's a big core issue regarding how the dispatcher does the pathing. One update won't fix everything since the dispatcher is soo large and complex

 

Yup I noticed that too . Even starting the day early taking the 5:59 Acela down to providence I noticed it.

 

So I believe the Boston route suffers from the same issue as Harlem. So I try Boston again spawning in around 445am and so far
Is is 0800am and no trains stuck. The same thing happens with Harlem and ran that route the whole day just rail fanning with no stuck trains. It seems that some services or just the specific time you spawn in. Depending where the AI trains are at would cause a pathing issue that then just starts causing other AI trains to not move and then you have a gridlock. I will keep running the Boston on XBOX X and see what happens.

 

So I tried several different ways and it looks like there’s an issue with one of the paths from one of the AI trains that comes from Boston and passing through redville. Is around 08:25am in the morning and it just becomes a stand off between 3 trains. The AI trains that comes off the main line then goes to redville gets there first and should be clear to go but for some reason it never gets the clear signal.

 

Saw something pretty weird today. I am doing MBTA 803 from Boston to Providence.

About a mile from 128 I passed another MBTA train on the track next to me (which is usually the Boston bound trains).

It had its headlights on the cab car, a driver in the cab car, but was heading TOWARD Providence. So basically running backwards.

I’ve never seen this before so don’t know what the deal is. I’m still playing so I’ll try and keep an eye on the map and see where he goes.

He passed me when I stopped at 128 and I snapped some pics, as you can see he’s heading southbound at speed with no headlights and the driver is in the cab car:

 

Wow... Reversing trains seems to be an issue in Boston lately. There is also the reversing ACS-64.

 

i’ve only ever encountered the stuck trains and gridlock issue on this route. thankfully so far i haven’t had this issue with NY-T

 

yup!! exactly! right around that time it seems to start getting stuck. i’ve always spawned in later in the day and notice multiple trains head to head on the stoughton branch as well. what a mess lol.

yeah, we’ve only had one update for this recently, but at the same time this route has been out for YEARS, so these issues are just so frustrating.

 

I saw this too. I was driving a southbound MBTA service, when at Readville I saw a train holding on the track that connects track 1 on the NEC to the Fairmont Branch. I was quite surprised as I have never seen anything on this track. After I passed, the train started heading the "wrong" way down track 1 (it was holding for a passing northbound service), then stopped to crossover to track 2 before Canton Jct. Another train at Canton coming off the Stoughton Branch had to wait for it because the train in question held on track 1 until I left Canton. After that the train kept following me and when I got to Providence it was still at it. Then I loaded a save I had made and walked back to the train when it got held at a signal. I couldn't take over the service, but I had tried to enter the "leading" F40, because I didn't realize the train was running backwards. Then, I spawned in at Readville at the time I had passed this mystery train... and it wasn't there!

What is going on here?

 

So to update on that backwards train…

He ended up stopping at a red just before Canton Junction. So I passed him again and did my station stop.

After the station stop I left and he crossed over to the “proper” track and ended up following me from then on. He skipped all the stations though so I am assuming the service is a dead head probably to Providence.

Then at Attleboro problems started. I made my station stop. He got a red light behind me and waited. I finished my station stop and left.

The train behind me never got a signal change and just stayed at the red. I continued to South Attleboro, and Providence. He stayed stuck at the red. Eventually another fast train (I think an Acela) came up behind him and that one got stuck at a red too. Timetable now broken since the southbound track is blocked and it will just be cascading reds.

So like others mentioned there are definitely still red light/dispatch/signal issues on the route.

I haven’t had one of my own player services impacted yet, but if you try to play multiple back and forth runs in a single session it’s likely only a matter of time before your game gets ended by a stuck AI somewhere. Kind of a bummer cause one of the fun things in this game is starting a day and just taking over multiple trains back and forth (I like that on SEHS and BML).

Pic of where he got stuck:


Acela stuck behind him later on:

 

For those who are interested, I just checked and the service I drove when I saw the mystery train at Readville was #803. I tried to drive the mystery train again, this time from the cab car, where the engineer was sitting but still couldn't take over the service. Can also confirm that the train gets stuck on track 2 at a signal guarding a crossover just before track 3 joins back to track 1 north of Attleboro. The Acela eventually pills right up behind it, #2155, which you can take over but which had no driver at all, in either end.

So many questions.

 

Today I wanted to try picking a MBTA service and see how long I could stay with the same train back and forth between Providence.

The answer was only 1 trip. I took MBTA 815 Boston to Providence during evening rush hour. Made it to Providence in decent time (I think 2 minutes late). Set up the cab car and waited until 17:19 when its new service would start (MBTA 828 Providence to Boston).

Could never make it out of the station. First signal after the platform was red. I stopped and waited about 10 minutes, contact signaller etc to no avail. Was stuck on red. No trains nearby, the closest one was an inbound MBTA near Attleboro.

But trying the same service by spawning into it from the menu had no issues, light turned green as soon as I opened my doors at platform.

 

MBTA 816, cabcar going northbound on approach to Route 128 I'm getting slowed to Restrict 20 and then having to get signaller approval to pass red at signal 2164. I've checked the map and there's no service ahead of me until at least Ruggles.

As soon as doors are shut at Route 128 I immediately get Clear 90.

 

Dispatch Beyond strikes again

 

Today I had an interesting event at the Boston track. At one stop of my personal train, the Acela express approached me from behind. It is interesting that the express was released by the ATC security guard into the occupied track section. I don't know if it's a mistake or the correct behavior of the track safety device.

 

Multiple occupancy in a block is a correct system of NORAC. It's normal.

 

Scenario Cold As Ice cannot be completed with all safety systems enabled.

Final stop at Boston South Station is impossible.
Stopped at the red signal 2070 ft from stop marker but check out South Station...

 

This route is still so broken. Doing another Journey run last night in the MBTA cab car. Not only are the doors not responding to anything other than direct opening and closing on the train side, passengers are just walking/clipping through the closed doors anyway. Not only that, stuck at Boston South, the passenger unloading circle finally completed, but won’t move on to the Lock Doors prompt. Really is a pile of buggy crud, should be pulled and given a total rework.

 

Update… on attempting to finish the scenario loaded the save. Passenger progress had reset to nothing but toggling doors open and closed failed to start the moving circle. Totally borked, 25 minutes of my life wasted and this is yet another Journey run on Boston that can’t be finished.

 

I gave up completely, uninstalled it, and reinstalled the TSW2 version.
I'll most likely continue doing the same for any route that gets a TSW3 downgrade.

 

The save doesn't work for me on any routes, I have given up on it for now, I would like to know what sort of witchcraft those who are having sucessful saves are using! Maybe it just doesn't work on some systems.

The only two issues I have with Boston Sprinter are the weird lighting in some of the tunnels and the very quiet track joint sounds in the cab car, which being as it is an old piece of kit should surely be louder.

I have to say I personally think the route looks very good in TSW3 with the new lighting and it has become a favourite.

 

Boston Sprinter now Boston Providence has come a long way. I agree about the funky lighting in some of the tunnels, but Brandon (cActUsjUiCe) has done an awesome job with the signalling. He’s now looking at ways to improve the timings of the timetable, which could well improve it even more. It could definitely become a favourite route of mine.

 

Well the scenario in question messed up before I saved it, on a straight play through. The only reason I resumed was to see if the final step could be salvaged and it couldn’t. Must admit, one of my least favourite routes - might kick it off, free up a bit of space for XP12!

 

Just ran MBTA Stoughton #903. Could only get a silver medal (6,962 AP). Gold requires 7,250 AP. As soon as I opened my doors at Stoughton, the service abruptly ended.

Getting to Stoughton I was delayed significantly on approach to Route 128 due to a red light (presumably a dispatch beyond issue) as I couldn’t see any train in front of me on the map. I ultimately ended up in Stoughton around 4-minutes late.

These delays cost a significant amount of AP due to the delayed arrival/departure times.

 

That is good to know, if the timetable is revised and matches the very good signalling it will be a very good route.

 

I have been having crashes. To desktop

Verified game files now updating video drivers.

 

Updated video driver yet hung and doesn't crash to desktop anymore.

I had to sign out of windows......

I turned graphics setting to LOW but it crashed all the same. Same place in the training.

Crashed to dektop this time with Unreal engine feedback popping up......

I tested Dresden route and it doesn't crash.

 

I figured it out.....

 

Hyde Park seems to have no NPC's (passengers)