Book Image

Learning AWS Lumberyard Game Development

By : Dr. Edward Lavieri
Book Image

Learning AWS Lumberyard Game Development

By: Dr. Edward Lavieri

Overview of this book

Amazon’s Lumberyard is a 3D cross-platform game development engine for building high-quality AAA games. It makes the process of creating multi-player games and adding realistic characters, stunning terrains, and special effects much faster and more efficient. This book will show you how to use Lumberyard to create a multiplayer 3D game with cloud computing, storage, and Twitch integration for user engagement. We will start with an introduction to Lumberyard and provide an overview of its capabilities and integration options. Once the game engine is installed, we’ll guide you through the creation of an immersive game world with characters. You’ll add animations and audio to bring the game to life. We’ll explore external interactions to support live multiplayer game play, data storage, user engagement, and the back end. By the end of the book, you will be efficient in building cross-platform games using Lumberyard.
Table of Contents (18 chapters)
Learning AWS Lumberyard Game Development
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface

Lumberyard's testing tools


In the previous section, we indicated that debug and profile builds can be used for debugging and testing your game. Debugging and testing are usually internal to a game project's team. Lumberyard supports these efforts with a couple of utilities. In this section, we will provide an overview of two tools that are part of Lumberyard's utility set: AzTestScanner and Statoscope Profiler.

AzTestScanner

The AzTestScanner utility can be run manually from the command prompt. You will need to locate the AZtestRunner.exe file on your system. Alternatively, you can use the lmbr_test.cmd script. This script file, located in the \dev directory, sets local and Python paths, sets a few properties, and then runs the command python -m aztest.

This scanning utility tests libraries and generates three reports. The first report is a detailed text log of the scanning results. Each library and executable file tested will have a corresponding XML file generated with test results specific...