Good morning TFP/Applicable parties,
I have less of a "Log problem" and more of an optimization problem. Specifically on my rig, I have issues with major FPS drops with very little time into the game. This, historically, has been one of my most played games in the span of its existence (I hopped on in A9).
Specifically, I have issues because of my large-thread CPU. For context, although dated, these are the hardware specifications for my Desktop:
AMD 2990WX Threadripper 32 core/64 Thread (3.00GHz Clock speed - Not overclocking)
-Set a service for Bitsum's Dynamic Local Mode as a background service
-Set Process Lasso for CPU Priority on high for 7dtd.exe
-Set Process Lasso for CPU Affinity on Node 1 for limited core input (Less starved threads)
-Set Process Lasso I/O priority for high for increased chunk read/write for responsiveness
128gb DDR4 Corsair Vengeance RAM
-Manually set to 2933MHz with looser cycles (16-18-18-38-52) to mitigate chunk page faults
2x NVIDIA RTX 2080 TIs (11gb VRAM per card)
-Linked via SLI bridge
-Set to maximize 3D performance for main profile, Maximum performance power profile
-Threaded optimization set to ON
-Triple buffering disabled
-Vsync disabled
Specifically, I'm not sure how root tasking is done, but I do think it is heavily CPU bound, and takes little advantage of VRAM. I can't confirm it, but it's a small amount of threads possible to load. The way I was able to troubleshoot this was by disabling core 0 (The windows fighting core) within ProcessLasso and evaluating the difference.
I'd be overjoyed if a possibility was implemented to assess hardware specifications before the game's first load. I know there's a considerable amount of overhead on this particular issue, and likely will result in egregious refactor of some root level services. If I can provide any further information, please let me know. I'd be happy to supplement where necessary.
Thank you for hearing me out on this rather long-winded topic. I would sincerely be overjoyed if something could rescue this game, as I've poured so many hours into it over time.
I have less of a "Log problem" and more of an optimization problem. Specifically on my rig, I have issues with major FPS drops with very little time into the game. This, historically, has been one of my most played games in the span of its existence (I hopped on in A9).
Specifically, I have issues because of my large-thread CPU. For context, although dated, these are the hardware specifications for my Desktop:
AMD 2990WX Threadripper 32 core/64 Thread (3.00GHz Clock speed - Not overclocking)
-Set a service for Bitsum's Dynamic Local Mode as a background service
-Set Process Lasso for CPU Priority on high for 7dtd.exe
-Set Process Lasso for CPU Affinity on Node 1 for limited core input (Less starved threads)
-Set Process Lasso I/O priority for high for increased chunk read/write for responsiveness
128gb DDR4 Corsair Vengeance RAM
-Manually set to 2933MHz with looser cycles (16-18-18-38-52) to mitigate chunk page faults
2x NVIDIA RTX 2080 TIs (11gb VRAM per card)
-Linked via SLI bridge
-Set to maximize 3D performance for main profile, Maximum performance power profile
-Threaded optimization set to ON
-Triple buffering disabled
-Vsync disabled
Specifically, I'm not sure how root tasking is done, but I do think it is heavily CPU bound, and takes little advantage of VRAM. I can't confirm it, but it's a small amount of threads possible to load. The way I was able to troubleshoot this was by disabling core 0 (The windows fighting core) within ProcessLasso and evaluating the difference.
I'd be overjoyed if a possibility was implemented to assess hardware specifications before the game's first load. I know there's a considerable amount of overhead on this particular issue, and likely will result in egregious refactor of some root level services. If I can provide any further information, please let me know. I'd be happy to supplement where necessary.
Thank you for hearing me out on this rather long-winded topic. I would sincerely be overjoyed if something could rescue this game, as I've poured so many hours into it over time.