It’s impossible to have a good game when it’s unresponsive, slow, has frequent FPS dips and can only work on a hardware that costs more than going to Harvard. It’s also impossible to finish a game if all you ever do is tweak everything for speed. But there are ways to approach it level-headed and get great results.
Making a game and mindlessly working on it without a goal or while constantly moving the goalposts is easy. Easy in the sense that it doesn’t involve any management or thinking ahead, you can always concentrate on here and now, sit down whenever you want and do whatever you want. And it works until one day you find yourself having no idea what to do.
Shaders are not an easy thing to work with with scant and/or hard to find documentation. Post-processing shaders are not easier (but they are harder only be a really small margin) and after spending a significant amount of time working things out I decided to share it for your benefit (and mine, in case I forget things in the future).
For some reasons I can no longer remember I wanted to update MonoGame from 3.5 to 3.6 It was pretty straightforward but I am still a C# newb so I worried things might not work the way they should. Here is my recollection of what I had done to achieve the update.
After a year since the release of Monstro: Battle Tactics it’s time to look at the project with a critical eye and see what was wrong. And there is a lot to say about what was wrong, unfortunately.