Difference between revisions of "Thread:User talk:Beaming/cpuConstant/reply (9)"
Jump to navigation
Jump to search
m (Reply to cpuConstant) |
(No difference)
|
Latest revision as of 21:38, 17 October 2017
Ok. I see why skipped turn event is not fired. But the wildly fluctuating cpu constants is still under the question. The cpu constant calculation is done within one call: it just long loop with heavy math.
Unless GC kicks in at random I see no explanation for it. The problem that it probably does it during the round as well, since I see wildly fluctuating timing in my profiler.