Capitalism 2 and Capitalism Lab Forum

ncmagus wrote: ↑Mon Mar 16, 2020 8:57 am I did notice the game is only using one core on the CPU. Those days, CPU improve the number of core instead of the speed of a specific core. I think you could get a lot more performance late-game if you found a way to implement multi-threading (If each opponent is running as a task, it might be possible to dispatch tasks to different thread without to much work)

qzd1989 wrote: ↑Fri Apr 17, 2020 10:21 am 支持 @ncmagus

如果不改进游戏速度,基本也就只能玩几小时,然后就会因为游戏速度过慢而没法继续下去

这是一个单机游戏,你们也没有计划将它改成网络游戏,所以有没有人修改游戏数据并不是那么重要.

如果不改进游戏速度,再多的新功能新玩法上来,也没法尽兴体验到~

it's a big problem.

ncmagus wrote: ↑Thu Mar 19, 2020 9:15 pm Of course, without knowing exactly how the game works, i can only assume things. So let's assume you compute several different solution and give each of them a score, and then you pick the best one.
In such a situation, i believe you could dispatch to several thread the processing part for every opponent. Then, when all solution have been found, one thread will gather all of those and will then choose the best solution which can be applied.

Let's say you have 3 opponents, and you generate a list of 5 possible outcome for each of them. You can either use 3 threads (one per opponent) or 5 threads (one by "type of outcome", let's say "evaluate building a farm").

Then, on the final thread, you look at the opponent 1, and choose the best solution for him. then the thread moves on to the next opponent and choose the best solution that is still possible, and so on.
Of course, once you processed the first opponent, there might be new solution for the second opponent, but that's how life works : You take decision based on incomplete data. If the opponent want to buy that specific building and it was bought by the previous opponent, then you move to the next best solution.
You could also "try to readjust" the solution: the first opponent bought the terrain you were hoping to buy, maybe there's one nearby that is "good enough".

To avoid having a bias toward the first opponent (he always have the first choice), you could process them (on the final thread) in different order every time.

I hope what i'm trying to say is understandable.

Also, you mention opening a guide might improve speed because you don't have to handle thing behind the guide window. Maybe that's the type of optimisation that could be pushed to a different thread ? (one to process the UI and the other to process opponent's decision)

Or maybe take a shortcut : if drawing the little moving cars take too much processing power, having an option to have less cars shown could be interesting for people with lower cpu. In the game development world, people seem to use a lot of tricks to minimize processing time here and there. Maybe you could find some nice tricks in the "game programming gems" book series (or other similar book)

I know ! it's easy to say something, it's harder to execute it