Path Request Added:unnamed Priority : (3402...huge Number)

Discussion in 'Technical Reports' started by Dakota, Sep 20, 2021.

Tags:
  1. Dakota

    Dakota Member

    Joined:
    May 13, 2018
    Messages:
    81
    Likes Received:
    37
    Seriously struggling making a Scenario. I spend several days, and the more I worked on it the crazier the signaling became. I have a nice video of an AI passing a Danger/Stop signal. My scenario is really simple. A player train going west on the North tracks, and a couple of AI trains going East on the South tracks. No conflicts. I decided to see what the heck is happening, so I enabled logging via " -LogMate -SetLogFilters="Signals,Pathing". I have burned literally a couple of days trying to get a repro scenario. What I can say is that when I see this in the log (scroll right to see the preposterous priority value):
    Code:
    2021/09/17 14:39:22.096 - [Pathing] - Trace cDispatcher.cpp : 319 = Path request added:Unnamed priority : 340282346638528860000000000000000000000.000000
    2021/09/17 14:39:22.096 - [Pathing] - Trace cDispatcher.cpp : 320 = Train type: Special Non-Electric
    
    if I keep working on the scenario (adding lighting, static consists, but no more AI trains(!!!)) the above statements start to multiply and grow like a cancer. Eventually the scenario becomes useless.

    If you can tell me the conditions under which the program logs this message, maybe I can discover the error of my ways.
     

Share This Page