Planetary annihilation titan portals how to#
Planetary annihilation titan portals update#

However, Pyxeralia are showing how to come back in style and within a week they were able to get it back into Mostly Positive overall. When it released with Linux support on May 27, they ended up quickly getting only a 23% positive user score giving them a considerably negative outlook. Mists of Noyah is a new co-op survival game from developer Pyxeralia, it's definitely pretty looking with some wonderful lighting and art but they had a very rough launch.

After a rough launch, Mists of Noyah seems to be turning things around.

One hadsjust to see how much delay has been introduced in 'Ashes of the singularity' updates. I know it's hard to make business with RTSs today. So are you here because you had nothing better to do at Uber, or is there something bigger coming next ? I guess nobody suspected Uber would be back on the PA front. And i guess it's all about balancing efforts and the chances of success. As i understand, fixing is not impossible but obviously not possible unless uber can allocate large amount of time to rework the system. To be honest i had hoped you could improved the navigation system to have larger groups of units moving alltogether without slowdown on a single planet. Let's see what you can do, i've not doubt you will come with brillant ideas Mike “Sorian” for all these details Sorian. And that doesn’t even get into other fun stuff like modern toolchain and Coherent GT updates. So, what’s next? There is still more work to be done with navigation, there is still the sim tick stuff to be investigated, and some AI updates as well (of course), starting with a much needed performance pass. There are so many little acceleration features and so much lazy loading that is simply prevents multithreading without a significant amount of work. On the multithreading front, the navigation system has proven to be quite difficult. The integrator is also doing a better job of allocating in blocks instead of individually.

I have a new system in place that saves off vectors of cost cells (the objects the integrator makes tens of thousands during voxel integration) for reuse. I am hoping to split some of the plan steps (our sim has plan, execute, and record steps for entities) out into a group that can also run at the same time as the navigation/physics update.įor the navigation system, I have been mainly focusing on the epic number of allocations the navigation system does during voxel integration.

Planetary annihilation titan portals update#

Right now I have it running alongside the economy update, but the economy update is only a small part of the overall update, so not much of a win there yet. I have also started work on restructuring the sim tick a bit to allow the navigation and physics updates to happen alongside other updates. However, when you throw threading into the mix it gets ugly. Under normal operation this isn’t a huge issue, as this is a single call that immediately returns and it was just being done thousands of times more than it needed to be. It turns out that there is no guarantee that the vector of pairs that we get back does not contain duplicates. The physics system utilizes an HGrid (described as a loose octree) to find potential entity overlaps using a function called buildPairs. There were the usual small issues to fix, but threading the physics update revealed a larger issue. I figured, since we should only be looking at two unique physics objects at the same time, it should be possible to thread this. Early this week I was focused on the physics update. I’ll be continuing right where I left off! This time I am digging further into the sim to see where I can split large groups of tasks over threads to speed things up. So, now that I am back, you may be wondering what I am working on now. Fortunately, there were not many areas of contention between threads and a performance win was born. Initial testing blew up spectacularly, as I expected it would. Their updates tend to only act on a single entity. Since navigation and physics are typically the worst performance offenders, separating updates by planet seemed like a good plan. The most natural separation was based around planets. My initial focus was on areas of the simulation where I thought it would be easiest to do things in parallel. My primary focus was attempting to improve performance by multithreading parts of the simulation. Two years ago I was given the opportunity to continue work on my baby, Planetary Annihilation, for the 99337 Performance Update. Is back working on server simulation performance with multithreading this month and we have a technical update to share on his work for the next update.