Route Midland Main Line - Feedback Thread

Directly relating to the above list:

• TPWS activated approaching Nottingham (on the C line, approaching the crossover to the A line) during the "Chasing Yellows" scenario. This was immediately after passing a signal showing single yellow at about 50mph. This should be easily reproducible.
• I've had one crash approaching Leicester in the small hours of the morning. This had been a regular trouble spot before the first patch. I had not played this route between the first and second patches, but I understood it to have been addressed by the first patch. I have also been able to approach Leicester without a crash, during the day. This seems to be an intermittent problem.

Additional bugs noticed so far:

• AWS magnets activating in both directions (giving Clear or Warning indications in the cab) on the Reversible line between Leicester and Syston. The ones applying to signals for the opposite direction should be suppressed.
• AWS magnet on the Up Slow approaching Loughborough, applying to a Morpeth warning, indicates Clear when the signal in advance (which has its own magnet) is clear. It should be a fixed magnet that always triggers a warning.
• Speed signs have the wrong sizes of numerals. This is especially noticeable on Morpeth warnings, particularly in the Up direction approaching Syston. There's also a sign in the Leicester throat which shows a differential limit with both speeds identical.
• Passing Syston in the Down direction on the Slow line, there is a spurious short section of 20mph track limit at the point where the bidirectional line diverges into a double track.
• Banner repeaters are very dim, both during the day and at night, to the point of actively being difficult to read. They should be visible from a similar distance as other signals.
• Several signals still carry a lit shunt signal below a main head, which is contrary to British practice. This should be replaced by a call-on signal which only illuminates when needed.

All of the above are on PC/Steam. I verified the files yesterday afternoon with no discrepancies found. Ryzen 2700X (liquid cooled), 64GB RAM, Radeon 6750XT 12GB, game installed on SSD.

 

When Spawning into game on foot in timetable mode, scheduled freight services do not appear. This is on PC Steam version and is repeatable. Spawn in to service mode using on foot icon to spawn in 5mins before any scheduled freight service in the timetable list at the appropriate station/location to get an example.

 

There are still no class 66 services in timetable

 

On what platform

 

Crash near Syston Station just after passing the 20 warning board. Service 2D25p with the 158. On PS5.

 

Here we go then. A day of driving MML and let's see what the update has achieved......

1. Crash at red light 0.8mile outside Nottingham on 0608 Part 2 of Etches to Nottingham HST
2. PIS on Platform 2 at Leicester still showing destination of London Paddington for services when they are northbound
3. Emergency brake application on the 158 leaving Leicester and 3miles from Syston on the 1328 to Nottingham
4. Another emergency brake application on the 158 0.6miles from Nottingham on the 1328 to Nottingham
5. Emergency brake application on HST 4.1miles from Loughborough Junction on the 1635 from Leicester to Derby

So, we have 3 different emergency brakes, a system crash and the PIS hasn't been fixed. All of which were supposed to have been patched I think.

It is a massive shame as really enjoy chaining services together over the course of the day but this is simply not possible with MML in this condition. It will go back on the shelf again until these are all fixed and until then I will be cross at myself for the £30 I spent

PS5

 

I think the patch is great and it shows Skyhook care for what the community want a fantastic route to look like

However, I have one caveat with the patch though:
Why did you change the PIS font on the 158? Before it was small and using 'sentence-case' lettering but now it is big and uses upper-case lettering, and I personally don't like that, can this be changed back to default please

My solution:
Go back to the original font with the 'sentence-case' lettering and just increase the size a little bit as it would look a bit better than seeing 'NOTTINGHAM' on the front of the train, I'd rather have 'Nottingham' like previously but rather than having it too small, increase the size a bit or even make it scroll like on the ScotRail examples up in Scotland

Any thoughts are appreciated and I hope this helps a bit with feedback too

 

I rode these things on an almost weekly basis back in the 1990s. The large, upper-case text is a feature of the segmented LCD display mounted in the cab window, and is entirely prototypical. That's why they changed it.

 

Even nowadays? I would have thought it would have been what it was before or the scrolling type but OK, thanks for the clarification

 

Just drove Leicester-Nottingham-Derby-Leicester in one session (three distinct timetable services), during night hours. At 2.8 miles approaching Leicester, got a crash. This is on a well-resourced PC as previously described.

So far, I've been able to arrive at Leicester successfully during the day, but not during the night. This could be a clue as to what is wrong.

 

Ive turned the DSD on you still cant reset the DSD when it goes off using the controller, I am on PlayStation 5 and I was driving the HST on East Midlands

 

XBox One X

Can’t make your mind up scenario is completable but the stop marker at Spondon is still in the wrong place halfway down the platform.

Derby County football ground is not present. Not a biggie but I have seen a screenshot from someone else (probably on a different platform) where it is shown.

 

PlayStation 5

Getting emergency break application northbound and southbound at Mountsorrel on the HST

 

When on the outside of the class 159 you can't hear the aws or see it light up

 

They will need to know what platform you’re using, Xbox, ps4 etc

 

I'm definitely not getting this on the PC. So there is still a difference between platforms in this respect.

 

Likewise. I've played through all of journey mode and a few random services on the PC/Steam version and the only issues I'm still getting are the spurious AWS when going the "wrong" way between Leicester and Syston, the HST and Mk3 numbering issue, the odd night time lighting in the Mk3s and the misplaced stop markers in "Can't Make Your Mind Up". I think the off-map destinations on the PIS boards are OK, but I honestly haven't looked at them closely. The point being, as a Steam user I have a perfectly playable route with some minor annoyances left over. It's evidently a different story on console, where there are some big discrepancies.

 

On PC, have now run 6 random timetable runs with the HST and have not encountered any AWS or TPWS issues since the last patch/hotfix. As noted in the post above, there are a number of non-play related issues which could be fixed, but the route seems to play fine which, for me, is the main reason I have TSW.

 

I think we’re seeing a common denominator emerge here….. update patch worked for PC but not consoles and those items not fixed on PC appear to not be in the patch notes.

Can somebody with a PC just go to platform 2 at Leicester and tell us the final destinations of the northbound services? That may be the clincher

 

Same here. All TPWS and signalling issues WERE fixed in the latest patch for PC Steam (but apparently not consoles).

 

Just checked and seeing Sheffield as destination for a 1007 service, but nothing past that. Most interesting, the AI train arrived, but the doors did not open.

Once this train left, 2 more services appeared on the PIS, a 1024 for Nottingham, then a 1035 for Sheffield.

Another question, is dynamic weather working in this route? I am using it starting with clear and nothing changes for the entire run. I mean, this is nice seeing how fast weather changes in the DTG routes.

 

Dynamic weather is 100% working on PC.

 

Well, there's still a bunch of unprototypical signal heads/aspects. That's an early known problem that I'm still seeing, and I'm almost sure that it was claimed to be fixed a while ago. Perhaps I should go back and look at the older patch notes.

I still need to try driving the 158 a bit. That's where I previously saw most of the TPWS problems, on the slow lines and approaching the low-numbered platforms at Nottingham. I'll also get to see the various improvements that have been made to the unit meanwhile.

 

I don't know if any PC players who use Epic or the Windows Xbox store have commented, but would be useful if someone could have a look, as I think all of the posters in this thread on PC are on Steam.

 

I can add to the PC/Steam crash issue when approaching Leicester at night. Ran a 158 service from Nottingham to Leicester (the last one you can take in service mode after 11 at night that isn't ECS) and got the same crash. I was 2.1 miles outside of Leicester. Only thing I can think I was doing is that I had switched to an outside camera for a bit, and the moment I switched back to interior view is when it crashed.

 

I'm playing this route on PC and I can honestly say that it's largely problem free, except for a couple of quirky speed limits ( one 90 mph in the yard ).

It's really quite well-modeled.

Even the night lighting, while not great, is better than BCC and Cathcart.

And I'm getting to like the 158, it has good acceleration and braking and excellent track sounds.

 

If that's service 2D62 Lincoln to Leicester, then I just ran that myself with no problems. If it's at all relevant my PC is Windows 11 with a Ryzen 7 3800X, RTX2080 Super 8Gb, 32Gd DDR4 RAM and I'm running TSW from an NVME SSD. I don't recall having any CTDs from this route and more generally TSW3 crashes very rarely for me.

 

I'd like to add my two cents to the crashing problem. I said this in the other thread already, but I'm afraid it may've been lost in all the drama. I'm playing on PC/Steam, and overall, I experienced 6 crashes on the route. This is 2 times more than I experienced in all the 900+ hours playing all the other routes combined. Looking at the playtime, a rough calculation shows that for me, crashes on MML happened about 100 times more frequently than everywhere else on average. That's pretty significant.

Post-patch, I've driven 2 services on MML. Amazingly, both of them resulted in a crash and required a reload. I don't remember which exact one was the first (I think it might've been 1B53; it definitely went to Leicester). The second one was 1D90 (terminating at Derby). Both are HST services, in case this might be relevant.

 

SeventeenF, I will run both today and see what happens. I am also on PC/Steam.

 

Just ran 1D90 without any problems. My computer specs are and I run with all settings maxed. This gives me a fps in the 40 range with, as is normally the case for most folks, stutters. Guess should add, I run no mods, though will put the one from LM and company in once released.

Intel Core i9-9900 @ 3.60 GHz
32.0 GB installed RAM
1 TB SSD HD
4 TB drive
Video
NVIDIA GeForce RTX 3070
8 MB GDDR6 memory

 

I ran 1D90 with no issues. But I have had no crashes on MML since it released; and no issues other than the typical stutter.

PC/Steam
Ryzen 7
RTX 3060
Settings Ultra / V-sync / fps limited to 59
Engine.ini foliage and shadow distance tweaks

 

Prior to the patches I did experience the TPWS and AWS issue noted, but not since.

 

The 50mph section approaching Loughborough in the Down direction (Slow lines) is still unsignposted. It begins roughly where I'd expect to see a Morpeth warning for the 40mph limit through the station, and there is a corresponding AWS magnet (inappropriately keyed to the signal in advance), but no sign whatsoever. A progressive reduction of 65-50-40 should be subject to a Morpeth warning, as would a single reduction from 65 to 40mph.

Point blades are still missing at Nottingham, between platforms 4 and 5. I don't think these are the only missing blades, but I'll have to look for the other places I think I noticed them.

 

I don't think it's a problem with particular services. For me, both services finished fine upon reloading a save (I still have a habit of saving often from TSC). This looks more like general instability. It also looks like crashes happen more often towards the end of a service, especially when entering Leicester/Derby.

 

I decided to run another HST from Leicester to Nottingham since the release of the patch. Since the release of MML, both before and after this latest patch, i have NEVER been able to complete a HST service that arrives into Nottingham without the game crashing, and that still persists today.

i also has the AWS/TPWS trigger in the exact same place as always, on the fast northbound line after Barrow-upon-Soar station before Mountsorrel sidings. Again, this happens on EVERY trip heading north in a HST with AWS switched on.

i play on PS4 (PS4 Pro)

the problems i've stated above happed on EVERY trip, but this trip on this occasion was 1D52 London St Pancras - Nottingham (Leicester dep 17:48, due into Nottingham at 18:20, calls at East Mid. Parkway at 18:04-18:05)

i had the weather set to light clouds in September (custom weather not dynamic weather)

but for me on PS4, it doesn't matter what service and what weather setting, the AWS/TPWS always triggers in the exact same place, and always crashes in the exact same place. If it's a HST and it's heading for Nottingham, i can guarantee it will firstly emergency brake, and secondly crash completely. I have tried approx 15-20 different services that are due to arrive Nottingham, all have the exact same outcome

i honestly hope something can be done about both these issues (incorrect emergency braking and the entire game crashing) as for me it's unplayable in its current state


also to add please: after the last two patches/updates, the AWS 'ping' sound when passing clear/green aspects is no longer audible on Class 158 when using external camera

 

for some reason i can never senr bug reports/support tickets, it never works from my end, so i can only do so via this forum, hope that's still alright!

 

Are you expecting to release another patch for consoles?

 

On my PS5 it often crashes near Syston Jct regardless of if I'm driving a scenario or timetable service.

 

I’m concerned that the crashing is not going to be able to be fixed despite DTGs best efforts.
If that is the case then for PS players at least, we have been sold a dud and wasted £30 of our hard earned money in these troubled times .
It is currently unplayable and if that continues, could we possibly be offered a refund or a online voucher for another route ?

 

Game crash on 2D10 timetable for the 158 ps5 reported via the ps system

 

Glad someone else mentioned this. I have had a suspicion that Dynamic Weather seems to be a lot more reluctant to change than it used to be. Not sure even if it is a general or route specific issue or even an issue at all? lol Anyone else noticing it?

 

I did a run over the weekend and started in light clouds and it changed to rain as I went along, so its working. I just think that SHG has adjusted it so its not as abrupt as it has been in other routes.

 

Yes, I think that is the case. You might have to play several timetable services in a row to get a noticeable weather change, which is significantly closer to how weather usually behaves in the real world. But it's still not randomised at the start, which would be the next logical step - but is a core DTG thing.

 

Does anyone have a list of what was actually released in the patch and what we were told was going to be released.

As on Xbox Series X I still have a bunch of safety system issues that I thought were fixed and don't seem to be.

Mainly controller still not acknowledging AWS or DSD. And random emegency breaks with no speed change for miles away.

 

That's not gonna happen since dtg has never done it. But also the argument of why only PlayStation that gets that. If for one, do it for all.

 

Agree , any platform that the game is unplayable.
I would rather the game was fixed to be honest . It has great potential.

 

Haven't seen rain in days