While that is very easy to set up, we also want to maintain the general look of the game, even when using lower quality settings. One way of handling it is to have both, allowing players to toggle between them based on whether they prefer higher performance or higher graphics quality. When choosing between options, we ask ourselves questions like whether we want the 70% quality fog that drops performance by 15%, Or the 80% quality fog that drops performance by 35%? When determining which features to add we measure 2 things:the performance impact, and the net gain of the visuals.įor example, something seemingly straightforward like Environmental Fog can be implemented in multiple different ways. There are many varieties of visual features we could incorporate into our game, but every single one comes with a certain cost.

Optimization is all about compromising and cutting corners. Through our performance tweaks, we have created ways that will allow us to have hundreds of monsters, and thousands of homing projectiles, active without affecting the game’s performance. For example, If we can only spawn inr 20 active monsters at any time, then that greatly restricts the kind of crazy battle scenarios we can have in the game.

So why are we chasing these optimizations so aggressively? Because every bit of extra performance we find means fewer restrictions on game design going forward. This third part will focus on various interesting elements we worked on for optimizations, including improvements to the CPU/GPU, gameplay optimizations, and other changes that our non-dev fans can get excited about. We then discussed the benchmark results we were able to achieve during the optimization process. Welcome to part 3 of our Death Carnival optimization series! In part one, we discussed our goal of achieving great frame rates on as many levels of hardware as possible.

Unity particle playground fog