Book Image

Panda3D 1.6 Game Engine Beginner's Guide

Book Image

Panda3D 1.6 Game Engine Beginner's Guide

Overview of this book

Panda3D is a game engine, a framework for 3D rendering and game development for Python and C++ programs. It includes graphics, audio, I/O, collision detection, and other abilities relevant to the creation of 3D games. Also, Panda3D is Open Source and free for any purpose, including commercial ventures. This book will enable you to create finished, marketable computer games using Panda3D and other entirely open-source tools and then sell those games without paying a cent for licensing. Panda3D 1.6 Game Engine Beginner's Guide follows a logical progression from a zero start through the game development process all the way to a finished, packaged installer. Packed with examples and detailed tutorials in every section, it teaches the reader through first-hand experience. These tutorials are followed by explanations that describe what happened in the tutorial and why. You will start by setting up a workspace, and then move on to the basics of starting up Panda3D. From there, you will begin adding objects like a level and a character to the world inside Panda3D. Then the book will teach you to put the game's player in control by adding change over time and response to user input. Then you will learn how to make it possible for objects in the world to interact with each other by using collision detection and beautify your game with Panda3D's built-in filters, shaders, and texturing. Finally, you will add an interface, audio, and package it all up for the customer.
Table of Contents (22 chapters)
Panda3D 1.6 Game Engine
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Time for action – removing tasks by name


For this lesson, we're going to make a second task to move self.cycle2. Then we're going to remove both of the cycles' movement tasks at the same time. We'll use remove first, and then we'll do it again with removeTasksMatching.

  1. First off, we don't want the cycle tasks removing themselves prematurely, so we need to delete the return task.done from cycleMove. Take out the if statement that triggers it as well, we don't need that anymore either. While we're at it, we should remove the lines that reference self.distTrav as well.

  2. To keep our command prompt from getting too cluttered, we should delete the line in cycleMove that prints delta time, print(dt). After that, copy the entire cycleMove method and paste a copy in beneath the original. Rename the original to cycleMove1 and rename the copy to cycleMove2. Finally, in cycleMove2, change all the references to self.cycle1 to self.cycle2. We can use Notepad++'s Find and Replace dialogue to do this. Bring...