Solved: Infinite Loading Screen

Discussion in 'Technical Reports' started by pietmaniack, Sep 8, 2023.

  1. pietmaniack

    pietmaniack New Member

    Joined:
    Sep 8, 2023
    Messages:
    5
    Likes Received:
    1
    Iam a route creator and I have the following issiue with my route.
    When I want to play a scenario the game just loads it to death. In the taskmanager I can clearly see it when the RAM ussage stays the same way and the processor is used about 7 to 9%. Normaly it is about 20% and the RAM ussage goes up to wathever it needs, when it is correvtly working. After that discovery I tried to use the Logmate, but since it immediately goes into this loading loop, nothing unusual is documented there, also not very much, since it seems to die instantly, after the first ~30 seconds.
    After that I played flawlessly a Quick-Drive-Scenario on the route on the same passage and then I loaded the scenario and I worked just fine, hm.... .
    => route works
    => scenario works
    So the solution is to load the QD and then the scenario.

    Idont think this is the way it should work, maybe you could look into that.

    My Team also tried to seperate the route in two so it wouldnt be so big, but deleting only the tiles does nothing, so the problem musst be the tracks.bin. We were able to delete the the tracks and anything that were on the deleted tiles, but the markers make us problems. Deleting the rails section alone with signals und speed signs is no problem, but if only one marker is on the network nothing works anymore. And we cant just delete all markers on the route and manualy deleting the tracks in game seems also off the limits.
    So my question is how does the game generate the markers in the tracks.bin?

    For reference my route:




    https://forum.railworks-austria.at/wcf/filebase/index.php?entry/228/
    (seperated route)
    The complete route is here to download:
    https://mega.nz/folder/nrJ1GTbY#nPGNvYrtSH5nPyqWGFO3vw/file/7jwSlZIR

    I hope someone could help me with that.
     
  2. Spikee1975

    Spikee1975 Guest

    I've taken a look at the RouteProperties.xml, the route dependencies is 128 DLC / product folders...! Instantly deleted it ;), as bugtracking could take a lifetime...
     
    Last edited by a moderator: Sep 14, 2023
  3. pietmaniack

    pietmaniack New Member

    Joined:
    Sep 8, 2023
    Messages:
    5
    Likes Received:
    1
    Spikee1975 Idont think its a provider problem, as the route works perfectly fine in QD and in Scenarios (after loading a QD first). It seams to me that it is some kind of core problem that triggers this. My work around to this is that Iam going to seperate the route in two, but it is still a core problem.... .
     
  4. Spikee1975

    Spikee1975 Guest

    Good luck, but I refuse to install routes having such a high number of assets providers used. Especially freeware, I do own a lot of these freeware assets and having a very large installation, I once updated some of the assets as different versions were around, I did fix some, but I don't wanna go through the process of installing another pile of assets and probably overwrite some, sorry.
     
  5. pietmaniack

    pietmaniack New Member

    Joined:
    Sep 8, 2023
    Messages:
    5
    Likes Received:
    1
    Spikee1975
    Like i said its not the assets, even when iam deleting all scenery tiles and Iam driving only with tracks and signals it still happens. Its not a provider/assets problem. This post was meant for the developers, as the game crashes/goes into a loop without any error.
     
  6. pietmaniack

    pietmaniack New Member

    Joined:
    Sep 8, 2023
    Messages:
    5
    Likes Received:
    1
    So I finally found out what was wrong, two Providers were corupted, @Spike1975 it seems you were right. I just reinstalled them. But it still concerns me why I could fix the issue back then by loading a QickDrive first and then loading the scenrio, doesnt make any kind of sense to me.
     
    • Like Like x 1
  7. Spikee1975

    Spikee1975 Guest

    Glad you're sorted. Corrupt assets can cause all sorts of strange behaviour in places you wouldn't expect them to show up.

    That's what I was initially trying to say - the more assets used by a route, the longer the troubleshooting takes.

    TSTools can give you a good idea (or at least a hint) of what's wrong with its asset/route checking features.
     
    Last edited by a moderator: Oct 1, 2023
    • Like Like x 1

Share This Page