Yeah, a month of waiting isn't nearly as bad as 2-3 months when we might get a minor fix. I also wouldn't get any updates from devs for a week or 2. The next day is a really good timetable. So, yeah, this is a much better environment, and we don't encourage dev crunch either.
And there is the problem. We are all paying for an inferior product that doesn’t work as promised. I’m sorry but I feel AAS should understand that this is not acceptable way to work. Instead though there is no real incentive for it to be fixed. and as for many who enjoy it, there’s many many more who can’t get it to work reliably or who are incredibly infuriated by the mistakes.
I do understand this critique. It's one of those if we pull it we can't fix it, if we don't, we can fix it scenarios [you can figure out what I'm saying]. Right now, there are no plans to pull it, and AABS is working hard on additional fixes. They aren't happy with it, and they have profusely apologized to the community. I know DTG has too. I apologize because there isn't an easy answer here.
I think those who purchased it and enjoy it are on relativley high end PC‘s. As a player on what is currently the newest console on the market, I have wasted €36 on a release that I bought on the 21st of October and still have not had a single enjoyable run on despite multiple patches. So sorry if I don‘t agree with your sentiments here Candace. I‘ve uninstalled this DLC and will wait for a while and see how things are if and when we see fixes for this route, the core and many other forgotten bugs in the game. One thing is now certain, no more day one purchases from me. Learn‘t my lesson.
I mean people who own this route did only just receive a patch that was done and ready 'some weeks ago', so i dunno. You must be privy to seeing things behind the scenes that instill the confidence that we are clearly missing.
If you agreed with me always, then you wouldn't be human, you'd be a robot. It's fine, there's no easy answer here, and that's okay! I know what's in the works even if I can't say it. I had hoped we'd have this update a few weeks ago, but it needed more time and some further fixes before anyone felt comfortable pushing it out. Was it disappointing that the time got extended? Yes. Am I glad they waited? Also yes.
That does make sense.. Thanks for making the effort to answer our (at times) stupid questions! Just a weird place in TSW right now where alot of the community dont know where they stand, on multiple fronts.. discord vs fourms, the future of TSW (and our investment in it), bug fixing vs new DLC, ect Im quite new round here.. granted.. but you are the only CM I see down here in the trenches actually trying to help us rather then give us nothing but a PR blurb in response to a valid question, Or only posting when trying to sell us something! Personally I appreciate that!
Yeah, i call total BS on that to be honest. Definitely hope i am wrong though, nothing would make me happier than having to apologise for the scepticism, because it would mean that the game is finally improving. I sincerely doubt that will be the case though.
Hey, I told them on hire, "I'm blunt, and that usually throws people in the UK off, so a heads up, I'll tell it like it is," and they still brought me in. So I'll give some info that may help about TSW: We have the core game: completely DTG, and it will only be fixed by our teams. DLCs: If it's a DTG DLC, then we fix it. If it's a 3rd party, we will send the information that you send to us straight to them. They then decide what's a priority and what is not. (Obviously, game-breaking issues are going to be a priority) Some of the 3rd party devs, like AABS and Just Trains, like to be in the community and reply. Some don't, and that's their prerogative. Release schedule: So a lot of the DLCs/Locos are already in development and run on a schedule that is only modified when fixes come out or if there is a delay to fix an issue or issues. Community Team: We take most of the fire and vitriol, then give feedback and issues to the devs, so you'll see us on all the socials. I work a little more 1:1 Community Focused, while some of the team work more on overall community stuff like livestreams. We've all been working to be more visible lately because y'all requested that, and I personally think it's made the community better. Discord v Forums: This is hard. Discord is more instant and easier to manage, honestly. Forums are a little on the older side, but it has been great to see all the info posted here. The problem is someone may post an update before you reply and you won't see it.
Platform: PS5 Uncompletable Journey Mode Chapter: Learning The Basics Broken Scenario: GJL Class 350 Introduction The Class 350 Introduction still crashes TSW6 after today's patch, and the first journey mode chapter still cannot be completed. I'm also guessing that the Contigency Measures scenario has not been fixed either since it wasn't mentioned in the patch notes. Here's hoping we get a more complete patch for this route soon!
It may have been back-burnered for the other issues, but I will let them know! Thank you for the heads up.
Probably in a couple of months. Very unlikely to be before Christmas anyway. Once again, hope I am totally wrong.
Coseley into Wolverhampton 8 to 12 FPS I’m done with this route it’s a disgrace being released like this! It’s a joke!! All aboard studios will never get another £1 from me!
PC/Steam Livery Designer Hi candacedtg The patch made in November and December fixes one issue, but made another as the plain livery of what is originally LNR Class 350/1, LNR Class 350/2 in Interim LNR and BTP livery, despite some major elements such as the door colours, gangway front colours, and the livery in the fourth (and in case in BTP, also third) carriage, are still baked in, but make what supposedly a working custom livery for Class 350/3 ruined, thanks to the all-black baked-in paint on the first and the last carriage. For example: Class 350/1 Class 350/2 in BTP livery Class 350/2 in Placeholder (in this case, should be clean) livery Class 350/3 (which suffered the most, since it was once the only well-executed one)
One of two things happened which I cannot forgive, either the route was tested thoroughly and the issues ignored or the route wasn’t tested and released as was. To my mind, things like AWS magnets not working is something you notice when testing. The AI SPAD issue, surely that came up in testing? The announcements issues, did that really not come up in testing? So, if we are left with the conclusion it was tested and that they ignored the issues and release anyway then either AAS or AAS and DTG took its customers for fools. Go on, tell me which it was! I dare ya!!
Thanks for the reply, I do understand everyone needs paying at the end of day, and it does seem as all aboard studios are trying to fix it, however as the fault lies within the product they have made unfortunately, Personally you shouldn't be paying them to fix a product which should not be in the state its been in, like with the santa fe pack that released recently and the mixed views on the quality of the locos paintwork and accuracy maybe a more thorough QA check should be inplace and upcoming dlc put on hold till current dlc and other issues are resolved. As a long time player of tsw and tsc I would prefer that more than new dlc that doesn't work.
Nothing else to feedback after finishing my run into Crewe last night. I do feel the route and maybe trains would benefit from some more optimisation in particular the poly count on all those trees and other vegetation which I still think is hitting performance. However even on my potato PC (I7 4770, GTX1650) apart from the usual jitters which are more of a core issue, I didn’t hit any slow down into single FPS. However that’s not to acknowledge there aren’t issues which still need to be addressed. As regards refunds it is a very subjective issue. When I first bought the route, due to having played TSW itself for some time before testing the route it had gone over the 2 hour Steam limit. Fortunately the patches have pushed it beyond the point at which I would want my money back. However if there are issues on the lower end consoles which cannot be addressed then that is a slightly different matter. You could argue it should never have been released on those platforms in the first place and if they can’t be addressed, even with drastic measures such as removing a percentage of the scenery for those versions only, then it should be pulled and those unhappy offered a refund or credit note. Under UK consumer law a product must be fit for the purpose for which it’s sold and you could argue this still applies to software (though has always been a grey area) if it doesn’t perform properly and the vendor can’t fix it. Sob stories about paying people’s wages don’t cut it in the world of business - you make money by releasing a robust fully tested product in the first place, not adopting the “Trotter’s Independent Trading” motto from Only Fools and Horses…
i tried a suggested work around of changing quality to HD rather than 4K as someone suggested but i still cannot play this service on the series X
I'm not on the greatest spec system, but since the patch yesterday the performance on this route is bad. It used to be playable with the odd slow down, but fps across the route now is pretty low, with single digit counts in place - Crewe and around Wolverhampton specifically. The area around Smethwick also seems to be the same as before performance wise. Whatever fixes went out yesterday seem to have made it worst where performance is concerned.
Just watching The British Ace’s video from this morning and appears the blurred textures on PS5 are still there but seem in a much better state than previously - ie they do unblur themselves (with all layers enabled). Suspect any further improvements are probably on DTG’s core rather than anything AAS are able to do from their end.
Hi candacedtg So if DTG repairs its own DLCs, why haven't any further updates been released for Dresden–Leipzig? And you didn't even answer my question there. So it looks like we won't be seeing any more updates for Dresden–Leipzig. Because that's DTG's normal procedure: whatever comes out gets maybe one update, and that's it. https://forums.dovetailgames.com/threads/bahnstrecke-leipzig-–-dresden-feedback.93913/
Had a quick run on Xbox Series X at lunch (didn't have time to get a full line run) but had no blurry textures. Still get a hard crash on that mid afternoon southbound Pendo service from Crewe though (sorry, forget the code).
Well, this is about B2C, so right now I'm going to move back to B2C. Not dismissing you, but I need to keep this on topic.
Back onto textures, could they not just split out the 350s in the layer menu somehow, so that the obviously problematic ex LM livery can be removed. OR disable the substitution of it etc, pretty much anything to get it out of the route. Kezz is pretty insistent that it’s not a problem, yet it’s by far the worst offender for this issue. As a foot note I’d like to say that AAS saying this route works for the majority of players & it’s mainly problematic on Series S is hilariously disingenuous. Any doubts I had about AAS being done over by DTG are completely alleviated now.
So just done a run on B2C same service as yesterday.. Today with the Core update.. I have more blurring in the cab of the 350 then I did yesterday.. Id say 75% of the time the cab labels were blurry today.. (text round dials, speed limit sticker ect) Where as yesterday they would reduce quality briefly.. then pop back for the most part! Also some weird flickering with the windows on the 350 that again were not there yesterday.. cant attach video as its to large so attempted some grabs.. obviously these dont show the flickering! But doing show the layers that flicker 'on and off" So something in the core update has 100% changed something on B2C today!
The issue is that anything that is close up to you like the train in front of you is meant to be high detail but if the pool of textures loaded in at that point is maxing out Unreal reduces the resolution of the most high res textures which is what is right in front of you at that time. Not impossible that the ex-LM 350 is contributing but Kezz is not necessarily wrong either based on how Unreal works and the fact it usually kicks in around the Smethwick area likely means that's where the optimisation focus needs to continue.
I’m not saying nothing else is an issue or gets effected, rather that particular unit is the worst offender.
Sorry if already been asked but do all the 350s do same jobs? Or do only go to certain places. Thanks
First time playing with new update PC/Steam/no mods Service Mode, 9W10 Crewe-London Euston 0943 Class 350/3 Pantograph is down upon loading in at the beginning of service at Stafford (not sure if intentional). Tunnel/bridge reverb is still mostly missing, especially north of Wolverhampton No other real issues and ok performance until I get to New Street. Arrival is at platform 4a with a red signal (legit as there's a train in the next section 4b). Stop at 3yds from the marker and no dice- keep in mind the signal (BM6604) is not visible from the cab this close to it. Try to roll forward but don't stop in time and SPAD. Deep breath, ok, i had a stop at Smethwick Galton Bridge so i reload checkpoint. Back to New Street after a few min and this time i stop as close as possible using external cam and it works- hooray! On time at 10:27. To then be greeted with a 6 minute "wait a moment"...grrrrr ....but i notice that the next instruction is "couple to vehicle", so ok i'll see what this is about. Chill and listen to the ambience of BNS announcements (admittedly very nice). Ok the time comes to 10:33.30 (ahem) and i get the "couple to" instruction for the train ahead of me. The signal remains red. I contact dispatcher. "Denied. Train in next section". I lose my patience and quit out. So like an hour and a half total to not even complete the service. After calming down i load into BNS on foot at 10:30 and head over to platform 4. Sure enough 9W10 is at 4a and at the appointed time it gets the shunting signal, couples up to the train at 4b, and departs on-time at 10:35 to Euston. So, who knows i guess lol Oh also since i did it twice in a row, the game definitely starts the 10mph section approaching BNS platforms about 10 yards before the sign. Not sure which is in the correct spot. Just don't believe the devs or QA ever play these services themselves. You'll never convince me.
I have noticed that the date for the weather seems to be locked to June 5th no matter what the actual date is. Could this be changed please so it does like other routes and show the actual date of the run. Like today in December 3d.
Apologies if this has been fed back, but two random services I’ve loaded have the same issue where the route in the description is not the what loads in. e.g 2G05, supposed to be Crewe to Birmingham New Street, loads in at Stafford… not sure if this is supposed to be the case and they have some shorter services by design that start mid way through, but the service description said it runs Crewe to BNS… then the actual destination is displayed as Crewe and the service announcements state calling points to Crewe, even though I’m running in the reverse towards BNS? (PS5 Pro)
Performance has improved quite markedly on PC, I haven't read the thread so I'm sorry for console users if thats not the case for you. There are still bugs of course but this would be an acceptable release product for PC at least. Major bug: Take service 2W60 in the 323, all of the platform announcements announce backwards then forwards, then backwards then forwards, and so on forever. It kills any immersion one might experience. Minor bugs: AI Pendolinos have their lights switched to day-time at night-time AI LNWR Trains only have their destination displayed on the front pis the back pis always says LNR
At galton Bridge what trains run on the above platforms. And what is with making us stop 2yds from a red signal at Birmingham and not registering if we dont stop dead on.
thanks for the suggestions on the cause for this (and previous replies!) I guess the main feedback is then that these should show as running Stafford to BNS in the service description… and also the service announcements and PIS should reflect the correct direction of travel. Only ran between Staffs and Wolverhampton, to dip back in and see the updates. No blurring so far but probs need to try a longer session
