Book Image

CryENGINE 3 Game Development: Beginner's Guide

Book Image

CryENGINE 3 Game Development: Beginner's Guide

Overview of this book

CryENGINE is a complete game development environment used by AAA game development studio Crytek to produce blockbuster games such as Crysis 1, 2 and 3. This complete Beginner's Guide takes the would be game developer through the steps required to create a game world complete with event scripting, user interface and 3D environment in the free CryENGINE SDK. Learn to create game worlds with the CryENGINE 3 Sandbox, the tool used to create AAA games like the soon to be released Crysis 3. Follow straightforward examples to sculpt the terrain, place vegetation, set up lighting, create game sounds, script with Lua and code with C++. Learn to navigate the interface within the CryENGINE 3 Sandbox, the tool used to create AAA games like Crysis 1 and 2, as well as the soon to be released Crysis 3. Learn to create your own worlds by following straight forward examples to sculpt the terrain, place vegetation, set up lighting, create game sounds, and script with the Lua language. The book covers all beginner aspects of game development including an introduction to C++ for non- coders.
Table of Contents (18 chapters)
CryENGINE 3 Game Development Beginner's Guide
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Index

Time for action - debugging the patrol Flow Graph


  1. Open the Flow Graph from the previous example or set up your own Flow Graph to debug.

  2. To enable the Flow Graph debugging, click on the icon that resembles a bug, as seen in the following screenshot:

  3. Each time that you enter the game mode with the debugger turned on, any of the Flow Graph outputs that are triggered within the level are highlighted in yellow. They will also display the number of times a port has been triggered. Finally, it displays the value triggered at each port, as shown in the following screenshot:

    Note

    Press the F and G keys to highlight the connections going in and out of a selected flow node. On large Flow Graphs, especially with tons of interconnected nodes, this can be very useful.

  4. Reset the debugger using the trash icon next to the debug icon.

What just happened?

The visual debugger can be invaluable when the Flow Graph is not reacting as you would expect. It can also be useful to use while actually designing a graph to...