I bumped into Paul Calf departing at Blackpool North. On a more serious note the route is good with nice detail. Was expecting it to be a little busier but its no issue. The only bugs ive seen are these: The passengers look a little ropey for some reason (see above) The passengers don't embark and disembark on the pacers Ive seen some passengers disembarking from the Class 47 being beamed up into the sky like the enterprise was sitting in orbit at Preston.
It gives you a Steam key and then you download as normal through Steam and it is permanently added to your Steam account so there shouldn't be any faffing about with future patches.
I'm not sure where to post this, but ordinarily when a new DLC is released Content Creators club is swamped with fantastic liveries and scenarios, but I've not noticed any featuring the 142. Am I just missing it?
There's another outside toilet at Salwick by the signal box. You'd think the signalman could at least buy some loo cleaner! the wages weren't that bad back in the 80s!
Regarding the crash at Preston, mine didn't crash but I got a menu flash over where all the controls wouldn't work. I pressed the windows key and re-maximised the game and it all worked again since I was approaching a red into Preston the light had just changed to a yellow but I still got a spad and end of the scenario!
unfortunately after more service runs I just couldn't deal with the passenger issues. Also I know the raildriver was mentioned late but thought it was just the pacer affected. I tried it on the 47 and it didn't work either. honestly the route looked great but i can't deal with the broken passenger issue so I refunded. Hope to come back soon after a fix. I will pause on getting any new DLC until the passenger system is fixed
Yes, I hear you. I'm still mulling over whether to get this route. I was really excited a few days ago because of the classic stock, but, if I can't use the RD, the route becomes largely unplayable for me. Why oh why would JT make such an elementary mistake? Dealing with passenger issues is a way of life with TSW, but it does seriously affect immersion if they behave idiotically or they are simply missing. So, we wait for the promised post- release patch and keep playing NYT, which has its own passenger problems. Such a frustrating game. You have to be really serious about trains to put up with all the BS.
Spotted a couple of spelling mistakes on the 142 destination blind - 'Morecombe' should be 'Morecambe', and 'Middlesborough' should be 'Middlesbrough'. Aside from that, really enjoying the route!
That is why I can't just keep buying stuff from DTG when we are still dealing with the issues in NYT and on top of that is passengers issues At some point you have to "say not this time". I knew that once the honeymoon period is over I wouldn't be able to just look the other way
This route is incredible so far. So much detail, and alot going on all the time in terms of AI. It is so much fun. One issue I am encountering is that the mastery tile won‘t show up. I have earnt it and the progress shows as completed, I have also ticked the box, but it just won‘t show up. I‘m on PS5.
I have played so many 'simulators' with so much worse underlying issues that many of these really don't phase me. Not that I'm defending the state the game gets released in at all, some of the offerings are real bad, but I think that's why I'm not anyways so bothered by them. At least they, for the most part, work '
So in a nutshell we weren't made aware of Raildriver being required until after the route had been completed and singed off. We are working on sorting out a patch to fix that ASAP along with the mastery tile fix with other bug fixes coming in a separate patch later on.
Just sitting at Preston for a bit watching the comings and goings is worth the admission price alone in my eyes. Having travelled and worked in the area its spot on.
The passenger system in this game is fundamentally broken- tbh i wish there was a menu option to toggle them off completely. I think DTG needs to redesign passengers from the ground up.
Jupp, one of the core features they need to work on! Immersion breaking everywhere, as it affects every route. Fantastic to drive an empty ICE train for 1h :-D The superb work from 3rd parties like JT on Blackpool or TSG on Niddertalbahn doesn't help if the developer of the software is not able to fix fundamental features.
Really appreciate your reply. I intend to purchase the route the moment that RD compatibility is implemented. Thanks.
Honestly, I'm looking at refunding it while I'm still within the window, the RailDriver has been and is built into TSW2 & 3, and now 4 how this was not a requirement is beyond me. My rail driver does show the speed of the train that is it, and even that little LED display is flickering. And then there is a weird artifact effect in the video, the recorded video doesn't show it so I sliced it an editor to show I see at times. There are Pathing issues, with what I can only describe as people wearing a bad costume, ie; male passengers are all sporting what looks like a fake orange Mustache from a costume shop, and the hair looks like a plastic afterthought on some, I know the '80s ware weird and the punk rock era and when cheech and chonk were up in smoke. And there is the Beam Me Up Scotty effects as they magically just appear or disappear. Yes, I know this is about the trains and all and they look good and bouncy ride and all, the fan even works, WoW man that's far out man, but all the cars and trucks are sporting grey windows as they are spread out to make it look like people park and ride at the train station and elsewhere, and that all lends to the immersion in IMHO or it at least should be all part of the experience, but it just looks not good. JT support took care of a purchase issue I made a mistake on directly through their website some time ago and for that, I give them high marks.
The passengers appearance is nothing to do with the route. That's just what TSW4s passengers look like, you'll see the same on NTP, and TVL. That visual tearing in your screenshot looks like you don't have V-Synch on or something. Certainly not doing it on my end.
The visual tear doesn't happen with other scenarios or timetable routes from other DLCs, this is the first I have seen this effect, yes I do have Vsync off. I do understand the passengers for the most part looked just a bit off on more than this newest DLC where it just looks more exaggerated.
I fully understand the feeling of those who look at things like passenger behavior and such as effecting the game for them. Some have said in many route threads that this makes the route unplayable and they have either not bought the route or are refunding it. This is your right to vote on how you feel via the wallet. Please keep in mind as you post your feelings that there are those of us who play the game for the driving of the trains and, unless, a bug/issue causes problems with driving, like NYT, we don't even notice a lot of thses external route related problems. I probably get out of the cab very rarely, so I don't even notice these problems, including passenger behavior.
Does that include the Preston crashes please, Benedict? Kind of key to decisions I make in the next day or two.
Well in my case as with some others, the Preston crash is that issue and if I don't get an assurance as requested above it's being actively tracked down then I'm left with little option but to send it back for a refund. Believe me, last thing I wanted to do but can't be having the issue I described happening, or worrying it's going to happen, every time I play the route, regardless of how good it is otherwise. Not for £30.
SGTDRE As Fawx said, this is a tearing issue in your screenshot, nothing related to this route. Same for passengers. Also you should not blame JT for not adding RD support. I'm looking forward to it by myself but when you read the post from JT Benedict it is clear that DTG doesn't set any standards or requirements for 3rd Party content, that's the problem here. JT will give us RD Support asap and in comparsion to DTG I believe them that they will do it in a short amount of time.
Masterpiece! Just Trains team can be very VERY proud! It was asked before: how can i use Class 31? Do i just need the Class 31 DLC or is Tees Valley route also necessary? Looking forward to RailDriver support where missing!
You need both. The Class 31 and TVL were introduced back when loco DLCs were tied to their home routes.
What can I say that hasn't been said before. The route looks absolutely stunning! The pacer looks and sounds really nice to me and I really appreciate the variety of the included rolling stock. It's obvious that a lot of care and attention have gone into these aspects. It's just a crying shame that apparently not that much care and attention has been spent on signalling, particularly regarding approach control. Someone already mentioned the signal at the junction south of Preston when heading towards Ormskirk, but I get the impression that approach controlled signals haven't been implemented anywhere. For example, I was running a non-stop service with the pacer from Preston to Blackpool North (1M35). At Kikham & Wesham there is a junction where you need to go from 75 mph to 30 mph through the junction. All signals before the junction were clear and the signal at the junction was at green with a feather. I feel that should have been approach control from red. The only times I encountered something resembling approach control was only because there was a go via marker right in front of it with the signal clearing as soon as I completed that go via objective.
OldVern, I have not bought the route yet, and am watching what is posted here and agree UE crashes are a driving issue that I am concerned about, as well as no Rail Driver support.
So there's not been many crash reports so far (if people could forward them to us though that would be appreciated) we're keeping an eye out though.
I was on a Pacer tutorial and thought I'd taken a wrong turn from this route and ended up in the Lake District, how did this happen!!! Cheerz. Steve.
Would have been nice if the 142 was selectable on the NTP route. Appreciate that route is set approx in 1983 but it is not too far out in terms of dates.
I don't think the £30 comes into it frankly. If I thought my PC was hardlocking from freeware I would remove it immediately.
I have SOS installed but I don't see the 16 ton mineral wagons anywhere on the route. I even saw the BBA steel carrier wagons hauled by a 40 through Preston. I didn't know that they would feature.
Do you have a log file available (or screenshot of one at the least?), if so please send it on to JT support, we've had 2 other known tickets through to support with CTD's and we want to nip it in the bud if it is something we can control, be it a bad asset or something along those lines that can be controlled. We'll contact DTG with our findings if needed, as I say it all depends on if it's something we can control. None of our team, nor the sizeable testing squad suffered CTD's, on a variety of specs, and it seems to be limited post release to a very small amount of users, unless I'm about to be hit with 40 people all saying they get a CTD approaching Preston from Ormskirk! Aware from your other posts that you said it was a hard PC crash, in which case if you can't get a log file then a refund might be the only option for you, sadly.
I've just done 2 Class 47 scenarios, the shunting at Burn Naze and the 1S91 service from Blackpool N to Stranraer and both times the driver is in the wrong cab from the start, especially the passenger train, after loading it then gives you the right of way out of the station, it never states to change ends at any time, is this a bug, or, are the locos the wrong way round, or, do we have to do a quick dash from cab to cab, which should have been an on-screen instruction, especially, for non-British users. Cheerz. Steve.
Appreciate the kind words, though I can say for certain I did pay care and attention with the signalling, it hasn't been half cut! Sadly some issues do creep through, be it through knowledge of my own not been up to scratch, or because I made an error. The issue at Farington should be a relatively simple change. Regarding Kirkham, AWS wasn't in place on the route in 1986, my understanding is that it's not possible for TSW to have approach control functioning without AWS in place, but I will query this again with DTG's in house signal team. The same issue goes for semaphore approach control, it's not in the code of TSW at present. Should it be added then we can make the route backwards compatible.
I've had a bit of a loco bash the past couple of days, doing runs on all the locos, and although that Pacer is a lovely, the locos really do take centre stage for me. Absolutely loving it!
Just one more small signalling anomaly.....approaching Kirkham and Wesham from Blackpool South, the colour light signal protecting the junction onto the main line was green, good. Upon crossing the junction I was presented with a rather tall semaphore, capable of showing clear/stop or shunt (i.e not distant). It showed clear, no worries. However, approaching the platform, the end of platform colour light was red, which I don't think is correct, as there was no distant/warning for the red signal. The signal cleared upon doors closed. I've a feeling this maybe due to DTG's colour light and semaphores not communicating with each other correctly? Maybe could be solved by not selecting the platform signal to change to green when doors closed? Anyway, I guess it's a lot of work to change, but still hugely enjoying this immersive route.
no I've noticed that too it seems you can not upload your liveries onto creators club at the moment I've tried to upload one myself no joy
Further to those asking about CTDs and the like. We are now aware of 6 users who have had a CTD approaching Preston and it appears to be to do with a display board/PIS. We will need to speak to DTG about this as it may be out of our control. If its within our control then an adjustment our end will be made ASAP. These were all Unreal error crashes rather than a system crash resulting in full pc restart. We have seen one other occurance of this in completely different circumstances. (The user coupled two pacers together when stationary, so unrelated issue to that above). The aforementioned CTDs (not system lockup) have all happened approaching Preston, from both sides. I should state these are very isolated, but are happening and we are looking into them as a matter of urgency.
This is with DTG and we are on their case regarding this issue, no ETA has been provided other than that they are aware and a fix will be actioned.
Just want to say again how much i'm enjoying this route and share a few pics. Just finished up a little pilot duty at Blackpool North in the last one
Fair enough, haven't been that direction yet (to Blackpool North) so didn't realise this. For me, I'd 100% rather have unprototypical AWS to get approach control to work, but I get it that some folks wouldn't!
Yes, either way it's unprototypical, unfortunately. The best solution we could come up with has already been applied specifically regarding the approach to Kirkham from Preston and that is the go via for timetable services to force the signal to stay red. I'm not against adding AWS for colour signals, though adding it for semaphores for me personally would be a bit much. It's a shame 39a cant be applied too, having said that I don't have an issue myself and just drive to the distant signal aspect. I do understand there's a number who would like it and obviously I'd prefer to do it 100% prototypical if we could.
There was a roadmap or article a few months ago about the route that said that Rule 39A couldn't be implemented because of the limitations of TSW's signalling system.
We know there are flaws in TSW and adding the go via is a way to do the approach control but as I said in a suggestion thread I wish we could remove those messages from the HUD as I don’t want to know what’s coming up other than the next station stop. Having worked absolute block no semaphores had AWS but the colour light distance signals did.
