C++/UNREAL-ENGINE DEVELOPER

I am Arne Olemans, I always dreamed of world domination, but my mother refused to fund those dreams. So I became a curious and driven individual with a lifelong passion for exploring technology and the world around me. From a young age, I've been fascinated by software and technology, starting with my early days of tinkering with Nintendo games and the family desktop PC. This curiosity has fueled my journey into understanding and creating within the software developent space with a special intrest in Unreal-Engine and Game engine Development!

Cinque Terre Symbol
GoldKnights - Czech/Prague | Internship | Feb 2025 - June 2025
Used Skills
  • Unreal Engine 4/5
  • C++
  • Widgets/UI
  • Materials
  • TortoiseSVN
  • Team work
  • On-site
  • Remote
  • Rider
  • Visual Studio



Symbol
ThreeForSimple - Multiplayer Unreal-Engine 5.6 GAS C++ Third-Person-Shooter self-taught project | Solo Project | Sep 2025 - Present
Learned Skills
  • Unreal-Engine 5.6
  • GAS
  • C++
  • Networking/Replication
  • Listen & Dedicated
    server support
  • Inventory System
  • AnimEvents
  • Interfaces
  • Components
  • Rider
Cinque Terre Symbol
ReVengine - 1993 Doom engine inspired, game engine - DirectX11 C++ custom game engine | Solo Project | Oct 2024 - Jan 2025
Used Skills
  • C++
  • Github
  • Component based
  • Multi SDL/SDL2
  • PhysX collision system
  • DirectX11
  • ImGui
  • SoLoud
  • Stb
  • Glm
  • Visual Studio
Cinque Terre Symbol
KnipTang-Engine - Custom C++ Game engine | Solo Project | Jan 2024 - June 2024
Used Skills
  • C++
  • Github
  • Self-made AABB
    collision system
  • SDL
  • GLM
  • XInput
  • SDL_Mixer
  • ImGui
  • SteamWorks
  • Visual Studio
Symbol
Form Frenzy - Two-Player Party Co-Op form matcher - Programmer & Game Designer - Unity | Team Project | Jan 2024 - June 2024
Used Skills
  • C#
  • Unity
  • Perforce
  • Visual Studio
Cinque Terre Symbol
Genetic algorithm perfectly plays Flappy Bird with a Neural Network | Solo Project | Sep 2023 - Dec 2023
Used Skills
  • C#
  • Unity
  • Github
  • Visual Studio
Cinque Terre
Behaviour Tree - Developed C++ BT framework(No UE BT used) & AI car - Unreal Engine 5
Solo Project
Cinque Terre
2D Vulkan engine
Solo Project
Cinque Terre
Ride Of Giri - Unwrap group GameJam project - Unreal Engine 5
Team Project
Cinque Terre
Dooom - Remake of Doom 1993 made in self made Game engine(ReVengine)
Solo Project
Cinque Terre
Pengo SEGA 1982 - Remake of Pengo made in self made Game engine(KnipTang-Engine)
Solo Project
Cinque Terre
BlurMePls In-Real-Time webcam face detection blur - OpenCV
Solo Project

Contact Me!

arne.olemans@outlook.com

GoldKnights
Internship
Czech/Prague
Feb 2025 - June 2025
Used Skills
  • Unreal Engine 4/5
  • C++
  • Materials
  • Widgets/UI
  • TortoiseSVN
  • Team work
  • Communication
  • Daily meetings
  • Feedback
  • Self study
  • Flexible hours
  • Time management
  • On-site
  • Remote
  • Rider
  • Visual Studio
About the studio

I successfully completed a 4-months internship at the Czech double-A studio GoldKnights.

I had the privilege to complete my internship at there studio in Prague itself. Programming wise GoldKnights was at the moment of my internship fully focused on Unreal. The employee skill level went from current students to experienced developers with over 10 years in the game industry.

Before the start of my internship they released two titles and worked on various client projects. Their most notable release has been “The Last Oricru”. This is a double A, action RPG with still active players, even 2 and a half year after release.

Because GoldKnights is a smaller indie studio I was in direct contact with Pavel Jiri the founder of the company to arrange my internship. During my internship I had less contact with Pavel besides a short daily standup meeting where everybody of the company went over what they had been working on in the last day.
I communicated on a daily bases mostly with Petr and Tomas.
Tomas was the artist I worked closest with. Throughout my internship we were in constant contact while implementing new features. He worked on the design and art while I did the implementation of the UI tasks. We gave each other constant feedback throughout the development process. This gave me the feeling that we were working towards an end result together, and it taught me how to work in a team dynamic.
Petr is one of the lead programmers of the company and he also became my supervisor during the internship. I worked mostly with him on the Oddin project. He taught me the best practices to keep in mind while working with Unreal. Petr was the first colleague I would contact if I had any question relation to the Unreal Engine. He really took his time explained to me all the good practices and provided me with incredible feedback. I’m really thankful to have been able to work with him.

Our main communication between colleagues during our daily stand ups happened on Discord.
During my internship I received half of my tasks through discord and the other half through FreedCamp.
FreedCamp, is a project management tool to easily display tasks in a team dynamic.
Additionally I had the chance to learn the source control TortoiseSVN on a daily bases.

During my internship I worked for the most part on Redneck Zombie Hunter. This was the main title of GoldKnights that they were currently developing during the majority of my internship. This project was a story based horror zombie survival game. The project got unfortunately canceled during my internship.
I was also allowed to work on two of GoldKnights clients projects, the Oddin CS project and the Oddin Dota2 project. Oddin CS is a first person competitive shooter based on the valve title, Counter strike global offensive. Oddin Dota2 is a competitive Multiplayer online battle area like game, based on Dota2.
For all of the above mentioned projects I reimplemented and developed the logic for most of there UI's and HUD's.
ThreeForSimple
Solo Project
Sep 2025 - Present
Learned Skills
  • Unreal-Engine 5.6
  • GAS
  • C++
  • Networking/Replication
  • Listen & Dedicated
    server support
  • Inventory System
  • AnimEvents
  • Interfaces
  • Components
  • Rider
During my internship at GoldKnights that lasted from Feb 2025 - June 2025, I had the opportunity to work with Unreal engine 4 and 5 for 8 hours a day on real ongoing game projects. These double-A projects from the studio itself and from clients of GoldKnights. All of these were in the Unreal-Engine and made me realize why there has been so much commission surrounding this engine for the last couple of years.
Besides the obvious graphical capabilities and ease of the engine, I was mostly surprised by all the build in futures Unreal provides. For every problem or assignment I faced, the engine had a tool to resolve it. It made it possible to achieve previously daunting tasks like providing networking in your game feel more accessible than always without to many constrains. It may seem like a insignificant aspect to some, but I was really blown away by the engine when I was asked during my internship to add multiple language support in one of the ongoing projects. After a quick search I found out that the engine already had a system setup for this. I was able to bind all game text to this localization system to setup a translation for everything the studio pleased.

I won't deny that I previously had a skeptical view towards the Unreal-Engine because of countless horror stories I heard surrounding the optimization difficulties and development process of the engine. After working with the engine for 4 months I came to the conclusion that most of these issues were now resolved in the engine or were the fault of those individuals that warned me about the engine, using the engine wrongly.

All of these above mentioned experiences made me fall in love with the engine and I decided to continue self educating after my internship.
I saw various studios that switched to the Unreal Engine working with the GAS plugin. While learning more about it I figuring out how streamlined it could make the communication of changing data between different objects, I figured that it would be worth it to include this system in my next learning project.
As many, I had been interested in making a multiplayer/networking project from the beginning of my programming journey. I played with some networking libraries/frameworks in the past but none of them really clicked with me or provided me the correct learning opportunities I was looking for. While learning other basics of the engine I felt like I still missed before I could start this project, I realized that the GAS plugin had excellent networking support and made the barrier to entry for multiplayer games even lower than it already was with Unreal.
It was finally time to make my childhood version proud. I started the development of ThreeForSimple. A Unreal Engine 5.6 C++ multiplayer third person shooter with as minimum blueprint usage as possible and using the GAS plugin. The main objective of this project was to have a shooter game with three attack/weapon types(Melee attack, projectile weapon, hitscan weapon), an inventory system and a lobby system.

I learned an immense amount during the development of this project. It took over my life and mind the same way programming would when I first started getting into it. It gave me an excellent introduction to the GAS plugin and how networking concepts work in Unreal. How everything in the engine can communicate with each other and how everything is connected over the network. I finally learned about the inner workings of the replication system of Unreal and how I can use hash tables to communicate changes in the inventory system over the network without having to pass entire objects.
I could keep going on about everything this project provided me so far. It offered me so many insights in how the Engine itself works and whats possible with it. For exactly this reason I will continue working on a daily bases on this project. It has been incredible motivating to work on this project because it provides me with so much new knowledge on a daily bases.

In the short term I am planning on finishing the intractable lootable chests and reworking the lobby to be able to self host games and see a list of currently running games that you can join. I will deploy this project to a server soon, as I believe that this will teach me more about networking and whats needed to launch multiplayer games after development. To view the project files, please visit the associated project Github page.
ReVengine
Solo Project
Oct 2024 - Jan 2025
Used Skills
  • C++
  • Github
  • Component
    based
  • Multi SDL
    SDL2
  • PhysX for
    collision system
  • DirectX11
  • ImGui
  • SoLoud
  • Stb
  • Glm
  • Visual Studio
I decided to start development of my own small scale version of this engine. I wanted to prove to myself that I would be able to develop a 3D game engine with the same 2D rending sprites as the first Doom from 1993 had. For the rendering I used DirectX11 and for collision detection I decided to use PhysX as I wanted to get familiar with a more AAA industry standard physics/collision library. However, once I was deeper in development with PhysX I realized that it didn't leave me with lots of freedom and forced me to used their build in actor components to be able to let collisions work.

For a more technical look at the engine and the documentation/reflection I love to invite you to the associated Github readme paper.

After the development of my first game engine(KnipTang-Engine) I was left unsatisfied by several aspects. Part of the KnipTang-Engine felt rushed because of time constrains. This took away parts of the learning opportunity the creation of that engine should have been.

Additionally, I was also relearning DirectX11 at the time. This gave me the idea to challenge myself to combine this new gained knowledge to create a 3D engine. After falling back into the world of indie engine development I was recommended the book "Game Engine Black Book DOOM". This book went in depth about the team behind the first Doom game engine of 1993, id Tech 1 and how they worked around the technical limitations that played a major roll at the time. Reading about this time period of the game industry and how they were able to accomplish such a ground breaking engine at the time was the main motivation during the development of ReVengine.
KnipTang
Solo Project
Jan 2024 - June 2024
Used Skills
  • C++
  • Github
  • Self-made AABB
    collision system
  • SDL
  • GLM
  • XInput
  • SDL_Mixer
  • ImGui
  • SteamWorks
  • Visual Studio
The first game engine I ever made from scratch.

The creation of this game engine took my engineering, C++, and programming skills to a whole new level.

I learned so much about all kinds of different technical fields and concepts. It opened the world of all varying kinds of gameplay patterns and which ones are best to use in what situations and others you should better avoid.

All the different techniques on how you could optimize and be capable of rendering and controlling all sorts of massive infastructors within your applications. Those patterns refueled the passion I had for programming, in the same way excitement I had when I first started out programming. Besides that, this project also taught me the crucial importance of good coding habits and practices, when working with a large code base that will keep increasing in size like this one did.

After finishing this engine I realized how much easier it has become for me to grasp concepts and tools in different game engines. Understanding the ins and outs of how game engines get developed greatly shifted my perception of game development overall.

I can say with certainty that developing this engine has been the most significant learning experience I had in my journey as a software engineer.

If you want to find more information about the technical aspects of this project feel free to visit my Github readme paper associated with this project.
Form Frenzy
Team Project
Jan 2024 - June 2024
Used Skills
  • C#
  • Unity
  • Perforce
  • Visual Studio
Form Frenzy… The first project I would develop in a group setting.

The creation of this piece allowed me to experience the full-length process of developing an indie game title. From brainstorming in panic when all our ideas fell apart after a closer look at them, to scrapping all of them, starting over, and combining our ideas like real team players!

Besides teaching me a large amount about what makes a game stick and how to avoid implementing game-breaking features, the most important lesson I gained while developing Form Frenzy was without a doubt the aspects of the group dynamic that came with it. It taught me about the importance of open, direct communication, the highs and lows of working with others, and the groundbreaking upper hand you can gain when you're not alone to steer the ball in the right direction when it starts rolling.

Overall I can state that it was a mind-altering adventure working with this team. I will take the achievements I gained with me for the rest of my career, in as well as outside of the industry.

If you want to read more about the process of developing this project, you can read the DevLogs on our itch.io page.
Flappy Bird Neural Network
Solo Project
Sep 2023 - Dec 2023
Used Skills
  • C#
  • Unity
  • Github
  • Visual Studio
This project was my introduction to neural network programming.

When I came up with the idea to develop this project I had no clue where to start. I knew that there would be a lot of new concepts I needed to grasp to successfully complete this project.

Besides all the technical concepts, the development of this project taught me something way more valuable. It taught me one of the most important thinking patterns I have learned about programming,
When trying to find solutions for problems you encounter while developing big or even small projects, it's of the highest importance to keep breaking down your problem into smaller pieces. Keep doing this until what seemed to be a gigantic unsolvable problem gets converted into lots of small easily solvable problems that have 9/10 times easy solutions.

If you want to find more information about the technical aspects of this project feel free to visit my Github readme paper associated with this project.