Tutorials Enable Multicore! Support For Cities Xl Platium

Is this a joke?

 

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.

 

I'm a little bit skeptic but if it actually works it's worth downloading.

 

we should to do it every time b4 start to play?

 

1. You're only setting the affinity to one core.
2. You don't need a secondary program wasting processing power and memory. Set the affinity with a shortcut.



C:\Windows\System32\cmd.exe /C START "Cities XL Platinum" /high /affinity 2 "C:\Program Files (x86)\Cities XL Platinum\CitiesXL_Platinum.exe"


http://www.eightforums.com/tutorials/40339-cpu-affinity-shortcut-program-create-windows.html

 

Is this process necessary for every time the game is started or do you only do this once?

 

I tryed this, but the game slowed down and i had to wait to load menu`s, to place buildings....without it the game works normal - I have an intel core I7....so I don`t use this anymore.

 

Yo Corel i7, mi juego es lento, además de tener 16 GB de RAM y 4 GB de vídeo, este método no interrumpe el funcionamiento de mi pc?, Algo, pero no hay manera de que este tutorial fue dado en español, ya que la traducción de google deja muchas lagunas y es difícil de entender qué hacer,

 

I hope you find a solution like this for inter core i7. Some cities of the population over the 600.000. Make me crazy about slow game.

 

Me abrí la supresión de la shadercache

 

I'll add my grain of salt to this...
There's a difference between talking about Multicore and Multi-thread, and also Parallelization
An application will support multicore if it's specifically written to leverage the power of multi-core CPUs, say for example, Raytrace Rendering, in which all cores will perform the same task with the same bank of data (each core will process its own fraction of the image)
There's also Multi-threading, in which an application can start "mini applications" (better known as threads) nested within the same process. Generally, each little app performs one task, say, one thread will control the audio, another will control physics, another could control data flow, etc. Note that I did not mention anything about the CPU and multi-threading, but each thread could be Multi-core optimized if it's made to do so.
Parallelization is the ability for a task to be completed by several independant workers, like the Raytrace example. Not every task can be parallelized though, if a calculation requires data that is not processed yet, or being processed by another thread.
The main difference is, Multi-core is about doing one common task with several CPU cores, and Multi-thread is about an application trying to do several tasks. An application that doesn't specifically support multicore may assign all of its threads to the only CPU that the OS assigns to it.
I think Cities XL might just be a regular Multi-thread application and the underlying Game engine may have support for Multi-core, but could be poorly implemented in Cities XL. By forcing the game to only use the CPU3 you are shifting all the game threads from the heavily loaded CPU0 to a free core, which bumps slightly the response time, because the CPU3 doesn't have to deal with any other concurrent Uni-core applications nor the OS. For the rest, it could be that the game engine senses the shift in core availability and adjusts accordingly. Then, by re-enabling the remaining cores, the game engine senses that again, and adjusts once again to use the rest of the system resources. But, that still might leave the Cities XL threads at CPU3, so you're offloading it a little bit more. Still, a noticeable boost in performance.