Live data from Hacker News

So You've Decided to Move from Unity to Unreal Engine

impromptugames.com

11–20 of 152 posts

Re: So You've Decided to Move from Unity to Unreal Engine

#12
A course that finally made Unreal "click" for me, after years of toying with it, was Tom Looman's 'Professional Game Development in C++ and Unreal Engine' course. The source for what you build (with the chapters available in the git history) is here. [1] It was based on a class he taught and so also includes homework, which I found infinitely more valuable than just following along in a 'Here's how to [x].' type lesson.

[1] - https://github.com/tomlooman/ActionRoguelike

Re: So You've Decided to Move from Unity to Unreal Engine

#15
post #8

I can't help but be reminded of the people who jumped from Twitter to Threads. Ultimately, the recent wave of enshittifications of major products - Unity, Twitter and Reddit off the top of my head - It's a hard reminder that lock-in and governance matters. Software is a long investment, so it's time to start thinking very hard about how the software you use is run, and how much control you have if it all goes sideway…

Game development is a very different space due to the extreme amount of middleware used and the fact porting between engines has been done since the 90's.

Re: So You've Decided to Move from Unity to Unreal Engine

#17
post #8

I can't help but be reminded of the people who jumped from Twitter to Threads. Ultimately, the recent wave of enshittifications of major products - Unity, Twitter and Reddit off the top of my head - It's a hard reminder that lock-in and governance matters. Software is a long investment, so it's time to start thinking very hard about how the software you use is run, and how much control you have if it all goes sideway…

Do not fool yourself here, Unreal's main competitor was never Unity, it was the different myriad of proprietary engines that exist in powerful studios, there is were the millions are.

Unity could never get into that piece of business and Unreal Engine is barely scratching it.

Re: So You've Decided to Move from Unity to Unreal Engine

#18
> I heard Blueprint sucks!

> Blueprint actually rules. Look, I get it - why would a visual scripting thing be good? They're all shit! I agree.

> Blueprint is the only one that's any good. It's amazing. It will also help you learn the engine. Everything you do there will be applicable to C++. No matter who you are, you should start in Blueprint. It's 100% true that you can build an entire game in Blueprint. Yeah, with multiplayer. Yeah, performantly. Yeah, maintainably. It's not just for rapid prototyping.

> Be a snob about Blueprint at your peril. I've helped a lot of people get good at Unreal and get hired for it, and Blueprint-related recalcitrance is the number one way people screw themselves - without realising, they sentence themselves to months of wasted time and frustration only to mould themselves into the type of Unreal user who sabotages any team they're on. Swallow your pride and look at some nodes.

Best advice in this page. Blueprints are excellent. They make the engine API extremely discoverable. You naturally gain a deep understanding of the classes and components and how they interact. They are performant. They can do 95% of what you want.

The C++ engine API is fine but it doesn't lend itself to learning the engine. I don't recommend using it unless you identify a specific need.

Post reply on HN