Ok, I do have a little niggle that maybe JT can sort out and that is with audio. When you open the pacer cab door into the passenger cabin you can clearly hear external audio such as engines idling in other platforms. Now, close the cab door and stand in the passenger cabin and amazingly there are no external sounds, even with the passenger doors open. This came up whilst I was doing a live stream tonight as I went to demonstrate the guard panel and opening/closing of the doors using the panel.
Having spent some time at Preston station after spawning in to timetable mode on foot, I cant help noticing that more than a few AI trains have the driver at the wrong end of the loco. For instance there is a ballast train that pulls out of Preston shortly after 9am with the driver happily sitting in the rear cab with not a care in the world. Not a game breaker as such but it does tend to ruin the immersion so I was wondering if the guys at Just Trains are aware of this problem or not? this was on PC Bought direct from JT site. (Steam version)
I saw someone mention a Mastery issue earlier in the week but can’t find it now. Is it a known problem that when completing tier 2, the station still doesn’t appear on the route? At first it wasn’t even showing up in the mastery tab as completed but after a few re-boots it was there and I have ticked it so should be showing?
Britain doesn't use short tons, but long tons and metric tonnes (which are much closer to each other); I assume TSW reports metric tonnes in the pause screen and service preparation screen. The data plates/panels that are the most convenient references would list long or metric tons, depending on era.
You should give at least an approximate location for this. None of us have any idea which 20mph restriction you're talking about.
Ah, Farington Curve Jn. But I see 20mph signs in both directions here - when entering the Ormskirk branch it's by the crossover of the Blackburn branch which is the first 20mph element, and when exiting the branch it's some distance clear of the sprung catch points under the bridges (marked with the triangular S sign).
Thanks for the information, but can you manage to find the advanced speed reduction warning signage before that 20 mph speed limit sign, I know in UK there should be a speed board saying you should be reducing your speed prior to the speed limit effective point, especially for this big drop of speed.
Getting the crashes coming in to Preston from ormskirk on the PS5 now as well. It had also got the buzzer locked on from the previous station so was hoping it would fix itself at Preston. This was while doing 2P06 on the ‘Pacing Around’ journey.
Watching intently and longing to buy this route but will wait until Rail Driver is added and these issues are somewhat sorted.
Does the old bug on 47 is fixed? At some moment she stops fully release the brake and stuck at 20 and you need to hold overcharge forever or she will pump up it to 20 again.
There is only one advance speed warning sign on the entire route - for the 15mph limit at Blackpool North station throat. That's how it was in the mid-1980s, as Morpeth Warnings were not widely deployed until much later. In 1986, in particular, the guidance as to where Morpeth Warnings should be installed had only just been updated in response to the second overspeed derailment at Morpeth - there was to be a third there in 1994 - because the original guidance had somehow excluded Morpeth itself, and a lot of similar places, on a technicality. Notice also the long stretches of line not fitted with AWS, though there are some fixed magnets at strategic locations on the branch lines. This was also a feature of the time.
Incredible how there wasn't much in the way of safety systems back then, hardly any AWS, no TPWS/ OSS etc. Just relying on the driver to observe signals. Couple that with fog/snow......
Out of interest were there any Class 45 hauled services in the area as that is emerging as a common factor? At least if the problem is occurring on the fixed hardware and firmware of the PS5 then it debunks claims of failing PC components or even my own theory of Windows Updates running behind TSW leading to the route crashing. Obviously seems there is a major issue here that JT need to get to the bottom of with some degree of urgency.
Well there is one known crash relating to station display boards which I don't believe is unique to Preston either, this seems to occur at random when entering or within an area with Display boards one of which happens to be Preston. I highly doubt the Peak itself is causing a crash, any occurence is more than likely a coincidence given its been out for nearly 3 years now never having given an issue.
Got a full game crash running the pacer from Preston to Blackpool North (Xbox One X). Not sure if this is related to the general TSW4 crashes on this platform or something route specific. Disappointing as it was my first ever run on this pack.
If it is the display boards, then as a temporary measure they need to remove these and get a patch out ASAP. As regards the Class 45, do we know if it has been modified in any way for this route or is it just a straight layer from NTP?
I am a complete layman here, but surely if it were to do with the 45, it would be a more predictable consistent thing. I enjoy driving the peak and so a lot of my mileage so far has been on it and I haven't had an issue with a crash yet, touch wood. Of course like I say I am a complete layman in the topic. Also I took the peak for a spin on NTP and WCL in the free roam (with other TT traffic) with no issues, so wouldn't have thought it's the loco.
On PC, I'm not seeing any crashes at all. Take that for what it's worth, as I have more than the average amount of RAM and VRAM. On the subject of the departure screens at Preston and Blackpool North, I've noticed that services scheduled for after midnight get sorted before the late-evening services, when these screens are seen in the afternoon and evening. The entries are being sorted by their 24-hour time rather than by their actual (scheduled) order of occurrence. The latter would be more logical. I do remember how these screens were set up (at least at some other stations, eg. Leeds and Lime St), and the present implementation doesn't match. There should be some general Departures screens (eg. at the entrance and in the waiting rooms) which show a listing of ALL trains from ALL platforms. Any screens specific to ONE platform should show a detailed description of just the NEXT train from that platform. There wouldn't be any screens that show a listing of future trains from any single platform (or pair thereof). The total number of unique screens would be limited, as there was a central computer with a bunch of Teletext video chips, from which the video signal was distributed to all the screens in the station. Rumour had it that it was a collection of BBC Micros wired together…
The departure screens at Preston Station main entrance show all trains from all platforms when you first spawn in, but as soon as they have to switch (because a train departed), they suddenly only show Platform 1 departures, which stays like that until you load into the route again...
No the Class 45 hasn't been touched in over a year if not longer, it is just a straight layer from NTP
Had my first crash just now. Ormskirk to Blackpool South, just before reaching the 30mph section approaching Preston. PS5
A funny thing happened to me when running the 0Z03 spoon from Ormskirk to Blackpool North. On passing the Go Via at Kirkham South the top left HUD disappeared, but the top right HUD stayed. (I'm on minimal HUD, so nothing at the bottom.) I drove on without time/ objective / speed / gradient, which didn't really matter as I knew where I was going and could still see the upcoming speed restrictions. Got stopped by a signal approaching Blackpool North station, which cleared after a minute or so, upon which the top left HUD reappeared as if nothing had happened
That's where it tends to happen and again, PS5 rules out it being outdated or life expired PC components. JT really need to get on top of this, with deference to those who haven't (yet) had an issue as the route gets more mileage on customer PC's and consoles the problem seems more widespread not just a handful of users.
I spent about 7hrs non stop on it today (no football) catching trains from Preston to Blackpool North/South, Ormskirk, spotting at Preston etc. Not a single crash, only thing I did notice was stuttering was getting worse with each journey, that'll be down to memory though. Night time was fantastic, best lighting I've seen in TSW. Still not too happy with the sounds though, Pacer is far too quiet and can't hear it at idle and the departure whistles and 47 horns are just waaaaaay too loud!
Have to say, this route is 10/10 bang on, outstanding work from JustTrains & lot of trainspotting in Preston, would love to see JustTrains work on the BR Class 37 & 20 on BR Blue livery as a DLC add on pack
Yes, I agree these pis screens are not prototypical, very odd to list all trains from that particular platform that a screen is on. I noticed at Preston that there appears to be duplicate entries (separated by, usually, only a minute or so) for trains bound for Manchester Victoria, throughout the day and it was listed on 2 different platforms that way:
JT Benedict JT Thomas Hi there, massively enjoying the route but there's things that need to be addressed. In case it's not being mentioned here (but reported in the General Discussions) Service 0B01 Blackpool North Shunting You must couple up your 08 to this consist, which is placed (yes I know it's not manually placed but datatrack-related as it's a service and not static) too close to the buffers leading to insta derailment as soon as you're coupled and SimuGraph kicks in. (The same issues plague the Class 31 pack consists layering onto GWE.) As a workaround, I'm just spawning at Blackpool North on foot @7:45, seeing that train arriving and boarding the 08. This time, it's a 47-hauled train - stopping before the buffers. I guess it's a datatrack mismatch, and therefore rooted in the game core calculating wrong stopping points / overshooting during timetable interpolation.
So today I went Past Class 47461 while doing a pacer run and when I did some research on that Loco I found out it had the Wrong name as 47461 should be names Charlies Rennie Mackintosh, and 47471 should be named Norman Tunna G.C.
So I've put the pacer into a custom timetable I'm creating, and every time I run the simulation the logs are just spammed full of the following: LogScript: Script Msg: Attempted to access index 1 from array 'LeftRVDoors' of length 1 in '/PBO_BR_Class142/Simulation/Components/BP_Cl142_DoorManager.BP_Cl142_DoorManager_C'! Haven't seen this on any other loco I've used previously, it doesn't seem to actually be causing any issues in the simulation, or in the game. Just thought I'd point it out.
Please don’t reduce the quality of the landscape and detail levels on this route to cater to consoles (or indeed lower end PC’s) that are suffering with performance problems. I’ve had no crashes and the route is surprisingly easy on performance for the detail levels. Please please don’t nerf that. I really think it’s time DTG consider separating the PC and console versions of this game, to everyone’s benefit. That aside, as I knew it would be, the DLC is a triumph. Congratulations to all involved, and if this is a first attempt I cannot wait for what’s to come in the future.
On a slightly different note, definitely think the Pacer bounce needs taming. Took one of the Cummins engine sets out of Penzance and getting up to 70 MPH coming through the curves at Long Rock it was doing a cross between the APT and those bouncing cars from GTA San Andreas. Really spoils the effect, suspension is too soft.
The suspension works on the unit’s native route which has been built specifically for it. I’m sure that will apply to all new DLC going forward. That it might not be perfect on another, much older route that is not set up for the new system is really neither here nor there IMHO. If they change it to work on WCL then it won’t work as designed on BPO.
Have to agree to disagree on that. The layer on WCL is official not something knocked up in free roam or scenario planner. Someone, somewhere must have tested the results and seen it is rolling around like a bouncy castle in the wind!
How can you disagree with it?! Official or not, unless they were to make a WCL specific version of the 142 (not gonna happen) then for them to adjust the suspension physics on the unit for it to work satisfactorily on that route it would break the way it works on BPO. That’s not something to agree or disagree with, it’s a fact. If I understood the stream(s) correctly (and I’m pretty sure I did) the track itself needs to be set up to work correctly with the new suspension. JT are not going to go messing with the track on a Rivet route because I’d imagine; a) they can’t b) they have no incentive to c) It’s likely a lot of work d) it would probably have consequences for all other trains used on that route This is just another example of the way this game has been designed coming back to bite everyone on the behind. It’s not ideal but I think you’ll be whistling in the wind thinking it’s going to change.
I’m not at home so can’t check - does the slider in the settings which adjusts the lateral movement also affect the bounce? I have it set on 50% on all routes as any more than that I find the way the Driver is thrown forward when you come to a stand unrealistic. I find the 142 bounce quite mild, so I wonder whether that’s related?
Fair enough, then why bother adding the layer to WCL? Best thing as noted in lctrrjip’s post is to turn down the sway effect a bit see if that tempers it. On a positive note, the Pacer is rather good fun on WCL as, bouncy bounce aside, you can get a sustained 70 MPH thrash.
I suspect the answer to that is that if they hadn’t people would be playing merry hell about ‘missed opportunities’ etc. Hopefully turning the head-sway down a bit solves the problem. Failing that I’ll bet there are some ini commands you could apply to WCL only using GodMode which might help matters.
The game is a triumph on PS5, only the last 3 miles into Blackpool North suffer any kind of slowdown, and the crashes reported in this thread are mostly from PC players. I've yet to have a single crash on PS5, if I do I shall just reload the game and continue enjoying the route. I agree completely that they shouldn't reduce the quality, but seperating consoles from PC wouldn't in any way help reduce these rare crashes. If anything it would result in twice as much work to fix anything and which do you think they would prioritise?, the PC version that modders can fix for them?, or the console version which can only be fixed by the devs?
The Pacer on WCL bounce is exactly as I remember it in real life, 70 mph being thrown around as the engines are screaming. Great fun
I guess in an ideal world, rather than just the planned on/off toggle for the suspension they could add a slider for intensity, that way we could just turn it down a bit for tricky routes. Having said that the pacer is going to be the outlier here, as I don't think anything else on the rails has ever been as bouncy, so other trains with the new suspension will probably just behave quite nicely regardless of the track they are put on.
I'm yet to see an IC livery 47 turn up in game, it's a shame 461 is in IC livery, would of preferred that (and all the named 47's) to have been in BR Blue. Speaking of named 47's, It's great seeing what turns up, many of the names I had forgot about! Also nice to see the big named plates e.g. "The County of xxx" ones. I hope JT go one better and release a pack of all named 47's in that era, would happily part with a few quid for it too.
