[13.5] Error when entering curve with train [reopened]

[Freddie612]

I get this code Internal error: Carriage::moveFrontJointForward frontRail rollingStockCount != 1
https://youtu.be/4RY3zqeHiHs
https://youtu.be/Z-oxUFg8DEE
SAVE:

[TruePikachu]

For a moment I thought you were reporting a bug with the signals...

[Freddie612]

What you thought that I was stopping my trains with the signals and thinking it was broken?

[Smarty]

i think i know what the problem is but can you provide the save to make sure.

[Loewchen]

...and are you using mods?

[TruePikachu]

What you thought that I was stopping my trains with the signals and thinking it was broken?

No, the title made me think the signals weren't stopping the trains.

[Freddie612]

i think i know what the problem is but can you provide the save to make sure.

Well I have worked around it, it's a certain spot which likes to break, I've just moved that 1 track else where and it's been fine but that spot in particular is breaking and no where else. It could be that glitches track

[Loewchen]

I think it is a combination of save migration and train compression. If you remove the second cargo wagon (r2l) and drive it instantly fires the error. Not the non-recoverable-rail error imo.

[kovarex]

This is fixed for 0.13.2

[fregate84]

still here in 13.5 !

https://www.dropbox.com/s/l7bwi0b1dleqj ... h.zip?dl=0
Take the double engine and drive a little forward

[Loewchen]

With what version of the game was the map originally created?

[fregate84]

0.11.1 I think .... but I play(and save) this game with all release step by step.

[Loewchen]

0.11.1 I think .... but I play(and save) this game with all release step by step.

Yes, but I think there are several fixes in the latest updates that only work if you migrate with those versions from .12 to .13, if you already saved with 13.0 it might be possible to bypass those fixes...

[Rseding91]

0.11.1 I think .... but I play(and save) this game with all release step by step.

Yes, but I think there are several fixes in the latest updates that only work if you migrate with those versions from .12 to .13, if you already saved with 13.0 it might be possible to bypass those fixes...

Correct. The bug that caused the rails to get messed up was fixed but any messed up rails would still exist.

You'll need to load an older save that hasn't been corrupt yet.

[fregate84]

I deleted all my track and I saw I have some Glitched rail tile that cannot be removed.

ScreenShot004.jpg (15.89 KiB) Viewed 3818 times

but I don't understand, because it's a solve problem, and theses rails should desapear.


viewtopic.php?f=11&t=27202&p=175358&hil ... ed#p175358

[Rseding91]

Mouse over the rail and enter this in the console:

Code: Select all

/c game.player.selected.fix_rail()

If there was a train *on* the rail during the migration it might not have migrated properly and you end up with unminable rails.

Also if you migrated, the rails went bad, and then you kept that save as you updated it would cause the same issue.

When loading a 0.12 save in 0.13 you should never get rails stuck in that state. If you do, please make a new bug report with the 0.12 save file.

[fregate84]

working. thx a lot for your time, your quick answers and this very good game !