IMO, program multi-threaded games is not that hard, but the problem is where and how to divide the game into parts. It will gain no performance boost if we divid the game in a wrong way.

The single threaded process is probably like this, Game State -> AI actions -> Physics -> Graphics and loop. If we cut them into pipeline stages, we probably gain nothing. We still have the same amount of delay in the game.

It has to be reodered to something like this

Game State -> AI actions thread and Physics thread -> Graphics. Each stage is dependen by the previouse stage result. By doing this, we only shorten the delay from 4 to 3 times of the longest stage. Multi-threaded utilization is only max at two in second stage.

In order to truly tab the power of multi-threaded envirnment, we have to shorten the stage as well. This is where the hardest part, especially with physics.

Where to optimize, IMO explotion is always a power monster, optimize that is first priority.

• 軒轅劍
• 軒轅劍貳
• 軒轅劍外傳－楓之舞
• 軒轅劍參
• 軒轅劍外傳－天之痕
• 軒轅劍肆
• 軒轅劍外傳－蒼之濤
• 仙劍奇俠傳DOS
• 仙劍奇俠傳WIN95
• 新仙劍奇俠傳
• 仙劍奇俠傳二
• 仙劍奇俠傳三
• 仙劍奇俠傳三－外傳問情篇
• 阿貓阿狗
• 阿貓阿狗2
• 霹靂奇俠傳
• 魔幻騎士

• 大富翁 3
• 大富翁 4
• 大富翁 4 之 超時空之旅
• 大富翁 5
• 大富翁 6
• 大富翁 6 之 大家來搶錢
• 正宗台灣16張麻將 2
• 正宗台灣16張麻將 3
• 軒轅伏魔錄
• 天使帝國 3
• 明星志願二
• 仙劍客棧
• 瘋狂搖搖杯