Ok I thought I read a thread (recently) that a particular service can't even be done properly due to loco power or something needing banking. East Coastway's missing track has no fix in sight either. It's things like this...
Yikes that is not a good look, to be clear from a customer side I don’t think anyone particularly cares exactly who is at fault and why a mistake was made, just that a faulty build was pushed. The lack of accountability is shocking, while it may not be a particular individuals fault per se there is clearly something wrong with the processes at DTG that lead to the wrong build being pushed at launch multiple times now. These issues can only be fixed if DTG accepts that the mistakes are on them and that they need to slow down and rework their processes so this stops happening.
It can be done, but it involves effectively driving both the lead and banking locomotives at the same time by jumping cabs continuously throughout the run
Clinchfield is a classic case of fire and forget abandonware that still leaves a bad taste in the mouths of many of us. Fixes to numerous issues were promised and those promises were promptly broken and are still out there to this day
You've said that neither are to blame, the problem is that ATS already effectively blamed DTG for pushing the wrong build so clearly some conversations are needed and there needs to be some transparency on when these issues are going to be fixed timeline wise, the promise of patches that seemingly never come needs to stop at this point. Either that or pull it from sale and refund those who have yet to refund the product. In the past DTG would post if a wrong build had been pushed, that hasnt happened and based off comments that you have made it seems that actually the correct build has been pushed so then ATS are using the wrong build narrative as a scapegoat, either way, both parties are to blame for what has to be one of the worst releases to date. But again, its time to get stuff fixed and give customers some transparancy on what that timeline looks like
That's a issue too, there's also a mainline service that softlocks because it encounters one of the shunting ones. There's also a portion of the line where there's no grass for a whole mile or two. Clinchfield is a very broken route, I'm just not sure DTG's ever committed to fixing them in the same way they committed to doing the horns.
That does make me wonder if that would fall foul of consumer protection laws, since the product is defective and does not work as intended. Like they advertise the 24 hour timetable but it softlocking is a defect.
Sadly Clinchfield is long gone from DTG's *to do" list and far down the list of forgotten content. However it was not without charm and still is on an enjoyable route to revisit a couple of times a year. Probably more than we will be saying about this Class 90 in 5 years time! (Clinchfield was released on 8th April 2021).
They didnt add train faults(one of the selling features off tsw 6) to the trains they promised they would add post release(class 802, nj alp-46, nj multi levels, db ice-t, db 146 and db 185) and we re 6 months in, i doubt they ll touch the older routes again
Now, thats not a very 'productive' attitude (lol /s of course) With all of the bugs/issues that have had my attention, i had forgotten about the Class 802. Thats a first party core TSW6 train, from TSW6's core launch - if thats not getting fixed, what hope does anything else have
It's not just the 802 that has problems. The class 220 Voyager has broken cab lighting and the AWS sunflower doesn't work at night. If they are Rivet Games products, they are never getting fixed.... just like the class 385.
Here's a thought DTG. You have so frequently released broken dlc that people no longer find it prudent to purchase content for the game until it has been confirmed to work. At that point, a sale is often closer than not and people who would previously buy your content at full price are getting it discounted, or by the time its fixed, not even bothering with it. You are the publisher, release is your responsibility, trying to present the situation as blameless comes off as childish and amateurish. This shoddy approach to releases is costing you potential sales, not to mention the additional man hours required to fix problems post release due to greater complexity. It's time to take some responsibility and sort out your process for releasing content for TSW, or you will undoubtedly pass the cost of these mistakes onto consumers which will depreciate your sales even further. Regards, a player that would prefer this franchise didn't die due to incompetence.
I’m not an expert, but is it difficult to ensure you are delivering the correct build when making the product available?. We’ve heard this a few times, so I’m just confused how this can even happen?
If QA is signing off the final release build the surely they would hand it direct to retail team for release. The fact that retail are getting the wrong build repeatedly makes me suspect that QA aren’t signing off the final build and its devs passing the build over to the retail team which would imply QA aren’t testing the final product before release. Unless this ‘wrong build’ is just an excuse and DTG are knowingly releasing unfinished content which haven’t passed QA, either due to internal or external pressures.
It might just be me, but I start to get the impression DTG are losing interest in their flagship product. On a recent stream (might have been the Czech route) the EP even admitted he hadn’t had much involvement prior to demonstrating it. I get the issue about toxicity but it is now rare to even see the CM’s on the forum and to some extent if you’re putting out an often flawed commercial product, it’s no good going in a huff when people post something caustic about it or the management of the thing (given of course that personal attacks are unacceptable). From Steam DB it looks like Wonders Of Sodor has not entirely been a runaway success so where do DTG go from here? They certainly need to tighten up, starting with QA brought back in house and testing of British products actually done by people in the UK, preferably with some knowledge of how the railway works. And certainly no more rubber stamping of inferior products just to get a bit more cash through the door to pay the Chatham rent!
I’m not sure Steam Database is that great a yard stick for children’s games, when mine where younger anytime they wanted to play computer games, the internet was disconnected and they played off line and I’m sure I’m not the only parent who does that.
That’s something else I don’t buy either, these are DTG owned and managed forums. The toxicity needs to be managed by them, retreating to discord is not the ethical way to deal with the problem and they have a responsibility to other forum users to stamp it out. Again I feel it’s more of an excuse than an issue they care about. Because if I was in charge and was getting staff telling me they where suffering from abuse on social media I’d be hauling the director for social media and community director in front of HR and demanding they do their jobs or clear their desks, not telling my staff to hide away from the problem.
It isn't, and even with automated release pipelines, it's something you always triple check manually. Releases are always tagged with dates, versions, build numbers, etc. But the fact that they didn't release the correct builds as a "hotfix" as soon as ATS notified them it was the wrong one makes me doubt some of the explanations we have been given.
I beginning to wonder if ATS where contractual obliged to release in FY25 and this is as far as they got with it by the deadline. As as you say if it’s just a wrong build they could have hot fixed it within 24-48hours with ease.
For those on PC if you want to get more out of the 90 a new updated 2019 TT for WCMLOS is out over at the TSC website, adding in 16 playable services for the 90 as well as some scenery adjustments to bring it up to modern day with new PIS and the reposition of Morecambe station to the the tiny thing it is today!
Hi everyone, Well, it's been a week since this supposedly faulty version was released. If that's really the problem, where is the final, correct version, the one we should have had on March 30, 2026, properly tested and verified ??? Best regards, tof
