Update 016 - Profiling
[p]We’ve packed Kabonk! with a ton of fun and exciting improvements! And did some profiling. Thanks Ari![/p][p]Originally, we planned to release the game in September/October, and technically, that could’ve worked. But as we’ve said time and time again: a game is never truly finished. Sure, there are plenty of "finished" games out there, and Kabonk! is, in a sense, complete. But like any development project, there’s always room to make it better: tweaking gameplay, refining code, boosting FPS, adjusting particles, enhancing VFX, and so much more.[/p][p]Over the past few months, with the extra time we’ve had, we’ve polished not only the visuals and game flow but also the fun* factor. Oh, and we’ve significantly boosted performance: we’ve even doubled the FPS on some machines! Why? Because why not? Why wouldn’t we aim to make this gameplay-heavy game run as smoothly as possible?[/p][h3]Dusting Off[/h3][p]We pulled some older laptops out of storage and tested Kabonk!... Crash. Wait, what?![/p][p]![]()
[/p][p]We’ve all seen, read, and heard players talk about Unreal Engine games crashing. How is it that games from 10+ years ago often look better, run smoother, and crash less than some of today’s biggest titles? Unacceptable, right? Well?:
*It’s complicated.[/p][h3]Develop Like a Gamer[/h3][p]We’re gamers ourselves. We’ve spent hours optimizing factories in games like Factorio, refusing to blame the game when FPS dipped... instead, we improved the factory until it ran smoothly. So why not apply that same mindset to Kabonk!? And that’s exactly what we did.[/p][p]We’ve been:[/p][p]Improving... building... zipping... uploading to Steam... deploying... updating Steam... playtesting... and repeating that cycle for days and days**.[/p][p]We won’t bore you with every detail (yet), but we even added an automatic safe mode. If the game may crash (and for all our sake, lets hope not), it dynamically adjusts performance (at the cost of some visuals) to ensure the game will start.[/p][h3]But Wait, There’s More![/h3][p]Here’s a quick rundown of what we’ve added and improved:[/p]
*It’s complicated.[/p][h3]Develop Like a Gamer[/h3][p]We’re gamers ourselves. We’ve spent hours optimizing factories in games like Factorio, refusing to blame the game when FPS dipped... instead, we improved the factory until it ran smoothly. So why not apply that same mindset to Kabonk!? And that’s exactly what we did.[/p][p]We’ve been:[/p][p]Improving... building... zipping... uploading to Steam... deploying... updating Steam... playtesting... and repeating that cycle for days and days**.[/p][p]We won’t bore you with every detail (yet), but we even added an automatic safe mode. If the game may crash (and for all our sake, lets hope not), it dynamically adjusts performance (at the cost of some visuals) to ensure the game will start.[/p][h3]But Wait, There’s More![/h3][p]Here’s a quick rundown of what we’ve added and improved:[/p]
- [p]Added 4 unique new achievements[/p]
- [p]Fixed physics for the splitting sphere bricks[/p]
- [p]Enhanced visuals and materials for splitting sphere bricks[/p]
- [p]Added sound effects for the ping pong effect[/p]
- [p]Introduced a brand-new song[/p]
- [p]Improved tiling for the dungeon and jungle themes[/p]
- [p]Added extra wow factor when finishing the main game[/p]
- [p]Reduced difficulty scaling in endless mode[/p]
- [p]Removed unused code, actors, and other clutter[/p]
- [p]Lowered memory usage in the lobby[/p]
- [p]Translated a bunch of words.[/p][p]
Remember when we said no UI? Nah, me neither.[/p]