Multicore Support with Cites XL!
- CitiesXL 2011
- CitiesXL 2012
- CitiesXL Platinum
Some of you might already knew this. But previous versions seems only work on AMD processors. Tested the ProcessHacker 2.32 with my intel i5, runs perfect!
Test Result: All four cores are processing, just like XXL. Slight fps boost in game. But the Game still slows down if you load a huge city for over two hours. Anyway, the XXL has the same problem.
3rd Party Tools: ProcessHacker 2.32 can be downloaded from tutorial file.
The Overall CPU occupation in pictures below seems pretty low because I Alt-Tabed out of Cities XL to make screen shot for processes. But you can tell from the charts about CPU occupations in previous period
Before Enableing Process Hacker:
After Enableing Process Hacker:
Follow the Step below carefully:
Open Process Hacker, then launch Cities XL.
In the Process tab of ProcessHacker, find Cities XL Process.
RightClick, then click affinity
Uncheck 3 CPU cores, only left 1, then hit OK.
Reopen affinity, check 4 cpu cores, then hit OK.
Cities XL is now running on Multicores, the core resource occupation is very similar to Cities XXL. It sounds crazy that a third party tool could make a single-core game running on multicores. But tested and it works just perfect.
Even after hours of play, and with cities xl as the only application running on my windows, 4 cores are always in use.
According to Monty:
"Multi core doesn't work like that, software must be specifically programmed to distribute the processeses.
To me it looks like you just moved the game's load from CPU0 to CPU3, and considering apps will usually use CPU0 that would explain the marginal performance gain.
I'm not an expert at all but is well known that activating multicore in non multicore applications is not possible, the best you can do is to distribute the load manually setting affinity, which not necessarily will improve performance."
So as monty said, it is just a re balance of CPU load, not really multicore-support! However I do notice a few fps improvement. I wish those who downloaded ProcessHacker can feedback your test results.
It's not long before we will be moving. The new hosting has been setup and the next thing to be done is to change the DNS. When it's changed it may take between 24 to 48 hours to take effect. During this time XLN will be closed so it can be backed up. When the new DNS takes effect, you will see a basic page with a message regarding the move. Note: It may take up to two weeks to get XLN up and running again.Dismiss Notice
Tutorial Enable MULTICORE! Support FOR Cities XL Platium
3rd Party Tools