Wcml Preston To Crewe Discussion

I have to say this seems to have been the worst JT launch by a considerable margin, notably it's their first TSW product on Steam to have mixed reviews.

https://store.steampowered.com/app/..._Preston_Route_AddOn/?curator_clanid=45756039

I hate saying it, but I really do think JT screwed up here, the route looks amazing in screenshots, but if the comes at the cost of it running well on mid to low-end machines I'm not sure it was worth it.

 

Please note this also happens on Preston-Carlisle when resetting physics, not sure if it's just the AC electrics or all locos. It is therefore not a new thing with this Crewe-Preston route.

 

There air braked mate

 

Dont there tell you on the wagons I cant remember.

 

I suspect the real issue is that we're reaching the limits of what the core is capable of in its current form.

There must be common factors between the blurry routes that can be identified, assuming the will is there to fix them (instead of, say, jumping to UE5 or some other engine and starting all over again). If not, they could still be used as guidelines to scale back on devs ambitions to mitigate this happening in future...

If that's not realistic, how about looking at some of the more problematic recent features that were introduced and backing them out of the core to free up machine resources? I wonder if all AI trains have to simulate the suspension physics, for example - would there be a way of stopping that, if so? Or how about removing the random faults? They don't really bring anything to the game IMHO. If we're already struggling to run the latest routes, what new "features" will TSW7 bring that'll break them even more...?

 

Someone correct me if I'm wrong, but isn't it the last letter that dictates breaking type, i think its say the wagons designation is HKA and the last letter being a means air-braked.

 

Yup, A = air brakes ... more details here: https://www.ltsv.com/w_ref_codes_tops.php

 

Meant to say in my earlier post that clearing the shader cache really made a difference on my PC - FWIW, it's an i7-10700 with 32Gb and a 6Gb rtx2060 GPU - nothing fancy, but it's good enough to run TSW. I wasn't experiencing any major problems with the new route but thought I'd do a bit of spring cleaning anyhow, and I was surprised by the difference after clearing out the shader cache. PITA to do it, mind, as you have to reboot a couple of times etc, but it was worth the effort. YMMV of course

 

Some interesting thoughts in there, for sure. Ther performance isn't great on this route. In fact, I was somewhat shocked on my first run just how bad the performace is. Felt like SPG on PS4 with its 10-15 FPS all over again.

It needs to be adressed. It's no use having a super impresssive route that runs poorly (or not at all for some). I certainly don't have any easy answers as to how it can be addressed, but this is not a standard for the future. JT have undoubtedly a lot of goodwill given their general quality and choice of vintage traction that DTG almost ignores, but that goodwill can also be lost. It would be a shame if their otherwise high qulaity stuff gets dragged down by performance.

 

I've posted what we're doing in the feedback thread for the route but we've making some headway with things which is great.

 

It's a bit harsh to blame JT for performance issues which arise because of DTG's crappy coding abilities (I'm surprised they aren't a government contractor at this point) and the poor core optimisation allowing bad performance issues to arise on consoles and low spec PCs.

The only performance issues that I experienced was some brief stuttering during my first run through Warrington but it's been fine since and also low resolution textures at distance due to DTG's so called "fix" or "optimisation" though that needs to be reversed as sitting at Crewe and not being able to read the blurry number of a 47 parked three lines over is unacceptable, but again, that's on DTG.

 

FWIW if you’re on PC clearing the shader cache does make a difference. Personally it runs well for me, but it sounds like I’m in the minority sadly.

 

On my PC I don‘t have any problems to run the route. Only little stuttering and no blurry textures. I have a five years old PC. Frankfurt S Bahn route has much more stuttering than this route.

 

In the process of giving that a try. Even if it just squeezes a few more FPS - though of course I guess the downer is that TSW will be rebuilding the shaders on every route the first couple of times you run them.

 

That's the flash mob choir Easter Egg.

 

Runs fine for me as well… doubtful you are in the minority, Just those that are having problems are doing the most comments as they should. The rest, we are enjoying the route

 

Bit the bullet and bought preston to crewe (series s)

Was expecting constant crashing at crewe so i spawned an 87 to see how it was (not sure exactly which service) and it ran smoothly on 4K with only a slightly low FPS. Switched over and am now driving 9K03 part 1 from Crewe and almost perfect frame rates and no blurring through crewe

Granted it definetly seems there is some static stock missing but it's a lot better a result than what i first expected. I'm pleasantly surprised by this as i expected it to run horribly on my series S after what i heard about series X.

 

Also bit the bullet thinking I can give it a couple of runs and refund if it runs badly.

I have an Lenovo Legion Pro 5 with i9 14900HX, 32gb RAM, RTX 4070 8gb laptop card, 1TB SSD. I run TSW at 1440p with 150% screen percentage and everything except the sky on maximum (Sky on very high). I also run Jetwash's tweaks at High. I limit FPS to 30 in game and run Nvidia Smooth Motion.

I did a run from Crewe to Preston and started at Crewe at around 45-50fps so not too bad at all.... After leaving Crewe this rose to 60fps..... All good till I got to Warrington where it dropped down to around 15-20fps so reduced screen percentage back to 100% and rose back up to mid 40s fps so I thought OK again. Had a look around whilst at Warrington and fps dropped right back down to 10-15fps. Went back in the cab and waited still no change....Paused the game for a minute or two and then un-paused but still at 10-15fps so saved and went out then reloaded the save and fps were back up at mid 40s again???

Carried on to Preston and again some big drops which then cleared up a bit and settled back at mid 40s fps which is still around 10-15fps lower than Preston on Blackpool and WCMLoS routes but I'm assuming the version of Preston has more on the tile with the extra branches in this version???

I then thought I'd see what it was like running into Crewe so spawned at Winsford on foot and spawned a 47/3 with some mk2f coaches and ran down to Crewe at 10:00 and got all the way in to Crewe station with fps not dropping below around mid 40s to 50fps.

Hopefully things will improve after a few more runs and I may try upping the screen percentage back to 150% to see if it's any better. (I'll keep this one route at 100% screen percentage for now via the relevant command in the GodMode .ini.



Also.... JT Benedict who's the Hale & Pace fan at JT then????? IYKYK.

 

"Right yew lot...Shut up, belt up and if you can't see the bl**dy exits you must be bl**dy blind!"

 

Thanks for the explanation. I didn't know that shunting signals could also look like this. I thought only the disc signals are for shunting.

 

LOL hale and pace, man did that just trigger a nostalgia bomb

 

I’m not trying to cast blame, sorry if that came off wrong from my side. I am in fact having a blast with the route (apart from the performance) as I had stated elsewhere. The many different threads make it hard to always give the full picture.

I’m on PS5, so no can do, but thanks

 

Are Wigan and Dordrecht twin towns?

 

Is there a Neutral Section guide as yet like there is for the WCMLoS route?

I think I saw mention of the same person doing one for this route but wasn’t sure if it was still in the process of being done or had been done and I’ve missed it?

 

Here it is:

 

Two things to note here, 33 reviews is hardly a sample size, need way more than that and also, it's since improved to mostly positive.

 

I've never left a review on steam. I think people are generally more likely to review if they aren't happy with a product.

 

What’s the difference between the red and green? The WCMLoS one was all in black.

The Facebook link doesn’t work as it says the post is no longer available so only got the image from the attachment.

 

Here's a fresh Facebook link:

https://www.facebook.com/share/p/196SNyG4p8/

Perhaps he decided to use different colours for stopping and non-stop?

 

Thank you sirs, for the links to the neutral section guide

 

I'm not claiming their exact sales numbers, I'm noting that the reception to this has been noticeably poorer than their other products on the same platform.

And on them being "mostly positive".

1: It's not for me, the reviews in the default review filter at the bottom of the page are, but then that's excluding non-english ones, and I see no good reason to ignore them.

2: It's still considerably lower than either of the 90+% recommended scores that the other two routes have on the same platform. And I see no reason to think that isn't reflecting a broader trend when JT have noted themselves many people have issues running this route, and are prioritizing performance fixes for it.

 

S’ok…. the image that was attached originally on here didn’t have a key. The images in the Facebook post have a key for the colours.

 

Trying to do a full Merry Go Around tour, what is the best way to do the banking from Warrington to Latchford, the 08s doesnt have enough power and doing it from the 20 seems impossible too.

 

i would ask how do you clear it but i will have a look later, i've only done one run but the stutter was bad compared to WCMLos but i haven't done any pc cleaning for a while

 

Depends on your graphics card I’m afraid - for my RTX2060 there’s an Nvidia control panel where I had to disable shader cacheing, reboot, delete the relevant cache directories (I used a 3rd party utility, can’t remember what it was but ping me and I can let you know if need be), re-enable cacheing and then reboot again.

Spawn on foot in the problem areas and walk around a bit (Crewe, Warrington, Wigan etc) then go for a run, and hey presto!