UI Designer's Engine Course, Unreal UMG Recipes (Beginner)

UI Designer's Engine Course, Unreal UMG Recipes (Beginner)

🍳Before we start...

❓What content will you learn?

🔎Practice Preview

In the practical section of this lecture...

You can learn everything all-in-one!
Now you can confidently say you've tried your hand at UMG, right?

🐤Expected Q&A

Q. Why Unreal 4 instead of Unreal 5? Do you know what era we're living in?🙁

• Yes, I completely understand that feeling of wanting to install the latest engine version right now and move into the new era! However, to bring up a somewhat sad topic, UMG didn't really have any remarkable developments in Unreal 5. In fact, bugs from version 4 were carried over as is. While there are some changes in terms of usability, the basic framework remains entirely the same, so for the introductory learning process where you need to master that framework, I thought Unreal 4, which lacks additional convenience features, would be more suitable. If you know how to use 4, you can quickly learn to use 5, but if you first learn with 5, it would be quite difficult to go back to 4 later (and you probably wouldn't want to either). Also, in our country's industry, there are many games built on Unreal 4 that are still being serviced, so Unreal 4 still has many practical applications. This is even more true for larger companies.

  
  
  But as I mentioned earlier, once you get past the beginner level, it would make sense to learn the new features of the latest version as well. After that, I only have plans for now, but if I proceed with more advanced lectures, I'm thinking of covering Unreal Engine 5's UMG at that time.

Q. I heard that UI designers can get jobs easily even without knowing engines. Is it really necessary to know engines?

• Actually, I hear that a lot from people who recently joined as new employees.

  
  That's right, getting hired might be possible even without knowing the engine, but the problem comes after that.

  If you don't understand how UI works within games

  It's easy to naturally become excluded both in meetings and during the implementation process.
  
  

  Not knowing the engine doesn't simply mean not knowing the technology,

  This means they don't know how their design actually moves and responds.

  That ultimately means giving up about half of design's power on your own.

  Knowing the engine makes you much more free as a designer.

  I can see how the UI I created is actually implemented in the game,

  Communication with programmers or planners also becomes easier.

  From that point on, you'll be recognized not just as 'just a designer' but as a 'core member of the development team'.

  Beyond getting a job, if you want to become a truly skilled UI designer with lasting abilities,

  You must know the engine.

📝Notes to Consider Before Taking the Course

👩‍🏫Who will teach us?