Okey, first of all: sorry guys for not replying before now... but when @AndrewT pinged me about this in the beta chat i was just so stunned and had to do tons and tons of googling.
Second: my god @Roflknifer11 you should have so much creds for finding this out.
Third: (this is the downer) Stellaris as an application does not handle the mapping between "hardware threads" and "software threads", this is entirely done by your OS, drivers and/or applications like msi afterburner.
So why 1 core is "clogged" is still a mystery for me, might be something in the stellaris threading code that encourage Windows (this does not seem to be an issue on linux nor osx) to just utilize 1 core (i do not doubt this tbh).
But question to you all that have solved the issue with "affinity":
Are you all running hardware throttling controlling software (as msi afterburner or similar)? Does the issue still remain if you disable it?
//Guraan
Second: my god @Roflknifer11 you should have so much creds for finding this out.
Third: (this is the downer) Stellaris as an application does not handle the mapping between "hardware threads" and "software threads", this is entirely done by your OS, drivers and/or applications like msi afterburner.
So why 1 core is "clogged" is still a mystery for me, might be something in the stellaris threading code that encourage Windows (this does not seem to be an issue on linux nor osx) to just utilize 1 core (i do not doubt this tbh).
But question to you all that have solved the issue with "affinity":
Are you all running hardware throttling controlling software (as msi afterburner or similar)? Does the issue still remain if you disable it?
//Guraan