Derailment / Buffer Block

06:34 Edge Hill shunting, you detail while passing the signal box coming onto the mainline

xbox series x

service mode/ timetable mode

spirit is steam Liverpool to Crewe

jubilee

edge hill shunting start time of 06:34 am

pull out of engine sheds and stop before a red, set junction so it matches the blue pathfinder line, set revereser to forward and depart for the mainline, after going up the gradient and passing the signal box it details and launch’s

video:

 

About time, DTG!

• Issue Summary: Instant Derailing
• Platform: PS4 TSW2
• Game Mode: Journey
• Route Name: MSB
• Loco Name: DB BR 185
• Service/Scenario Name + Start Time: DB 83115 at 07:04h
• Step-by-Step Instructions: Just fire up the journey/service/timetable and wait for it. All these services have been successfully concluded BEFORE SoS Patch 1.86 (which was suppose to address the derail issue on SoS but messed up many routes.)

 

• Issue Summary: Instant Derailing
• Platform: PS4 TSW2
• Game Mode: Journey
• Route Name: MSB
• Loco Name: DB BR 185
• Service/Scenario Name + Start Time: DB 83127 at 11:21h
• Step-by-Step Instructions: Just fire up the journey/service/timetable and wait for it. All these services have been successfully concluded BEFORE SoS Patch 1.86 (which was suppose to address the derail issue on SoS but messed up many routes.)

 

• Issue Summary: (Almost) Instant Derailing
• Platform: PS4 TSW2
• Game Mode: Journey
• Route Name: GWE - Diesel Legends
• Loco Name: Class 08
• Service/Scenario Name + Start Time: 5X03 (Put a Gronk) at 03:22h
• Step-by-Step Instructions: Just fire up the journey/service/timetable, release the brakes and wait for it. This one seems to have overly suppressed buffers. HINT: Whenever you hear that penetrating *CLANK* sound, OR: when you see the station shaking, get your heart prepared ... This sound came up with Patch 1.86 (which should have been rolled back immediately, but that´s just IMHO.)

 

Just a few shots from wrong coupler distances. I do not believe this is just optical perfume, because it came as well with that damned 1.86 Patch when the whole derailment issue started. You can see this basically on every route (I own) between the loco and the consist.

 

Issue Summary: Game crash
Platform: PC Steam
Game Mode: Scenario
Route Name: MSB
Loco Name: BR 185
Service/Scenario Name + Start Time: Fuel Exchange 10.00
Step-by-Step Instructions: Get the consist to Heigenbrucken and uncouple banker loco. Continue to Lohr and uncouple last 5 wagons, then hand over to next driver. Then on the way to hand on to next driver, game crashes. I am not savvy enough to do videos etc.. However this has been mentioned in the forums since January 2021 and the most recent posts are dated as late as July this year!It is able to be completed if one either a) removes the five wagons at Heigenbrucken, or b) arrive at Lohr, apply brakes, apply handbrake to last wagon, then return to cab, 'stretch' consist out (releasing pressure on buffers), shut down loco and head to hand over to next driver. These issues are all over the forums.This happens in TSW 2. I will NOT purchase TSW 3 due to these bugs in TSW 2 not being fixed. I submitted a ticket on this matter 10 days ago (#49752 Game Crash) and that is still current.
https://forums.dovetailgames.com/threads/msb-fairly-unplayable-due-to-bugs.56046/
+Screenshots
+Video Links

 

• Issue Summary: Random/Spontaneous Derailment

• Platform: PS5

• Game Mode: Scenario/Timetable

• Route Name: Sand Patch Grade

• Loco Name: GE AC4400CW (Possibly even the C40-8W)

• Service/Scenario Name + Start Time: Powering America Part 2 at 14:30 hours. (Any timetable going downhill to Cumberland as well)

• Step-by-Step Instructions: Step 1: When going downhill at recommended speed (15-20mph) apply the dynamic brake. Step 2: When approaching a sharp-ish turn shortly after reaching Sand Patch, locomotive should derail. Step 3: Profit.
• Screenshots: N/A
• Video Links: N/A

 

Alright, fair enough. I´ll feed you with more precise data:

• Issue Summary: Wrong Coupler Distances

• Platform: PS4 TSW2

• Game Mode: Class 31 Journey

• Route Name: TVL

• Loco Name: Class 31

• Service/Scenario Name + Start Time: 6E35 - Tees Yeard - Eastgate @ 15:12

• Step-by-Step Instructions: Take over the loco, see coupling example attached; uncouple, then run around and couple back side, see coupling example attached...

Stay tuned, there´s more to come.

 

• Issue Summary: Wrong Coupler Distances (this time the other way around - see smashed into each other buffers)

• Platform: PS4 TSW2

• Game Mode: Class 08 Driver Journey/Scenario

• Route Name: TVL

• Loco Name: Class 08 + Class 101

• Service/Scenario Name + Start Time: Three Become Two @ 11:20h

• Step-by-Step Instructions: Take over the loco, couple as per instruction,see coupling example attached; then run around and couple back side, see coupling example attached...

 

• Issue Summary: Wrong Coupler Distances

• Platform: PS4 TSW2

• Game Mode: DB BR187 Journey

• Route Name: SKA

• Loco Name: Db BR 187

• Service/Scenario Name + Start Time: DB 83168 Westbound Mixed Cargo @ 20:30

• Step-by-Step Instructions: Just get to the loco and have a look ....

 

• Issue Summary: Wrong Coupler Distances

• Platform: PS4 TSW2

• Game Mode: Journey

• Route Name: HHL

• Loco Name: Db BR 112

• Service/Scenario Name + Start Time: RE80 11462 Hamburg - Lübeck @ 10:33

• Step-by-Step Instructions: Just get to the loco and have a look ....

 

• Issue Summary: Wrong Coupler Distances

• Platform: PS4 TSW2

• Game Mode: Freight Journey

• Route Name: HHL

• Loco Name: Db BR 182

• Service/Scenario Name + Start Time: DB 89401 Rothenburgsort - Lübeck @ 4:30

• Step-by-Step Instructions: Just get to the loco and have a look ....

 

• Issue Summary: Shaking surroundings (or loco depending on your POV) - HUD indicating wheelslip?!?!

• Platform: PS4 TSW2

• Game Mode: BR 363 Journey

• Route Name: RSN

• Loco Name: DB BR 363

• Service/Scenario Name + Start Time: SH08 Collect First Inbound Steel Train @ 17:00h

• Step-by-Step Instructions: Start scenario and enjoy the earthquake ... Bug introduced together with the derail bug, via the glorious Patch 1.86. Possibly related.

 

• Issue Summary: Coupler distances, automatic coupler rendered useless, only manual coupling possible (still with coupler gap!)

• Platform: PS4 TSW2

• Game Mode: BR 363 Journey

• Route Name: RSN

• Loco Name: DB BR 363

• Service/Scenario Name + Start Time: SH08 Collect First Inbound Steel Train @ 17:00h

• Step-by-Step Instructions: Start scenario, reverse and couple as per instruction, enjoy the bouncing BR363 " Kangaroo" ... Bug introduced together with the derail bug, via the glorious Patch 1.86. Possibly related.

 

TrainSim-Matt

Matt, I´m resting my case now. I´m sure other forumites have more to contribute. Occam´s Razor will lead you to a simple root cause. Means: it´s not so much route/scenario/journey/time &date related, but a common core issue (stiff buffers, stretched couplers, resulting in jerky consists) which came with the SoS patch.
Producing these evidences is obviously quite time-consuming. I just felt I owe you, since your Patch 1.90 installed me a route which I´ve never purchased, just FOR FREE. So, thanks a lot!

And please fix this!

 

100% a core issue since it's present in all trains, locos and Waggon

 

..I have a problem with rapid transit...while playing the magdebur markleeberg scenario - when I leave the leipzig connewitz station in the direction of Markkleeberg nord, my train derails.

Platform: Steam TSW3
DLC Rapid transit
Loco Name: BR1442 Talent 2 MD
Service/Scenario Name 0841 Magdeburg - Markkleeberg-Gaschwitz
The train derails in the place that is in the picture.. a little past the traffic lights when I leave the Leipzig Connewitz station.

 

• Issue Summary: Wrong Coupler Distances
• Platform: PC (Epic)
• Game Mode: Training module
• Route Name: Training Center
• Loco Name: BR 182 Dispolok
• Service/Scenario Name + Start Time: BR 182 Dispolok training module
• Step-by-Step Instructions: Follow the instruction to couple the loco to the train
• +Screenshots:

 

• Issue Summary: Wrong Coupler Distances

• Platform: PS4 TSW2

• Game Mode: Freight Journey

• Route Name: DRA

• Loco Name: DB BR 143

• Service/Scenario Name + Start Time: Freight Röderau - Dresden @ 11:35h

• Step-by-Step Instructions: Just get to the loco and have a look ....

 

• Issue Summary: Wrong Coupler Distances

• Platform: PS4 TSW2

• Game Mode: Freight Journey

• Route Name: TVL

• Loco Name: Class 37

• Service/Scenario Name + Start Time: 0Z05 Redcar Ore Terminal @ 5:45h

• Step-by-Step Instructions: Just get to the loco and have a look ....

 

Definitely a buffer issue!

 

I know there was a ticket submitted about this by Calidore 266 in August of this year and I've heard nor seen anything since. Makes one question the usefulness of the entire system.
https://forums.dovetailgames.com/th...affected-by-the-derail-bug.56913/#post-514396

 

Just to follow up on your follow-up: I got the generic "ticket closed" email on August 10th (ticket submitted on the 5th), which states that "the issue has been understood and recorded for further investigation." With TSW3 coming out soon after, and the heightened focus on fixing the save game feature, I could understand the delay, but it's a bit disheartening that this problem seems to have fallen through the cracks entirely. At least it's been noticed again now, though. I've only been in the game a couple of times since this bug was introduced in May, to help define it and to check if it was still a problem after a patch. I'm making some progress clearing my backlog of other games, but I do miss my TSW2 heavy freights.

 

And there is my big worry..............that with the release of TSW3, TSW2 will be neglected and those of us who see no value in TSW3, will be left with these bugs forever.
Thanks for the follow-up.

 

• Issue Summary: Instant derailment at the same location
• Platform: TSW3 Standard Edition on PS5
• Game Mode: Journey
• Route Name: Brighton Main Line
• Loco Name: Bombardier Class 387 GTX
• Service/Scenario Name + Start Time: Chapter 5 Service 1D24 starting at 07:59
• Step-by-Step Instructions: Going at maximum speed permitted then the train derails for no reason at the exact same place after leaving London Victoria
• Screenshot: Derailment location at the white crosshair
• Video Links:

 

Well, I don't understand that. I just ran the service on PC/ Steam and had no problems. Perhaps it's a PS 5 issue? Don't know if this helps or not, but I like to do runs that are troubling others and see if it happens to me as well. Cheers.

 

Crazy.

 

Yeah very random and I thought it was a thing of the past remaining in TSW2 but nope it’s still happening on any routes with any trains. After around 10 takes I finally managed to complete the service now this instant derailment is occurring on another route

 

All very good, but my question is this: IF and when DTG has a fix for this issue, will it be applied to TSW2 as well as the new baby TSW3? I somehow doubt it, as all the language coming from DTG at the moment is directed to the new version and we appear to have been left behind/forgotten.I have given plenty of voice to my concerns in the forums, but have yet to see any concrete denial of no further fixes for our version. That is, those of us who, for whatever reason, will not be purchasing the next new thing.

 

This MUST be fixed in TSW2 and TSW3.

 

You'd think that, wouldn't you? Alas, I hear nothing but crickets in response to my reply to DTG Alex, so I suspect strongly that we are stuck with the bugs we own. Grand, isn't it?

 

Last DTG said, they intended to bring the bugfixes to both TSW2 and 3. If nothing has changed, no need for them to keep interrupting their other work to repeat themselves here.

 

Could you please point me to the article or video (with timestamp) this was said?
I have seen them beeing very careful about this so i think they are only going to apply the things that are easy to implement in TSW2 and dont take additional time.With the Buffer issue, my money is on -> TSW3 only.

 

I´d like to give them the benefit of doubt and WANT to believe they´ll fix this bug. It was introduced AFTER I´ve spent a small fortune on TSW2 DLCs. (Goddamn Patch 1.86). It would be shabby from DTG if they just forget about this fact. And, as I believe, very bad for business.

Matt confirmed in this very thread that it´s going to be fixed. And in other threads before:

https://forums.dovetailgames.com/th...-updated-to-tsw3-standards.57847/#post-541016

 

• Issue Summary: Derailment
• Platform: PC Steam - TSW3
• Game Mode: Timetable
• Route Name: Kassel - Wurzburg
• Loco Name: Railpool BR185
• Service/Scenario Name + Start Time: 45153 Hannover Linden - Verona Quadrante Start Time: 03:55
• Step-by-Step Instructions:
  Run the service with AFB (set at 115kph) and PZB mode M (LZB does not work at all in this loco)
  It is not a resumed save
• +Video Links
  

 

Good. I must have missed that in amongst all the hype about TSW3. Thanks for the clarification.

 

Thanks. I have bookmarked this one for future reference, should nothing happen.

 

So who's a silly boy than? Just tried this scenario (AGAIN!), to see if anything has changed. It hasn't. Waste of my time, and at my age, I don't have a lot left to waste.
Issue Summary: Instant derailment no reason.
Platform: TSW2 PC/Steam
Game Mode: Scenario
Route Name: Sandpatch
Loco Name: AC4400CW
Service/Scenario Name + Start Time: Powering America (2)
Step-by-Step Instructions: 27 MPH after Sandpatch heading to Cumberland, train brake at initial; Dynamic brakes at 4/5; independant brake bailed off. Everything as it should be, no buffer noises, no jolting of the consist and just passed Mance and instant derailment.
This makes an entire route unplayable for me! What makes matters worse is that I did once earlier, submit a ticket on this issue (#47972; two months ago) and I recieved a blurb about train physics etc. etc. That ticket was closed I believe with the 'fix' for SOS derailments. Now you tell me what it is I'm doing wrong!

 

Two instances, both on NTP:
Platform PC/Steam TSW3
Game Mode Scenario/Journey
Route NTP
Loco Class 47
Scenario Red Bank Changeover (I think)
Details - After getting the instruction to approach and couple to the failed train with the Class 47, I did so at less than 2 MPH, applying the train brake as I approached the Class 45. On contacting the Class 45 buffers the 47 bounced back violently and SPADed the signal in rear. Second time I used the straight brake and same thing happened. Workaround was to stop short but within trigger distance of the couplings.

Second Occasion:
Loco Class 45
Scenario Timetable run from Manchester to Leeds (it’s the one in the snow after Red Bank Changeover on Journey Mode).
Details - Approaching Leeds I was slightly over the 10 MPH speed limit, 14 MPH with the train brake applied on Initial. Hit one of the double slips in the throat, loco and my drivers view surged forward then got the train derailed message. Yes I was speeding but only slightly and 3 to 4 MPH should be within tolerance, given I have exceeded the line speed considerably more on Clinchfield and WSR!

 

Any news on this? Will it be fixed with the next patch?

 

I just did Redbank Rotation in Journey mode TSW2 (I refuse to purchase another bucket of bugs). Moved up to failed loco at a snail's pace, using outside camera to assist in distance, just as one gets near the buffers (not touching!), the buffers on the failed loco are bouncing in and out of their housing; manage to couple and then get to Redbank Carriage sidings, uncouple empties; then drive forwards, reverse to destination and uncouple. Again, uncoupled utilising the external camera; As soon as one uncouples, same thing again, buffers going crazy! Hope this is some assistance if you should desire to go through the fruitless (at the moment) task of submitting a ticket.

 

I just did this journey also, no speeding, I'm a good boy really. Did not experience any derail, but the clanking and banging from the buffers every time I slowed down, or applied brakes was horrendous, so I took a few screenshots as driving, of the buffers between the loco and consist.
What a surprise! Carriage buffers are halfway into loco buffers! Then, coming into Leeds, took another as we were going through the points and this show clearly that we have a buffer problem Houston!

 

Maybe, this issue has a connection to this one:
https://forums.dovetailgames.com/th...sion-failed-without-reason.58932/#post-546625
I suspect a kind of 'covert / invisible' derailment of the Jubilee locomotive, which triggers the (very frustrating) "mission failed" issue I mentioned in the other topic above; it was already on beginning of september, when I (sadly) hit that new issue and opened the topic in the forum

 

I suspect it's all connected. None of this started happening until the update which was to fix SOS issues came into play. We then had another update that acknowledged the SOS update was causing derailments. Now, whilst it fixed some, it did not fix all of them. I also noticed the other day while driving GP38 on Peninsula corridor, the traction lock is still showing red in the HUD, after releasing all brakes. Not a game breaker by any means as I drive hudless, but still, a bug that hasn't been fixed in TSW2 and I suspect now, never will be.

 

Perhaps the game could be returned to the state it was before the first SOS buffer update as the problem only really presented itself on unfitted/partially fitted freight trains that were driven with particularly heavy handedness. If you were gentle on the brakes it never happened.

I still don't understand why different types of buffers and couplers don't have different characteristics. All couplers are not equal and each type should have different editable parameters so a fix doesn't cause havoc across the game.

 

• Issue Summary: Two objects cannot occupy the same space at the same time (Well, in TSW it seems they can?!)
• Platform: PS4 TSW2
• Game Mode: Journey
• Route Name: NTP
• Loco Name: Class 45
• Service/Scenario Name + Start Time: Leeds - Manchester Victoria - Express @ 19:23h
• Step-by-Step Instructions: Fired up the journey, leaving Leeds and just made some uncoupling / coupling to illustrate the issue. During the journey to Manchester you get quite a few of those nasty *CLANKS*.