Project H8ck – Hello, Unreal Engine

Creating an Idle-style game with Unreal Engine is proving very interesting, but I have not found many details on it. This has me thinking that I need to create a video series. Contact me if you think this would be useful.

The extensive full-game development has started in earnest. But there is a twist: I switched from Unity to Unreal Engine. I will tell you why and catch you up on all the news.

Let me start by saying that I have not used Unreal Engine before, so this project is also a way for me to learn parts of the engine that I need, along with developing the game.

So far, I have solved every problem I encounter as development progresses. This alone gives me hope, as I have not hit some of the issues Unity presented during the core engine building.

To begin with, one primary reason that had me considering the switch of engines was finding things that presented more challenging problems than I felt they should have been with Unity.

For example, multiplayer features like simple leaderboards and data sync have frustrated me as I tried Unity's services and Firebase. I talk about some of this in my UIBuzz Podcast episode, which can be found at this link.

I know some folks will point out that there are Unity packages and plenty of tutorials to help set up support for these services. But my point is that it was more frustrating than necessary. Plus, even when I got them working, I was unsatisfied with the many hoops I had to jump through—a.k.a. plenty of code smells.

Not everything Unreal Engine is better.

At this early stage of learning, one thing stands out to me: Packaging for distribution with Unreal Engine is far more complicated than with Unity. So, let me give Unity a high five.

The problem starts with the Unreal Engine Editor.

On a Mac, it runs as Intel on my Apple M1 chip, which means there is a performance hit before I even start work. Even at the app opening stage, it is noticeable when the engine needs to recompile all the shaders.

So, I pulled out my Windows gaming laptop (it's a beast). Naturally, Unreal's Editor runs silky smooth on a Windows machine. Maybe that is due to the Epic and Apple relationship. Who knows.

The problem now is packaging for Android and especially iOS on a Windows machine. I still have not been able to make Unreal Editor happy with my JetBrains install of Android Studio to successfully compile and package without complaining.

I can only get an iOS compiler to work by running Unreal Engine Editor on the M1 Mac and exporting it to Xcode, where I deal with all the code signing and other issues. But it does at least work.

The Good News

The good news is that I have at least figured out a system for moving forward as I learn more. I think this will ultimately make it better for me to maintain and expand the game while giving you, the player, a better experience.

Remember, you can now play the single-player version beta on Android and iOS by signing up to the game site and signing up. Help craft the game as it moves forward.

Onwards and upwards!

[Follow up article on how it's going]

Project H8ck – Hello, Unreal Engine

Comments

More from this blog

Stop Forcing AI Disclosure

What will WWDC 26 bring for developers

Fun with Pygame

Learning Rust, some early thoughts

Some software development career truths

Not everything Unreal Engine is better.

The Good News

Command Palette

Comments

More from this blog

Not everything Unreal Engine is better.

The Good News