Hi.
Path activation is done by executing several successive stages. in your case, looking at the messages in white displayed at the bottom left of the screen, stage 1 has been been successfull, but stage 2 seems to have failed on some path clearance check :
Stage 1 is normaly executed immediately on path assignment with no delay and checks that all needed ressources are available (all path objects lock available, tcb locks available, exclusive set available), then will lock all ressources, and will set all path objects in their target state or direction (except the entry signal that remains at red EX_STOP ). If successfull, stage 1 posts a timer message to start stage 2 five seconds later.
Stage 2 is more a verification process that the path is now fully available : all path objects are checked that they are still in the correct target state or direction ; the path is scanned to check there is no extra consist on it ; ... and a few other checks exist that my old brain do not remember without looking at the script code ; then if all checks are fine the entry signal is changed to its target state (automatic or proceed or any other state) and the path state is set to path active.
In your case, on your last screenshot there is a truncated message saying that the path clearance check has failed with a search that has not found ???? (The displayed message is truncated). The full message has been written to the debug log.
What is needed now is to retrieve the full message that should explain what check has failed and has blocked path activation in stage 2 : it may either be a path object not in its target state, a tcb ressource now occupied, an extra consist detected, ...
Just re execute your session and pause it just after the failure message has been displayed. then display the debug log and look inside for the full message. There is a trick to retrieve easily in the log messages emitted by EIT, MCM, STT : all messages begin with the current game time and include a « >>> » string (a three superior sign string) . when looking to the log, I personally copy the whole log to a text file and use ultraedit editor to filter and display only lines with « >>> » . this way I can easily scan all the log messages emited by EIT, MCM or STT component.
If you have any problem understanding the debug log content, you can send me a copy and I will have a look to what is causing the problem.
Regards.
Pierre.
*** edited this morning after looking at the activation script code ***
I have looked this morning to the activation script code to find when and why a message begining by "search has not found … " can be emited.
The matching message seems to be "Path clearance check has failed for path <pathName> search has not found next object on path <mapObjectName> while scanning path". This message is only emited when the path clearance final check detects some incoherence between the path objects definition in the path object and the path objects found while scaning the track to check all path objects are in their correct state.
This can happen only if the order of path objects are not the same in the path definition and along the track (should have been detected by the path editor with a path displayed in orange warning color) or if some path objects present in the path definition still exists on the route but are no longer on the path track (should also be detected by the path editor). Last possible situation is a very long path activated with stream objects active (not in maximise compatibility mode) where all path objects have been loaded during stage 1 and some path objects have been unloaded between stage 1 and stage 2 (most unprobable but this possible situation is currently not correctly processed).
Could you first check your path (CMB to Yard NB) under the path editor to check there is no error detected while editing the path ? Could you confirm that you are currently using Maximise compatibility Mode or Stream Objects option (this setting is under the developper tab in your configuration setup) ? And if no errors is detected by the path editor, can you package your route and session in a cdp with also path objects dependencies not available on DLS and send it the the email adress I will send you via PM so that I have a look to understand why there is an incoherence detection when activating the path and produce a fix if it is a false error detection or an error due to stream objects processing … Thanks in advance for your help to make EIT more reliable …
I do not need any rolling stock dependency as I only need your route and session and junction, signal and crossing dependencies to check your path definition and activation processing ...
Regards.
Pierre.