So You've Decided to Move from Unity to Unreal Engine
11–20 of 152 posts
Re: So You've Decided to Move from Unity to Unreal Engine
#12Re: So You've Decided to Move from Unity to Unreal Engine
#13Re: So You've Decided to Move from Unity to Unreal Engine
#14Re: So You've Decided to Move from Unity to Unreal Engine
#15I 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…
Re: So You've Decided to Move from Unity to Unreal Engine
#16Re: So You've Decided to Move from Unity to Unreal Engine
#17I 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…
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> 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.
Re: So You've Decided to Move from Unity to Unreal Engine
#19Re: So You've Decided to Move from Unity to Unreal Engine
#20Is anyone aware of unofficial (and maybe illegal in some jurisdictions) releases of Unreal toolchain that strips off the Epic Launcher and can be downloaded without making an account?