[2.0.76] Rolling stock ghost cannot revive when an adjacent rail is a ghost

[BurninSun]

Take the following setup, note the rail ghost on the right:

05-14-2026, 18-11-56.png (406.46 KiB) Viewed 135 times

place a rolling stock ghost within 2 rail segments of the rail ghost:
/c LOCO = game.player.surface.create_entity{name="entity-ghost", inner_name="locomotive", position={-1.9, -1}, force="player"}

05-14-2026, 18-12-35.png (310.53 KiB) Viewed 135 times

Attempting to revive the locomotive ghost fails (/c LOCO.revive()) even though the bounding box is completely within the built rail segments.

A manually placed rolling stock is possible get much closer to the ghost rail segment as shown here.

05-14-2026, 18-15-14.png (347.57 KiB) Viewed 135 times

Additionally, this locomotive is unable to be revived simply because the branch rail is a ghost.

05-14-2026, 18-17-29.png (636.24 KiB) Viewed 135 times

With this setup, the placement order doesn't matter. Having a built straight rail with a ghost locomotive, the locomotive becomes unrevivable as soon as the ghost rail branch is placed.

This is causing a bug in space exploration where I'm trying to revive rolling stock ghosts at the edge of the space elevator. Rolling stock can become unrevivable due to a nearby rail ghost even though the rail ghost shouldn't be interacting with the rolling stock.

[boskid]

Thanks for the report however i am going to classify this as a Not a bug. This is because this behavior is specifically here to fix issues like 72295 where you could have a rolling stock ghost revived on top of real rails but it would not be able to connect to a neighbour rolling stock it was supposed to because in the gap between two rolling stocks there was a ghost rail. That would be a real issue because rolling stocks would be connecting or not connecting based on the order entity ghosts were revived.