so the diagram is this. what is suppose to happen is that 1R15 is meant to pass Rugby platform 5, followed by 1R16 and 1R17 (which are not in the picture). After 1R17 passed, 1Y11 would end up at platform 1 and 5W18 would use the Up North line and head up to Platform 6, the latter of which is suppose to use the section of track after all the 1R trains have already passed. However, this long on going issue where 1R15 would just be stuck at Platform 5 with a red signal. 5W18 is suppose to leave its starting position at 07:55:00. And 1R15 suppose to past Rugby at 07:49:00 (but currently it passed earlier at 07:47:00 ish). The last train to be at Rugby is 1R17 stopping at 07:55:00 and leaves a minute after. 5W18 has been set to the lowest service priority (light engine) yet for some reason train 1R15 who is set at express is stuck at the red signal. since i cant find the exact reason as to why this has been the case. I decided to make another mock up from the ground up of replicating the scene, including all trains that are suppose to start at Rugby in the original scenario, same start location and service priority. And the result: 1R15 can pass, 1R16 can pass and 1R17 can stop at Rugby and leave with no blockage as 5W18 took its time and arrived at Rugby platform 6 on time. So with that test result. I have no idea why it wasnt working the same in the official scenario. I have followed RTT's timetable nearly exactly the same, even if 1R15 is early to pass Rugby they should've been able to pass easily with no red signal. I just dont know where to look for the issue because clearly this isnt a service priority issue.
i conducted more test and i even removed 5W18 from the scenario. But it still made no different. NR6000 is still red, but in the other test it works. 1R15's pathing and service priority (set at express) are all the same. So i dont get what is wrong??? the first picture is from part of the scenario. the 2nd image below is the test that i made as a completely new separate scenario. which this works.
