Since our latest patch (v.1.4.2883) we have introduced a new shader to Crash Force. This shader is applied by implementing in UE4, a post effect to both the Camera and as a Post Process Volume. The Sobel Effect of the Edge Detection and the RGB decolouration are implemented on the Volumes throughout the maps. The Grain FX and the rest of the lens artefacts have been implemented directly on the players' cameras. We chose to allocate the lens effect on the camera so we could keep things tidy.
This graphical change was implemented first in our map Aquila Plains, as you can see from the editor screenshots below:
ThenCicumaForest (our second map) was adjusted accordingly as you can see below:
Clava Tombs, our last map was then adjusted to match the rest of the changes of the other two maps:
Lastly, our Main Menu "room" was then adjusted to meet the map changes:
Overall, we think that this art direction really benefits Crash Force and gives it a futuristic sci-fi approach, and at the same time solves the issue of low brightness in specific areas of our maps and pops out the detail of both the hovercrafts and map.
We posted a small gaming clip to on Facebook to show the graphical changes in Aquila Plains :
Hello, everyone! Last time we saw how we created our hovercraft system and incorporated it in the Shooter game example provided by Unreal Engine 4. Today, we will see how the shooting system was implemented and why. First things first, the very first shot ever fired by a hovercraft in Crash Force was a "cheat". What I mean by that is we made the hovercraft "hold" a weapon on its turret and shoot it. Then, we went and created bone sockets for our weapons to fire from and assigned to each hovercraft a weapon that would be the one it would fire. We created projectiles for those weapons and handled the properties of those projectiles (i.e. damage, range, ammo, fire rate). Now, each hovercraft had a weapon it could fire.
Playing with weapons a new suggestion came to the table. What if each hovercraft had two weapons? We fancied the idea of being able to wield two weapons instead of one, so we started walking down that avenue. We created two different weapons per hovercraft and assigned them these weapons. Then we created a slot where the equipped weapon would be held in memory, where the other one would be considered holstered or not equipped. We created the logic behind toggling weapons and firing the equipped weapon only and voilà.
Now all that we thought was left weapon wise, was to create different weapons for each hovercraft and assign them those weapons. This is how we created the base of our weapon system.
I want to tell you a story, our story, more specifically the story of our game Crash Force and how it became to be. Crash Force today is an online multiplayer arena shooting game with a lot of RPG elements where players are different hovercraft types. The thing is though that, like most things, it did not start like that. It took a lot of implementation cycles and changes along the way to becoming what it is. What I hope to do is create a roadmap of the way getting there.
First things first. Crash Force began its journey with a different name. Back in 2013, when our project idea first started, Crash Force was named Car Wars and it was an internship project created in European University of Cyprus. At the time, Car Wars (as the name suggests) was an idea of a game where cars will shoot each other. The first draft of the idea started forming in Unreal Development Kit (Unreal Engine 4 was not available at the time). By the end of the internship, we had created a prototype LAN-based game where cars (and a motorcycle) could move and shoot each other down with different weapons. It was a very simple concept for a month-long internship.
Upon the internship ended, we went on with our lives since we had other obligations (whether it was finishing a Bachelor’s degree or looking for work or working). The seed of Car Wars though was planted. We all had it in the back of our heads. We all wanted to resume it at some point in our lives. In February 2015, we decided to proceed with the development of Cars Wars in our own time. We were working at the time, making development harder. We scratched the original prototype and decided to try creating our game with Unity. The idea of Car Wars evolved along the way, adding gas points for a refill, different speed limits for our cars and new weapons.
Nine months later we decided that creating games was what we loved doing, and we should proceed to do that on a more professional level. After creating our company Ascanio Entertainment, we decided to start everything from the start with the correct structure and utilizing the knowledge that we had gained through our two prototypes. This journey begins with the day we started developing Crash Force in Unreal Engine 4 as a company and will continue all the way until today. Enjoy!