[0.10.8] Rail blocks improperly connected by forked rails

[Glyph]

I searched the forum and common issues. This bug is related to the one reported here: https://forums.factorio.com/forum/vie ... nal#p35886. However, that bug was supposed to be fixed by 0.10.3 and involved a different forking setup (joining instead of forking) so I'm assuming this is a related but distinct bug.

A train which is NOT in the next train block is able to block another train under certain circumstances with forked rails.

In this first image you can see that the left train is stopped at a red signal even though nothing is in the block to its immediate right. I have my cursor over the rail signal that should separate the block the train on the left wants to enter from the block that the train on the right occupies. You can see that the signal reports that it is not related to the fork at the top.
http://i.imgur.com/efyl3E8.jpg

Moving the second signal before the fork (and unfortunately before my train stop) alleviates the problem. Removing the upwards fork (this example not pictured) also fixes the signal on the left.
http://i.imgur.com/1lEegN1.jpg

A diagram of what I figure is happening with the blocked signal:
http://i.imgur.com/KOHFVrR.jpg

[ssilk]

This is the problem with the signals placed too near to the switches and the (simulated) hitboxes of the trains shows then, that a waiting train from the other side touches the curved rail, which is as player hard to understand, cause the train cannot wait into that direction. if you move the first switch one tile left, it will work.

Besides that: The player should have a clear visible view of the reach of a block (different colors?), when placing signals or when hovering over a rail, cause as you see in the first pic the incoming and outgoing block number is the same.

[Glyph]

as you see in the first pic the incoming and outgoing block number is the same.

Hey I never noticed the block number! That helps some when "debugging" my rails.

[slpwnd]

Ssilk is right. This is not the bug. But the visualization should be better. That is a feature request. Though a good one. Putting it on our scary TODO list.