Take it easy. It's not like they are fixing stuff that is broken, it's perfectly playable as it is. Have some patience.
That was my initial reaction as well, but then I read the change log and saw that the update for PS would have got rid of the updated Audio files. So it would have gone back to how it was upon release. So as annoying as it is, I think it is the right decision.
This is exactly how patch notes should be. This is all the community and player base wants. Communication, transparency and consistency.
Great work, especially impressed that certain signals have been fixed, shows it can be done fairly quickly.
Yes. THIS is how you do patch notes. DTG take note. If anything, it shows the full extent of the work that has gone on behind the scenes, whilst leaving us in no doubt what has changed. Win Win
Quick question for the route signalling experts, could this be applied to AF1 and AF3 as well (New Hythe area)?
Those are 2 aspect repeaters (Y/G) followed by 3 aspect signalling. Until quite recently the blueprints for AWS 'read through' the distant to the next main aspect, so you'd get a horn instead of a bell at those locations on MVL: AWS Horn > Distant=Green > 3A Yellow > 3A Red. These were changed by DTG in core, but MVL had to use SEH derived signals. We made the decision late in the day to use a work-around to make the AWS give the right code. As such those two signals were set up to give a failsafe aspect.
Many thanks for the explanation, good to see that accurate signalling is being employed as best as the sim allows.
Hello I don't enjoy playing this route because of the sound of a rail joint at every track circuit. There is an actual gap in the rail but there is an insulator that fills this gap, so smooth ride no clickery clack.
Unfortunately Networkers doesn't seem to like Dispatchers very much, they would just close the doors and go off without permission. Seen for the 10:08 service. Also after this happens an electrostar pulls into the platform and refuse to leave after closing the doors and giving signal.
It was in the release notes it would not work with networkers in dispatcher mode, only the two 375 variants that come with the route.
Any idea when the update patch for the ps5 is expected to go live, happy they didn’t just push it out and break stuff, good call on the devs
Firefly when will we see the AI 377/3 at tonbridge and 375/9 implemented on MVL? Would be much better to see southern at tonbridge as per real life. Also on console there’s still a small issue on the GSMR where at the end of the signal number the last number is stretched.
The 377/3 is down to Rivet to sort, so you would have to ask them. We've submitted the ticket, so it's in their hands, and has been for a few months now.
As a PS5 player I thought I'd chip in and say I sincerely appreciate you holding back the updates until they can be released in the right state for the game. But from the updates I've seen they are fairly substantial to a route that was already a 10/10 for me anyway! Look forward to receiving the update when it happens, and I hope DTG can follow on with holding stuff back until it is ready to be released for consoles.
Thank you for the list but in answer to “Issue with a duplicate collectible ID fixed allowing 100/100 collectibles to be attained” This is not the case as the one at Tonbridge West Yard is still not collectable! Only 99/100 are attainable.
I just wanted to say thank you to the developers of this fantastic route, had blast this morning driving this route with smooth performance on my 6.5 year old system, (i5 9600k and RTX 2080). It's my local area and the detail in this route is amazing! I also appreciate the detailed patch notes you provided for the update. Other Devs should definitely follow your lead on this one. Well done all round, look forward to see what you come up with next .
has anyone found an optimal weather setup to see a rainbow? i’ve done 4 services with varying amounts of rain, and 1 with dynamic weather (clear skies to start with, ended the service with a thunderstorm. of course i did), but am yet to see one