Devs need to code the game to use more than one core. That is an old game that requirements only state it needs a cpu of a certain speed. Nothing mentioned a dual, quad core or higher so it likely wasn't coded to use more than 1 core

EDIT: missed you mentioned the remaster. While that does list CPUs with more than 1 core it's possible that your CPU can handle doing most if not all of the work on a single core

Originally posted by Supafly:

Devs need to code the game to use more than one core. That is an old game that requirements only state it needs a cpu of a certain speed. Nothing mentioned a dual, quad core or higher so it likely wasn't coded to use more than 1 core

oooh that makes sense actually. thx man :)

Originally posted by JPEG.PNG:

Originally posted by Supafly:

Devs need to code the game to use more than one core. That is an old game that requirements only state it needs a cpu of a certain speed. Nothing mentioned a dual, quad core or higher so it likely wasn't coded to use more than 1 core

oooh that makes sense actually. thx man :)

Did edit while you were replying. Your CPU is 50% better than recommended CPU

Originally posted by JPEG.PNG:

i keep seeing in most of my games that only one cpu core is getting some decent workload, one example would be system shock 2 remaster where only one core is maxed out while the rest is chillin. Is that normal behaviour or am i misunderstanding the readouts?

My system runs an i7 9700k and an 2070 super

In most cases software will use the resources it needs that are available. If it's using fewer resources than you assume it ought to be, but the software is still running fine, well the problem is probably your assumption.

And in general not every bit of software benefits from arbitrarily throwing more cores at a problem. if the work is entirely sequential in nature, where each bit depends on the previous bit, it might not be a use case for multiple cores. But something where the work can always be split up and bits done on all the cores and reassembled at the end, like say video encoding, will often use all the cores.

There just isn't a one size fits all solution to how many cores a program should be using. And the number of cores being utilized can also vary within the program itself. again video encoding, when you're just poking around the UI and configuring settings, you're probably only using a single core. When you actually begin the work of encoding then all the core might be engaged.