Browse Library
Sign In Start Free Trial
Close icon Search icon
Account
Browse Library Advanced Search Sign In Start Free Trial

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Augmented Reality Game Development
  • Toc
  • feedback
Augmented Reality Game Development

Augmented Reality Game Development

By : Micheal Lanham
5 (3)
close
Augmented Reality Game Development

Augmented Reality Game Development

5 (3)
By: Micheal Lanham

Overview of this book

The heyday of location-based augmented reality games is upon us. They have been around for a few years, but the release of Pokémon Go was a gamechanger that catalyzed the market and led to a massive surge in demand. Now is the time for novice and experienced developers alike to turn their good ideas into augmented reality (AR) mobile games and meet this demand! If you are keen to develop virtual reality games with the latest Unity 5 toolkit, then this is the book for you. The genre of location-based AR games introduces a new platform and technical challenges, but this book will help simplify those challenges and show how to maximize your game audience. This book will take you on a journey through building a location-based AR game that addresses the core technical concepts: GIS fundamentals, mobile device GPS, mapping, map textures in Unity, mobile device camera, camera textures in Unity, accessing location-based services, and other useful Unity tips. The technical material also discusses what is necessary for further development to create a multiplayer version of the game. At the end, you will be presented with troubleshooting techniques in case you get into trouble and need a little help.
Table of Contents (11 chapters)
close
close
Preface
Preface
What this book covers
What you need for this book
Who this book is for
Conventions
Reader feedback
Customer support
Free Chapter
1
1. Getting Started
1. Getting Started
Real-world adventure games
Getting into mobile development with Unity
Getting started with Unity
Summary
2
2. Mapping the Player's Location
2. Mapping the Player's Location
GIS fundamentals
GPS fundamentals
Summary
3
3. Making the Avatar
3. Making the Avatar
Importing standard Unity assets
Summary
4
4. Spawning the Catch
4. Spawning the Catch
Creating a new monster service
Checking for monsters
Summary
5
5. Catching the Prey in AR
5. Catching the Prey in AR
Scene management
Introducing the Game Manager
Loading a scene
Updating touch input
Colliders and rigidbody physics
Building the AR Catch scene
Using the camera as our scene backdrop
Adding the catching ball
Throwing the ball
Checking for collisions
Particle effects for feedback
Catching the monster
Summary
6
6. Storing the Catch
chevron up
6. Storing the Catch
Inventory system
Saving the game state
Setting up services
Reviewing code
Monster CRUD operations
Updating the Catch scene
Creating the Inventory scene
Adding the menu buttons
Bringing the game together
Mobile development woes
Summary
7
7. Creating the AR World
7. Creating the AR World
Getting back to the map
The Singleton
Introducing the Google Places API
Using JSON
Setting up the Google Places API service
Creating the markers
Summary
8
8. Interacting with an AR World
8. Interacting with an AR World
The Places scene
Google Street View as a backdrop
Slideshow with the Google Places API photos
Adding UI interaction for selling
The game mechanics of selling
Updating the database
Connecting the pieces
Summary
9
9. Finishing the Game
9. Finishing the Game
Outstanding development tasks
Missing development skills
Cleaning up assets
Releasing the game
Problems with location-based games
Location-based multiplayer game
Firebase as a multiplayer platform
Other location-based game ideas
The future of the genre
Summary
10
10. Troubleshooting
10. Troubleshooting
Console window
Compiler errors and warnings
Debugging
Remote debugging
Advanced debugging
Logging
CUDLR
Unity Analytics
Issues and solutions by chapter
Summary

Monster CRUD operations

Currently, our Inventory service only creates the same monster, and we need it to create new monsters and perform other operations, such as read, update, and delete monsters. By the way, the standard database operations of Create, Read, Update, and Delete is often referred to as CRUD. So, roll up your sleeves; we are actually going to do a little coding and build the monster CRUD.

Open up the InventoryService script in the editor of your choice again and scroll down to the CreateMonster method. Delete the CreateMonster method and perform the following instructions to replace it and add the other new methods:

  • CREATE: Add the following method in order to replace the CreateMonsters method:

    public Monster CreateMonster(Monster m) 
{ 
    var id = _connection.Insert(m); 
    m.Id = id; 
    return m; 
}

    Instead of creating a hardcoded monster, we now take a monster object and insert it as a new object/record in the database. This returns the...

End of Section 6
Next Section
bookmark search playlist download
font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected
Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete