Did The Last Tsc Core Update Create Issues

Discussion in 'Technical Reports' started by holt.alistair, Dec 17, 2023.

  1. holt.alistair

    holt.alistair Member

    Joined:
    Oct 17, 2019
    Messages:
    64
    Likes Received:
    6
    Hi, has anyone else been running into previously unknown issues since the last TSC core update in mid November? Thanks Fred
     
  2. railroadamerica

    railroadamerica Active Member

    Joined:
    Nov 9, 2022
    Messages:
    105
    Likes Received:
    193
    no error on my side at the moment.
     
  3. 749006

    749006 Well-Known Member

    Joined:
    Dec 10, 2016
    Messages:
    10,093
    Likes Received:
    3,145
    The question is rather random.

    Tell us the problems you are having and if its route specific and somebody can have a look.
     
  4. triznya.andras

    triznya.andras Well-Known Member

    Joined:
    Jun 29, 2019
    Messages:
    2,334
    Likes Received:
    2,795
    Yes, I got my first ever Vertex Buffer error.
    I never had it before, my game could perfectly handle Alt-Tab. Now it can't anymore.

    By the way, Setup_Audio.bat is back as well (didn't run just noticed), and I seem to have certain audio not playing, or not audible.

    Edit: After a restart said audio played. Either pausing or Alt-Tabbing killed it - unless it's just random.
     
    Last edited: Dec 17, 2023
  5. Spikee1975

    Spikee1975 Guest

    Running better than ever.

    One scenario was reported to be incompatible - a design error that somehow got through on older versions, but will not run on the new code.

    It is Peninsula Corridor's [GP38-2] UP Mission Bay Hauler, which I have fixed and sent to DTG to include in an update.
     
    • Like Like x 1
  6. cunningn#3154

    cunningn#3154 Well-Known Member

    Joined:
    Mar 22, 2023
    Messages:
    226
    Likes Received:
    298
    I've encountered an unwelcome change in behaviour since the finalised update (which is weird as I was on the beta and hadn't noticed them then).

    New OOM on trying to 'drive' two of my standard scenarios - Fatal error in mode LOAD_SCENARIO during update within DISPATCHER. These were previously working scenarios (though I cannot swear to the date at which they stopped working).

    Running Logmate is showing this new errmsg:
    "2023/12/28 15:40:06.054 - [Pathing] - Trace D:\RGBuild\CoreRelease\Code\DLLs\Dispatcher\DispatcherV1\cSearchPath.cpp : 430 = Found deleted node while traversing path."
    In all cases it is in the pathing section and is followed by a cheerful 'pathing succeeded' - so it may not be relevant...

    Annoyingly I cannot edit either scenario as the editor crashes with the same OOM. I have tried random modifications via RWTols without success (not surprising).

    Usually I would just chalk it up to experience, ditch them from the next release and move on - but they are two really good scenarios (one of them by someone else) so I'm loathe to lose them.

    I'd be interested to know if anyone else has encountered either the OOM or seen the logmate message?
     
    • Like Like x 1
  7. rd#7546

    rd#7546 Member

    Joined:
    Oct 9, 2023
    Messages:
    27
    Likes Received:
    42
    I'm having a number of similar issues with routes I've modified or built myself, as well as select workshops routes. I've started another thread to see if we can get to the bottom of it.

    Safe to say, all is not well and indeed, I was happy with the beta but now am not so happy
     
    • Like Like x 1
    • Helpful Helpful x 1

Share This Page