This is especially an issue with somewhat older AMD CPUs, which have significantly lower single-core performance than otherwise equivalent Intel chips. follow the default core scheduling)Īdditionally, being mostly a single-core game, your CPU's single-core performance is most important, not number of cores or other traits. You'll find most programs behave this way, not just RW (i.e. This means that, even thought it COULD be split between cores, it simply doesn't happen the default algorithms are generally quite conservative, and this type of behavior is best for making MANY different processes work best together, rather than making one small set the fastest ^^'.
This has little impact, however, because it uses the OS's default core scheduling, whichever OS you're using, instead of using a custom algorithm. It's possible, as well, for a mod to have both issues.Ĭontrary to popular belief, RW IS multithreaded, although not massively so. Conversely, mods with a lot of item definitions and changes take a long time to load. This is exactly why script-heavy mods slow down gameplay. Some slowdown is inevitable, over time, as you add more and more pawns and items that require "per-tick" calculations.
0 kommentar(er)
