I have come across numerous instructions on how to accomplish this task, but unfortunately, none have proven to be effective.

My current objective is to initiate a game and configure it to utilize all available cores. This action is necessary because the game, specifically Assassin’s Creed Odyssey, encounters crashes when running on newer CPUs. However, I have noticed that manually setting the game to utilize all cores post-launch results in the cessation of these crashes.

As of now, I have managed to launch the game using a shortcut that contains the following code snippet in the target box:

“`cmd.exe /c start “” /Normal /affinity FFFFFFFF “G:GamesAssassin’s Creed – OdysseyACOdyssey.exe”“`

Previously, the game ran flawlessly on our old i7-4790K without any issues. The transition to my current setup, featuring an i9-14900K with 32 cores (CPU0 to CPU31), prompted me to input a series of thirty-two ‘1’s into a binary-to-hex converter, resulting in the hexadecimal value FFFFFFFF.

Despite successful experiments with adjusting the priority within the shortcut, I have encountered difficulties in modifying the processor affinity settings.

​I have come across numerous instructions on how to accomplish this task, but unfortunately, none have proven to be effective. My current objective is to initiate a game and configure it to utilize all available cores. This action is necessary because the game, specifically Assassin’s Creed Odyssey, encounters crashes when running on newer CPUs. However, I have noticed that manually setting the game to utilize all cores post-launch results in the cessation of these crashes. As of now, I have managed to launch the game using a shortcut that contains the following code snippet in the target box: “`cmd.exe /c start “” /Normal /affinity FFFFFFFF “G:GamesAssassin’s Creed – OdysseyACOdyssey.exe”“` Previously, the game ran flawlessly on our old i7-4790K without any issues. The transition to my current setup, featuring an i9-14900K with 32 cores (CPU0 to CPU31), prompted me to input a series of thirty-two ‘1’s into a binary-to-hex converter, resulting in the hexadecimal value FFFFFFFF. Despite successful experiments with adjusting the priority within the shortcut, I have encountered difficulties in modifying the processor affinity settings.  Read More

​