I feel your pain i done hoboken to dover all stops had a door fault at every station and 6 wiper faults. And thats on normal setting. I think its a bit excessive
Unfortunately like dynamic weather and guard mode I think random train faults is another feature that will be permanently switched off or not used as it doesn’t seem fit for purpose and will probably never be. I’d be surprised if it ends up being a loved part of the game. Again first impressions are nice idea but poorly executed. The first thing I did in the game was to switch them off but I still got a random fault notice on a 150 service. So please DTG at least allow us to disable them from the game.
I really do think that features like faults or random events are going to enrich the game. But those features have been released in such a half-baked state that it's hard to warm up to them right now. Once the frequency is toned down a bit (or rather a lot), I'll gladly have some faults every now and then. Keeps me on my toes I'd also like to see them being added retroactively to existing locos, but that might be too much wishful thinking...
I am doing a run from Plymouth to Exeter St. Davids and I already got like 10, or 15, engine stalls, stopped counting somewhere along 10+ and I got faults set on normal ... I mean, if engines kept stalling like that IRL, the engineer would probably call for a backup unit lol
If I remember correctly, this is how the engine turned off even on the preview stream... one of them turned off twice during one stay at the station........
Today's update seems to have broken the fault frequency completely. Faults now occur every 30 seconds or more, on either frequency setting I disabled them completely now, to be able to even drive. Tested it on the BR 294. And I'm on PC/Steam.
Having read the patch notes, and driven the GWR 150 just now, I can't understand why the engine faults have not been reduced on the 150 as well as the Voyager? I have my faults on normal and had 3 engine faults before I even reached the first station. My main problem with the fault system right now is that it feels like there is no randomness. I am not sure if this is just because of the frequency being far too high but it feels like the game just throws you a fault as soon as it possibly can. Multiple times I fixed an engine fault to get another just as I went to move off, about 20 seconds after fixing the previous one. For true randomness you should have some runs with no faults for half of it or runs with a couple faults straight away and none for the rest.
It honestly feels like the faults on the Class 150 have gotten even worse since this latest patch, which is extremely frustrating. I jumped into service 2T19 from Exmouth to Paignton, and within just 6 minutes of driving, I’d already had 7 engine faults occur... :/
reading the latest comments I'm like daaamn... I was looking forward to playing the game today after work :/
PS5 ..... setting on normal So DTG really did it ...... Service with BR294 from Dresden Hbf to Friedrichstadt, within two minutes before departure ..... Fault Handbrake Engine off Control panel off ...... to start the engine it is necessary to turn it on..... Engine started,..... Handbrake applied Engine off ...... and so on, after five minutes when I did not start and Driver Assist windows kept popping up we ended it. ..... so currently unplayable
Same problem with train faults, unplayable because a very large number of anomalies in a few minutes.
It reminds me a bit of the old digital game Just wait for the hare, where the wolf ran with a basket from henhouse to henhouse and caught eggs... I ran around the locomotive in a similar way and it was really good, the faults were pouring over each other But still a good way to avoid blurring textures .......
So fault's seem to be broken, trying to complete a run with the following: - Class 150: - 6 engine faults between Exeter St David's & StarCross - 3 Door Stuck faults at Exeter St David's - ALP-45DP: -1 Panto drop fault before leaving Dover - 3 Headlight Fuse faults within 2 miles - 1 HVAC fuse fault within 2 miles Making the game undrivable right now unfortunatly.
whyyyyy... I was like... just get through the work and then have Leipzig Dresden bonanza afterwards... but if the faults have gone wild with latest update, I guess Hollow Knight or F.I.S.T. or sth will have to do :/
I agree with the others that it seems to be worse after the patch. Just took a Talent 2 from Dresden to Leipzig and the faults were going crazy. At least once every minute even with the low setting and sometimes 3 within 10 seconds. Luckily you can turn them off. Maybe it’s best for DTG to turn it off by default and label it as a beta feature for now.
And of course being Friday, highly unlikely any of this will get looked at let alone fixed before Monday.
Everyone can probably turn it off, so an update in the sense that it will be turned off by default is better not...so that something else doesn't turn it off again........ for a change, I haven't come across any TSRS yet, even though I have it turned on at Normal frequency, I'm going Dresden - Leipzig
Time out on TSW6 for now, then. Went to do a 294 run on Ludwigsbahn, faults set to low in Settings almost immediately I had the engine shut down. Not playing it like this. Sort out your LOVE Dovetail.
I would say that in the real world things don't break every day, at least I think so, so reality is best described by the OFF state. I rather mind that they don't talk about blurry textures anymore, or at least I don't know that it would be solved .......
Yeah it happens a little too often, even on "low" setting. I had like 20 engine stalls on a riviera run ect. Our trains seriously need to be re-routed to the workshop like yesterday before they fall apart.
Sure was nice to find out that for some reason the game decided to change settings on its own to where the train fault setting turned itself back on at a "normal" (supposedly) frequency and yet the setting for the alert had been turned off. And the 150 engines are still failing so often they should probably be taken out and scrapped
Thanks for the update on separating fault likelihood - this is great cause ideally I'd like a lot of route disruption but train failures a "rare treat" - but the voyager engines are still failing ridiculously often on low setting. Could we perhaps have an option to set a probability (i.e. the actual number, idk how this is implemented but say 1 failure per 5 hours gameplay or something, which would still be ridiculously crazy frequent compared to reality but far enough apart in gameplay to be fun)? Something isn't right anyway with the current implementation and it's odd. I should imagine this is a relatively simple fix fortunately. As a software engineer I have my suspicions about the causes and if it's what I think it could be I'd just say look very carefully at the maths underpinning it and the assumptions driving those maths, and also whether probability is in 100% or 1...
I have a hunch that the either the wrong build was put out or some of the patch is missing. The notes state that TSRs now have AWS warnings, I had a few TSRs this evening and none of them had an AWS magnet. Also getting an insane amount of faults on Normal frequency setting. I put this on the Discord, but here's what I personally think the fault %'s should be set at for each option: Low: 1% chance of random behaviour during a service. Normal: 10% chance of random behaviour during a service. High: 50% chance of random behaviour during a service. When set to Low or Normal, you should have more runs where nothing happens than runs where faults do occur. High should be the only option where it's very rare to have a fault free drive. Edit: Another alternative option is to have a percentage slider against each fault option. That would give us even more flexibility.
Today's patch definitely, completely broke the train faults. Prior to this, I had a couple of train faults occur over a few journeys on normal frequency, which seemed fine to me. As soon as I installed the patch, on Riviera line I had diesel engine failures every several seconds, and getting much closer together as I neared the end of the timetable route. This was resuming from a save game. Tonight I've gone back to the same route but selected a journey mode chapter. The moment I started pulling out from the station, I immediately got a diesel engine failure. So I tried the new US route instead. Maybe less than a minute after starting the timetable mode, before I'd attempted to get the train running, I got a random fault with the pantograph dropping. So I've turned it off. I know I can disable the random faults feature, but I'd rather this gets fixed before I jump back into TSW6. I thought random events were a brilliant new feature and they had pulled me back into the sim, but this is sadly now ruined. I know some bugs don't show themselves up in dev builds, but isn't it usual practice to test games and patches on a release build? If literally every player is experiencing the constant train faults issue no matter the frequency setting, you would think this would have shown up in testing.
Constant problems on Voyager related to restarting the engine. I get an error, start the engine from the panel (or hotkey on Z), the failure is corrected, but after a short period of time the situation repeats itself. Maybe I'm doing something wrong, but I suspect that the problem is most likely in TSW. Platform PC Steam, Rivera Line services 1V47 & 1M61, the problem occurs periodically, ranging from a few seconds to several minutes.
https://forums.dovetailgames.com/th...-game-update-10th-october.94537/#post-1051705 "Morning folks. We pushed a fix late last night that should resolve issues players were having with Train Faults occurring too frequently (I.e. several times a session), and still appearing when set to 'Off' in Settings. This has only been released on Steam at the moment, but we're hoping to release on other platforms over the weekend. Thanks!" yeah I noticed a small update shortly before going to work, so I am going to turn them back on and see if that fixed anything... or maybe wait... and see if it fixed stuff to players who actually have them on
Will try this later on. But someone needs to be on the carpet for tea and biscuits come Monday morning for letting this slip through and the supervisor who signed off on it.
Exactly this! We need to ensure that things are thoroughly tested before they are rolled out on a large scale...
for now I will leave the train faults off till I see more ppl confirming it's been fixed... also, I noticed that they added PZB to speed restrictions, but yesterday as I was playing Dresden to Leipzig in ICE T, and I got 70 kph restriction, upon pressing PZB acknowledge no 1000 Hz supervision appeared
If the fix has worked, I have to say thank you for the fast response, and hopefully this is now setting the standard for the way forwards. Now onto the bugs outstanding for months or years
Providing that train faults are train specific and not route specific it appears the fix has worked. I've just done 2 Voyager runs in free roam (Peterborough to Grantham on ECML and Milton Keynes Central to Watford Junction on WCMLS) without any faults occurring.
However lessons still need to be taken forward about how the patch (or possibly wrong version) was pushed out in the first place. Surely this process is not left to some low grade tech, but subject to peer review and the EP himself signing off on pushing the button? Damage limitation this time but the sentiment expressed earlier applies. We expect and deserve better from a company at this level and charging what they do for the product.
Seems like the fix helped, I just did a 20 minute shunting operation on Ruhr-Sieg-Nord with the 294, and not a single fault! Good job DTG, fixing today what you broke yesterday
I think the faults are loco-specific rather than route-specific. I've got none of the TSW6 routes yet, but I've got the 294. Used it on Bremen-Oldenburg, Ruhr-Sieg-Nord, Ludwigsbahn and Hamburg-Lübeck so far, and had train faults on each of them.
so you can confirm that for you Random Faults - Normal works now as intended, pretty much? so I can now turn em back on? yay
On PS5 last night even after the last update patch/fixes the random fault system is still completely broken. On the Riviera line and set to "normal" the 150 and 220 suffer ridiculous levels of engine stalls that need fixing. These happen every minute of two at best and end to end at worst. On the 220 you can clear the "error" by just holding down the start button even whilst on the move! On the 150 you need to stop, put the reverser into neutral and the engine off first before restarting. In both trains you often get another engine stall immediately or within a minute or two. Changing the fault setting to low does NOT lessen the frequency. When it rains you can guarantee a wiper failure which can be reset on the 150 by switching on then and off again. The 220 is much more fussy and I have had an occasion where it failed to reset despite repeated attempts and I just gave up on the service completely. As far as the door failure, I had one on the 220 and got out of the car to investigate. Thankfully I did not need to go far as it was the passenger door nearest to the driving cab. Amazingly I watched as the passengers just went straight through the closed stuck door like some creepy supernatural apparitions! I reset the door as intended but the actual implementation of the fault visuals were just so jaw droppingly shoddy that immersion ceased to exist. Whilst on subject of random events, I have not seen any signal delays. ZERO, even after switching the setting to high. Does this heavily hyped feature actually exist? Finally TSRs are the only random option that appears to work to some degree. Since the update they seem a bit more controlled than before when they were all over the place and often badly situated. Even now you sometimes see markers for other tracks that seem in wrong places. The random faults at present are worse than useless and actually kill the game by making it unplayable. Even turning this function OFF does not work with wiper failures still happening! Whilst I would expect some minor teething problems with features in a "new" release, it was unexpected for it to be such a complete mess leaving the game unplayable until the much vaunted exciting new features are switched off and even then the problems won't fully go away. I have three questions for DTG. 1) Do you actually do any testing on TSW before releasing it ? 2) When are you going to fix these problems ? 3) In your opinion, has the launch of TSW6 been a success delivering the new functions that you sold the product on ?
I bet now they wish they had gone for Save Game improvements and more graphic options. Though they would probably have ballsed that up too… Well at least with TSW on hiatus until (if) the mess is sorted out, I’m rediscovering the delights of Farming Sim, Snowrunner and maybe later SimRail too. But I just can’t bring myself to pour any more money into TSW until DTG pull their socks up and show a bit of competency in dealing with this stuff. They’ve been doing it long enough.
Ps5 Pro I downloaded the patch today, I think version 1.008 I drove a service with Class 150, about 1 hour, Train Faults set to Low. During the ride I ended up having three faults ..... 1x Engine, 1x Wipers, 1x Doors stuck ....... quite a lot at low frequency ...... then I drove about 15 min service, marked Part 1, and there I had peace ..... no faults EDIT: I found out that with a stuck door, you just need to move the camera and click... you don't have to get out of the cabin.
Every freakin option is disabled. And guess what? Exactly! The doors have broke on Arrow III. I can't open them. Doors open button says "Doors Locked". Da hell DTG! Game wants me to lock the doors. They are already locked!!! This is the most incompetent work you've ever done. Not only are you incapable of setting up the configs, but you even incapable to implement on/off functions!
PS5 with TSW6 version 1.009. Did some testing last night and can confirm that the random faults at normal setting have now been hugely reduced to the point of not happening at all in the nearly two hours I ran a 150 on the Riviera line. Similarly I had no incidence of random signal delays and about one TSR per service run. Whilst hardly enough to live up to the "expect the unexpected" tag line, it is a huge improvement from the nearly unplayable state the game has been in since launch. I actually got to relax and enjoy just driving the Riviera route without continuous problems ruining everything. It really is excellent and worth the full price. That in itself is something I cannot remember saying about a TSW route apart from the two beautifully crafted Just Trains routes. As for the random faults and delays, hopefully DTG eventually get them working to a point where they are a useful addition to gameplay but at the moment it is just a good idea very poorly implemented.
PS5 with TSW6 version 1.009. I drove the service for about an hour today, Exeter - Paignton ....... 1x Engine and at the end station 1x Door and Wipers and 1x TSRS
did some runs with HST and Voyager, also no faults, except one door not closing, which I closed using camera 3
Ps5 During a longer service, around an hour, I have never had it be without faults. I am testing it on Riviera Line and settings Low
For an expert loco the faults and troubleshooting part is a fun and interesting thing to do. For a newbe even to learn the connection between the systems But as a core feature in a Tsw...,no please. Way too simplified to be fun, way too frequent to make it enjoyable. Instead the way dtg implemented this was rather fire and forget. They really should have spent more time on the other feature (signal delay and diversions / speed restrictions) and leave the fault thing for expert locos. Most annoying, when turned off its still happening. (Even with the expert 101, i like to have the faults max. 1 every ride or preferably less). Seriously if your engine is stalling 4 times in a row the train should be taken out of service .?)
This is still not fixed on the Talent 2 on Dresden - Leipzig. I've just had another door failure despite them being turned off. Please, please fix this DTG. I've turned it off, why is any code related to it being called?? EDIT: I've found it far more likely to happen when using the keyboard shortcuts (Y/U) to close the doors. I'm wondering if it's got something to do with the ridiculous "keep spamming the close door button until the doors are closed" action you perform when closing doors with the shortcut.
The nerf does appear to have gone too far. I left my faults set at medium after the patch debacle but two runs over Riviera with the Voyager and 150 not had a single one (don’t think they are enabled on the Cucumbers though they seem to get stuck enough without the extra algorithm!).”
