Developing with Unity3D on Ubuntu

October 31, 2015

Well, I never thought I’d see the day! Over the course of one week, specifically from the 19th of October 2015 to the 26th of October 2015, I took part in’s first ever Linux Game Dev Jam.

Over the course of that one week, I took the experimental Linux build of Unity3D [version 5.1] and built a first-person shooter game for Linux. With how everything worked, I can say successfully that I developed for Linux on Linux!

Here’s a video that shows some footage from the game, and also includes a time lapse of my development over the 7 days.

The Linux version of Unity3D is not without bugs though. Several I personally experienced were:

  • The Editor would crash everytime I tried to bake the Lightmap for all static objects in the scene.
  • RenderSettings does not obey changes from the script-side, but does obey Inspector-side changes.
  • Mecanim would not reset certain animations after changing scenes a certain number of times.

There were a couple more nuances with the editor, but in the end I was able to make use of most of it. The final game was of course buggy, had a hideous night atmosphere, and all around felt quite unpolished. It did however showcase what can be done by one semi-knowledgable individual in the span of one week with a lot of pre-made assets and a few self-made ones.

The power of the new UI system has to be one of the more enjoyable aspects of Unity 5. The previous OnGUI would have prevented a lot of the cool things I managed to get done in this one week. For example, interacting with certain crates would generate a UI with information on what was inside the crate in real-time thanks to the new UI system and prefabs. Trying to do this with OnGUI is unimaginable. You would have to code everything down to where exactly on the screen things would go and how they would need to respect the aspect ratio. With the new UI, you can do all that inside the editor directly and entrust it into prefab form. Is it the most beautiful looking game? Not at all. However, the shear amount of functionality I could squeeze in for a duration of 7 days is amazing.

I’m very thankful to the Unity team for bringing this amazing piece of software over to the Linux side. Here are some links for those interested.

Link to the game I made:

Link to the GOL Game Dev Jam page:

Link to the Linux build of Unity3D:

How to compile and run FRAPIX on Ubuntu

March 25, 2015

In my quest to look for more On-Screen Displays (OSD) for showcasing framerates in OpenGL games on Ubuntu, I’ve come across Frapix.

Now, to get this up and running, we’ll need to build it from source code. It’s not that difficult, but I would put this at intermediate difficulty especially if you’ve never coded or compiled anything before.

Compiling FRAPIX

Download the source code

To start, we’ll need the source code for two things. libimago and frapix.

Just click Download Zip for each. You’ll want to extract both of those onto your Desktop to make things easy.

Alternatively, if you don’t want to you use the Download Zip button but instead want to use git, we could do it like this. The following will clone (download) the source code to whichever directory your Terminal is currently in:

git clone
git clone

Installing the dependencies

Before compiling, we need a couple of things installed first. Go ahead and copy/paste this into a Terminal and hit Enter.

sudo apt-get install -y libx11-dev mesa-common-dev libjpeg-dev libpng-dev

Alright, we’re set, let’s first build and install libimago. After that we can build and install frapix.

Building libimago

First, cd into libimago’s folder wherever you extracted it to. For me, that’s on the desktop. This is what it should look like (ismail is my username).

cd '/home/ismail/Desktop/libimago-master'

Now, let’s start building it. Enter the following one-by-one.


This is what it should look like so far:

Installing libimago

Hopefully, no errors turn up here. Time to install it system wide.

sudo make install

Building FRAPIX

With that done, we can now build frapix. Open a new Terminal, and CD into the frapix source code folder wherever you extracted it. For me, that is on the desktop and looks something like this:

cd '/home/ismail/Desktop/frapix-master'

Now, let’s start building it.


Installing FRAPIX

sudo make install

That’s it, we’re done! You should now be able to run frapix with any OpenGL application or game and get a suitable fps OSD to display. The cool thing about frapix is that it changes the color of the numbers depending on the background color. If it’s a dark background, the OSD turns to a bright color to constrast it and vice versa.

Running FRAPIX

To test if frapix is working, we can run it with glxgears like so:

frapix glxgears

You should see a neat little OSD with fps numbers on the top right like I do. If you want to run it with Steam games, that’s also possible. Just right click your favourite game in Steam, and add the following to the Launch Options for that game like so:

LD_PRELOAD=/usr/local/lib/ %command%

Click OK and now all you have to do is start the game, it should work! This is what I get in Cities Skylines:

There is one problem though. If you’re on a 32bit OS, you should be fine. However, if you’re on a 64bit OS like me, you’ll end up with the 64bit version of frapix. What does this mean? Any game or OpenGL application that is 32bit-only will not have the frapix OSD appear.

I’m not yet sure how to overcome this problem, as there doesn’t seem to be a way to have both the 32bit version and 64bit version installed at the same time unlike GLXOSD.

Additionally, I have been unable to get any OSD to work in Wine which is the ultimate goal I’m setting out to achieve here. So, sadly, this does not work in Wine.

This should work on any Ubuntu version, but I’ve only really tested it on Ubuntu 15.04 (both 32bit and 64bit versions). I hope this post was helpful to you in one way or another! :D

Running Unreal Engine 4 on Ubuntu

March 14, 2015

With Unreal’s latest announcement that they are making the engine available freely to all, I figured I might as well try the IDE client on Ubuntu. These steps should work on any version of Ubuntu, but I’ve only really tested it on Ubuntu 15.04.

This post assumes you know your way around Ubuntu, and have played with Terminals before.

First things first, you still need a Github account and an Unreal account. Why? At the time of this post, the Unreal Github repository is private, so to gain access you must follow Unreal’s requirements to gain access.

  • Make your Github account here (it’s free).
  • Make your Unreal account here (it’s free).

With those setup, you need to link your Unreal account to your Github account before you can access the source code for the Unreal Engine. You do that here, enter your Github username and click save.

Go back to your Github page, and you should see an invitation from Unreal. Accept it. “But wait!” I hear you say, “isn’t the client downloadable for Windows and Mac OSX? Why do we need the source code for Linux?”. In it’s current state, Unreal Engine 4 is not ready for release on Linux (according to the Unreal developers). So, we must make do with the source code for the foreseeable future.

You could use Git to clone (which means download) their source, but it’s just easier if you click Download Zip on the right, and extract it to your desktop once it’s downloaded. Look for the Download Zip button on their page here. Looks like the following. Easy.

Install Required Dependencies

You’ll very likely need quite a few dependencies installed before being able to continue. So, let’s get those installed. Open a terminal, and enter the following:

sudo apt-get install -y mono-gmcs mono-xbuild mono-dmcs libmono-corlib4.0-cil libmono-system-data-datasetextensions4.0-cil
libmono-system-web-extensions4.0-cil libmono-system-management4.0-cil libmono-system-xml-linq4.0-cil cmake dos2unix clang-3.5 xdg-user-dirs libqt4-dev

Setting Up Unreal Engine 4

Alright, we’re set. Let’s get to prepping Unreal Engine 4 to work on Ubuntu. Open a new Terminal, and CD to the directory where you extracted UE4’s source code. For me, that was on the desktop, so my command looked like this:

cd '/home/ismail/Desktop/UnrealEngine'

Once in this directory, we need to run the Setup, so enter this into the Terminal:


Go ahead and hit Enter. It may complain that it needs to install extra dependencies (in case we missed any), just type in your password and it will auto-install it for you. It may take a while, since it’s downloading the rest of the UE4 editor files (3GB or more). Once it’s done, let’s run the following:


If you’re successful so far, you should see something like this in your Terminal:

Encountering Errors with Clang

If, after running GenerateProjectFiles, it returns an error like the following:

*** This version of the engine can only be compiled by clang - refusing to register the Linux toolchain.

Generating data for project indexing... 0%
UnrealBuildTool Exception: ERROR: GetPlatformToolChain: No tool chain found for Linux

This means Unreal’s source still can’t be built using Clang 3.5, or it simply can’t find Clang (may not have successfully been installed). Thus, you will need to uninstall Clang 3.5 (if it’s present on your system), and instead install 3.3 as instructed by them here. Personally, for me, Clang-3.5 worked so it should work for you as well. If this error did not occur, you can skip this part! To remove Clang 3.5, enter the following in a new Terminal:

sudo apt-get remove clang-3.5

In Ubuntu 14.04 and above, you should have access to Clang 3.3, 3.4, and 3.5. So, let’s install Clang 3.3. In the same Terminal as just now, enter the following:

sudo apt-get install clang-3.3

Once that’s done, just rerun the GenerateProjectFiles command as shown above (make sure your Terminal is in the same directory as the UE4 folder).

Building the Editor and it’s Components

Time for more commands! Yay! Alright, shouldn’t be long before we get the editor up and running now. Enter the following in the same Terminal as before:

make SlateViewer

That should have been pretty straightfoward and successful. Now, let’s actually build the Editor itself. Note that this part can actually take a seriously long time, that’s normal and ok. In the same Terminal, enter the following:

make ShaderCompileWorker UnrealLightmass UnrealPak UE4Editor

This part WILL TAKE LONG! It took me over 1 hour to compile, and that’s with an Intel i7-4770 3.4GHz CPU. Clang and Mono ate my RAM like crazy, and when compiling certain modules it actually took up 100% of it, which is 8GB of RAM. Do not attempt this if you have less than 8GB of RAM.

Once it’s completed compiling, it should look like this:

Running the Unreal Engine 4 Editor on Ubuntu

Finally! We’ve made it, let’s run this beast. Be prepared, it took me 20 minutes before I was actually able to use the Editor for the first time, since it needs to prepare shaders for first-time use.

Head into your UnrealEngine source folder, enter the Engine folder, enter the Binaries folder, and finally enter the Linux folder (that’s Desktop/UnrealEngine/Engine/Binaries/Linux for me). Scroll down until you see UE4Editor. It should look like this in your window manager:

All you should need to do is double click it to run it! Give it a minute or two before anything appears. The first thing you should see, should look something like this (fullscreen image here):

After 10 minutes for me, the main Editor appeared, but still required another 10 minutes to finish it’s Shader setup.

That’s it! Happy UE4 Linux game developing! Hopefully I haven’t excluded anything important. Please note that at the time of this post, Unreal Engine was at version 4.7.2.

Modifying and running VoglPerf on Ubuntu

March 12, 2015

So, we’ve gone and compiled VoglPerf . If you haven’t yet, go here for a quick tutorial. That’s fine and dandy, but how do we go about using it?

Good question. I’m going to assume you have the voglperf folder on your desktop. So, first things first, let’s open a Terminal and enter that directory.

cd '/home/ismail/Desktop/voglperf'

Here’s what it looks like:

Note, change the word ismail to your username! The name ismail here is my username for Ubuntu. To make things even easier, instead of typing the full directory just drag-and-drop your folder into the Terminal. It will auto complete the directory for you.

Alright, time to fire up VoglPerf itself. Enter this into the same Terminal:

sudo -u ismail bin/voglperfrun64

Here’s what it looks like so far:

Note, once again change ismail to your Ubuntu username! On top of that, note that I’m using voglperfrun64 and not voglperfrun32. Which one you use depends on the game you want to run. If the game is a 32bit executable, then run voglperfrun32 instead.

Hitting Enter should now yield the following in the Terminal:

What it’s given you is an IP address. Fret not! Open up your favourite Internet Web Browser (I use Chromium here), and enter the IP at the top.

Sweet! We’ve got VoglPerf up and running. Now, before starting a game, let’s enable fpsshow so that it will show a frame counter in any Steam game we connect it to.

fpsshow on

Ok, time to start a game with VoglPerf. Enter the following (change the numbers to the game you want to start!). Here I’m starting Cities Skylines using VoglPerf:

game start 255710

You might get a long warning message from Steam asking if you want to allow it to launch this way, just click Ok. There’s nothing to worry about.

You’ll know it’s starting up successfully if you see the following appear in the Terminal:

Awesome sauce! We’ve got it running and it’s showing the frames per second on the top left! Well, it’s really kind of tiny, and my gosh red is a bad colour (go here for a fullscreen image to see just how tiny it is).

Modifying VoglPerf

So, let’s go ahead and change that. I’m also going to remove the information at the end of that since I only want the fps numbers. If you follow the rest of this, you will need to recompile VoglPerf as we will be editing the source code :)

Head into your voglperf folder. Inside the src folder, open voglperf.c in your favourite text editor. Look for the line that has the following:

// static const char g_MessageBoxFontLatin1[] = "-*-*-medium-r-normal--0-120-*-*-p-0-iso8859-1";

Let’s uncomment that code, by removing the // at the beginning. I’m going to change it to the following (more information on this can be found by searching for the X11 Protocol when it comes to fonts):

static const char g_MessageBoxFontLatin1[] = "-*-*-bold-r-normal--0-280-*-*-p-60-iso8859-1";

What I’ve done is increase it’s size and changed it to bold. But, to make it take effect we will need to uncomment the lines following it. It should then look like:

XFontStruct *font_struct = X11_XLoadQueryFont(dpy, g_MessageBoxFontLatin1);
if (font_struct)
gcflags |= GCFont;
ctx_vals.font = font_struct->fid;

Next, I’m going to change the font color to magenta, as that is the commonly used color besides green for framerate counters. Scroll down a bit further and you should come along these two lines.

ctx_vals.foreground = 0xff0000;
ctx_vals.background = 0x000000;

I’m only going to change the foreground color, so this is what it now looks like:

ctx_vals.foreground = 0xff00ff;
ctx_vals.background = 0x000000;

On to the last part, I want to adjust the position of the text since we’ve resized it to a greater size. Scroll a bit further down, and you should come across the line:

X11_XDrawString(dpy, drawable, glinfo->gc, 10, 20, s_frameinfo.text, (int)strlen(s_frameinfo.text));

This is what it should look like after setting the new position. Note that 20 is the x position on the screen, and 60 is the y position.

X11_XDrawString(dpy, drawable, glinfo->gc, 20, 60, s_frameinfo.text, (int)strlen(s_frameinfo.text));

Lastly, I’m going to remove that unnecessary information appended at the back of the output. You will need to scroll up for this one (or use Ctrl-F and search).

"%.2f fps frames:%u time:%.2fms min:%.2fms max:%.2fms",

Now, make it look like this:

"%.2f fps"

That’s it. Save it and close it. We can now recompile voglperf. CD your Terminal into your voglperf folder. Let’s cleanup first before compiling by running:

make clean

Alright, compile voglperf like normal. More details here for compiling. Running voglperf should now yield a cool fps counter like this:

A fullscreen image of it here. We’re all done and set. This tutorial should work on any Ubuntu version, but I’ve only tested it on 14.04, 14.10 and 15.04. I hope you found this tutorial useful or helpful in one way or another :D

Gamemaker and making Children objects run their Event code and their Parent’s Event code

March 3, 2015

Slowly as I move forward with my Gamemaker project, I’ve learned new things along the way. One such thing I’ve learned is that when a Child object makes its own Event, it will override the Parent’s Event code. Sounds like pretty standard procedure, but what happens when you need the Parent’s Event code to run as well?

Let’s say, that there’s a Parent object that never gets instantiated. This Parent object’s sole purpose is to provide code to it’s children for managing mouse over events. Why place this code in the Parent object? We want to remove redundancy. Instead of manually calling this script in all the Children objects, let’s just call it in the Parent object so that all Children objects get it automatically. This Parent object’s code runs in the Step Event. Great, so all Children associated with this Parent object now have that Step Event as well.

Except, the Children objects require other code unique to their instances to run in the Step Event as well. If you’ve gone ahead and added code to the Child object’s Step event, you’ll find that it’s missing functionality when running. Specifically, the Parent’s Step Event code never gets run.

You need both the Parent’s Event code to run, and the Child’s Event code to run. The solution is pretty simple in GameMaker through GML. Just add event_inherited() inside the Child object, and do this before calling the Child’s Event code and you should be golden.

In the above pictures, the Child object will first run the Parent’s Step Event code, and only then will it move onto it’s own Step Event code (which is calling a script in this case). There you go, we have bypassed the Child object’s ability to override the Parent object’s Event code.

Turning a laptop into a desktop

January 21, 2015

Alright, so this post is going to be quite long. Basically, what I’ve been doing the past 4 days is to migrate the internals of a HP Envy 17 2001tx laptop into a desktop casing (AVF).

Why am I going down this path? The HP Envy 17 has to be the worst engineered laptop in the history of HP (it even had class action lawsuits filed against it). The bloody thing would overheat to 80 degrees celsius when on idle after a couple of minutes.

Please take note, this was just a very quick DIY. There was no real planning involved except “what size casing will we need to fit the motherboard in?”.

Instead of throwing it out, I attempted to breathe new life into it. My dad was very eager to use his power tools as well, so we cooperated in the process.

The locations of the screws on the back:

After unscrewing the screws, it’s time to remove the harddrives. They are connected via a single SATA cable, both of differing lengths.

The sata cable has a black plastic piece on top of it, which is meant to be pulled. It is connected to the motherboard in a downwards motion.

Now it’s time to unplug the Wifi module and remove it.

Notice the two small cables have a numbering on them. It’s important to reconnect them later with the right numbers (thankfully the module has the numbers written on it in white).

The cables are removed by pulling them upwards. I recommend doing it gently, and with the aid of a screwdriver or flathead to slowly remove them from their positions.

Now that they are removed, you’ll need to unscrew the 2 black screws that connect it to the motherboard. After unscrewing, you’ll notice it rises. That’s ok and normal.

The Wi-Fi module removed completely will look like the above.

Now, it’s time to unscrew the hidden screws beneath the rubber stamp legs. For these, use a flathead or toothpick-like tool to pry them from the body. They are connected to the body via glue.

Finally, the bottom should look like the following with everything unscrewed and removed (no need to remove the RAM).

Now, moving on to the top part, we first need to remove the keyboard.

To remove the keyboard, all screws underneath need to be removed. If it still feels like it’s being held strongly, then there might be a screw not yet removed. The idea behind removing the keyboard is to push at the spaces on the top part, until the entire top is free, and to pull towards the screen. This is because the bottom has metal potrusions to hold it in place ( I just pulled it from all directions, since it wasn’t going back into the laptop body).

There will be four cables to remove before pulling off the top cover.

The first two will be the keyboard and touchpad connectors, as seen below:

These parts are pretty easy to remove. just slowly unclip the top black or white plastic holder, and slide the cable out via the blue plastic meant for fingers.

You’ll want to remove the other keyboard connector, it’s a small orange cable to the top right. You’ll also notice there was one screw in the center that holds the keyboard in.

Don’t forget to remove the power switch cable connector on the top left. It’s a small blue-ish cable.

Now, we are ready to start peeling off the top cover. You’ll need something to get between the crevices to pull it off, but once you get one clip to unhook it should be straight forward.

Now, it’s time to remove the rest of the power cables and connectors so we can pull out the main motherboard unit. There’s also two additional screws.

First, remove the card reader cable connector.

Then, unscrew the BD-Rom drive and pull it to the right to dislodge it from the motherboard (there’s no cables for this).

Unplug the speakers/LED power.

The monitor is attached to the motherboard via a single cable that branches out into two connectors.

You’ll want to pull the white cable branch to the left to remove it from its place.

The other branch just needs to be pulled upwards to disconnect it.

Lastly, remove the power cable that connects the power brick to the motherboard. It’s this small white 8-pin cable.

Now, the unit is removable from the body.

The mess we’ve made so far, before we start cleaning the parts and moving them into a new house.

Now, onto the cleaning! The most important part to clean is the cooler. This unit connects to the CPU and GPU in one go.

I went with this thermal paste (Cooler Master E1 IC ESSENTIAL Thermal compound) as it was affordable, and it came with grease which really helped with the cleaning process.

I forgot to take pictures of the unscrewing and cleaning, but basically you’ll want to unscrew 7 screws (4 for the CPU, 3 for the GPU). After which, remove all previous grey/white thermal compound. You’ll know they did a shoddy job, if the thermal paste isn’t only on the shiny parts, but also on the green sections around the metal encasings (it shouldn’t be that way).

All spick and span, you’ll want it to be shiny enough that it looks like a mirror.

Don’t forget to clean the bottom parts of the copper cooler as well! Don’t leave any of the old thermal residue there.

Unscrewing the fan and it showcases that HP didn’t actually test this against massive dust build up. They didn’t even have the courtesy to make it easy to clean for end-users.

So, now that it’s all cleaned let’s put a single drop of thermal compound on each die. The CPU die cover will require a slightly larger drop, but basically you want to make sure it won’t leak over to the edges. Only apply the thermal compound to the onboard CPU and GPU, no need to put any on the cooler. Now, put the cooler back on and screw it in.

Alright! Cleaning is done, let’s get that new fang-dangled case ready for a new tenant.

Why’d I go with this case? As you’ll see later on, the area for cable management allowed me to do some pretty unorthodox installing of this mobo into it. REMEMBER! It’s a laptop, so both sides of the motherboard has connectors. You’ll need to figure out how to make sure both sides get the cables that they need connected.

We used a black & decker drill to make the holes in the casing, so that I could screw the motherboard in. 2 was more than sufficient (it’s a light motherboard).

One thing became apparent, we would need the power switch from the laptop to be able to turn this unit on. So, it was time to saw the piece off.

At this point, it had been over 12 hours on working with this. My mind was starting to wander, and I’d forget to take pictures often. Apologies in advance for missing information.

We were able to fit the motherboard in nicely, and the two harddrives fit as well. One had to be screwed onto the casing’s motherboard wall section (the SATA cable connector was too short). The other fit snugly in the actual HDD compartment.

After connecting the power switch, we’re basically holding it on the back of the case via sticky tape. Later on we’ll actually make a hole in the back casing cover and slip this guy into it to look slightly less hideous.

For the monitor, since the laptop monitor was still good, we detached it from the laptop body and drilled holes into the sides of the casing to get it to fit.

The Wi-Fi dongle is in this monitor, so you’ll need it anyway to get the in-built Wi-Fi working.

Plugging in the power, we ran it to see if it would start. Lo and behold! It works!

The Windows install was corrupted though, and the HDD’s RAID mode was the cause. So I had to disable that.

This is where the power brick connects to. I forgot to take pictures of the process, but it’s pretty straight forward. The white 8-pin power connector stretches out over a cable length and then connects directly to the HP power brick.

After having Windows 7 poop it’s pants, I needed to confirm if the hardware was actually faulty. Ubuntu 14.10 64bit to the rescue!

My younger brother then tested it for a couple of hours, and confirmed no shutdowns due to overheating, no RAM issues (hanging, screen corruption). The HDDs seemed to be fine as well, as the SMART test inside Ubuntu showed them to be fully operational.

That was the end of day 1! So, what took the other 3 days time? Installing Windows 7. I’ll give you a hint. Don’t use the original Windows 7 ISO, instead use a SP1 version. On top of that, if you find that using a disc or USB drive isn’t working, then you’ll have to go through the hell I did.

I extracted the 7 SP1 ISO into a folder, used Windows Updates Downloader to slipstream the DEC 2014 updates into the ISO. ( I followed this guide ) Then, I went to the HP driver page and downloaded the necessary storage, wifi, and USB drivers. I used NTLite to slipstream those drivers into that same ISO.

After which, I just simply copied it (the extracted version) into a pendrive, plugged it into the USB2.0 slot, and finally Windows 7 would install. Pretty difficult, compared to installing Ubuntu 14.10. I just plugged my Ubuntu USB into any of the USB slots, booted it up and installed it. (HP Envy 17 wasn’t built to run Ubuntu, yet here we are)

If you’re looking for NTLite, get it here:

If you’re looking for Windows Updates Downloader, get it here:

If you’re looking for Ubuntu (it’s free), get it here:

So, was this a professional DIY? Not by any means. In fact, this was probably the most adventurous DIY project I’ve ever done. What matters though, is that we now have a working computer, and it’s able to operate at it’s full power.

Compiling VoglPerf on Ubuntu 14.10

January 16, 2015

Well, whilst taking a short break from designing my inventory, weapon, and attribute systems for my little game, I’ve been doing some game benchmark videos pitting Windows against Ubuntu.

In this quest, it usually helps to have a suitable FPS OSD. On Windows, most often it will be MSI Afterburner or FRAPS. On Ubuntu, I have the choice of GLXOSD (preferred), Valve’s VoglPerf and Steam’s own Beta FPS counter.

The issue today is that I can’t seem to get GLXOSD to cleanly inject itself into Dota 2 for some tasty benchmarking. Thus, I have to resort to using VoglPerf, which is really aimed at developers who want to pinpoint where in their game performance is lost, and why. (Take note that VoglPerf only works with games that are on Steam)

I just need the FPS counter.

That said, after downloading VoglPerf from Github here, we can get started:

Please note that this guide will work on Ubuntu 14.04 and 15.04 as well. I’ve tested it myself.

I usually just extract it to my desktop, so that’s where all my terminals will point to later when compiling VoglPerf.

First off, you’ll need a couple of dependencies. I recommend installing them one-by-one to see if any issues arise or Ubuntu is unable to find them. To install the following, just simply open a terminal and enter them. Let’s get started on how to compile Voglperf on Ubuntu.


If you can’t be bothered with entering the following one-by-one, and want to get it over with quickly, then just copy this into a terminal, hit Enter, enter your password, and hit y to agree. It should install all required dependencies in one go:

sudo apt-get install build-essential cmake mesa-common-dev libc6-dev-i386 gcc-4.9-multilib g++-4.9-multilib lib32ncurses5-dev


It’s always best to start with the essentials, and so I usually do this:

sudo apt-get install build-essential

Now, for the required dependencies:

sudo apt-get install cmake

If you get the error regarding

fatal error: GL/glx.h: No such file or directory #include <GL/glx.h>

then you need mesa-common-dev:

sudo apt-get install mesa-common-dev

If you get the error regarding

fatal error: sys/cdefs.h: No such file or directory #include <sys/cdefs.h>

then you need libc6-dev-i386:

sudo apt-get install libc6-dev-i386

If you get the error regarding

fatal error: bits/c++config.h: No such file or directory #include <bits/c++config.h

then you need gcc-4.9-multilib and g++-4.9-multilib:

sudo apt-get install gcc-4.9-multilib g++-4.9-multilib

Moving on, it also looks like you’ll need the following if you’re compiling on a 64bit system and you’re trying to compile VoglPerf64 (although most games on Steam are 32bit binaries, so I believe the most useful version is VoglPerf32 regardless of your system’s architecture):

sudo apt-get install lib32ncurses5-dev

You’ll know if you need the above, when trying to compile and you get the following error:

Linking CXX executable /home/ismail/Desktop/voglperf-0.2/bin/voglperfrun64
/usr/bin/ld: cannot find -ltinfo
collect2: error: ld returned 1 exit status


Now that you have the required dependencies installed, let’s actually compile VoglPerf so we can use it. Open a new terminal, and CD to your VoglPerf folder. For me that would be:

cd '/home/ismail/Desktop/voglperf-0.2'

Protip: After typing cd and hitting the space bar, simply drag and drop your Voglperf folder into the terminal and it will autocomplete the entire directory path to the folder. Very neat, and seriously saves time.

Once I’m in, I have the choice of doing one of three things. I can either compile both the 32bit version and 64bit version, or I can compile each one one-by-one. I chose to simply compile only the 64bit one so that I may trace any problems easily. So, to compile both, all you would do is:


If you’re looking to just compile the 32bit version, then do the following in the same terminal:

make voglperf32

For the 64bit version, do the following in the same terminal:

make voglperf64

If you compiled successfully, it should look something like the following:

Now, please take note that after you’ve compiled a build, that folder will be in the voglperf folder. You’re building to the same folder you’re taking the source from. What this means is that, if you want to start fresh, or have made changes to the code, I recommend deleting the build folder (aptly named build32 for the 32bit version, and build64 for the 64bit version) before compiling a new build.

After all that compiling, you can find what you’ve built in the bin folder inside the voglperf folder. After all, what you’ll be running is the executable (which should be voglperfrun32 or voglperfrun64). You should have one of either of these, or both like I do:

Also, if you feel uncomfortable using the terminal, for the most part you can make use of the Ubuntu Software Center to install the dependencies. For example:

Please note, that while my Ubuntu system was a fresh install, it may be possible that I’ve installed other required libraries or dependencies previously that I have forgotten about or unknowingly done so. If you find any dependencies not listed here, please feel free to comment and add them so that others may know what they are and how to resolve them.


Get every new post delivered to your Inbox.