Bridge deletion corruption issues

[Rollmaterial]

Does this cause corruption when removing tunnels? Asking to avoid potential duplicate bug reports.

Mod note: This has been split from this unrelated topic

[Matthew]

Does this cause corruption when removing tunnels? Asking to avoid potential duplicate bug reports.

I seems unlikely, though this kind of thing is way out of my depth.

I tried building tunnels in the latest client's single-player mode and nothing strange happened, though that does not test for out-of-sync errors in network games.

[Rollmaterial]

What I'm describing doesn't seem to occur when removing the entire tunnel by using the general remove tool on a portal. It only occurs with the way removal tool.

[Matthew]

What I'm describing doesn't seem to occur when removing the entire tunnel by using the general remove tool on a portal. It only occurs with the way removal tool.

I'd suggest you open a separate bug report with steps to reproduce. This bug report is about sync_step which I think (I mioght be wrong) handles routine movement of convoys, not way construction/destruction. I suggest you also skim-read these two bug reports. Also, please note whether the affected tunnels have Public right of way (PROW), because that could be important, since the PROW code was recently changed.

[Ranran on indefinite leave]

Does this cause corruption when removing tunnels? Asking to avoid potential duplicate bug reports.

This seems to be another bug. I haven't looked into it because I don't have time, but I'm guessing it's a merge retake error.

https://github.com/Ranran-the-JuicyPork/simutrans-extended/commit/c7fcb7b183fac385acedcc564267ac47368d8fcf
I don't know why the result of cherry picking this commit again was as this, but I'm guessing it was the cause.

[Matthew]

This seems to be another bug. I haven't looked into it because I don't have time, but I'm guessing it's a merge retake error.

https://github.com/Ranran-the-JuicyPork/simutrans-extended/commit/c7fcb7b183fac385acedcc564267ac47368d8fcf
I don't know why the result of cherry picking this commit again was as this, but I'm guessing it was the cause.

That commit was announced in this post.