Two findings, one a bug and one the real cause. Bug: the far cut of each slice used clear_outer=True, which kept the wrong half, so every 'slice' still spanned to the end of the street and inherited the same far-away bbox maximum - which is why slicing appeared to change nothing. Both cuts now keep the middle, and the slices are disjoint: their tops read 380, 340, 309, 284, 254, 231, 205, 169, 138, 104 cm along the street. Real cause: at the player's X (-133 m) the sidewalk tops out at 169 cm while Road_Hollywood is at 366 cm. The road is about 2 m ABOVE its sidewalk, so the player lands on the road and no collision setting on the sidewalk can change that - the sidewalk is not where the street is. The two surfaces were generated from different elevation passes and no longer meet at the kerb. That is site-pipeline data, not placement. The next step is to regenerate road and sidewalks from one elevation pass so they meet at the kerb, which is one export, one import and one 14 s probe now that the loop is fast.
57 KiBLFS
57 KiBLFS