# C++ I tried posting in Unreal forum but my post doesn't appear so trying here. Help with an issue in the c++ Battery Collector tutorial. Screenshots included.

## Recommended Posts

I am looking to learn C++ in Unreal so have commenced the tutorial '3rd Person Battery Collector Power Up Game'.

It is on the 3rd video of the series that I have come across an issue. In the screenshot I have attached labelled 'picture 1', this is the tutors class which is correct. My screenshot 'picture 2' is where I see some issues.

- my #include is in a grey colour font. It should be red right?
- I also do not have a #include "BatteryCollector.h" in my class also. In the tutors example this line of code is present.

Can anyone help me with why I have these issues. I am using Visual Studio 2015 as well. I thought would using VS'17 help so I installed this today. I have yet to try this out with that though but then I thought. Shouldn't it work fine on VS'15 anyway, would using VS'17 make much difference at all.

I am very keen to work through this tutorial today so if the forum might be able to help me I would be so so grateful.

Thank you.

Edited by GameDevCoder

##### Share on other sites

Case matters. "Pickup" is not the same as "PickUp".

I notice that the .h file is called Pickup, while you are trying to include "PickUp.h". Same with all the functions.

##### Share on other sites
19 minutes ago, Lactose said:

Case matters. "Pickup" is not the same as "PickUp".

I notice that the .h file is called Pickup, while you are trying to include "PickUp.h". Same with all the functions.

Oh my, thanks very much for spotting. I shall open up the project and see if this sorts it all out. I hadn't realised I made an error with how I named the class. Well spotted and thank you again for spotting this. Shall post an update with how it turns out.

##### Share on other sites

Took awhile to try this out as I was finding it tricky to just remove the class i had before, done now though. So now making it again with the correct title. 'include' is still grey unfortunately. Maybe it being grey doesn't matter, possibly just something i can change in the font colour merely. It's strange how the examples code has that other line of text in it though too. I may just try pressing on with the tutorial and find out if this include thing is stifling me down the line.

##### Share on other sites

The color of things is your preference, they have no effect on C++ what-so-ever.  I personally prefer the dark scheme for visual studios as the white strains my eyes I find after many hours coding.  You didn't have to remove your previous class to fix your mistake, you merely had to change #include "PickUp.h" to #include "Pickup.h" the filenames don't effect the class in any way at all.  You could have also just right clicked on the file in Solution Explorer on the right side and picked Rename too.

Also, instead of posting your worries/concerns here, hit F7 to build your project and see if there are errors.  Then post those errors if you, after researching them (best way to learn), still cannot figure out the solution.  But just retyping someone else's code is no way to learn.  You need to try and understand what the code is doing and why it is working.

##### Share on other sites
11 minutes ago, Mike2343 said:

The color of things is your preference, they have no effect on C++ what-so-ever.  I personally prefer the dark scheme for visual studios as the white strains my eyes I find after many hours coding.  You didn't have to remove your previous class to fix your mistake, you merely had to change #include "PickUp.h" to #include "Pickup.h" the filenames don't effect the class in any way at all.  You could have also just right clicked on the file in Solution Explorer on the right side and picked Rename too.

Also, instead of posting your worries/concerns here, hit F7 to build your project and see if there are errors.  Then post those errors if you, after researching them (best way to learn), still cannot figure out the solution.  But just retyping someone else's code is no way to learn.  You need to try and understand what the code is doing and why it is working.

thanks for the post. some very handy tips there. Just want to mention. One issue i was having was the #include for my class was greyed out. In the tutorials example 'include' is in blue font. I don't mean the white background or anything. Would you be able to comment on this bit at all? I think u may have covered something about this but I just wanted to clarify my concern I was having.

##### Share on other sites

Yes, the very first line of my reply covered it.  The color of your #include has zero effect on what C++ does.  It's merely an IDE preference you can change.  Had you tried to compile, it may have been successful.  The UE4 team likely changed their color scheme to make it more readable on stream/video or just prefer their IDE that way.  The # indicates a preprocessor event.  If you type #define SOMETHING above the #include it will be the same color as the #include.  As it's the # that decides what color the IDE assigns to the following text (until the space).

Again, hit F7 and see what happens.  Do you get errors/warnings in the output window below about it?  If not, there is nothing to worry about, carry on learning.  Also learning "C++" from UE4 tutorials will not really teach you C++.  They have a lot of very specific and highly custom things they've coded up that do not exist in C++.  Just be forewarned you will likely have to unlearn things to program in C++ outside the Unreal engine.

##### Share on other sites
6 minutes ago, Mike2343 said:

Yes, the very first line of my reply covered it.  The color of your #include has zero effect on what C++ does.  It's merely an IDE preference you can change.  Had you tried to compile, it may have been successful.  The UE4 team likely changed their color scheme to make it more readable on stream/video or just prefer their IDE that way.  The # indicates a preprocessor event.  If you type #define SOMETHING above the #include it will be the same color as the #include.  As it's the # that decides what color the IDE assigns to the following text (until the space).

Again, hit F7 and see what happens.  Do you get errors/warnings in the output window below about it?  If not, there is nothing to worry about, carry on learning.  Also learning "C++" from UE4 tutorials will not really teach you C++.  They have a lot of very specific and highly custom things they've coded up that do not exist in C++.  Just be forewarned you will likely have to unlearn things to program in C++ outside the Unreal engine.

Thanks so much for your replies. They both read incredibly helpful. I will have to go over them properly later on when I'm in Unreal also. Much appreciated and thanks very much again for the reply. Most helpful.

## Create an account

Register a new account

• 10
• 17
• 9
• 13
• 41
• ### Similar Content

• By vvvvv
oh boy howdy howdy
i know little to nothing about game design and programming but i am a seasoned artist and am a huge gamer always have been
i recently got a very small taste of the industry if you can even call it that from the last UE4 game jam i helped with voice acting concept art writing and vector art
i absolutely loved it and am already itching to learn and do more but??? i have no idea how to go about it
the person i was working with during the game jam is years ahead of me and is already looking into getting me into some contract work and teaching me 3d modeling/painting/sculpting but at the moment hes currently busy with making a game for RTX!
while hes busy i thought id delve into some forums and get my feet wet
any info or tips on how or where to get started would be amazing thanks!

• I am trying to build a particle system for unity based on "Destiny particle architecture " released in Siggraph.
I encounter a problem in trying to understand how they iterated this:

Converted to spline function and the result is

i wanted to know how did they converted the function in the editor to represent the graph ??

• Overview
Welcome to the 2D UFO game guide using the Orx Portable Game Engine. My aim for this tutorial is to take you through all the steps to build a UFO game from scratch.
The aim of our game is to allow the player to control a UFO by applying physical forces to move it around. The player must collect pickups to increase their score to win.
I should openly acknowledge that this series is cheekily inspired by the 2D UFO tutorial written for Unity.
It makes an excellent comparison of the approaches between Orx and Unity. It is also a perfect way to highlight one of the major parts that makes Orx unique among other game engines, its Data Driven Configuration System.
You'll get very familiar with this system very soon. It's at the very heart of just about every game written using Orx.
If you are very new to game development, don't worry. We'll take it nice and slow and try to explain everything in very simple terms. The only knowledge you will need is some simple C++.
I'd like say a huge thank you to FullyBugged for providing the graphics for this series of articles.

What are we making?
Visit the video below to see the look and gameplay of the final game:
Getting Orx
The latest up to date version of Orx can be cloned from github and set up with:
git clone https://github.com/orx/orx.git Once cloning has completed, the setup script in the root of the files will start automatically for you. This script creates an $ORX environment variable for your system. The variable will point to the code subfolder where you cloned Orx. Why? I'll get to the in a moment, but it'll make your life easier. The setup script also creates several projects for various IDEs and operating system: Visual Studio, Codelite, Code::Blocks, and gmake. You can pick one of these projects to build the Orx library. Building the Orx Library While the Orx headers are provided, you need to compile the Orx library so that your own games can link to it. Because the setup script has already created a suitable a project for you (using premake), you can simply open one for your chosen OS/IDE and compile the Orx library yourself. There are three configurations to compile: Debug, Profile and Release. You will need to compile all three. For more details on compiling the Orx lbrary at: http://orx-project.org/wiki/en/tutorials/cloning_orx_from_github at the Orx learning wiki. The$ORX Environment Variable
I promised I would explain what this is for. Once you have compiled all three orx library files, you will find them in the code/lib/dynamic folder:
orx.dll orxd.dll orxp.dll Also, link libraries will be available in the same folder:
orx.lib orxd.lib orxp.lib When it comes time to create our own game project, we would normally be forced to copy these library files and includes into every project.
A better way is to have our projects point to the libraries and includes located at the folder that the $ORX environment variable points to (for example: C:\Dev\orx\code). This means that your projects will always know where to find the Orx library. And should you ever clone and re-compile a new version of Orx, your game projects can make immediate use of the newer version. Setting up a 2D UFO Project Now the you have the Orx libraries cloned and compiled, you will need a blank project for your game. Supported options are: Visual Studio, CodeLite, Code::Blocks, XCode or gmake, depending on your operating system. Once you have a game project, you can use it to work through the steps in this tutorial. Orx provides a very nice system for auto creating game projects for you. In the root of the Orx repo, you will find either the init.bat (for Windows) or init.sh (Mac/Linux) command. Create a project for our 2D game from the command line in the Orx folder and running: init c:\temp\ufo or init.sh ~/ufo Orx will create a project for each IDE supported by your OS at the specified location. You can copy this folder anywhere, and your project will always compile and link due to the$ORX environment variable. It knows where the libraries and includes are for Orx.
Open your project using your favourite IDE from within the ufo/build folder.
When the blank template loads, there are two main folders to note in your solution:
config src Firstly, the src folder contains a single source file, ufo.cpp. This is where we will add the c++ code for the game. The config folder contains configuration files for our game.
What is config?
Orx is a data driven 2D game engine. Many of the elements in your game, like objects, spawners, music etc, do not need to be defined in code. They can be defined (or configured) using config files.
You can make a range of complex multi-part objects with special behaviours and effects in Orx, and bring them into your game with a single line of code. You'll see this in the following chapters of this guide.
There are three ufo config files in the config folder but for this guide, only one will actually be used in our game. This is:
ufo.ini All our game configuration will be done there.
Over in the Orx library repo folder under orx/code/bin, there are two other config files:
CreationTemplate.ini SettingsTemplate.ini These are example configs and they list all the properties and values that are available to you. We will mainly concentrate on referring to the CreationTemplate.ini, which is for objects, sounds, etc. It's good idea to include these two files into your project for easy reference.
Alternatively you can view these online at https://github.com/orx/orx/blob/master/code/bin/CreationTemplate.ini and here: https://github.com/orx/orx/blob/master/code/bin/SettingsTemplate.ini

The code template
Now to take a look at the basic ufo.cpp and see what is contained there.
The first function is the Init() function.
This function will execute when the game starts up. Here you can create objects have been defined in the config, or perform other set up tasks like handlers. We'll do both of these soon.
The Run() function is executed every main clock cycle. This is a good place to continually perform a task. Though there are better alternatives for this, and we will cover those later. This is mainly used to check for the quit key.
The Exit() function is where memory is cleaned up when your game quits. Orx cleans up nicely after itself. We won't use this function as part of this guide.
The Bootstrap() function is an optional function to use. This is used to tell Orx where to find the first config file for use in our game (ufo.ini). There is another way to do this, but for now, we'll use this function to inform Orx of the config.
Then of course, the main() function. We do not need to use this function in this guide.
Now that we have everything we need to get start, you should be able to compile successfully. Run the program and an Orx logo will appear slowly rotating.

Great. So now you have everything you need to start building the UFO game.
If you experience an issue compiling, check the troubleshooting article for Orx projects    for help.

Setting up the game assets
Our game will have a background, a UFO which the player will control, and some pickups that the player can collect.
The UFO will be controlled by the player using the cursor keys.
First you'll need the assets to make the game. You can download the file  assets-for-orx-ufo-game.zip which contains:
The background file (background.png😞

The UFO and Pickup sprite images (ufo.png and pickup.png😞

And a pickup sound effect (pickup.ogg😞
pickup.ogg
Copy the .png files into your data/texture folder
Copy the .ogg file into your data/sound folder.
Now these files can be accessed by your project and included in the game.

Setting up the Playfield
We will start by setting up the background object. This is done using config.
Open the ufo.ini config file in your editor and add the following:

[BackgroundGraphic] Texture = background.png Pivot = center
The BackgroundGraphic defined here is called a Graphic Section. It has two properties defined. The first is Texture which has been set as background.png.
The Orx library knows where to find this image, due to the properties set in the Resource section:

[Resource] Texture = ../../data/texture
So any texture files that are required (just like in our BackgroundGraphic section) will be located in the ../../data/texture folder.
The second parameter is Pivot. A pivot is the handle (or sometimes “hotspot” in other frameworks). This is set to be center. The position is 0,0 by default, just like the camera. The effect is to ensure the background sits in the center of our game window.
There are other values available for Pivot. To see the list of values, open the CreationTemplate.ini file in your editor. Scroll to the GraphicTemplate section and find Pivot in the list. There you can see all the possible values that could be used.
top left is also a typical value.
We need to define an object that will make use of this graphic. This will be the actual entity that is used in the game:

[BackgroundObject] Graphic = BackgroundGraphic Position = (0, 0, 0)
The Graphic property is the section BackgroundGraphic that we defined earlier. Our object will use that graphic.
The second property is the Position. In our world, this object will be created at (0, 0, 0). In Orx, the coordinates are (x, y, z). It may seem strange that Orx, being a 2D game engine has a Z axis. Actually Orx is 2.5D. It respects the Z axis for objects, and can use this for layering above or below other objects in the game.
To make the object appear in our game, we will add a line of code in our source file to create it.
In the Init() function of ufo.cpp, remove the default line:
orxObject_CreateFromConfig("Object"); and replace it with:
orxObject_CreateFromConfig("BackgroundObject"); Compile and run.
The old spinning logo is now replaced with a nice tiled background object.

Next, the ufo object is required. This is what the player will control. This will be covered in Part 2.