# Lecture 1 - Overview
### SET09121 Games Engineering
### Welcome

<br /><br />
Kevin Chalmers and Sam Serrels

School of Computing. Edinburgh Napier University

## Demo 2
sneaky little slide down here

---

# What is Games Engineering
![Wikipedia for Engineering](assets/images/engineering.png)

* Engineering is design, building and use of engines. 
* Games Engineering is the application of this to video games - we are going to design, build and use an engine to make a game. 
* Many technical members of a games development team are called engineers. 
* We are using the same analogies that are applied to software engineers. 
* This module will focus on the development of a game engine 
 * Entity management, physics system, AI, other management functionality.

---

# Module Aims

* Gain experience in games development, particularly the technical aspects of games development.

* Examine the technical aspects of games and break these down to understand how games work.

* Put together a basic game engine for 2D games.

* Examine some of the fundamental technologies used in games development, such as artificial intelligence and physics.

---

# Learning Outcomes

- LO1: **Design, develop and evaluate** a games engine through *robust software engineering techniques*

- LO2: **Examine and evaluate** modern software *development, deployment, and testing procedures*.

- LO3: **Examine game design principles and procedures**

- LO4: **Demonstrate a working knowledge** of the *technical components of a games engine*

---

## Teaching and Assessment

---

# Structure -- Lectures

- Two one-hour lectures a week.  
    - Thursday @ 9am in B32.  
    - Thursday @ 1pm in G2.  
- Attendance at both lectures is mandatory -- this is not a repeat lecture.  
- Lectures will cover:  
    - Game design concepts. 
    - Software engineering for games.  
    - Game technology.
    - How our game engine works.

---

# Structure -- Practical Sessions

- Two-hour practical session. 
    - Thursday @ 10am.
- Practicals take place in D2 (The Code Lab). 
- Labs will help you develop the engine you need to use for the coursework. 
    - 2D development with SFML.
    - Physics with Box2D.
    - Management infrastructure for the engine.
- You need to do these practicals and keep up -- they form the basis of the coursework submission.

---

# Coursework

- Out Now!

- Develop a game using the game engine.
    - **You cannot use one of our samples and just change the graphics**, or likewise with samples for SFML, Box2D, etc. -- this will be a **FAIL**!

- You will work with a partner, think who you might want to work with.

- Coursework has four submissions.
    - [Week ~4:] Game pitch presentation.
    - [Week ~7:] Game design document.
    - [Week ~15:] Implementation and report.
    - [Week ~15:] Demo and peer assessment.

---

# Support and Assessment

| **Learning Outcome** | **Supported By** | **Assessed In** |
| --- | --- |--- |
| LO1: Design, develop and evaluate a games engine through robust software engineering techniques. | Lectures, Practicals | Coursework |
| LO2: Examine and evaluate modern software development, deployment, and testing procedures. | Lectures, Practicals | Coursework |
| LO3: Examine game design principles and procedures. | Lectures| Coursework |
| LO4: Demonstrate a working knowledge of the technical components of a games engine. | Practicals | Coursework |

---

# Work Plan

- We know every lecturer says it, but if you took Programming Fundamentals, Computer Graphics, or Physics, you will know we mean it.
- You __**WILL**__ have to work around 14 hours per week on the module.
    - 4 hours of contact (lectures and practicals).
    - 10 hours of self-study.
- The coursework requires working in pairs which will require some organisation outside class time.
    - Use the Games Lab -- it is what it is there for.
- Keep up with the practical work!  There is one every week.
    - Apart from reading week we will not be pausing.  The practicals build the engine you need.  Falling behind one week means trying to catch up the next!

---

## Module Outline

---

# Focus of the Module

- **Game design:** Initially we will focus on basic design ideas and show how we can use these to engineer our game.
- **Software modelling:** Applying common modelling techniques to games development.
- **Game mechanics:** Developing the underlying rules and procedure for our game (AI, physics, etc.).
- **Software development:** Programming our design, model, and mechanics to produce a working game.
- **Playing games:** Yes, you will have to play games.  However, you will start to analyse games more closely and understand more about what is happening within them.

---

# Not the Focus of the Module

- **Introduction to C++ programming:** If you do not have experience with C++ then get a book to learn the basics quickly.  We will cover some concepts, but not the basics.
- **Object-orientation:** We will refresh the basics in the context of C++ and games development, but if you require more knowledge then you are recommended to get a book.  You will likely learn more about object-orientation in this module by doing the work provided.
- **Graphics and sound creation:** Although some websites will be pointed to, you are generally expected to find or produce your own content.

---

# Lecture Series -- Part 1

- Overview.
- Workflow and repository management.
- Formal elements of games.
- Systems dynamics.
- Game entities and entity management.
- Object-orientation in C++.
- Game design documents.
- Design patterns for games.
- Memory and resource management.
- Game engine architecture and operation.
- 2D physics overview.

---

# Lecture Series -- Part 2

- AI in games.
- Pathfinding.
- Steering behaviours.
- State machines.
- Decision trees.
- QA and TRC.
- Game testing.
- Performance testing.
- Performance optimisation.
- Basic networking principles.
- Scripting.
- Review.

---

# Practical Lab Series

- Git Workflow and CMake.
- Introduction to SFML.  **Pong**.
- Entity Management.  **Space Invaders**.
- Tile Engine 1.  **Maze game**.
- Tile Engine 2.  **PacMan**.
- Physics and Resource Management.
- AI: Steering Behaviours and Pathfinding.
- AI: Behaviour via State Machines and Decision Trees.
- Deployment and Testing.
- Performance Optimisation.
- Networking.
- Scripting.

---

## Recommended Reading

Game Design Workshop

Game Design Workshop: A Playcentric Approach to Creating Innovative Games. Tracy Fullerton.

Game design elements of the module come from here.

This book will make you look differently at games.

C++ Primer

C++ Primer. Lippman, Lajoie, and Moo.

If your C++ needs some work this is a reasonable book to pick-up.

Covers most aspects of C++ that you will require.

Artificial Intelligence for Games

Artificial Intelligence for Games. Millington and Funge.

Very good book covering the algorithms and techniques used within game AI.

Lots more in here than we cover in the module.

Beginning Math and Physics for Game Programmers

Beginning Math and Physics for Game Programmers. Wendy Stahler.

A basic book really, but if your maths is not great this should give you enough to solve common problems.

Anyone with a reasonable grasp of "games" maths should instead look towards...

Mathematics for 3D Game Programming and Computer Graphics

Mathematics for 3D Game Programming and Computer Graphics. Eric Lengyel.

Has a number of good bits of information and techniques. Easy enough to translate 3D to 2D.

If you want to get better at "games" mathematics I recommend this book.

# Useful Websites

- **SFML:** https://www.sfml-dev.org

SFML provides our graphics system for our game engine.  You will need to use this resource when working with SFML.

- **Box2D:** http://box2d.org

Box2D provides the physics system for our game engine.  Again, you will need to use this resource when working with Box2D.

- **C++ Resources Network:** http://www.cplusplus.com

The goto place for C++

- **Game Programming Patterns:** http://gameprogrammingpatterns.com

Want to know more about some of the patterns we use and other patterns useful for games?  This website provides a number of examples.

---

# Contacting the Module Team

### Contact details:

MY  EMAIL

**S.Serrels@Napier.ac.uk**

*Please don't add me on facebook*. It's Weird.

- I am generally responsive to queries so ask as soon as you have any issues.
- The best time to ask for help is during the practical sessions.
- Try and complete the practical before the class and then ask questions during the lab time.

---

# And finally...
		
- I hope you have fun during the module.
- The module has been designed to be challenging but with effort everyone can succeed.
- We brought this back as we thought it was fundamental for the Games Development students.
- But for everyone else we hope you will learn:
    - How games work and how you can put them together.
    - How to do software engineering properly (from Kevin and Sam's point of view!)