Introducing C++ Part 1

Hello again!

This post was initially meant to go straight on with the Unreal coding standards and the way they express C++ in the engine code.

I’ve made a little detour, as this series was meant to include both those new to C++ and those new to Unreal.

I don’t feel that the Unreal coding standard is much used outside of the Unreal Engine, so in the first posts that actually involves how to write C++ I’ve chosen to use my own coding standard.

All the content from the posts that contain C++ introductory material will also be posted to the C++ page on this blog, and it is also meant to be read by those that wish to learn C++ and not necessarily the Unreal Engine as well.

This might seem a bit clunky, and indeed it is, but this is the way I’ve decided to do it.

So this post and the next few posts will mainly contain C++ until I’ve presented what I believe is a minimum of required knowledge to get started with game development using any engine with a C++ API.

So, let’s get started.

C++ Introduction

C++ is a general purpose programming language with a bias towards systems programming that supports data abstraction, object oriented programming and generic programming.
C++ is a compiled, statically typed language, which means that the compiler must know the type of every object used in a program.

C++ is used in various fields of computer science including computer games.

It received a massive overhaul with the C++11 standard that introduced many new features, such as auto type deduction, lambdas and closures.

The development continues with the C++14 standard and compiler vendors have a great deal of work to do to make their compilers support all the latest features.

What makes C++ a good choice for mobile platforms and systems programming and games is that C++ produces very effective executable code that has low power consumption on mobile platforms combined with great performance in general.

This introduction will make use of some of the new features introduced in C++11, as these features makes C++ easier to understand and more safe to use in many ways.

Most popular compilers that I know of support most of the C++11 standard at the time of this writing, at least what we’ll present in this series of posts.

Why learn C++?

There are many reasons for learning any programming language. What makes C++ a good choice for those who plan on doing programming as a part of their careers?
First of all, C++ has been used in all kinds of systems since the language became an ISO Standard in 1998 and also before that.
Many of those systems that was created back then are still in heavy use today and demands maintenance programmers to keep them up to date.
A great deal of software that we use in our day to day lives today depends on C++ to keep running.

Many new software systems created today also uses C++ because of its universal properties, making it a safe, stable and long-term alternative for cross platform development of various systems, not tied to any manufacturer and not owned or governed by any company.

For more information on C++ as a language and links to various standards, compilers and libraries, visit:

There is a ton of valuable information on that page, covering a vast amount of topics.

How to learn C++

If you’re reading this, my guess is that you either want to learn how to use C++ in your programs.
I do not claim that the introduction offered in this series of posts will be anywhere near sufficient to make you a C++ developer.

This is only meant as a starting point for learning more of the intricate nuances that C++ programming is all about.

I want to introduce you to some of the concepts that I found tricky to wrap my head around when I started learning about the C++ programming language, before the YouTube age and the massive amount of learning opportunities available today.

The fact that the sources for learning C++ has become so many and so diverse actually doesn’t make it that much easier, because you have to know what sources to trust as being good and that in it self is a rather hard task if you don’t know what to look for!

I’ve seen both paid and free resources available for learning C++ that range in quality from down right pathetic and plain wrong to excellent and well worth your precious time. Just remember: What you pay for is not necessarily what you get.

In these posts I’ve tried to extract knowledge from various books I wish I had when first learning C++, and turn it into easily digestible bits of information.

Some of the books I highly recommend and that I’ve used as inspiration for writing this series include:

Programming – Principles and Practice Using C++ 2nd Edition by Bjarne Stroustrup et. al
C++ Primer, 5th Edition by Lippman, Lajoie and Moo
Think Like a Programmer – An Introduction to Creative Problem Solving by V. Anton Spraul
Understanding and Using C Pointers by Richard Reese
Effective Modern C++ by Scott Meyers
Safe C++ by Vladimir Kushnir
The C++ Programming Language 4rd Edition by Bjarne Stroustrup

These are all books that are verified and accepted as good learning material by the C++ community at large and is a safe bet if you want to know more about the vast areas of programming and to find specific information about using C++ in the best ways possible.

How to structure the material

I’ve seen many attempts to divide the beginning concepts of C++ into logical parts that makes it “easy” or easier to understand.
Some introduce functions before references and pointers, some introduce classes before general compound types and some choose to ignore the concepts of memory, pointers and references all together in the beginning chapters.

To me that’s all a bit too abstract. I prefer a more direct path.
Before learning to use functions I feel that it is imperative to know something about constants and references, as this will get more important when trying to write various functions that can both manipulate its arguments directly or being denied to change its
arguments as a whole.

I also feel that even though Object Oriented Programming (OOP) has many important uses it is also maybe the most abused concept in modern programming. This is a direct consequence of pure OOP languages such as Java that requires you to create a class just to do a simple “Hello World!” program.

In C++ OOP is an option but not a requirement. You can choose when to start introducing objects into your code and if you can do without it, why complicate matters if it doesn’t lead to anything other than unnecessary complexity?

Well, enough said.
Let’s get on with the actual introduction to programming in C++.

Variables and Basic Types

C++ defines a set of built-in primitive types that include the arithmetic types and a special type named “void”.
Void will be described later when we start talking about functions.

Arithmetic types are divided into “integral” types (numbers) and also include characters (char), like ‘A’ and Boolean (true/false) and floating point types (numbers with a fractional part), like 3.14.

Before continuing on, let’s detour into how these types are stored in a computer.

How machines represent the built-in types

As many knows, computers store data as a sequence of bits. each holding either the value 0 or 1. This is referred to as the binary number system.

That is a stream of bits, like 0001110011001110 …

To keep track of the stored values in memory, computers group chunks of “bits” and the smallest chunk of addressable memory is referred to as a “byte” and is usually made up of 8 bits.

The computer’s basic character set is used to define the size of a byte and in C++ a byte has “at least” as many bits needed to hold a character.
Most machines operate with 8 bit bytes and the ASCII basic character set.

The basic unit of storage is called a “word” and consists of a small amount of bytes grouped together. On 32-bit systems this is usually 4 bytes (4 * 8 = 32) and on 64-bit systems it is the double of that, 8 bytes (8 * 8 = 64).

You can visually represent a word like this:


There is also a concept of Big-Endian and Little-Endian that describes the order of the bytes in memory and in transmission over a digital link. This is not something you need to concern yourself with when starting out, but it is an important topic later on.
The concept of “Big-Endian” vs. “Little-Endian” can be further investigated here:

The following is a short description of the various arithmetic types.

C++ is designed to let the programmer exploit hardware specific optimizations and therefor provides a number of different types to squeeze the most out of any given hardware platform.

In practice, and when beginning to learn about C++, don’t get caught up in all the details.
The provided information is only provided for the sake of completeness.


There are a few different character types available, to accommodate for various needs and extended character sets.
The basic character type is called char and big enough to hold numerical values corresponding to the machine’s basic character set.
In addition there is wchar_t, char16_t and char32_t, all used for extended character sets.

char16_t and char32_t are intended for Unicode characters. Unicode is an example of an extended character set.
wchar_t is guaranteed to be large enough to hold any character in the machine’s largest character set, whatever that may be.

The character types has corresponding numerical values that maps to the different characters thay can represent,
like the character ‘A’ correspond to the decimal number 65, ‘B’ is 66 and so on.

Floating Types

These represent single (float), double (double) and extended precision (long double) values.
The standard only specifies a minimum number of significant digits but most compilers provide more precision than the required minimum.
Typically a float is represented in 32 bits giving it around 7 significant digits of precision, a double is stored in 64 bits with around 16 digit precision and a long double is stored in either 96 or 128 bits. The precision of all floating types are hardware dependent and the use of long doubles are largely dependent on the given hardware support.

Signed and Unsigned Types

Except for bool and the extended character types, the integral types may be “signed” (can contain negative values) or “unsigned”
(can only contain values 0 or above).
One way to remember this is that to use a negative number, you have to use a sign (the – sign), hence you need a signed type.

The types int, short, long and long long are all signed types and can contain values below 0. (negative numbers).

We can get the corresponding unsigned type by adding the word “unsigned” before the name of the type, as in unsigned int.
In the case of int you can use the abbreviated form of just unsigned, as in:

unsigned count = 0;

Signed and Unsigned Characters

To complicate things a bit more, there are three different types of characters.
char, signed char and unsigned char are all distinct basic character types.
There are actually only two representations of characters in memory, signed or unsigned, but the plain char uses one of these depending on the compiler you use.

The 8-bit unsigned char can hold values from 0..255 (inclusive) while the signed char can hold values from -127..127.
Most modern machines use representations that allow -128..127, but the standard only guarantees -127..127 (inclusive).

What to use when?

As mentioned earlier, all though C++ provides a staggering amount of arithmetic types, you’ll find yourself using only a handful of these on a day to day basis.

Some rules for what to use when can include:

  • Use an unsigned type when you KNOW that the values should never be negative
  • Use regular int for integer arithmetic. (short is usually to small and long usually has the same size as int)
  • Use long long if you KNOW that the value will exceed the minimum guaranteed size of an int
  • Use double for floating point computations
  • Don’t use char or bool for arithmetic expressions. Only to hold characters or true / false respectively

Next time I’ll cover some information regarding type conversion!

Stay tuned.



This section will explain what a project in Unreal is about, and some of the terminology used in the Unreal Engine Documentation, such as objects, classes, actors and pawns.


So, what exactly does a UE4 project consist of and what is going on when you create one?

A project consists of everything you want to include in your game, all content and all code for interacting with the objects in this content and can be seen as a self-containing entity from which your game is created.

When you create a project you include the source code for the engine in the project and basically you’re working on a separate version of the engine for every game you create.

This is why the start-up of a new UE4 project is taking so long, as the source code must be compiled before you can use the engine in your game. The next time you open your project, things will start a lot faster.

From the Project Page in the Unreal Editor, you can define the basic properties for your project, such as whether you want to start off with a Blueprint or a C++ based solution.

As mentioned earlier, this choice does only concern how the initial gameplay is defined within your project and can be changed around later.

Also, the Project Page defines what Build Target you’re developing for, as in Desktop / Console, Mobile or any other target you plan on developing for.

This is also a setting that can be changed later, in the Project Properties page in the editor after creation.

You can chose between Scale-able 2D / 3D and Maximum Quality graphics. This setting is also configurable after initial creation and is mostly relevant if you create for mobile platforms.

The project I’ll be creating in this series is called “TheMadMan”, and will be a basic UE4 C++ project that contains no starter content.


The assets used in the project can be downloaded from GitHub along with the source code and project files if you care to follow along.

I’ll cover setting up a GitHub repository for your own projects in a separate post, where I’ll also give you the address for my project files used in this series.

The different templates you can choose from are examples of different gameplay modes and will be discussed later. For now I’ll go with “Basic Code”.

When I hit “Create Project”, the UE4 Editor starts working with setting up the source code for my project and Visual Studio launches to work through the code produced by the editor.

The editor will detect changes to the code made in Visual Studio and reload any changes back into the editor, and changes initiated in the UE4 Editor will update in Visual Studio.

The default “map” or “level” or “scene” is created in the UE4 Editor. The terminology I’ll use for this is a “level” as this is what it is often referred to in the UE4 Documentation and I personally feel that it gives more meaning than “map”.

The level that starts up with your project is by default called “Untitled”, and you can see this in the lower right of the viewport and on the tab in the upper left corner of the screen.

You can save the level with a different name by choosing File → Save As, or using Ctrl+Shift+S and giving it a new name.

When the Unreal Editor starts your project it will look in the Project Settings to determine what level (map) that loads as default into the editor.

Even if you save your map with a new name, it will load the Untitled map when you start your project if you don’t specify otherwise in the Edit → Project Settings → Maps & Modes → Default Maps → Editor Startup Map.

You can see your newly saved level (map) in the Content Browser, which is a central component of the UE4 Editor.


A project is stored with a .uproject extension

Although a project is often referenced by the .uproject file associated with it, they are actually two separate files that exist alongside each other. The .uproject is a reference file used to create, open, or save a file, whereas the Project contains all of the files and folders associated with it.

You can create any number of different Projects which can all be maintained and developed in parallel. Both the Engine (and Editor) can easily switch between them, which will allow you to work on multiple games at once or have several test projects in addition to your main game Project open at any time.


The basic building blocks of the Unreal Engine are Objects of various kinds. The base that most elements in the engine gets functionality from or more correctly “inherits” from is the Object class, UObject.

From C++, UObject is the base class of all other Unreal Engine Objects and contains essential functionality for other objects you create, such as garbage collection and property support (through UProperty).


An actor is any object that you can add to your map (aka level). You could say that anything that can be “acted on” is an Actor. Actors support basic properties such as transformation (movement), rotation and scale in 3D space and actors can be made to spawn (get created) and destroyed by your gameplay code.

In C++ AActor is the base class for all actors. Actors can be static meshes, cameras, lights, particle emitters or skeletal meshes to name a few.

Actors will include “Components” that define their behavior and what they can do, like a light actor will include a component that defines what type of light it is, like a spot light will have a spot light component that defines how light is emitted and so on.

The actor will have access to and can use the functionality provided by the component.


Classes define the properties (state) and behavior of actors and objects in your game.
Classes in C++ defines a hierarchy where a given class can inherit from their parent classes and also pass information down to new child classes (sub class) that inherits from it.

I’ll have much more to say about classes when I start writing some actual code.
One thing worth mentioning is that you can also use Blueprints to define Unreal classes using the editor.


A Pawn is a sub-class of Actor that can act as a character in your level and can be controlled by a human player or as an NPC (Non Player Character) controlled by the game’s AI. (Artificial Intelligence).

A player controlled by a human player is said to be “possessed” and an NPC is said to be “unpossessed”.


A Character is a sub-class of a Pawn that’s intended to be used as a player character.

It includes collision properties (how it reacts to other objects in the environment) and input bindings for bipedal (two legs) movement among other things that can be controlled by the player.


The PlayerController Class is used to take player input and translate that into interactions in the game and every game has at least one PlayerController in it. A PlayerController often possesses a Pawn or Character as a representation of the player in a game.

There are also many other terms that I’ll cover as the need shows up, but this is the fundemental terminology you’ll need to understand to follow tutorials on beginning game development in Unreal Engine 4.

What’s up next?

The next post will cover some more details on how to write C++ code in the “Unreal Style”, so that your code will blend easier with the existing code and the code that gets created by the Unreal Editor.

Unreal has their own coding standard that is slightly different from most mainstream coding standards used in C++ programming, so it deserves some attention.

Introduction to Game Development with Unreal 4 and C++ – Part 1

Welcome to the first post in the series I’ve called “Introduction to Game Development in Unreal 4”.

The posts will not be very long in the beginning, just bite-sized chunks of newly acquired wisdom.

You can start a new instance of the Unreal Engine through the Epic Launcher that gets installed when downloading UE from

First, off course you have to download and install the engine itself. This should be self-explanatory.

So, when you first fire up the Unreal 4 Engine, you’re presented with various options for creating a project from different templates. You can choose a “Blueprint” project or a C++ project, and you can enable or disable the option of including the “Starter Content”.

The choice of project type is not too important, as you’re free to create “Blueprints” in a C++ projects and vice versa. Content can also be imported into your project after its initial creation, so don’t worry too much about choosing the “correct” option early on.

First off, let’s spend some time (this first post) on describing a little bit about the difference between a Blueprint and a C++ project. What is a Blueprint?

The answer to this will depend on who you ask, and how competent this person is with Unreal Engine.

First of all, Blueprints are not necessarily a “beginners” way of creating a game in UE.

Basically one can say that Blueprints is a way to visually develop game logic using nodes and to configure the connections between these nodes with wires.

That’s not an overly technical definition, but I think you get the point.


While it is easier to understand Blueprints initially, and most newcomers will indeed prefer to create their games this way, I’d say that if you try to create a fairly complex game using only Blueprints, you’re in for some serious headache. It WILL get complex and unwieldy pretty fast.

Rather, the way I see the most potential in Blueprints is in the prototyping stage of a level and for trying out different options in a game to present to a client or a friend, then, when you’ve settled on a prototype, you’ll start coding it in C++. This is a much more viable path to follow when creating a computer game.

It will be far easier to edit a class in an editor, than to drag wires along a path of hundreds or thousands of nodes in a Blueprint.

Here’s an example starting to get slightly out of control:


This certainly doesn’t look like my idea of something simple to work with.

But for basic prototyping, Blueprints are a great tool to enhance productivity and development speed, especially in the early phases.

Blueprints can certainly be used for many purposes, but in essence it works best as a tool to extend a core C++ system. As mentioned, C++ can be used to call into a Blueprint and a Blueprint can call C++ code, so the synergy of the two is most often the ideal.

It exists similar tools as add-on’s to the Unity Engine as well, all though probably not as streamlined as the integrated Blueprints in Unreal.

Blueprints should be one of the areas you plan on learning when using Unreal 4, because many people are using them and it is important to be able to understand the concepts if you want to be able to transfer the logic behind a Blueprint graph into C++ code and to be able to send messages between the two.

Whether you choose to focus on learning Blueprints first or the C++ API’s first is a matter of preference.
You don’t have to know Blueprints to program a game in Unreal with C++.

I don’t think I’ll talk very much about Blueprints in this series, but instead focus on the basic interaction between the engine and the development environment, which in my case is Visual Studio 2015 at the time of this writing.

You can certainly use Unreal 4 on both Linux and Mac OSX as well and I’ve tried both.

In both cases you can choose to use the Qt Creator IDE, which is also available to use on Windows.

Qt Creator is a multi-platform, very nice IDE that’s a good alternative to Visual Studio, and can be used to create a wealth of different types of applications including GUI applications that runs on all supported platforms unchanged.

For some tips on using Qt Creator on Windows:

For more information on setting up the engine to work with Qt Creator on Mac OSX and Linux, refer to the Unreal Documentation and do some Google searching!

If you’re just starting out and have access to a computer running Windows, you’d probably want to use this setup, as it is the most widely tested configuration to run Unreal Engine 4 in and generally will give you the least problems early on.

This is a moving target though, and many people have started using Unreal 4 on both Linux and Mac machines, so expect this to be a truth with room for modification.

To keep this as simple as possible, I’ll use only Windows and Unreal 4 in this series, but may create some posts using Linux as well, because this is my favorite operating system in many ways.

I guess that’s all for this time!

I’ll be back.

Unreal Engine 4 vs Unity 5

Oh, great. Another post about Unreal vs. Unity…

This is not a Unreal vs Unity, “what is best” type of comparison, just my thoughts on why I decided to go all in with Unreal 4 instead of settling for the arguably more popular (and more forgiving) Unity 5 game engine for learning game programming.

First of all, let me point out that there is no clear cut way of saying that one option is “better” than the other, it all depends on your needs, prior knowledge and how much time you have available for learning new stuff.

My focus with this series of blog posts is to cover beginning game development using C++, so with that criteria, the choice between the two is self explanatory.

But if Unity is so popular and easy to use, why choose something more complex if all you want is to create some fun games? And if C# is so much more forgiving and easier for most people to understand, why use C++ in all its complex glory?

Good questions. The answer is not obvious, but for me, being able to access the game engine’s source code is of great value. I’m not a fan of obscurity, and if something is not doing what I want it to do, I want to be able to know why it is behaving as it does and to have the ability to change it. This is something you can’t do with a closed source engine like Unity, at least not at the time of this writing.

C# is a very productive language to code in, and it is easier to learn than C++, no doubt about that.
But C++ is the “lingua de franca” or common standard programming language in many areas of computing including games, also it is a platform neutral programming language.
C++ is also the common base that other languages such as Java and C# is influenced from, making it a very useful language to know in the world of programming.

Arguably, C++ also tends to produce faster executable code than other higher level languages, and when your programs get more complex, it is vital to be able to churn out all the juice your processors has to offer. Learning to code in C++ gives you the ability to do just that. It has a good mixture of low-level and high-level features making it ideal for something like games.

So, all though Unity and C# may be a better match for newcomers to programming, I do believe that investing the time to learn C++ and Unreal gives a better value in the long term.

Also, there are some annoyances associated with using Unity if you don’t pay for the Pro version, like not having the ability to customize the start screen you get when starting your games. It will say “Made with Unity Personal Edition” or something like that, and that doesn’t exactly portray a professional game as I see it. It is also a constant reminder of your limited freedom and the fact that there is better options available.


This may or may not be an issue if what you are developing is an indie game anyway, but I like to be in control and Unreal gives the developer more control.
There is no “Pro” version of Unreal, just the source code that is shared by all users of the engine, and that’s kind of how I like it to be.

The reason I chose to create these posts is because I’m now in a position in life where I have some time on my hands, and I’ve chosen to use this time to learn more about game development.

I already know a fair amount of programming, both using C# and C++ from previous jobs I’ve had and from my personal interests through the years which has involved programming in some form or the other.

For people new to both programming and game development, there is a great deal to learn and I will not be able to cover anywhere near what you need to learn as this would amount to around a three year full-time study at some university for being able to produce professional quality games.

But, I do hope that the posts about C++ and Unreal will give some insight into how this works and possibly making it easier for someone to grasp the overall picture of how creating games in this environment can work out.


More to come…

New blog series on Unreal engine and C++ coming up


Hi there people!

Thanks to my loyal followers for bearing with me with not posting much of anything lately.

I’ve decided to start a new series of posts dedicated to the Unreal 4 game engine and programming it in C++.

I’ll keep things simple, as I’m learning about Unreal 4 as I keep going with the posts, so don’t expect any Unreal expert trickery to be exposed in this series!

I do believe that creating simple games can be a great way to learn about programming in C++ and if you’re new to either C++ or Unreal
(or both), and wish to get going with some coding and simple game development, there should be something interesting in the posts to come!

I’ll be back!