[2.0] Rebuild all rails in an 1.x base

[Vasya228]

I've just got auto-updated to 2.0.8 from the latest 1.x release, and now I cant add rails to my existing base where I need it (error is "legacy rail is in the way" or something). Is there any workaround or fix available?
Also I noticed that rail turn radius in now larger, and as I use roundabouts a lot, I'll need to rebuild every one of them?

Are devs serious about that? I can't imagine the amount of work required to rebuild the whole rail infrastucture in a large base.

[SirSmuggler]

I've just got auto-updated to 2.0.8 from the latest 1.x release, and now I cant add rails to my existing base where I need it (error is "legacy rail is in the way" or something). Is there any workaround or fix available?
Also I noticed that rail turn radius in now larger, and as I use roundabouts a lot, I'll need to rebuild every one of them?

The workaround is to play on version 1.1.

Are devs serious about that?

I belive so.

On a more serious note, check out the FFF posts on rail changes for 2.0. There is a lot.
https://www.factorio.com/blog/search/rail

Edit - The search I linked might not be the best, but look at the dates and you can dissmis the ones that are more then a year old.

[mmmPI]

Are devs serious about that? I can't imagine the amount of work required to rebuild the whole rail infrastucture in a large base.

The devs always stated that it is better to play a new save game with the expansion, the older rails are not removed, but you can only add the new ones to them, however your previous base should still work with legacy rails, and no rebuilding work should be "required"

[Vasya228]

no rebuilding work should be "required"

I try to expand my rail network to fix fluid warnings, and I end up with this kind of rail placement (see attachment). I can not see how I fix that in a good way without rebuilding the whole intersection, which would require rebuilding all rails around it, also rebuilding parts of production.

And may I remind you that an update to v2 was an automatic one, without a huge warning with huge red letters "INCOMPATIBLE CHANGES UPDATE AT YOUR OWN RISK".

rails00.png (4.62 MiB) Viewed 4149 times

[Tertius]

The rails from 2.0 have a different spacing with curves, they're not compatible with 1.1 rails. You cannot mix both, and you cannot build new 1.1 rails. You're able to connect a 1.1 rail system with a 2.0 rail system at straight horizontal or vertical rails, but not at curves. I recommend you deconstruct all curved 1.1 rails and replace them with 2.0 rails. Or just start a new 2.0 base to not have to deal with these kind of issues.

The 2.0 rails have a slightly bigger curve radius, making all kinds of fancy branching and interconnection possible that wasn't possible with 1.1 rails. So it's well worth using the new rails!

[robot256]

I agree the decision to make 2.0 an automatic update was probably not a good one for many reasons, rails and mod compatibility chief among them.

You should still be able to place legacy curve rails by blueprinting your existing pieces and placing the blueprint. Though that intersection really would benefit from a redesign anyways

[Panzerknacker]

The autoupdate to 2.0 sucked indeed because it also messed with the player-data.json and achievements.dat files. How are we gonna roll that back if we want to go back to 1.1.110?

I didn't autoupdate but I manually updated to 2.0 to see what's up. Then going back to 1.1.110 I was greeted with some errors after starting the game.