Hello fellow Trainsimmers,
I need help with a problem regarding the out-of-the-box JAPAN1 or Tokyo Hakone Route.
In this video, you can see what happens.
This uncoupling and derailing bug happens on the default Tokyo Hakone between Tamagawa Gauken Mae and Machida and it affects BOTH tracks in BOTH directions. However, it ONLY happens when I am running a train using couplers that can be detatched. In permanently coupled trains (with couplers that cannot be uncoupled like the Acela or Series 7000LSE) there is no problem.
Unlike the infamous Cutbank Problem (named because it happened at Cutbank on default Marias Pass) and the NEC Interlocking Problem:
Both were caused by there being a distance greater than 5 miles between turnouts (red nodes). For example if turnout a and turnout b are 5 miles apart but turnout c is six miles apart from turnout b, then the coupler breaks when the train hits turnout c with a coupler break and medium-sized derailment at best, a massive wild derailment at worst.
Both were solved by adding a red node (either through x-tracks dummy nodes or adding a crossover or switch in general) to the offending track. (In Cutbank, the south track was not affected because it already had two turnouts to break up the track - one at Ethridge for a grain elevator, and one for the Oil Refinery. The NEC Problem was solved by adding more crossovers to break up the track.)
However, this bug does NOT happen at a turnout so we can rule the "Cutbank Problem" out as a culprit.
I've attached a file showing the problem area so if you want to try to recreate the problem you can try so you can better understand what happened.
Because I know people will ask as these have caused problems on other routes before:
1. NO, I did NOT install X-Tracks, much less use them in the route.
2. I did NOT modify the route in any way shape or form.
I remember playing this route as a kid and I was all like "what the heck?" when my train derailed at this spot (and I was not using MSTS Bin at the time so we can rule out MSTS Bin (or lackthereof) as a problem.)
If anyone can provide a solution, I would really appreciate it, thank you!
I need help with a problem regarding the out-of-the-box JAPAN1 or Tokyo Hakone Route.
In this video, you can see what happens.
This uncoupling and derailing bug happens on the default Tokyo Hakone between Tamagawa Gauken Mae and Machida and it affects BOTH tracks in BOTH directions. However, it ONLY happens when I am running a train using couplers that can be detatched. In permanently coupled trains (with couplers that cannot be uncoupled like the Acela or Series 7000LSE) there is no problem.
Unlike the infamous Cutbank Problem (named because it happened at Cutbank on default Marias Pass) and the NEC Interlocking Problem:
Both were caused by there being a distance greater than 5 miles between turnouts (red nodes). For example if turnout a and turnout b are 5 miles apart but turnout c is six miles apart from turnout b, then the coupler breaks when the train hits turnout c with a coupler break and medium-sized derailment at best, a massive wild derailment at worst.
Both were solved by adding a red node (either through x-tracks dummy nodes or adding a crossover or switch in general) to the offending track. (In Cutbank, the south track was not affected because it already had two turnouts to break up the track - one at Ethridge for a grain elevator, and one for the Oil Refinery. The NEC Problem was solved by adding more crossovers to break up the track.)
However, this bug does NOT happen at a turnout so we can rule the "Cutbank Problem" out as a culprit.
I've attached a file showing the problem area so if you want to try to recreate the problem you can try so you can better understand what happened.
Because I know people will ask as these have caused problems on other routes before:
1. NO, I did NOT install X-Tracks, much less use them in the route.
2. I did NOT modify the route in any way shape or form.
I remember playing this route as a kid and I was all like "what the heck?" when my train derailed at this spot (and I was not using MSTS Bin at the time so we can rule out MSTS Bin (or lackthereof) as a problem.)
If anyone can provide a solution, I would really appreciate it, thank you!
for a Series 7000 ) and had the broken coupler end of activity at that point. Obviously bad track there. I don't know how to fix Dynamic Tracks, never use it myself in route building.
Comment