PC Dresden Area Seems Poorly Optimized

Discussion in 'TSW Troubleshooting & Issues Discussion' started by wxtr7, Sep 11, 2021.

  1. wxtr7

    wxtr7 Well-Known Member

    Joined:
    Jun 1, 2019
    Messages:
    210
    Likes Received:
    751
    After seeing a couple reports of crashes around Dresden and my computer seeming to work harder than it usually does around Dresden (though I've had no crashes), I ran a little test.
    I took an ICE service out of Riesa (Frankfort Flughafen - Dresden ~10AM), which I'll be using for reference.
    For reference, my computer:
    i7-9700K, GTX 1050Ti, 16GB RAM, SSD, in game graphics settings are on high, 100% scaling
    I usually average ~40-50 FPS, and rarely if ever fall below 30FPS

    Starting in Riesa, monitoring TSW process from task manager:
    - Leaving Riesa, TSW using ~4G RAM - which is normal. CPU usage ~35-45%, occasional spikes to 50%, again normal. This remained relatively constant through until about halfway through the avoiding line.
    - About 16km before Dresden-Neustadt, RAM begins climbing, and by the end of the avoiding line it's up to 4.7G.
    - ~7.5 - 6.8 km from Dresden-Neustadt, CPU usages begins to average 50% & RAM has climbed to 5GB
    - At Dresden-Neustadt, RAM is now 6GB, CPU is averaging 55-60%
    - By Dresden Hbf, RAM maxed around 6.3/6.4G, and CPU continued at 55-60%

    My GPU behaved normally and it never maxed out the available 4G VRAM (maxed ~3.7).

    Now I realize that Dresden area has quite a few assets that are loaded so it may just be this is what this route is, but given that this behavior is specific to in and around Dresden and even busy areas of other routes (like HMA) don't work my computer like that, something seems off. This isn't necessarily alarming or concerning b/c everything is still operating within normal range, but does seem like some optimization work may be needed. Also, even though this is just one run, I've noticed similar results just randomly checking CPU/RAM stats.
     
    • Like Like x 1

Share This Page