1 min
For the BETA we have a stripped back version of the Mario kart. It had one track that was playable but had a lot of the functionality found in the original. There were a range of systems that we had implemented in the BETA to be able to produce a game similar to Mario kart.
The toolkit is used as the asset pipeline so it imports all our models, sprites, sounds or any data that we need the toolkit is also used to organize and change the Json files that use to store all the data for the game.
The physics showed how we got track collision working so it allowed th kart to be able to go around track such as Mario Kart Stadium fine as it used a ray cast to check if its near the track and then it would stick to it.
The camera system showed off the different cameras we had in the game such as a cinematic cam for the intros, a follow cam for each player and a orbit which span around the player once they had crossed the finish line.
The items work in the same way to the original Mario kart in that a player would go through an item box to pick up an item and then be able to use that item when they pressed a certain button.
The sounds system is used to play certain sound effects or music at certain points in the game.
The system displayed all the information that a player needs to know such as their current lap, position and what item they have. This what specific to each player.
Subscribe to this blog via RSS.
Low level programming dev diary 28
Text based adventure dev diary 6
Level design developer diary 3
Game engine programming dev diary 14
Audio-visual production dev diary 7
Audio-Visual Production: Particle System Mesh Spawning Issues
Posted on 20 Feb 2020Low level programming dev diary (28) Text based adventure dev diary (6) Level design developer diary (3) Post mortem (4) Ex-machina dev diary (11) Game engine programming dev diary (14) Network game dev diary (11) Audio-visual production dev diary (7)