I use a legacy version on GOG and have to give the game access to Cores 0 and 1 on my computer just for it to properly run, otherwise, I get runtime errors before it starts. But when I do, it runs perfectly and smoothly. No errors, nothing.

Originally posted by Amaterasu:

I use a legacy version on GOG and have to give the game access to Cores 0 and 1 on my computer just for it to properly run, otherwise, I get runtime errors before it starts. But when I do, it runs perfectly and smoothly. No errors, nothing.

That's kind of weird... but, then I don't know all the specifics about your system either. In my case, I disable 'virtual' cores or secondary threads per core and only use physical cores--1 thread per core. This is done in the Bios. And, I disable additional (extra) cores so that only the first four are ever used--also done in the Bios. Basically, it leaves me with an overpowered quad core cpu that can hit higher speeds with it's Turbo mode--more cores = lower top speeds since there's a reduction for each additional core used after the primary / core 0. Anyway... I really don't run into problems running games... nothing more than possibly an issue with a really old game needing some compatibility setting--which is an easy fix. So, it perplexes me a bit why a person might have to "give the game access to Cores 0 and 1" or, maybe I'm just not clear what that even means... giving access. The operating system controls which cores get used for things.

@rodsfm162
Check this thread...
https://steamhost.cn/steamcommunity_com/app/208580/discussions/0/624075566863672441/

Originally posted by Mardoin69:

Originally posted by Amaterasu:

I use a legacy version on GOG and have to give the game access to Cores 0 and 1 on my computer just for it to properly run, otherwise, I get runtime errors before it starts. But when I do, it runs perfectly and smoothly. No errors, nothing.

That's kind of weird... but, then I don't know all the specifics about your system either. In my case, I disable 'virtual' cores or secondary threads per core and only use physical cores--1 thread per core. This is done in the Bios. And, I disable additional (extra) cores so that only the first four are ever used--also done in the Bios. Basically, it leaves me with an overpowered quad core cpu that can hit higher speeds with it's Turbo mode--more cores = lower top speeds since there's a reduction for each additional core used after the primary / core 0. Anyway... I really don't run into problems running games... nothing more than possibly an issue with a really old game needing some compatibility setting--which is an easy fix. So, it perplexes me a bit why a person might have to "give the game access to Cores 0 and 1" or, maybe I'm just not clear what that even means... giving access. The operating system controls which cores get used for things.

@rodsfm162
Check this thread...
https://steamhost.cn/steamcommunity_com/app/208580/discussions/0/624075566863672441/

I enter task manager and set affinity, because by default, KOTOR 2 only uses Core 0 of my 12 core CPU. For some reason it won't run if I only allow it to use a single core, but runs flawlessly if I have it run on cores 0 and 1.

How it's done on Win 11 at least is you open task manager, go to details, scroll down to find swkotor2.exe, right click on that and then select set affinity. Then you can select what cores it can use.

Ok, I get what you're saying. So, that setting affinity in task manager is basically limiting the number of cores being used while the game is running. And, you are dictating specifically which cores are used also. And, yes... assigning only one core is not great cuz that limits the game AND windows to one core while the game is running in the foreground. You want that extra core for windows to do it's routines with while playing the game. A good rule of thumb is always use one extra core on top of however many cores a game works optimally with. For example, I've found through performance benchmarking that some games will get the highest fps using 3 PHYSICAL cores--never use 'logical' or virtual cores / additional threads per core for games as it 'can' reduce performance. Anyway, with that testing in mind, I then activate 4 cores... 3 that will be mostly used by game and one additional for Windows--in case it needs to run some extra tasks while playing. This way windows doesn't cut into the performance of the game--theoretically. But, play-testing shows that this method seems to work quite well.

Now, onto your situation... a lot of times CPU's are advertised with "12" cores but, may actually only have 6 physical cores and 2 threads per core for a 'logical' (virtual) 12 cores. Then the core numbers are assigned as 0 and 1 with 0 being the physical core and 1 being the 2nd thread for that core. It continues with 2 and 3, 4 and 5, 6 and 7, 8 and 9, 10 and 11. So, when you set affinity, you actually want to set core 0 and 2 in order to activate two 'physical' cores. Now, this is a general rule of thumb and your specific CPU maybe configured a little differently, idk... would have to research your exact cpu make and model to know for sure. I have seen the case where AMD would assign the physical cores as 0, 1, 2, 3, and the logical cores (2nd thread per core) as 4, 5, 6, and 7. So, have to look it up to be sure. On top of that... is it a 6/12 (physical / logical) cpu or actually just a 12 physical core cpu? Also wouldn't know without looking up the make and model. Anyway, that's just some info for you to take a look at / think about.