So You've Decided to Move from Unity to Unreal Engine
impromptugames.com
So You've Decided to Move from Unity to Unreal Engine
1–10 of 152 posts
Re: So You've Decided to Move from Unity to Unreal Engine
#2I'm curiously to see whether a big player switches side. Likely not as all big players were probably consulted.
Re: So You've Decided to Move from Unity to Unreal Engine
#3> Read the documentation on the Gameplay Framework. All of it!
Is it just me or is this an unviable learning strategy? My approach for learning anything has always been to follow small tutorials, build an intuition, and only consult docs when I need some specifics.
Re: So You've Decided to Move from Unity to Unreal Engine
#4> Read the documentation on the Gameplay Framework. All of it! Is it just me or is this an unviable learning strategy? My approach for learning anything has always been to follow small tutorials, build an intuition, and only consult docs when I need some specifics.
Everybody is different. It's certainly unviable for some people.
For me, the ideal thing is a book, and great docs can feel like this. Something well thought out, comprehensive, deep, and importantly error checked/reviewed. The downside is books are increasingly rare and get outdated really quickly.
Re: So You've Decided to Move from Unity to Unreal Engine
#5wow, great resource even if you just like to know more about both.
Re: So You've Decided to Move from Unity to Unreal Engine
#6> Read the documentation on the Gameplay Framework. All of it! Is it just me or is this an unviable learning strategy? My approach for learning anything has always been to follow small tutorials, build an intuition, and only consult docs when I need some specifics.
As someone who recently learned UE: yes, this is completely unviable. The UE API docs are almost useless. Use Rider and its code navigation instead, you'll get much better results.
The docs about the concepts are better, those are worth reading.
Re: So You've Decided to Move from Unity to Unreal Engine
#7> Read the documentation on the Gameplay Framework. All of it! Is it just me or is this an unviable learning strategy? My approach for learning anything has always been to follow small tutorials, build an intuition, and only consult docs when I need some specifics.
I think it's just different learning styles. My preference for learning e.g. a new programming language has always been to read a book cover to cover as the first step (if it's a language established enough to have a book anyway). Note that it's not important that I actually understand everything on this first pass. The cover to cover is mostly about getting the lay of the land so I know what exists, then, even years later when I have a problem that could be solved by using some bit of the language that I read about but didn't really understand but vaguely recall is a thing it springs to mind and I can do my deep dive on that aspect then.
Re: So You've Decided to Move from Unity to Unreal Engine
#8I 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 sideways.
I realize that OSS options like Godot aren't really comparable, but since Unreal's main competitor is Unity, it feels likely that Unreal could do something similar since they don't have a competitor keeping the pressure on about price anymore.
Re: So You've Decided to Move from Unity to Unreal Engine
#9I'm curiously to see whether a big player switches side. Likely not as all big players were probably consulted.
I get the impression that Unity did not do a lot of homework before rolling this out. Several aspects of the policy they’ve waffled on, and when asked about who would pay the fee for GamePass games, they said the distributor would, but it appears the distributors were not consulted on this.
Not to say they didn’t consult with the major Unity players, but it seems plausible that they didn’t based on the carelessness of the rest of the rollout.
Re: So You've Decided to Move from Unity to Unreal Engine
#10> Read the documentation on the Gameplay Framework. All of it! Is it just me or is this an unviable learning strategy? My approach for learning anything has always been to follow small tutorials, build an intuition, and only consult docs when I need some specifics.
Yeah I agree. For me personally the best combination seems to be a quick start guide to get me bootstrapped and let me get the gun poinTed at my feet, and then solid normal documentation for me to mend my feet each time after I shoot myself.
Some of it is a matter of it being hard to even have the language to know how to ask the questions you have, so a bootstrap or quick start to let you just get in there and start looking around helps a ton and makes the full documentation a lot more accessible.