Unreal has some issues with its Blueprints.I cannot put my game all into the engine as I want to because the engine is unstable, and crashes often. Because UE 5 does not support the Gtx Geforce 2070 card and warns of issues when you start up the engine....The engine also suffers from an irregular heartbeat and does not sync up consistently with its own timing. So it suffers from timing changes. Even crashes after a while when having nothing in the engine in a new blank project it still tends to crash after a few hours of leaving it idle. Everything is also put all into one big massive cache file so I can't load the game in modules as everything is all put into one big container.. fiile so I see it being Suitable for building small to medium sized projects. But not large projects if you not got lots of storage space for all the thousands of raw files needed that the editor loads in which can go up into a hundred or more gigs. and my game is a large project. Was a little dismayed when downloading one of those meta human rigs from bridge only to find the meta human took up 1.6 gigs up of file space and had over 700 asset files to the rig itself. I have over 300 npc characters in my game because my game is on different worlds, so meta humans was not going to work. 700 x 300 - 210 thousand files, Hmm I don't think so. Just to do one hundred 1028 x 1028 head textures takes up abt 200 megs of space.. When I downloaded just one of those 8k res textures, it took of nearly 400 megs up of space. Unreal also adds in alot of extra files.
Hey woody! Would you be interested in having the lighting and post process setup redone for your avatar scene? I can create various suggestive scenarios with your scene and you will be able to use them at your discretion, also some nice character lighting setup on top of that. Let me know :)
i just got it and this is prob fixed in updated versions but crashing trying to do anything... lol, i didn't want to do all the sign up bs so got it alternatively... they had go here click download ez mode, wasn't broken, DO NOT FIX IT.
You don't pick up unreal to "Learn Unreal", no single person can learn Unreal. You learn how to make A GAME on unreal. Just decide what game you want to make, find out what you need to learn, implement each lesson as you go. Don't worry if you need to restart the game from scratch a few times. That's game dev. Your game needs a solid foundation and you're in the process of learning to make them.
Absolutely! Have a core concept, figure out how it works, and learn what you need to make it work. I want to make a flight sim, with unique aerodynamic dogfighting. It's an idea I've had for a very long time and it's pretty well thought out. Most of my "dev" work is figuring out what I need to build something, not actually building it haha. Once I learn, the work itself comes easy. The key is to break big ideas down into smaller chunks. Figure out a chunk, and if that chunk turns out to be too big, break it down again. This makes progress possible, and even the smallest steps are still steps forward. It just takes time.
@@NickRomick I’ve restarted my games like 20 times because when I was starting out I had so many ideas and I couldn’t make up my mind and sometimes I would mess animations up and it would be too far gone lol
The reason I quit UE in favor of unity (and in future, if they add some decent terrain tools, maybe Godot) is mainly for 3 reasons: 1) First and foremost un utterly long compilation times. If you use nanite, lumen and all the goodies, compilation can take DAYS. With a (good) laptop, I can't afford that. 2) C++: I already know some C++, however, compared to C# it needs way more care and it's difficult to master the huge UE library without someone pointing you in the right direction. C# is way more solo dev friendly. 3) Resources: if you use the latest technologies, you'll need a extremely powerful machine to run your dev environment without frustration. Overall, even if UE gives you a ton of amazing stuff, as a solo developer I'll never be able to unleash it's full potential, and will probably end up developing a game that can be done in Unity way faster. I spent some time with godot, too. But it is just not there yet. Not for games requiring huge maps like the ones I love. So I'm sticking to Unity for now. That being said, I still have UE (4) installed, because I port assets (often free) from UE to unity.
The truth is, you have to just spend the time. Try things until it works. It can be super frustrating to follow a tutorial to the letter and it doesnt work. And nothing you try works. That is why you have to learn the basics and then just make things on your own. When you start thinking through what you want to do, implementing and then having it work, it is like hitting a hole in one in golf. But the work you will have to do to get to that point is crazy. When you get super stuck, take time away and think about it from time to time. That helps me. Coming at it fresh.
then u find out that u need pre-experience u gained from working in a game studio or you wont be able to do anything in ue because not enough educational material online. unity has much more educational material online. unity wins for normal people.
@@bestboy007I don't agree with this I think both can be used for "normal people". I think the difference is unity will have a lot of 2d games while people see unreals potential and they all of a sudden want to make a 3d RPG with a billion features. You can learn just as well from both and yes unity has more educational material because of the community and partially because of how it's been for a long time....but that doesn't mean it's much "harder" to learn unreal either.
I feel like I disagree with evrything you said. I switched from Unity to Ue5 and I can say that I am glad I did that. I had way better results way faster and everything wad way more stable without random buggs coming from some where. And that Blueprint system was for me personally very easy to grasp. Still some people might be overwhelmed or have a harder time learning Ue5 which I can understand too
Agreed. Used to work with a global arch viz firm who was always into innovation and pushed us to innovate and find the best. We were one of the first to implement VR, AR, photogrammetry and AI into the design pipeline (does anyone remember Blenders game engine?). Looked into Unity, UE and Godot and a lot of other realtime tech. Personally, what I love about UE is the visual scripting. I'm more of an artist than a coder, so for me I was able to program using BP in UE is so awesome in the sense that as long as you know your stuff, it fits so perfectly.
Right like how do you get confused by blueprints unless you have zero engineering logic skills. It’s simple flow. And literally ALL blueprints are fundamentally the same, they just are used differently. Animation blueprints are the same as actors blueprints, it’s basically just the parent classes that matter.
You disagree reason 4 !!? Are you sure about this I'm using unreal engine never touched unity but really I'm struggling with finding tutorials for certain things
Unreal Engine is made for AAA in mind where you have dedicated people for a job and can focus on only one tool to master it. Also UE has limited access to learning resources or non existing for certain fetaures. There are also problem with UE API, its embeeded itnto an engine and needs to work with certain workflow so if you working on something outside of scope of engine and is non standard FPS, TPS or other generic game it makes things difficult. For example i am working on space sim game and physics and extending editor for new tools is tricky and almost non documented. This is required for my game to create planet rendering tech , i will love to do that with unreal, i know it is possible but requires soo much digging that will take more time than it should and i can already do that with Unity.
@@SVAFnemesis Unreal Engine is developed with the intention of providing all the tools required to develope a game to the quality and standard of a AAA studio title. It supports some of the best graphics I have seen across engines (if that matters to you and if not you can simlify with sacrificing any preformance). It offers the vbersitility to accomplish just about anything you set your mind too, especially with the blueprint system. Granted, the blueprint system does have limitations that can hold it back in comparison to code and if you wanted to, you can use C++ in tangent with UE to fix those limitations. Not everyone is going to want to learn C++ though and the nice part about blueprints is that all you really need to learn is some basic programing logic terms and that is it. You can no model and adjust models within UE (a feature new with UE5). You can import models and animations with relitive ease. The list goes on. UE is built with the goal to give solo and indi developers the same range of potential as a AAA studio without having to go through the nuance effort of building an engine from scratch, learning to code, and relying on a dozzen third party programs to support the development. Where I believe the OP is having their actual issue is in that UE was originally designed as a FPS/TPS engine. Prior to 4.0, the engine didn't really support anything else all that well whichy is why the engine didn't start to boost in popularity until we got into the 4.0 period (as far as I am aware. I am sure someone more educated on the history of UE could correct any errors I made here). All that said and one, the problem with UE is that most other genres are new. It was built for shooters and now that is supports more than just chooters, it has been a slow gradual community effort to showcase its newer potential. Granted, 4.0+ (as far as I know) is what introduced the concept of UE being used for more than just shooters and while that is still several years old, its still considered new support. What I can say to that though is that the community for UE has been incredable. I am on three discord channels for UE, two of which are community made and all of them have been absolutly amazing tools to learn UE. I can see some people being put off over the commen attitude of "here is some advise, but you need to try it to learn it" method. (Literally, no one is going to spoon feed you answers), but their help and advise has been incredable to me. In addition to Discord, there is the UE Redit group that is arguably equally helpful and very resourceful and there are a few select TH-cam channels that are great follows for new devs. Unreal Sensi and Vertus Hub being the two I would immideatly recromend. Going to be brutally honest, based on what I have expiearienced, it sounds an a lot like the OPs problem is simply being lazy.
I am going to stand very hard against a lot of what you have said here mate. Please do forgive me as this is going to sound harsh but I do stress I do not mean it as an attack against you or an attempt to start a fight. Based on what you have said, I have two comments to make here. 1. Unreal Engines support of genres outside of the shooter range is still, despite being available for years, new. It is very young in its ability to branch out and you are not alone in feeling the flack for it. Does that mean the engine is incapable? Absolutly not. Unreal Engine is at a point now that you are nearly limitless in what you can do with it. I would say though, that if a physics engine is what you need, either you will need to modify Unreal Engine itself (source code is open to the public) or loom for a dedicated physics engine. However, I strongly stand by in my belief that UE is at a point where even a physics system will come into play in due time and it won't continue to be a problem. 2. This is where this is going to sound harsh, but the impresion I get is that you just arn't making the effort to get the answers you need. And I am not talking about googling for tutorials or other devs posting tests of concepts and such. I mean getting online for a few hours, engrosing yourself in the UE community and asking for help, sharing your problems, collecting feedback about how things could be done or could be done better, and puitting the time in. iAs I said in point 1, UEs support for games outsisde shooters is new. There are a lot of genres it can support now and the community has been chipping away at revealing that potential day by day. Given time, presistance, and connecting with people willing to help you test those boundries is going to be probably be your best choice if you stick with Unreal Engine. However, I am a little more confused on why you bothered with UE if you could make it work in Unity? Was there something about UE specuifically that has enticed you to switch? If you can make the game in Unity with less problems, make it in Unity. If that is where your skills are strongest, I would keep your primary work in Unity and just explore UE until you get to a point that you feel you can transision fully, if that is your intention. Otherwise, what you want is simply going to take several years to get as the community keeps hacking away at testing the limits of the engine. I know three good Discord groups worth joining for help. Reddit is a good source too. Vertus Hub and Unreal Sensi are also worth the investment for beginners. I will had it to you, Vertus does not have a great track record with compleing tutorials, but part of that has simply been that he has a full time commitment to a project and UE updates faster than he produces. Currently. But in all of this I strongly suggest being more agressive and reaching out to the UE community. I know some of the Discord groups are slow to respond, but you arn't being ignored and if someone can't help, chances are they know someone who can. Unreal also has its own forums page you can post questions on and get further assistance.
@@christopherpoet458 I'm hoping to see more AAA made with UE, as for as I know, Unity has acounted for more major production so far. (I'm avoiding the word AAA since it has never been defined in game industry)
I love Unreal 5, it was a steep sharp end of the hockey stick learning curve, but now I’m feeling past the initial curve and just love it. It was definitely worth pursuing. Woody your mess analogy was great in describing this. Don’t be afraid to fail and make a mess. The message is in your mess people.
In terms of performance targets how possible would you say it is to get games to hit 60 fps on a ps5? Playing ue4 games like Spyro for them to run at a horribly framepaced refresh rate really made me dislike ue4 titles. I just want to know if that will be an issue this gen too
In terms of performance targets how possible would you say it is to get games to hit 60 fps on a ps5? Playing ue4 games like Spyro for them to run at a horribly framepaced refresh rate really made me dislike ue4 titles. I just want to know if that will be an issue this gen too
@@Cfreezy12 Did you play spyro on PC or Ps4 and if you played on PC what specs you have,because i sure didnt have any bad frame pace playing that game on mediocre PC,also engine by itself doesnt do mirracles devs can fuck up by doing stuff that is not recomended or take time to optimize game etc,there is many variables.
I wrote an AI script that was so terrible i wanted to cry. Then I watched a tutorial on unreal on behavior trees, blackboards etc and was rewrote it to be much better
@@BlackwoodHDEnglish thank you, what CPU do you have? It's hard to imagine the CPU can cause the difference between a few minutes to a few hours. Thanks.
Honestly, the thing that's helped me stick it out is that most of the C or C++ libraries I've used or written in the past tend to just work in Unreal. It took a bit of adjustment to get used to UE's build system, though.
Try bp unreal with native code, unreal in visual scripting is most easiest unreal try unity with ai and just collect the errors try animation state there try alot of things it need along time for practice. I start make games with unreal in two weeks this unity with them component is really confusing .
Any insights or resources you found to help ease that transition from C/C++ into Unreal C++ and the build pipeline? Im in a similar position in that I am a C++/C# programmer and am just running from one confusing situation (and crash) into another.
@@wopsieneter As far as the build pipeline is concerned, you can find a pretty decent, simple starting point with reub's video titled "Learn this before C++ - Unreal Engine Build Tool Guide." He's also got an overview of plugins. Now, as far as getting started making a project in Unreal using C++, if you have an idea of the sort of project you're looking to make, I'll do my best to point you in the right direction. I've found that following along with someone making a small- to medium-sized project has tended to clear up my doubts about the quirks of using C++ in Unreal and also the limitations of the Unreal Header Tool. (For example, a couple that stumped me for a while were not being able to put classes with the UCLASS() annotation inside of namespaces, as well as not realizing that modules and plugins are linked dynamically rather than statically.) I'd also recommend joining the Unreal Slackers server on Discord. I've found the answers to a lot of my more bizarre questions there, either by searching the chat history or asking the question myself. Let me know. Cheers!
@@littledemo3605 You should NOT use BP for most of your code, its messy, and its slower... you should be using more C++.... then BP.... Drives me crazy when people are taught this bad behavior, and this is why so many games are badly coded and run terrible....
@@recon5107 it's not really that slower, there's definitely overhead but rewriting your codebase to save 5 milliseconds isn't going to give you....great results, and you're generally not making a low-spec game with unreal anyway that's not to say that performance isn't an issue, it's just that switching most of your code from BP to cpp brainlessly won't fix an issue if there is one because the performance gain may be extremely minimal, that's why you use a profiler to figure out what should be written in cpp and what simply doesn't need to be or to figure out whether what you wrote simply isn't up to the task even if it works I would also go as far as to say that that's not the reason games run terribly, they run terribly because people write crappy code, switching your entire codebase to cpp won't fix that, learning how to make better code will regardless of what you're writing it with The discussion about speed does matter if you're comparing something like python to cpp, but there's countless of videos that compare bp and cpp code and their compilation output and while bp is definitely slower, it's usually not slow enough to make an actual impact. In an ideal world maybe saving those 5 milliseconds should be sought after, but people usually don't have that luxury be it due to time constraints or some other reason such as them LEARNING how to develop games...
Just started learning Unreal a week ago and I’m hooked. I picked it up pretty quick and achieved results that were unimaginable in other 3D software. BUT, I’ve been working as a VFX artist for years. And even before that have 5+ years of animation and 3D education. That said…don’t get discouraged! Sh*t took me literally 7+ years of beating my head into a wall wondering why things don’t work in order to start getting results I like. The VFX/game dev/animation pipelines are HUGE. Thousands of people huge actually. SO, take your time, work on smaller projects first, or even start with one job in the pipeline like 3D modeling or something. Once you get comfortable with that, then move forward. You’ll get there…I’m rooting for you all!
I just can not grab my head around it just to create movies. like what i need to learn? Do i need blueprints for it? why does it create blueprint when i import a character or metahuman.... its all so confusing.
Dont trust him. After 1 week you knowledge in UE = 0, after 2 week you level in UE = 0, after 3 week you level in UE = 0, only after few months ago you knowledge in UE = basical nub level. For typical use, much easy and fastly use Unity, i think Unity 2019 was really good solution for indie projects. (new versions a slowly) But for nice look 3D, UE really better.
@@ailanezz Dude, for basic newbie level in UE you need learn it few months, ofcouse you need blueprints, ofcouse you need learn also C++ if you dont know it. Just do something every time, and you make progress your skill.
The main reason is because people nowadays are unable to create their own assets. Just like unity it's a bunch of kids downloading stuff and sticking it together then calling it a game.
One thing I've noticed is an extremely complex task can be done in maybe 10 blueprint nodes. And sometimes something that should take maybe 2 lines of code can also take 10 blueprint nodes to implement 🙃
what I do is make a .gif of what node combo does what, so next time it will take 10~15 seconds, by just following what the gif shows on another screen.
some things can be easier in c++ so nothing stops you from using both. If you use unity you'll need to learn c#, needing to learn c++ isn't the end of the world
The reason I quit Unreal Engine is that the editor is extremely unstable in Linux -- crashes every 10 minutes or so. Even an unmodified project template left open while stepping away to attend to something else will have crashed and be frozen when you come back. The Unity editor has a few problems in Linux (mostly with the way pop-ups and progress bars are rendered) but at least it works. Unreal Engine doesn't look that hard, and it looks like it would make somethings easier (other less so), but I need something that works.
Thanks for this, been struggling with this engine but have been determined to keep going with it, my ADD keeps me learning new stuff but never in sequence and never unison with other skills... which is something I know I have to keep working on. This video was actually encouraging knowing I'm not alone in being a bit lost with what I'm doing with not as much resources available as I first expected.
Same, ADD here too, I will try to save you suffering and suggest you to follow a tutorial series for like an rpg or an fps and expand with your own things along the way. Itll be easiet
Not a professional but what helped me was getting on ADD medication. My life has improved soooo much and I have a wife and kids so even with a lot going on it has helped immensely. I’m learning unreal engine and Houdini right now
@@joshcruzmadeit as a professional myself we did not have you tube or any one helping us, so trial and error is the best way to learn, take your time and learn... failure is going to happen, and will only make you better... Alot of you tubers teach people BAD habits...it drives alot of us nuts, when we see it at the studio from new developers.... if you do this for fun, sure watch videos, but don't depend on them, many of them will steer you in the wrong direction but there are some good ones...
@@recon5107 Yes I have found I actually remember things better when doing it without tutorials. I mean I follow along but end up experimenting a lot and doing my own thing. Documentation helps of course. I get tired of tutorial hell quickly you know?. Could you name a good channel perhaps?
I'm learning UE on my own, but currently developing games on Unity. Each has its own learning curve, so anyone wanting to make anything substantial and meaningful, must put in the time and effort to learn the tools. UE is really great for artists wanting to quickly showcase their work (thanks to all the default templates), and friendly for less programming-savvy folk with Blueprints. Unity is very good for programmers since C# is arguably easier and more modern than C++, requires a much smaller storage/install footprint and has lots of tutorials. You can ultimately build identical games in either engine (there's a video a game dev did doing exactly that), so its really a matter of preference.
I also has the same thought. I'm really interested UE5 but C++ is pain. As a programmer, I like C# more. I don't like visual scripting like Blueprint and Bolt either. At some point, I have the plan to learn UE5.
@@jumpsneak I have made and published my own game thanks to Unity. As far as I can remember there was no pleasure at all. From the beginning until the end. Not to mention the random crash when I generate my apk. Yes, random: clean cache, restart and recompile: 19mn 32s each time. With Godot every problem I have had so far was my fault. It's so much better. Yes you are right: I have been really disappointed by Unity and after 3 years I have decided to give up. Go for Godot!
And I think what decided me to not cone back is the speed. Instant launch and when I generated the exe for Windows it was so fast I thought it didn't work! Lol
This is some good advice! Because a lot of systems in Unreal touch other systems, I was afraid to set things up wrong, but the cool thing is that if you set up things ‘wrong’ it doesn’t matter because things are flexible enough so that your way will work. I definitely brute force stuff: blueprints makes it pretty easy and fast to try out lots of different methods quickly.
I don’t even remember learning Unreal Engine. It was almost like I just woke up one day knowing everything about it. I guess it was just a hardcore ADHD hyperfocus month that got me to where I am.
As someone that's not a programmer at all (Actor, creator), but knows basic things, I wanted to quit several times, it's so frustrating for everything, but then I see all the possibilities regarding filmmaking, makes me continuing wanting to learn. So let's just keep being strong.
Funny. As someone who IS a programmer I HATE unreal. Because almost none of it involves programming.if you approach it from trying to do most things in code you are going to have a bad time
My work has given me one instruction: learn to use UE5. we have VR projects coming up which will involve lots of back end programming, so my focus is blueprint and C++. I did a crash course in C++ and it REALLY helped with the understanding of Blueprint. I'm still very much a beginner, but I can make things happen in UE5 now lol.
A lot of people make this mistake, with the Epic's blessing... No, you can't use Blueprint without learn C++. BP is just graphic C++. Learn C++ first, you will really understand what you are doing in BP after ;)
Dat intro!!! This was relatable! My BP started getting bulky and It started making me feel anxious. There aren’t a lot of content or doc on how to optimize bp or a level. So it feels really messy right now and makes me anxious if it’s ok to just keep adding things on top of it 😣
I feel like node based scripting is very sensitive to having a proper structure. In other words if you just throw things together, it becomes hard to read much quicker compared to regular code. To clean up a blueprint, you have to look for sections that have an enclosed functionality and pack them into functions, then use these functions instead of your original code to make things look cleaner. Alternatively you can assume what generic functionality you will need to do your thing and make functions for that ahead of time (and also test them) before working on the main script. These are really just programming fundamentals so maybe you should look for that instead.
That’s actually great advice. To be honest, I haven’t released any finished projects in any type of game engine but I’ve gotten really close. Usually it was for one roadblock or another and I just got bored and wanted something new, but I’ve learned a huge amount from those failures and unfinished projects. I’ve spent most of my time in gamedev using UE4, but my biggest problem with it is that it’s just too much. Everything gets thrown at you all at once. It doesn’t help that, as you mentioned, there’s very little in the way of good documentation and that creates so many roadblocks, especially just jumping into it when you’re still getting used to the editor and the way it likes things being done. TH-cam tutorials can only get you so far. That’s why I recently switched over to Godot (honestly don’t know why I didn’t start there). But that knowledge I gained from when I failed still sticks with me and helps me out when I get stuck or encounter problems outside of unreal.
one thing that is usefull for me, is write blueprints and their function in a word file for example how to switch a light, then when i need to use it, i remember this blueprint. Unity is more ez, but i think that if you are an 3d artist and do you love create assets, unreal is your engine.
Number 1 for me (and the only reason why I'm still using Unity/Godot and why Unity is still in the first place as a game engine on Steam) - is the lack of user-friendly language support. Blueprints are meh for me, I mean they are great for tweaking but making a core logic of your game in blueprints is probably not the best idea ever, starting from performance and ending on spaghetti. I really wish Unreal has some user-friendly language support like c# or maybe some of their own Python-like language or something. And yes... UE is getting just too big and overwhelming for a single dev, and Unity or Godot is more usable - but it's just only me. Not to mention that my laptop is dying using UE5.
@@leeoiou7295 C++ and C# are NOT similar. If you think that, you're definitely at the start. That being said, if you do have programming experience, then yes, it feels quite easy doing things in C++/Unreal Engine. Once you do pure C++ though, you'll learn how big of a difference C# and C++ have. C# is in fact more similar to Java than C++.
@@leeoiou7295 I'm not trying to say C++ is hard to program in. If you already have programming experience, then I'd definitely agree that you can learn it in ~month. I also did that. My point stands though that C# is very different to C++. It's not neccessarily about the syntax, but more about the way of how things are done
@@leeoiou7295 Tell this to million devs working with Unity, Godot, or any other engine which doesn't use c++ to use with them. You missing the point between going into the game industry and with going into software development to create engines or work for an AAA corporation making games using for example UnrealEngine. And no, c++ is not user-friendly, starting from memory management when compared to for example c#. You learned Unreal Engine and c++ in two weeks - LOL, sorry but this is B$. But hey, have fun using c++ in UE and I will have my fun using c# in Unity or Gdscript in Godot and we both will be happy.
@@tomtomkowski7653 Sorry but i have to disagree here too. It is clear that you have never used Unreal C++, or at least dived deeper into the topic. Unreal includes a lot of stuff you mentioned as a counter argument starting from Garbage Collection/Memory Management. Native C++ is indeed more complicated than c#. I agree with that. But the way unreal exposed all their functions, solved includes, used custom types, tons c++ macros etc... It is MUCH easier than native C++. So your argument just is not valid. Unreal's C++ is basically the same as Unity's C#. The syntax is different and it's a bit annoying that you have header and cpp files. But this can all be solved and simplified with IDE Plugins. Of cause you can do fancy pointer math if you need to. But almost every time there is a "Unity" way to do stuff. Heck, i could literally take a unity script right now and translate it 1:1 into Unreal c++, with only the function names being different. I find it much easier to program in Unreal Engine actually, because of the Blueprint system. You create your complicated game logic in c++ and then expose nodes for your game designers to work with. This makes communication and collaboration much easier. Also Unreal has much more features implemented, resulting in an overall more powerfull framework for me to work with. In Unity you need to implement a lot of the basic stuff yourself. If i need to do less, that is a good thing for the production pipeline. Also there might be million devs working with unity or godot, but most of them are indie devs. Big studius prefer unreal over unity. I can name you 20 TrippleA titles without much thought that are made in unreal. But for unity the only big games that sticked were Escape From Tarkov, Life is Strange, Subnautica and a lot of mobile games. The rest is indie.
Great video! I've recently just started moving from Unity over to Unreal - really enjoying my time with Unreal, and learning Unity first (C#) has really helped when it comes to using C++
@ジャス / jasu First, learn C++, C# is just a toy and will give you very bad programming habit ;) You can find pretty good begineer course on TH-cam or Udemy.
I've done a few games in Unity and I am working on my first UE game. TBH I think there is a ton of info on UE but it's hard to get up and running without just jumping in and trying/failing until you build up a foundation. Unity has good documentation but UE has these massive 1-5 hour long dev sessions where the UE devs show how to do specific things. UE has insane 3D performance and I am enjoying it so far :)
Welcome to game development.. here is the problem today.... how do you think us older developers started?? no one took us by the hand and we did NOT have you tube to take us around....We did it by failing...!!!!
Some general game dev advice: To be a good game developer, you need to be a little unhinged. You need to just throw yourself at the problems, and even if you don't find a good solution you will be a heck of a lot closer to a good solution than if you spent 3 weeks "thinking" about it and just getting paralyzed by the problem, speaking from experience. As a game new developer you will be much beter off not trying to map out every thing before you start. Just go until you can't, then start over and do everything better until you can't. By repeating this process you will learn much faster. Once you get past a certain point the learning curve will really start to flatten out. Once you've been here for a while there aren't that many first experiences left and only then you can start to think about optimization or refining you architecture or things of this nature.
I totally agree with #4 which is why I always post a tutorial or comment if the information is scarce. Dead end searches can halt whole portions of a project and when you are your own team, that's a big deal.
BUGS ! LOTS OF BUGS ! From project files not saving, import glitches, or simple features that saves a ton of time, are just a pain in the ass ! The only reason I use UE is graphics...
My 5 cents on your thesis, for those who are about to jump into the magic of UE for whatever reason: 1) You don't start with Unreal. Unreal is your final destination, so to speak. One who is starting has to wrap head around concepts of storytelling in 3d world - from modeling, rigging, texturing, lightning, simulations, film language, animation, etc. 2) Too menu tools is a two-sided dagger - if you don't know what you are up to, you can easily cut yourself on the way down the rabbit hole. UE has been used (especially from v5.0 onwards) by so many folks - from game designers and programmers to architects and movie makers. You really don't need them all, not from the very beginning at least. Planning is everything - if you know whats your goal and if you can grasp a path to achieve it - don't mind the other tools in this swiss knife. Thats why I find #1 so important. 3) Is, again, totally about #1. Keep the basic understanding of concepts under the belt, find your niche (if you are into simulations, take few years/lifes to master Houdini, for example) and for the rest of the job find someone who is into sth else (movie directing or programming, respectively). Most important thing is to know what do you want! 4) I'm in love with UE community so I'll skip this one :P 5) Can't agree more - trust the process! Most of the time UE tasks are a long way paths, so your anticipation, patience and willingness to learn are ''a must have'' on this, pretty much, neverending journey. Good luck to yall
"You feel you gonna make the wrong decision at any turn" It's valide for only 2 types of people : - The one who dont know what they are doing - The one who can't go out of the box and want to do everything by the book. Informatic in general is "no limit" it's not like you can by mistake create a glitch that can burn your entire life. In fact, all along your devs life, you have your best friend "CTRL-Z/W" to help you undo mistakes.
Too many tools is bullshit, try working with 3D for mechanical engineering companies like car industry, you will have to learn, revit, 3dx max, maya, blender, substance, pixiz, catia, rhino, freecad, cad, unreal, unity, c++, c#, python,... just because every customer you want has different tools, use different software, and you have to be flexible because you want the job. Unreal has like how many basic 10 different tabs ?
I still Remember the first time i opened ureal engine. It was 5 years ago i believe... Ue lasted only 15minutes in my pc 😂. I was already used to unity and compared to unreal engine it looked way more clean and user friendly so i lefted unreal engine so quickly because it looked like a total mess and a waste of time. But a few days ago i decided to reinstall unreal engine because i was curious to see some of the features pf the 5th edition of this software and with some patience i learned the basics of this engine and then i realized how much potential it has. Also a cool thing about unreal engine is blueprints! I don't know how to code in C++ and also a thing that slowed me down in my developing process in unity was learning the engine library. At the contrary with blueprints you don't have to learn almost nothing and also is very intuitive to me. It still took 2 days to code the basic movements of the first person character of my project but the next time i'll be way faster.
Really great video I can so relate to the documentation issue. I have found many times finding the official epic documentation page and it is just here is the node. No deeper explanation. They do have good introduction tutorials on the official channel which I have found useful. But yes far too often my search ends on an unanswered UE forum.
I used UNITY for over 10 years at work and I hated everyday of it. Once I started using unreal I never looked back it’s the easiest and most fun engine I’ve ever used as an artist.
Hi I'm a beginner when it comes to unreal. I find Unity bit easier compared to Unreal. Can u share the process (and links if possible) on how you started learning unreal, since you mentioned that it's the easiest. I'm curious to learn more.
i agree with poor documentation , i was learning both unreal and unity, but unitys documentation is just straight and simple, and they give plenty of example too.
One thing I also understand when working in UE is that you just have to follow their process of doing things. In Unity is different where you could just create an approach that you think is right. In UE they have this game framework built into it. You just have to understand how those works and carefully plan you to fit that into your project. The learning curve is very steep but once you get past that, everything is a breeze
I also have found that alot of people give up because they come into the game engine WANTING to make a game. This means that you must learn what you need to know. Bruh, stop, relax HAVE FUN. PLAY with the game engine, see what you can do do on a small level and then PLAY with manipulating those small things. THATS how you learn the engine, make it a fun puzzle game. Play, figure out what works, what doesnt work, what breaks and whats cool. Stop going into this with the "I have a tool and I must learn this tool, I must master this tool, I MUST become great at this tool!!! With out me my game engine is useless, with out my game engine I am useless, This is my game engine and their is no other game engine like mine!!!" No. go in with the mentality "This looks interesting I wonder what happens when I use this with this." Then when you've had your fun slowly start focusing in on what you need to do what you really want to do. Lol, if people did this more they would find unreal engine fun and easy to use. Instead they find it monotonous, tedious and aggravating. It's not a school project, it's recess. It's not reading a dictionary it's reading a harry potter series. It's not a dcumentary, it's an avengers movie. lol. Great vid by the way, appreciate the time you took to make it.
Awesome video! Some great advice. As a Unity dev one of my fave features is how easy it is to find documentation and answers - hopefully as time goes on Unreal will catch up!
You are so unique in this platform. Hopefully I can learn this kind of art. I'm looking forward to learn animation and this kind of 3D work but I don't know where to start haha.
Why I hate UE after 8 years using it: - Bad documentation as you said. You have to guess almost everything or hope that someone found and wrote the info you need somewhere online - Bad design. Nothing is logic, most settings can be enabled/disabled in 10 different places, a setting can be moved between two updates. - Bugs. Epic priority is adding new experimental broken features rather than fixing bugs, no matter if those features will never be production ready and will be removed in 1 or 2 years because they never fixed it. - You spend more time trying to make the engine work, not crashing, than working on your project. - Bad performance. Epic is always advertising about how good there rendering look but never about performance because they know their engine is worst engine in terms of optimization. That's why 99% of UE realesed games looks dated, why Epic Games biggest game Fortnite, a stylized game, and why good looking UE games have so bad quality/performance ratio.
I cannot agree with documentation. I think that is one of unreals strong point. I think what people mean is little community support which is where unity shines.
I love the engine, my first contact with it was amazing on Art and Design part. You can do anything using blueprints but some projects and systems you will notice that c++ is a better call for it and thats an issue for me. For someone used to the fast iterations you get on unity C#, intellisense on C++ is no way as fast as it is on unity C# and compiling C++ unreal projects can be very tedious and slow and sometimes even requiring you to restart the engine what makes the whole process slower.I would stick to Unity for rpg games with deep systems where you would want to code it instead of using blueprints and go for Unreal if game mechanics are some how simpler or covered by the innate templates. Its way easier and faster to get great visual on unreal engine especially if you got some 3d art background.
I've put in hundreds of hours trying to learn UE5, but the platform is just complete garbage. It doesn't work at all. I reluctantly had to give up on it and start using another platform. Safe to say the devs at Epic Games are epic f6ckups!
Character animations are a nightmare.. every time you make a change it breaks everything else.. the spline road system broke everything.. the grass system broke all the time.. everything was breaking all the time..
Game engines are typically great for those who have experience more than 7 years in game industry it’s not for those who are just started from scratch well good luck it will take couple years to overcome
I'm a 3d modeler who's trying to make my own project to learn something new. And yes, Unreal documentation sucks. Thank God, we have forums and TH-cam. But it's Adobe that annoys me at the moment. I do use Substance Designer a lot so I use their plugin. And still no Update for 5.2. Adobe, I do need good old displacement maps at leas for bricks on my walls. By the way, blueprints are really great and handy feature. though I'm looking at C++ from time to time. I learned java at Uni, so progamming is kinda familiar to me.
Every time I see an article that's like look at what this person did in unreal 5, it's just the started mannequin with some generic animations thrown in. Because the skeleton system can be a nightmare.. trying to put another character in the game is hard ans you pretty much have to start all over from scratch and program every single thing for each character if it has a different skeleton. That can take weeks. Even if you already did it before. You have to do it again.
That is why nobody is doing that. You have to work in a modular way to benefit from ue which means, first, create a base class and work on that as you go.
@@furkannarin2844 I've tried that and it won't work. Unless it's the same models made for the same skeleton. Switching it out breaks everything and it will even break all your animations. It doesn't make any sense but if you switch a skeleton in a copied base class it will wreck everything in the original base class. It's weird.
@@thothheartmaat2833 I agree here. And he did mention this a bit, because I solved this by learning to Rig in Blender. It’s an easy fix with GRT or Mixamo but yeah it can be layered heavy with the extra learning
Iam compiling an presentation on using Unreal engine for the company iam working right now, this helped a lot! I hope i can convince them to start working with Unreal but keeping in mind the drawbacks.
The newer case studies for UE are that Adidas prop hunt and currently the one exploded in popularity Farlight 84.. I think what exploded in popularity for Unity was mostly pixel games like Flappy Bird and Deadcells. So based from actual successes it mostly depends on graphics, Yes UE can do pixel games, but can anyone mention any pixel games that exploded in popularity and is made in UE? Yes both can do "everything" but one is a chance, two is a coincidence, three is a pattern. There are much more hardcore devs out there, I think we should follow the success patterns.
As a 10+ year Unity pro who is skilled at basically every aspect of game design, I'd love to get into Unreal but its interface is an absolute unmitigated nightmare for someone who hasn't already been fighting through it for years. There's just so much crap on the screen that I don't know why I need it up or what it's for, whereas everything in the default Unity UI is stuff I always use in every project. I feel like using Unreal is like using Blender before the UI redesign. It's just nothing but pain and suffering. Weird ugly panels full of garbage bolted onto/inside of other unwieldy panels, weird naming conventions, etc. Even just setting up a blueprint seems like a lot of fighting with the UI. I'd rather just write code in Unity as I always have than try using a node-based script that I can barely figure out how to work. At the end of the day, besides, there's nothing stopping anyone from making a AAA game in Unity. So, it's not a huge loss that I can't seem to deal with Unreal, though it's a bummer because I've been interested, and certainly some of the UE5 features seem neat.
This is a good point! I think building a game really requires use to know what at truly want out of the game and have the ability to pick various technologies from various game engines and build those technologies for our specific games, so really ...reverse engineering certain technologies like Nanite, and Lumen so we can use it in our custom game engine.
"You just gotta make a mess. And make a prettier mess every time, until one day you're like 'Oh, this isn't a mess anymore.'" That is such a good way to put it!
When I tried it, tutorials on TH-cam were like 4 hours long and tedious. The engine throws tons at you before you even know what you need for your goals. It doesn't make compositional design easy to do. Blueprints are easy but learn little about game dev and algorithms... but then their c++ docs kind've suck compared to unity c# docs because unity give examples. Plus c# is easy and I don't need the performance of c++ to bother adding that complexity. Unity only falls hard if you making a AAA game or something that requires huge scaling, but 90% of indie devs don't need or tap into c++ so use blueprints which becomes spaghetti some times.
im struggling a lot and i dont know where to start to turn the blueprints in my project to c++ because teacher asked us to implement a few things such as data table, actor components, behavior tree and then for the last exam turn everything from BP to c++ lol e_e. Im gonna bleed a few months im sure of it. But since im artist ill learn another 3d software instead i hate coding.
Oh well Unreal has started to give abit more Informations about it to the folks but i dont think they will make everything clear for everyone. They are Industry focused so wouldnt make pretty much sense for them
To be honest unreal engine 4 is significantly better for beginner developers because the UI isn't as complicated as ue5's. I also agree about the part where there's way too many different editors, components that do the exact same thing, and code things that are super helpful but impossible to know about without someone else telling you about it or a miracle happens.
Sounds like a preference thing. UE is my first game engine experience. Yes it has a lot of features, you just need to know what you want to do with what the engine provides. Biggest issue with UE is instability; it crashes a LOT!
I think one of the reasons why people quit Unreal Engine or as a matter of fact, any other thing in life is INTEREST. I was so interested in learning Unreal so much so that I breezed through all the quirks and inadequacies in the engine. It is not a perfect engine nor is it the easiest to learn but with interest comes consistency and with consistency comes results.
My main problem with Unreal is blueprints. For some asinine reason they decided to make them binary files which makes collaboration with source control an unnecessary hassle. I do everything I can in C++ and just use blueprints for gui and particles for this reason. Also I find it impossible to organize blueprints without it looking like spaghetti, where I do not struggle the same with code.
I feel the information point you made. I'm not a programmer and I'm only new to Unreal and everytime I get stuck, I gotta figure it out on my own cause there is barely any documentation out there. Sometimes it feels like I'm not going to be able to achieve my goal because I'm going to get stuck on one thing and will never be able to figure it out...
I am learning unreal 5 cause i want to make more complex games, but at the same time unity is kinda great for 2d games especially with its new input system, that new input system really has me in love with it. The only thing I am concerned about with unreal is assets.
Yeah, documentation. That's my biggest gripe. I've been using unity for about 10 years, and... When I started trying unreal, i found out that the documentation is... unreal XD Its approach to everything seemed to be basically "it's easy, you just click this button", except that button is hidden in the third tab of the fourth item of the fifth submenu of a dropdown button next to the item on a sixth line of the property window of a specific component on the actor... and nobody tells you that. nobody tells you that PATH, they just tell you "oh, it's a button with this name". And it's not just documentation, I've noticed that community advice has a very similar problem. It's like just because there's a button or menu item for almost everything, that means that it's easy and obvious, and you don't have to tell people where to find stuff, just informing them that it's PRESENT somewhere there is enough. Oh, and my friend who's been working with unreal professionally for the past 10 years (including actual c++ programming in it) totally agrees with me on this point. It's probably the only point we both agree on in our engine debates =D
A lot of good points there but i believe everything comes down to dedication and effort user puts. I pick up UE5 for cinematics, lightning and animations so i can make shirt movies and showcases. Im not interested to make a game but ...: BluePrints for animations so i can us characters in my movies. Niagara, sequencer, a nimations, materials and blueprints. All related to cinematography and making locations and sets for recording its on my list to learn. Knowlage of Photoshop, premiere, Davinci, blender that's something necessary in my opinion to go along for my purpose. I just make small projects and just learn on the go if i stuck then google, reddit and YT are my friends. So far im really enjoying UE5 but i had my fair share of frustration and demotivation. My advice just concentrate on what you need and then expand.
@@WoodyDevs anther thing on my list in near future is Reality Capture but i dont understand there's pricing model exactly. Foe 10 or 20$ you get scan points ?! What i need to know how many scans can average Joe do with one of this plans scanning typical stuff around like hydrants bench in park or statues. Once i will get idea what im paying for ill jump in to it as well.
Unreal is great for art related things but it's a pain to work for programmers and c++ coders. Api is not documented, has wired structure and long compilation times once project grows in size.
Great stuff man I dug the video. I am really looking forward to checking out ue5 but still working on my current game in ue4, soon though I will get to check it out. I am looking forward to it.
The most difficult thing in unreal is learning blueprints . As if you are not from programming field. TH-cam provides everything you want , but its really hard to understand as a beginner becoz they just do it without telling in a understandable way . Unreal official youtube channel provides many tutorials but in a showoff way , not like a true tutorial. But overall you have to understand by your own by giving time in it.
@@marcapouli7805 What you are saying have no sense. BP are just graphic C++, it's exactly the same thing. If you don't understand C++, I can tell you that you are not understanding what you are doing in BP too. You need to start with the start, programming basics, C++ basics. It's pretty normal to not understand it just "like this".
@@AliziaKaline I've tried also python, css, java, html, and c# and I came to the conclusion scripted languages are not for me, and i don't like it anyway. With BP, I can easily create a variable, a function, access almost anything I want and create anything I want. Maybe you are right I don't understand anything but when I take a forward vector and multiply it by something, I don't need to understand all the non sense c++ hiding under. An other thing I've noticed. 9/10 c++ users I've talked to think they are superior, bashing BP users, it is elite they understand everything while other are just stupid people. I would fear to become a morron myself if by miracle I'd understand c++
The documentation was great during UDK / UE3 times. But now they just had too many updates recently and with all these new tools the documentation is just not enough.
So my learning experience, has been watch a 5-6 hour tutorial on TH-cam, day 1 I learned texture and material mapping, day 2 the difference between baked lighting and lumen and how lighting works, day 3 was landscapes and mesh stuff, day 4 was me let loose building a world map from scratch, I'm not done yet I'm taking my sweet time detailing the world pretty much letting my imagination run wild, letting the props and environment tell a story, but when I wanted to add a lake I had to take a whole lay just to learn how the water plugin works and how to set it up. My goal is to just slowly develop this world, flesh it out, then start implementing gameplay mechanics and stuff My road map right now is world environment, then character design, then implementing crouching, simple actions. Item pick up and all that jazz, but it's been a long time since I've found a passion for something and I think development is it, I can't draw for shit so, this is letting my imagination free 😁
I started using unreal and love it, but I have been using it for a few weeks anyway especially after using unity for years.. You are right about trying and failing. I initially tried to learn unreal last year but gave up since it was too overwhelming to learn a new engine (especially after knowing how to use unity so well) I gave up. Then a few months later I spent a week simply following tutorials it was a real struggle so I actually gave up again. A few weeks later I tried again, and this time it was obviously significantly easier to follow (the same tutorials again), whereas before i had to struggle to get these tutorials now I would speed through them. I guess it would be even harder for someone new to gamedev, I do think having breaks in-between failures giving it a chance to reset without completely losing the knowledge is a good idea.
What really has been gate keeping for me is the amount of game architect technical directors that has told me not to bother with UE, every single one of them told me they are development unfriendly.
When you are unable to find help from the forums or documentation, try finding a live stream or video(from the Unreal Engine channel) about the general topic you are stuck on. As for me, the live streams have been a really great help, moreso than the vast majority of tutorials.
You need to set a goal. Have a clue on what it is you want to do. Coming from a vfx background and going into UE5 is great because it helps that you know the process of a production and what to look for. At the end of the day, its a tool for you to create. You only need to learn what you need, honestly there's too much and they're always adding on to it. You definitely need a blueprint before you actually start creating. That way you don't lose track of where you're going in your project. Create a story first, then think of a look you want to go for. Add on to that with your base locomotion because that's what the players going to be playing 24/7. Everything else after is up to your imagination really. Good luck everyone!
I got back to ue4 because ue5 always crashes on windows 11 ( i know, i know..-.-) so for every project i have to change from DirectX12 to 11 and every couple mins it still crashing :(
The SAVE/LOAD game system for me was/is by far the most frustrating hurdle to overcome in both unity and unreal. i still have no idea why both companies avoid this feature which happens to be a necessary feature for practically every decent game since the 1980s every project ive given up on, it was the save system that caused it all to fall apart
Where to start? You responded yourself: what do you want to do? Too many tools? UE5 is very straight forward from the beginning, even intuitive. UE5 is a tool, like all engines are. Use the one that fits with your project.
As a game designer I really like UE, it gives me possibility to make game on my own without programmers and without necessary to learn any programming language. This the huge pro of UE. Tools helps to make game faster/easier/better - there is no real competition between UE and other engines.
The unreal slackers discord helps me a lot for the bad documentation there are so many experienced helpful people. I don't know how people leran UE without a support discord
The blueprint video I mentioned here is live: th-cam.com/video/ygowvzFmkGA/w-d-xo.html check it out
Sheeesh
Thanks bro 😎 lots of blessings and love to you and your family 🙏😇
Unreal has some issues with its Blueprints.I cannot put my game all into the engine as I want to because the engine is unstable, and
crashes often. Because UE 5 does not support the Gtx Geforce 2070 card and warns of issues when you start up the engine....The engine also suffers from an irregular heartbeat and does not sync up consistently with its own timing. So it suffers from timing changes. Even crashes after a while when having nothing in the engine in a new blank project it still tends to crash after a few hours of leaving it idle. Everything is also put all into one big massive cache file so I can't load the game in modules as everything is all put into one big container.. fiile so I see it being Suitable for building small to medium sized projects. But not large projects if you not got lots of storage space for all the thousands of raw files needed that the editor loads in which can go up into a hundred or more gigs. and my game is a large project.
Was a little dismayed when downloading one of those meta human rigs from bridge only to find the meta human took up 1.6 gigs up
of file space and had over 700 asset files to the rig itself. I have over 300 npc characters in my game because my game is on different worlds, so meta humans was not going to work. 700 x 300 - 210 thousand files, Hmm I don't think so. Just to do one hundred 1028 x 1028 head textures takes up abt 200 megs of space.. When I downloaded just one of those 8k res textures, it took of nearly 400 megs up of space.
Unreal also adds in alot of extra files.
Hey woody! Would you be interested in having the lighting and post process setup redone for your avatar scene? I can create various suggestive scenarios with your scene and you will be able to use them at your discretion, also some nice character lighting setup on top of that.
Let me know :)
i just got it and this is prob fixed in updated versions but crashing trying to do anything... lol, i didn't want to do all the sign up bs so got it alternatively... they had go here click download ez mode, wasn't broken, DO NOT FIX IT.
You don't pick up unreal to "Learn Unreal", no single person can learn Unreal. You learn how to make A GAME on unreal. Just decide what game you want to make, find out what you need to learn, implement each lesson as you go. Don't worry if you need to restart the game from scratch a few times. That's game dev. Your game needs a solid foundation and you're in the process of learning to make them.
Thank God I'm making cinematics and not games.
Absolutely! Have a core concept, figure out how it works, and learn what you need to make it work. I want to make a flight sim, with unique aerodynamic dogfighting. It's an idea I've had for a very long time and it's pretty well thought out. Most of my "dev" work is figuring out what I need to build something, not actually building it haha. Once I learn, the work itself comes easy. The key is to break big ideas down into smaller chunks. Figure out a chunk, and if that chunk turns out to be too big, break it down again. This makes progress possible, and even the smallest steps are still steps forward. It just takes time.
I learned Unreal.
@@NickRomick I’ve restarted my games like 20 times because when I was starting out I had so many ideas and I couldn’t make up my mind and sometimes I would mess animations up and it would be too far gone lol
@@KayoWR I know that feeling! My game is starting to pick up a lot of media attention now, so I must be doing something right! :)
The reason I quit UE in favor of unity (and in future, if they add some decent terrain tools, maybe Godot) is mainly for 3 reasons:
1) First and foremost un utterly long compilation times. If you use nanite, lumen and all the goodies, compilation can take DAYS. With a (good) laptop, I can't afford that.
2) C++: I already know some C++, however, compared to C# it needs way more care and it's difficult to master the huge UE library without someone pointing you in the right direction. C# is way more solo dev friendly.
3) Resources: if you use the latest technologies, you'll need a extremely powerful machine to run your dev environment without frustration.
Overall, even if UE gives you a ton of amazing stuff, as a solo developer I'll never be able to unleash it's full potential, and will probably end up developing a game that can be done in Unity way faster.
I spent some time with godot, too. But it is just not there yet. Not for games requiring huge maps like the ones I love. So I'm sticking to Unity for now.
That being said, I still have UE (4) installed, because I port assets (often free) from UE to unity.
The truth is, you have to just spend the time. Try things until it works. It can be super frustrating to follow a tutorial to the letter and it doesnt work. And nothing you try works. That is why you have to learn the basics and then just make things on your own. When you start thinking through what you want to do, implementing and then having it work, it is like hitting a hole in one in golf. But the work you will have to do to get to that point is crazy. When you get super stuck, take time away and think about it from time to time. That helps me. Coming at it fresh.
then u find out that u need pre-experience u gained from working in a game studio or you wont be able to do anything in ue because not enough educational material online. unity has much more educational material online. unity wins for normal people.
@@bestboy007I don't agree with this I think both can be used for "normal people". I think the difference is unity will have a lot of 2d games while people see unreals potential and they all of a sudden want to make a 3d RPG with a billion features. You can learn just as well from both and yes unity has more educational material because of the community and partially because of how it's been for a long time....but that doesn't mean it's much "harder" to learn unreal either.
I feel like I disagree with evrything you said. I switched from Unity to Ue5 and I can say that I am glad I did that.
I had way better results way faster and everything wad way more stable without random buggs coming from some where. And that Blueprint system was for me personally very easy to grasp.
Still some people might be overwhelmed or have a harder time learning Ue5 which I can understand too
Agreed. Used to work with a global arch viz firm who was always into innovation and pushed us to innovate and find the best. We were one of the first to implement VR, AR, photogrammetry and AI into the design pipeline (does anyone remember Blenders game engine?). Looked into Unity, UE and Godot and a lot of other realtime tech. Personally, what I love about UE is the visual scripting. I'm more of an artist than a coder, so for me I was able to program using BP in UE is so awesome in the sense that as long as you know your stuff, it fits so perfectly.
Right like how do you get confused by blueprints unless you have zero engineering logic skills. It’s simple flow. And literally ALL blueprints are fundamentally the same, they just are used differently. Animation blueprints are the same as actors blueprints, it’s basically just the parent classes that matter.
You disagree reason 4 !!? Are you sure about this I'm using unreal engine never touched unity but really I'm struggling with finding tutorials for certain things
Same. I gave up on Unity like 8 years ago.
@@A_Train The BGE was ridiculous lol. I kinda miss it but I get why it was trimmed.
Unreal Engine is made for AAA in mind where you have dedicated people for a job and can focus on only one tool to master it. Also UE has limited access to learning resources or non existing for certain fetaures. There are also problem with UE API, its embeeded itnto an engine and needs to work with certain workflow so if you working on something outside of scope of engine and is non standard FPS, TPS or other generic game it makes things difficult. For example i am working on space sim game and physics and extending editor for new tools is tricky and almost non documented. This is required for my game to create planet rendering tech , i will love to do that with unreal, i know it is possible but requires soo much digging that will take more time than it should and i can already do that with Unity.
So in what way is UE designed with AAA in mind?
@@SVAFnemesis Unreal Engine is developed with the intention of providing all the tools required to develope a game to the quality and standard of a AAA studio title.
It supports some of the best graphics I have seen across engines (if that matters to you and if not you can simlify with sacrificing any preformance). It offers the vbersitility to accomplish just about anything you set your mind too, especially with the blueprint system. Granted, the blueprint system does have limitations that can hold it back in comparison to code and if you wanted to, you can use C++ in tangent with UE to fix those limitations. Not everyone is going to want to learn C++ though and the nice part about blueprints is that all you really need to learn is some basic programing logic terms and that is it.
You can no model and adjust models within UE (a feature new with UE5). You can import models and animations with relitive ease. The list goes on. UE is built with the goal to give solo and indi developers the same range of potential as a AAA studio without having to go through the nuance effort of building an engine from scratch, learning to code, and relying on a dozzen third party programs to support the development.
Where I believe the OP is having their actual issue is in that UE was originally designed as a FPS/TPS engine. Prior to 4.0, the engine didn't really support anything else all that well whichy is why the engine didn't start to boost in popularity until we got into the 4.0 period (as far as I am aware. I am sure someone more educated on the history of UE could correct any errors I made here). All that said and one, the problem with UE is that most other genres are new. It was built for shooters and now that is supports more than just chooters, it has been a slow gradual community effort to showcase its newer potential. Granted, 4.0+ (as far as I know) is what introduced the concept of UE being used for more than just shooters and while that is still several years old, its still considered new support.
What I can say to that though is that the community for UE has been incredable. I am on three discord channels for UE, two of which are community made and all of them have been absolutly amazing tools to learn UE. I can see some people being put off over the commen attitude of "here is some advise, but you need to try it to learn it" method. (Literally, no one is going to spoon feed you answers), but their help and advise has been incredable to me. In addition to Discord, there is the UE Redit group that is arguably equally helpful and very resourceful and there are a few select TH-cam channels that are great follows for new devs. Unreal Sensi and Vertus Hub being the two I would immideatly recromend.
Going to be brutally honest, based on what I have expiearienced, it sounds an a lot like the OPs problem is simply being lazy.
I am going to stand very hard against a lot of what you have said here mate. Please do forgive me as this is going to sound harsh but I do stress I do not mean it as an attack against you or an attempt to start a fight. Based on what you have said, I have two comments to make here.
1. Unreal Engines support of genres outside of the shooter range is still, despite being available for years, new. It is very young in its ability to branch out and you are not alone in feeling the flack for it. Does that mean the engine is incapable? Absolutly not. Unreal Engine is at a point now that you are nearly limitless in what you can do with it. I would say though, that if a physics engine is what you need, either you will need to modify Unreal Engine itself (source code is open to the public) or loom for a dedicated physics engine. However, I strongly stand by in my belief that UE is at a point where even a physics system will come into play in due time and it won't continue to be a problem.
2. This is where this is going to sound harsh, but the impresion I get is that you just arn't making the effort to get the answers you need. And I am not talking about googling for tutorials or other devs posting tests of concepts and such. I mean getting online for a few hours, engrosing yourself in the UE community and asking for help, sharing your problems, collecting feedback about how things could be done or could be done better, and puitting the time in. iAs I said in point 1, UEs support for games outsisde shooters is new. There are a lot of genres it can support now and the community has been chipping away at revealing that potential day by day. Given time, presistance, and connecting with people willing to help you test those boundries is going to be probably be your best choice if you stick with Unreal Engine.
However, I am a little more confused on why you bothered with UE if you could make it work in Unity? Was there something about UE specuifically that has enticed you to switch? If you can make the game in Unity with less problems, make it in Unity. If that is where your skills are strongest, I would keep your primary work in Unity and just explore UE until you get to a point that you feel you can transision fully, if that is your intention. Otherwise, what you want is simply going to take several years to get as the community keeps hacking away at testing the limits of the engine. I know three good Discord groups worth joining for help. Reddit is a good source too. Vertus Hub and Unreal Sensi are also worth the investment for beginners. I will had it to you, Vertus does not have a great track record with compleing tutorials, but part of that has simply been that he has a full time commitment to a project and UE updates faster than he produces. Currently. But in all of this I strongly suggest being more agressive and reaching out to the UE community. I know some of the Discord groups are slow to respond, but you arn't being ignored and if someone can't help, chances are they know someone who can.
Unreal also has its own forums page you can post questions on and get further assistance.
Not and have it look as good tbh.
@@christopherpoet458 I'm hoping to see more AAA made with UE, as for as I know, Unity has acounted for more major production so far. (I'm avoiding the word AAA since it has never been defined in game industry)
My reason is that it crashes so often for no reason all the time, even when doing nothing
I love Unreal 5, it was a steep sharp end of the hockey stick learning curve, but now I’m feeling past the initial curve and just love it. It was definitely worth pursuing. Woody your mess analogy was great in describing this. Don’t be afraid to fail and make a mess. The message is in your mess people.
In terms of performance targets how possible would you say it is to get games to hit 60 fps on a ps5? Playing ue4 games like Spyro for them to run at a horribly framepaced refresh rate really made me dislike ue4 titles. I just want to know if that will be an issue this gen too
In terms of performance targets how possible would you say it is to get games to hit 60 fps on a ps5? Playing ue4 games like Spyro for them to run at a horribly framepaced refresh rate really made me dislike ue4 titles. I just want to know if that will be an issue this gen too
@@Cfreezy12 Did you play spyro on PC or Ps4 and if you played on PC what specs you have,because i sure didnt have any bad frame pace playing that game on mediocre PC,also engine by itself doesnt do mirracles devs can fuck up by doing stuff that is not recomended or take time to optimize game etc,there is many variables.
How many hours until you hit that steep end of the hockeystick?
I wrote an AI script that was so terrible i wanted to cry. Then I watched a tutorial on unreal on behavior trees, blackboards etc and was rewrote it to be much better
My biggest issue with UE5 is “compiling 8206 shaders………”, TWICE EVERY TIME!
Move object 1 inch it's start again
@@vikramthewrench True xD I feel your pain
not you biggest issue with ue5, it has been the biggest issue with unreal engine in almost a decade
But Tbh, with a good CPU it only takes 2 Minutes max. So for me it is not a problem :D
@@BlackwoodHDEnglish thank you, what CPU do you have? It's hard to imagine the CPU can cause the difference between a few minutes to a few hours. Thanks.
Honestly, the thing that's helped me stick it out is that most of the C or C++ libraries I've used or written in the past tend to just work in Unreal. It took a bit of adjustment to get used to UE's build system, though.
Try bp unreal with native code, unreal in visual scripting is most easiest unreal try unity with ai and just collect the errors try animation state there try alot of things it need along time for practice. I start make games with unreal in two weeks this unity with them component is really confusing .
Any insights or resources you found to help ease that transition from C/C++ into Unreal C++ and the build pipeline? Im in a similar position in that I am a C++/C# programmer and am just running from one confusing situation (and crash) into another.
@@wopsieneter As far as the build pipeline is concerned, you can find a pretty decent, simple starting point with reub's video titled "Learn this before C++ - Unreal Engine Build Tool Guide." He's also got an overview of plugins.
Now, as far as getting started making a project in Unreal using C++, if you have an idea of the sort of project you're looking to make, I'll do my best to point you in the right direction. I've found that following along with someone making a small- to medium-sized project has tended to clear up my doubts about the quirks of using C++ in Unreal and also the limitations of the Unreal Header Tool. (For example, a couple that stumped me for a while were not being able to put classes with the UCLASS() annotation inside of namespaces, as well as not realizing that modules and plugins are linked dynamically rather than statically.)
I'd also recommend joining the Unreal Slackers server on Discord. I've found the answers to a lot of my more bizarre questions there, either by searching the chat history or asking the question myself.
Let me know.
Cheers!
@@littledemo3605 You should NOT use BP for most of your code, its messy, and its slower... you should be using more C++.... then BP.... Drives me crazy when people are taught this bad behavior, and this is why so many games are badly coded and run terrible....
@@recon5107 it's not really that slower, there's definitely overhead but rewriting your codebase to save 5 milliseconds isn't going to give you....great results, and you're generally not making a low-spec game with unreal anyway
that's not to say that performance isn't an issue, it's just that switching most of your code from BP to cpp brainlessly won't fix an issue if there is one because the performance gain may be extremely minimal, that's why you use a profiler to figure out what should be written in cpp and what simply doesn't need to be or to figure out whether what you wrote simply isn't up to the task even if it works
I would also go as far as to say that that's not the reason games run terribly, they run terribly because people write crappy code, switching your entire codebase to cpp won't fix that, learning how to make better code will regardless of what you're writing it with
The discussion about speed does matter if you're comparing something like python to cpp, but there's countless of videos that compare bp and cpp code and their compilation output and while bp is definitely slower, it's usually not slow enough to make an actual impact. In an ideal world maybe saving those 5 milliseconds should be sought after, but people usually don't have that luxury be it due to time constraints or some other reason such as them LEARNING how to develop games...
Just started learning Unreal a week ago and I’m hooked. I picked it up pretty quick and achieved results that were unimaginable in other 3D software. BUT, I’ve been working as a VFX artist for years. And even before that have 5+ years of animation and 3D education. That said…don’t get discouraged! Sh*t took me literally 7+ years of beating my head into a wall wondering why things don’t work in order to start getting results I like. The VFX/game dev/animation pipelines are HUGE. Thousands of people huge actually. SO, take your time, work on smaller projects first, or even start with one job in the pipeline like 3D modeling or something. Once you get comfortable with that, then move forward. You’ll get there…I’m rooting for you all!
I just can not grab my head around it just to create movies. like what i need to learn? Do i need blueprints for it? why does it create blueprint when i import a character or metahuman.... its all so confusing.
Dont trust him.
After 1 week you knowledge in UE = 0, after 2 week you level in UE = 0, after 3 week you level in UE = 0, only after few months ago you knowledge in UE = basical nub level.
For typical use, much easy and fastly use Unity, i think Unity 2019 was really good solution for indie projects. (new versions a slowly)
But for nice look 3D, UE really better.
@@ailanezz
Dude, for basic newbie level in UE you need learn it few months, ofcouse you need blueprints, ofcouse you need learn also C++ if you dont know it. Just do something every time, and you make progress your skill.
@@DimitryArsenev Just save the knowledge as gifs, and if u forgot how to do something, just look at your gifs.
A real VFX artist can import camera tracking 😂 unreal is garbage
The main reason is because people nowadays are unable to create their own assets. Just like unity it's a bunch of kids downloading stuff and sticking it together then calling it a game.
One thing I've noticed is an extremely complex task can be done in maybe 10 blueprint nodes. And sometimes something that should take maybe 2 lines of code can also take 10 blueprint nodes to implement 🙃
This is only true if you don't create your own node with these 2 lines of code... :D
what I do is make a .gif of what node combo does what, so next time it will take 10~15 seconds, by just following what the gif shows on another screen.
Thats... linear complexity and its good.
I'm UE fan btw
some things can be easier in c++ so nothing stops you from using both. If you use unity you'll need to learn c#, needing to learn c++ isn't the end of the world
The reason I quit Unreal Engine is that the editor is extremely unstable in Linux -- crashes every 10 minutes or so. Even an unmodified project template left open while stepping away to attend to something else will have crashed and be frozen when you come back.
The Unity editor has a few problems in Linux (mostly with the way pop-ups and progress bars are rendered) but at least it works. Unreal Engine doesn't look that hard, and it looks like it would make somethings easier (other less so), but I need something that works.
Thanks for this, been struggling with this engine but have been determined to keep going with it, my ADD keeps me learning new stuff but never in sequence and never unison with other skills... which is something I know I have to keep working on. This video was actually encouraging knowing I'm not alone in being a bit lost with what I'm doing with not as much resources available as I first expected.
Same, ADD here too, I will try to save you suffering and suggest you to follow a tutorial series for like an rpg or an fps and expand with your own things along the way. Itll be easiet
Not a professional but what helped me was getting on ADD medication. My life has improved soooo much and I have a wife and kids so even with a lot going on it has helped immensely. I’m learning unreal engine and Houdini right now
@@joshcruzmadeit as a professional myself we did not have you tube or any one helping us, so trial and error is the best way to learn, take your time and learn... failure is going to happen, and will only make you better... Alot of you tubers teach people BAD habits...it drives alot of us nuts, when we see it at the studio from new developers.... if you do this for fun, sure watch videos, but don't depend on them, many of them will steer you in the wrong direction but there are some good ones...
@@recon5107 Yes I have found I actually remember things better when doing it without tutorials. I mean I follow along but end up experimenting a lot and doing my own thing. Documentation helps of course. I get tired of tutorial hell quickly you know?. Could you name a good channel perhaps?
Wow, perfect description of my ADD
I'm learning UE on my own, but currently developing games on Unity.
Each has its own learning curve, so anyone wanting to make anything substantial and meaningful, must put in the time and effort to learn the tools.
UE is really great for artists wanting to quickly showcase their work (thanks to all the default templates), and friendly for less programming-savvy folk with Blueprints.
Unity is very good for programmers since C# is arguably easier and more modern than C++, requires a much smaller storage/install footprint and has lots of tutorials.
You can ultimately build identical games in either engine (there's a video a game dev did doing exactly that), so its really a matter of preference.
I also has the same thought. I'm really interested UE5 but C++ is pain. As a programmer, I like C# more. I don't like visual scripting like Blueprint and Bolt either. At some point, I have the plan to learn UE5.
@@w1-w2-w3 If C++ is a pain, try Godot. It's very clean, and IMHO it's the best fit for an indie developper.
@@OlivierPons haha just wanted to promote Godot too
@@jumpsneak I have made and published my own game thanks to Unity. As far as I can remember there was no pleasure at all. From the beginning until the end. Not to mention the random crash when I generate my apk. Yes, random: clean cache, restart and recompile: 19mn 32s each time. With Godot every problem I have had so far was my fault. It's so much better. Yes you are right: I have been really disappointed by Unity and after 3 years I have decided to give up. Go for Godot!
And I think what decided me to not cone back is the speed. Instant launch and when I generated the exe for Windows it was so fast I thought it didn't work! Lol
This is some good advice! Because a lot of systems in Unreal touch other systems, I was afraid to set things up wrong, but the cool thing is that if you set up things ‘wrong’ it doesn’t matter because things are flexible enough so that your way will work. I definitely brute force stuff: blueprints makes it pretty easy and fast to try out lots of different methods quickly.
I don’t even remember learning Unreal Engine. It was almost like I just woke up one day knowing everything about it. I guess it was just a hardcore ADHD hyperfocus month that got me to where I am.
@@NickRomickUnreal is love, unreal is life.
@@Megasteakman This is soooo true, Kial!
As someone that's not a programmer at all (Actor, creator), but knows basic things, I wanted to quit several times, it's so frustrating for everything, but then I see all the possibilities regarding filmmaking, makes me continuing wanting to learn. So let's just keep being strong.
Funny. As someone who IS a programmer I HATE unreal. Because almost none of it involves programming.if you approach it from trying to do most things in code you are going to have a bad time
My work has given me one instruction: learn to use UE5. we have VR projects coming up which will involve lots of back end programming, so my focus is blueprint and C++. I did a crash course in C++ and it REALLY helped with the understanding of Blueprint. I'm still very much a beginner, but I can make things happen in UE5 now lol.
Out of curiousity, what course?
Yeah what course?
A lot of people make this mistake, with the Epic's blessing... No, you can't use Blueprint without learn C++. BP is just graphic C++. Learn C++ first, you will really understand what you are doing in BP after ;)
@@AliziaKaline I learned C++ with Blueprints so :-?
Dat intro!!! This was relatable! My BP started getting bulky and It started making me feel anxious. There aren’t a lot of content or doc on how to optimize bp or a level. So it feels really messy right now and makes me anxious if it’s ok to just keep adding things on top of it 😣
Maybe it’s not for you :(
Wat? lol
I feel like node based scripting is very sensitive to having a proper structure. In other words if you just throw things together, it becomes hard to read much quicker compared to regular code.
To clean up a blueprint, you have to look for sections that have an enclosed functionality and pack them into functions, then use these functions instead of your original code to make things look cleaner. Alternatively you can assume what generic functionality you will need to do your thing and make functions for that ahead of time (and also test them) before working on the main script.
These are really just programming fundamentals so maybe you should look for that instead.
Have to tried using comments and Macros? They can help reduce and organize nodes in your Event Graphs
@@2tired2sleep2 yes! I started doing this more as I am learning & getting deeper into using Blueprints! Thank you for the tips ❤️
DONT WATCH TOO MANY TUTORIALS! You won't remember it anyway
Do small little projects like he said.
That’s actually great advice. To be honest, I haven’t released any finished projects in any type of game engine but I’ve gotten really close. Usually it was for one roadblock or another and I just got bored and wanted something new, but I’ve learned a huge amount from those failures and unfinished projects. I’ve spent most of my time in gamedev using UE4, but my biggest problem with it is that it’s just too much. Everything gets thrown at you all at once. It doesn’t help that, as you mentioned, there’s very little in the way of good documentation and that creates so many roadblocks, especially just jumping into it when you’re still getting used to the editor and the way it likes things being done. TH-cam tutorials can only get you so far. That’s why I recently switched over to Godot (honestly don’t know why I didn’t start there). But that knowledge I gained from when I failed still sticks with me and helps me out when I get stuck or encounter problems outside of unreal.
Yeah, for me Unreal Engine is basically a game that I rarely close
one thing that is usefull for me, is write blueprints and their function in a word file for example how to switch a light, then when i need to use it, i remember this blueprint. Unity is more ez, but i think that if you are an 3d artist and do you love create assets, unreal is your engine.
Number 1 for me (and the only reason why I'm still using Unity/Godot and why Unity is still in the first place as a game engine on Steam) - is the lack of user-friendly language support.
Blueprints are meh for me, I mean they are great for tweaking but making a core logic of your game in blueprints is probably not the best idea ever, starting from performance and ending on spaghetti. I really wish Unreal has some user-friendly language support like c# or maybe some of their own Python-like language or something.
And yes... UE is getting just too big and overwhelming for a single dev, and Unity or Godot is more usable - but it's just only me. Not to mention that my laptop is dying using UE5.
@@leeoiou7295 C++ and C# are NOT similar. If you think that, you're definitely at the start.
That being said, if you do have programming experience, then yes, it feels quite easy doing things in C++/Unreal Engine.
Once you do pure C++ though, you'll learn how big of a difference C# and C++ have.
C# is in fact more similar to Java than C++.
@@leeoiou7295 Not even close... c# is way more user-friendly.
@@leeoiou7295 I'm not trying to say C++ is hard to program in. If you already have programming experience, then I'd definitely agree that you can learn it in ~month. I also did that. My point stands though that C# is very different to C++. It's not neccessarily about the syntax, but more about the way of how things are done
@@leeoiou7295 Tell this to million devs working with Unity, Godot, or any other engine which doesn't use c++ to use with them.
You missing the point between going into the game industry and with going into software development to create engines or work for an AAA corporation making games using for example UnrealEngine. And no, c++ is not user-friendly, starting from memory management when compared to for example c#. You learned Unreal Engine and c++ in two weeks - LOL, sorry but this is B$. But hey, have fun using c++ in UE and I will have my fun using c# in Unity or Gdscript in Godot and we both will be happy.
@@tomtomkowski7653 Sorry but i have to disagree here too. It is clear that you have never used Unreal C++, or at least dived deeper into the topic. Unreal includes a lot of stuff you mentioned as a counter argument starting from Garbage Collection/Memory Management.
Native C++ is indeed more complicated than c#. I agree with that.
But the way unreal exposed all their functions, solved includes, used custom types, tons c++ macros etc... It is MUCH easier than native C++. So your argument just is not valid.
Unreal's C++ is basically the same as Unity's C#. The syntax is different and it's a bit annoying that you have header and cpp files. But this can all be solved and simplified with IDE Plugins.
Of cause you can do fancy pointer math if you need to. But almost every time there is a "Unity" way to do stuff. Heck, i could literally take a unity script right now and translate it 1:1 into Unreal c++, with only the function names being different.
I find it much easier to program in Unreal Engine actually, because of the Blueprint system. You create your complicated game logic in c++ and then expose nodes for your game designers to work with. This makes communication and collaboration much easier. Also Unreal has much more features implemented, resulting in an overall more powerfull framework for me to work with. In Unity you need to implement a lot of the basic stuff yourself.
If i need to do less, that is a good thing for the production pipeline.
Also there might be million devs working with unity or godot, but most of them are indie devs. Big studius prefer unreal over unity. I can name you 20 TrippleA titles without much thought that are made in unreal. But for unity the only big games that sticked were Escape From Tarkov, Life is Strange, Subnautica and a lot of mobile games. The rest is indie.
Great video! I've recently just started moving from Unity over to Unreal - really enjoying my time with Unreal, and learning Unity first (C#) has really helped when it comes to using C++
@ジャス / jasu First, learn C++, C# is just a toy and will give you very bad programming habit ;)
You can find pretty good begineer course on TH-cam or Udemy.
I've done a few games in Unity and I am working on my first UE game.
TBH I think there is a ton of info on UE but it's hard to get up and running without just jumping in and trying/failing until you build up a foundation.
Unity has good documentation but UE has these massive 1-5 hour long dev sessions where the UE devs show how to do specific things.
UE has insane 3D performance and I am enjoying it so far :)
What pc specs do u have? I'm planning on playing around with ue5, but I'm afraid my pc ain't powerful enough.
Welcome to game development.. here is the problem today.... how do you think us older developers started?? no one took us by the hand and we did NOT have you tube to take us around....We did it by failing...!!!!
@@recon5107 I too had to walk through -90 degree weather and constant drive-by shootings to get to pre-school
You forgot UE's god-awful compiling time.
Sorry, the first reason is absolutely silly, with the tonne of tutorials for all levels (just type in "unreal beginner tutorial") flooding YT.
first off, the intro was amazing and the advice was great .
Some general game dev advice:
To be a good game developer, you need to be a little unhinged. You need to just throw yourself at the problems, and even if you don't find a good solution you will be a heck of a lot closer to a good solution than if you spent 3 weeks "thinking" about it and just getting paralyzed by the problem, speaking from experience.
As a game new developer you will be much beter off not trying to map out every thing before you start. Just go until you can't, then start over and do everything better until you can't. By repeating this process you will learn much faster. Once you get past a certain point the learning curve will really start to flatten out. Once you've been here for a while there aren't that many first experiences left and only then you can start to think about optimization or refining you architecture or things of this nature.
Agreed. This is where ADHD is both a blessing and a blessing, for once 🤣
I totally agree with #4 which is why I always post a tutorial or comment if the information is scarce. Dead end searches can halt whole portions of a project and when you are your own team, that's a big deal.
BUGS ! LOTS OF BUGS ! From project files not saving, import glitches, or simple features that saves a ton of time, are just a pain in the ass ! The only reason I use UE is graphics...
I would love to find more people that can be hired to answer questions, coach, tutor, etc. Would make my experience vastly better.
Why the hell am I watching Metaverse Jesus talk about Unreal Engine at 3am?
My 5 cents on your thesis, for those who are about to jump into the magic of UE for whatever reason:
1) You don't start with Unreal. Unreal is your final destination, so to speak. One who is starting has to wrap head around concepts of storytelling in 3d world - from modeling, rigging, texturing, lightning, simulations, film language, animation, etc.
2) Too menu tools is a two-sided dagger - if you don't know what you are up to, you can easily cut yourself on the way down the rabbit hole. UE has been used (especially from v5.0 onwards) by so many folks - from game designers and programmers to architects and movie makers. You really don't need them all, not from the very beginning at least. Planning is everything - if you know whats your goal and if you can grasp a path to achieve it - don't mind the other tools in this swiss knife. Thats why I find #1 so important.
3) Is, again, totally about #1. Keep the basic understanding of concepts under the belt, find your niche (if you are into simulations, take few years/lifes to master Houdini, for example) and for the rest of the job find someone who is into sth else (movie directing or programming, respectively). Most important thing is to know what do you want!
4) I'm in love with UE community so I'll skip this one :P
5) Can't agree more - trust the process! Most of the time UE tasks are a long way paths, so your anticipation, patience and willingness to learn are ''a must have'' on this, pretty much, neverending journey.
Good luck to yall
Very inspiring channel for someone moving into UE5 for the first time. Glad I found you!
"You feel you gonna make the wrong decision at any turn"
It's valide for only 2 types of people :
- The one who dont know what they are doing
- The one who can't go out of the box and want to do everything by the book.
Informatic in general is "no limit" it's not like you can by mistake create a glitch that can burn your entire life.
In fact, all along your devs life, you have your best friend "CTRL-Z/W" to help you undo mistakes.
Too many tools is bullshit, try working with 3D for mechanical engineering companies like car industry, you will have to learn, revit, 3dx max, maya, blender, substance, pixiz, catia, rhino, freecad, cad, unreal, unity, c++, c#, python,... just because every customer you want has different tools, use different software, and you have to be flexible because you want the job. Unreal has like how many basic 10 different tabs ?
UE blueprint is still too hard to learn OR perhaps only me ...
I still Remember the first time i opened ureal engine. It was 5 years ago i believe... Ue lasted only 15minutes in my pc 😂. I was already used to unity and compared to unreal engine it looked way more clean and user friendly so i lefted unreal engine so quickly because it looked like a total mess and a waste of time. But a few days ago i decided to reinstall unreal engine because i was curious to see some of the features pf the 5th edition of this software and with some patience i learned the basics of this engine and then i realized how much potential it has. Also a cool thing about unreal engine is blueprints! I don't know how to code in C++ and also a thing that slowed me down in my developing process in unity was learning the engine library. At the contrary with blueprints you don't have to learn almost nothing and also is very intuitive to me.
It still took 2 days to code the basic movements of the first person character of my project but the next time i'll be way faster.
Number 6: constant crashes. This is why I quit Unreal.
The last time Unreal crashed (and it wasn't because my code), it was in 4.21... You need to check your installation :p
Really great video I can so relate to the documentation issue. I have found many times finding the official epic documentation page and it is just here is the node. No deeper explanation. They do have good introduction tutorials on the official channel which I have found useful. But yes far too often my search ends on an unanswered UE forum.
I used UNITY for over 10 years at work and I hated everyday of it. Once I started using unreal I never looked back it’s the easiest and most fun engine I’ve ever used as an artist.
Oddly, I found the exact opposite - but then I am a coder.
Hi I'm a beginner when it comes to unreal. I find Unity bit easier compared to Unreal. Can u share the process (and links if possible) on how you started learning unreal, since you mentioned that it's the easiest. I'm curious to learn more.
did you get a job on UE?
i agree with poor documentation , i was learning both unreal and unity, but unitys documentation is just straight and simple, and they give plenty of example too.
One thing I also understand when working in UE is that you just have to follow their process of doing things. In Unity is different where you could just create an approach that you think is right. In UE they have this game framework built into it. You just have to understand how those works and carefully plan you to fit that into your project. The learning curve is very steep but once you get past that, everything is a breeze
I also have found that alot of people give up because they come into the game engine WANTING to make a game. This means that you must learn what you need to know.
Bruh, stop, relax HAVE FUN.
PLAY with the game engine, see what you can do do on a small level and then PLAY with manipulating those small things. THATS how you learn the engine, make it a fun puzzle game. Play, figure out what works, what doesnt work, what breaks and whats cool.
Stop going into this with the "I have a tool and I must learn this tool, I must master this tool, I MUST become great at this tool!!! With out me my game engine is useless, with out my game engine I am useless, This is my game engine and their is no other game engine like mine!!!"
No. go in with the mentality "This looks interesting I wonder what happens when I use this with this."
Then when you've had your fun slowly start focusing in on what you need to do what you really want to do.
Lol, if people did this more they would find unreal engine fun and easy to use.
Instead they find it monotonous, tedious and aggravating.
It's not a school project, it's recess.
It's not reading a dictionary it's reading a harry potter series.
It's not a dcumentary, it's an avengers movie.
lol.
Great vid by the way, appreciate the time you took to make it.
I found unreal tutorials better than Unity tutorials
pls, turn down the background music.
Fantastic video! I needed to hear this. Thank you.
Awesome video! Some great advice. As a Unity dev one of my fave features is how easy it is to find documentation and answers - hopefully as time goes on Unreal will catch up!
Good video, this Unity dev hasn’t tried Unreal yet but you made it sound less intimidating. Thanks for the tips 🤙🏼
You are so unique in this platform. Hopefully I can learn this kind of art. I'm looking forward to learn animation and this kind of 3D work but I don't know where to start haha.
I might have something for you! th-cam.com/video/HjvxfCs_Mxo/w-d-xo.html
Why I hate UE after 8 years using it:
- Bad documentation as you said. You have to guess almost everything or hope that someone found and wrote the info you need somewhere online
- Bad design. Nothing is logic, most settings can be enabled/disabled in 10 different places, a setting can be moved between two updates.
- Bugs. Epic priority is adding new experimental broken features rather than fixing bugs, no matter if those features will never be production ready and will be removed in 1 or 2 years because they never fixed it.
- You spend more time trying to make the engine work, not crashing, than working on your project.
- Bad performance. Epic is always advertising about how good there rendering look but never about performance because they know their engine is worst engine in terms of optimization. That's why 99% of UE realesed games looks dated, why Epic Games biggest game Fortnite, a stylized game, and why good looking UE games have so bad quality/performance ratio.
I cannot agree with documentation. I think that is one of unreals strong point. I think what people mean is little community support which is where unity shines.
I quit unreal 😂 to Blender because it’s impossible to import third party camera tracking to unreal 😂
sick video dude
I love the engine, my first contact with it was amazing on Art and Design part. You can do anything using blueprints but some projects and systems you will notice that c++ is a better call for it and thats an issue for me. For someone used to the fast iterations you get on unity C#, intellisense on C++ is no way as fast as it is on unity C# and compiling C++ unreal projects can be very tedious and slow and sometimes even requiring you to restart the engine what makes the whole process slower.I would stick to Unity for rpg games with deep systems where you would want to code it instead of using blueprints and go for Unreal if game mechanics are some how simpler or covered by the innate templates. Its way easier and faster to get great visual on unreal engine especially if you got some 3d art background.
I've put in hundreds of hours trying to learn UE5, but the platform is just complete garbage. It doesn't work at all. I reluctantly had to give up on it and start using another platform. Safe to say the devs at Epic Games are epic f6ckups!
Character animations are a nightmare.. every time you make a change it breaks everything else.. the spline road system broke everything.. the grass system broke all the time.. everything was breaking all the time..
After ten years of Blender i'm so glad I work now in UE5 Much Better!
Game engines are typically great for those who have experience more than 7 years in game industry it’s not for those who are just started from scratch well good luck it will take couple years to overcome
Really?
@@mrgammer2.0yt85 even highly educated trained experienced developers from AAA studios it takes atleast from 6 months up to 1 year.
I'm a 3d modeler who's trying to make my own project to learn something new. And yes, Unreal documentation sucks. Thank God, we have forums and TH-cam.
But it's Adobe that annoys me at the moment. I do use Substance Designer a lot so I use their plugin. And still no Update for 5.2. Adobe, I do need good old displacement maps at leas for bricks on my walls.
By the way, blueprints are really great and handy feature. though I'm looking at C++ from time to time. I learned java at Uni, so progamming is kinda familiar to me.
Every time I see an article that's like look at what this person did in unreal 5, it's just the started mannequin with some generic animations thrown in. Because the skeleton system can be a nightmare.. trying to put another character in the game is hard ans you pretty much have to start all over from scratch and program every single thing for each character if it has a different skeleton. That can take weeks. Even if you already did it before. You have to do it again.
That is why nobody is doing that. You have to work in a modular way to benefit from ue which means, first, create a base class and work on that as you go.
@@furkannarin2844 I've tried that and it won't work. Unless it's the same models made for the same skeleton. Switching it out breaks everything and it will even break all your animations. It doesn't make any sense but if you switch a skeleton in a copied base class it will wreck everything in the original base class. It's weird.
@@thothheartmaat2833 I agree here. And he did mention this a bit, because I solved this by learning to Rig in Blender. It’s an easy fix with GRT or Mixamo but yeah it can be layered heavy with the extra learning
@@thothheartmaat2833 Trick is to just rig everything to UE skeleton
@@williamtolliver749 I never got into blender.. maybe that's possible.. there are just too many things wrong with ue5..
Man, I really needed this video. I was close to dropping unreal but maybe I'll try a little longer.
So, how's it going?
Iam compiling an presentation on using Unreal engine for the company iam working right now, this helped a lot! I hope i can convince them to start working with Unreal but keeping in mind the drawbacks.
1:00 Can you make the music louder? I can't hear it!
The newer case studies for UE are that Adidas prop hunt and currently the one exploded in popularity Farlight 84.. I think what exploded in popularity for Unity was mostly pixel games like Flappy Bird and Deadcells.
So based from actual successes it mostly depends on graphics, Yes UE can do pixel games, but can anyone mention any pixel games that exploded in popularity and is made in UE?
Yes both can do "everything" but one is a chance, two is a coincidence, three is a pattern.
There are much more hardcore devs out there, I think we should follow the success patterns.
As a 10+ year Unity pro who is skilled at basically every aspect of game design, I'd love to get into Unreal but its interface is an absolute unmitigated nightmare for someone who hasn't already been fighting through it for years. There's just so much crap on the screen that I don't know why I need it up or what it's for, whereas everything in the default Unity UI is stuff I always use in every project.
I feel like using Unreal is like using Blender before the UI redesign. It's just nothing but pain and suffering. Weird ugly panels full of garbage bolted onto/inside of other unwieldy panels, weird naming conventions, etc. Even just setting up a blueprint seems like a lot of fighting with the UI. I'd rather just write code in Unity as I always have than try using a node-based script that I can barely figure out how to work.
At the end of the day, besides, there's nothing stopping anyone from making a AAA game in Unity. So, it's not a huge loss that I can't seem to deal with Unreal, though it's a bummer because I've been interested, and certainly some of the UE5 features seem neat.
This is a good point! I think building a game really requires use to know what at truly want out of the game and have the ability to pick various technologies from various game engines and build those technologies for our specific games, so really ...reverse engineering certain technologies like Nanite, and Lumen so we can use it in our custom game engine.
Amazing video, Im a Unity guy myself (12 yrs daily, I cannot swap now!) but you held my interest and I enjoyed, subbed.
I quit Unreal Engine!
I prefer Unity 3D or Blender!
Hope that Meta Quest might make a 3D Remake!
"You just gotta make a mess. And make a prettier mess every time, until one day you're like 'Oh, this isn't a mess anymore.'"
That is such a good way to put it!
When I tried it, tutorials on TH-cam were like 4 hours long and tedious. The engine throws tons at you before you even know what you need for your goals. It doesn't make compositional design easy to do. Blueprints are easy but learn little about game dev and algorithms... but then their c++ docs kind've suck compared to unity c# docs because unity give examples. Plus c# is easy and I don't need the performance of c++ to bother adding that complexity.
Unity only falls hard if you making a AAA game or something that requires huge scaling, but 90% of indie devs don't need or tap into c++ so use blueprints which becomes spaghetti some times.
im struggling a lot and i dont know where to start to turn the blueprints in my project to c++ because teacher asked us to implement a few things such as data table, actor components, behavior tree and then for the last exam turn everything from BP to c++ lol e_e. Im gonna bleed a few months im sure of it. But since im artist ill learn another 3d software instead i hate coding.
@@Damian_DH It's easy to work with tbh, just a matter of knowing where to go. Code is code is code, even blueprints.
totally agree with the documentation. unreal really really need to get their sht together with it. unity's isn't prefect either but its a lot better
Oh well Unreal has started to give abit more Informations about it to the folks but i dont think they will make everything clear for everyone. They are Industry focused so wouldnt make pretty much sense for them
To be honest unreal engine 4 is significantly better for beginner developers because the UI isn't as complicated as ue5's. I also agree about the part where there's way too many different editors, components that do the exact same thing, and code things that are super helpful but impossible to know about without someone else telling you about it or a miracle happens.
I think the UI is very comfortable for 3D artists (specially coming from Blender) who are UE beginners
I fucking hate the new interface... It was WAY better in UE4.
Sounds like a preference thing. UE is my first game engine experience. Yes it has a lot of features, you just need to know what you want to do with what the engine provides.
Biggest issue with UE is instability; it crashes a LOT!
If UE is crashing a lot for you, it must be something you’re doing wrong or going about in the wrong way.
I think one of the reasons why people quit Unreal Engine or as a matter of fact, any other thing in life is INTEREST. I was so interested in learning Unreal so much so that I breezed through all the quirks and inadequacies in the engine. It is not a perfect engine nor is it the easiest to learn but with interest comes consistency and with consistency comes results.
My main problem with Unreal is blueprints. For some asinine reason they decided to make them binary files which makes collaboration with source control an unnecessary hassle. I do everything I can in C++ and just use blueprints for gui and particles for this reason. Also I find it impossible to organize blueprints without it looking like spaghetti, where I do not struggle the same with code.
I feel the information point you made. I'm not a programmer and I'm only new to Unreal and everytime I get stuck, I gotta figure it out on my own cause there is barely any documentation out there. Sometimes it feels like I'm not going to be able to achieve my goal because I'm going to get stuck on one thing and will never be able to figure it out...
I'm trying to use it in my motion design workflow. I hope to see more tutorials on that.
Me who is into Unreal, doing job since past few years as an Unreal Dev. Guys it is easy to learn but hard to master.
I am learning unreal 5 cause i want to make more complex games, but at the same time unity is kinda great for 2d games especially with its new input system, that new input system really has me in love with it. The only thing I am concerned about with unreal is assets.
Yeah, documentation. That's my biggest gripe. I've been using unity for about 10 years, and... When I started trying unreal, i found out that the documentation is... unreal XD
Its approach to everything seemed to be basically "it's easy, you just click this button", except that button is hidden in the third tab of the fourth item of the fifth submenu of a dropdown button next to the item on a sixth line of the property window of a specific component on the actor... and nobody tells you that. nobody tells you that PATH, they just tell you "oh, it's a button with this name". And it's not just documentation, I've noticed that community advice has a very similar problem.
It's like just because there's a button or menu item for almost everything, that means that it's easy and obvious, and you don't have to tell people where to find stuff, just informing them that it's PRESENT somewhere there is enough.
Oh, and my friend who's been working with unreal professionally for the past 10 years (including actual c++ programming in it) totally agrees with me on this point. It's probably the only point we both agree on in our engine debates =D
A lot of good points there but i believe everything comes down to dedication and effort user puts.
I pick up UE5 for cinematics, lightning and animations so i can make shirt movies and showcases. Im not interested to make a game but ...:
BluePrints for animations so i can us characters in my movies. Niagara, sequencer, a nimations, materials and blueprints.
All related to cinematography and making locations and sets for recording its on my list to learn.
Knowlage of Photoshop, premiere, Davinci, blender that's something necessary in my opinion to go along for my purpose.
I just make small projects and just learn on the go if i stuck then google, reddit and YT are my friends.
So far im really enjoying UE5 but i had my fair share of frustration and demotivation.
My advice just concentrate on what you need and then expand.
This is why I got into it!
@@WoodyDevs anther thing on my list in near future is Reality Capture but i dont understand there's pricing model exactly. Foe 10 or 20$ you get scan points ?! What i need to know how many scans can average Joe do with one of this plans scanning typical stuff around like hydrants bench in park or statues. Once i will get idea what im paying for ill jump in to it as well.
Unreal is great for art related things but it's a pain to work for programmers and c++ coders. Api is not documented, has wired structure and long compilation times once project grows in size.
Great stuff man I dug the video. I am really looking forward to checking out ue5 but still working on my current game in ue4, soon though I will get to check it out. I am looking forward to it.
I sub'd purely because your video is animated and not just a person talking lol. Well done!
The most difficult thing in unreal is learning blueprints . As if you are not from programming field. TH-cam provides everything you want , but its really hard to understand as a beginner becoz they just do it without telling in a understandable way . Unreal official youtube channel provides many tutorials but in a showoff way , not like a true tutorial. But overall you have to understand by your own by giving time in it.
C++ is way harder. I've learned blueprints quite easily, but I never managed to understand basics of c++
@@marcapouli7805 What you are saying have no sense. BP are just graphic C++, it's exactly the same thing. If you don't understand C++, I can tell you that you are not understanding what you are doing in BP too.
You need to start with the start, programming basics, C++ basics. It's pretty normal to not understand it just "like this".
@@AliziaKaline I've tried also python, css, java, html, and c# and I came to the conclusion scripted languages are not for me, and i don't like it anyway.
With BP, I can easily create a variable, a function, access almost anything I want and create anything I want. Maybe you are right I don't understand anything but when I take a forward vector and multiply it by something, I don't need to understand all the non sense c++ hiding under.
An other thing I've noticed. 9/10 c++ users I've talked to think they are superior, bashing BP users, it is elite they understand everything while other are just stupid people. I would fear to become a morron myself if by miracle I'd understand c++
The documentation was great during UDK / UE3 times. But now they just had too many updates recently and with all these new tools the documentation is just not enough.
So my learning experience, has been watch a 5-6 hour tutorial on TH-cam, day 1 I learned texture and material mapping, day 2 the difference between baked lighting and lumen and how lighting works, day 3 was landscapes and mesh stuff, day 4 was me let loose building a world map from scratch, I'm not done yet I'm taking my sweet time detailing the world pretty much letting my imagination run wild, letting the props and environment tell a story, but when I wanted to add a lake I had to take a whole lay just to learn how the water plugin works and how to set it up. My goal is to just slowly develop this world, flesh it out, then start implementing gameplay mechanics and stuff
My road map right now is world environment, then character design, then implementing crouching, simple actions. Item pick up and all that jazz, but it's been a long time since I've found a passion for something and I think development is it, I can't draw for shit so, this is letting my imagination free 😁
I started using unreal and love it, but I have been using it for a few weeks anyway especially after using unity for years..
You are right about trying and failing. I initially tried to learn unreal last year but gave up since it was too overwhelming to learn a new engine (especially after knowing how to use unity so well) I gave up. Then a few months later I spent a week simply following tutorials it was a real struggle so I actually gave up again. A few weeks later I tried again, and this time it was obviously significantly easier to follow (the same tutorials again), whereas before i had to struggle to get these tutorials now I would speed through them.
I guess it would be even harder for someone new to gamedev, I do think having breaks in-between failures giving it a chance to reset without completely losing the knowledge is a good idea.
What really has been gate keeping for me is the amount of game architect technical directors that has told me not to bother with UE, every single one of them told me they are development unfriendly.
When you are unable to find help from the forums or documentation, try finding a live stream or video(from the Unreal Engine channel) about the general topic you are stuck on. As for me, the live streams have been a really great help, moreso than the vast majority of tutorials.
You need to set a goal. Have a clue on what it is you want to do.
Coming from a vfx background and going into UE5 is great because it helps that you know the process of a production and what to look for.
At the end of the day, its a tool for you to create. You only need to learn what you need, honestly there's too much and they're always adding on to it.
You definitely need a blueprint before you actually start creating. That way you don't lose track of where you're going in your project.
Create a story first, then think of a look you want to go for. Add on to that with your base locomotion because that's what the players going to be playing 24/7. Everything else after is up to your imagination really. Good luck everyone!
I got back to ue4 because ue5 always crashes on windows 11 ( i know, i know..-.-) so for every project i have to change from DirectX12 to 11 and every couple mins it still crashing :(
What kind of system are you running? I'm just curious, thanks.
The SAVE/LOAD game system for me was/is by far the most frustrating hurdle to overcome in both unity and unreal. i still have no idea why both companies avoid this feature which happens to be a necessary feature for practically every decent game since the 1980s
every project ive given up on, it was the save system that caused it all to fall apart
Very happy in UE4, hope i can finish a game soon, first game, no original assets, design or sound.
Why People actually quit unreal:
Computer can't handle running a blank scene. It just crashes.
RIP GPU drought.
Where to start? You responded yourself: what do you want to do? Too many tools? UE5 is very straight forward from the beginning, even intuitive. UE5 is a tool, like all engines are. Use the one that fits with your project.
Best video on UE5 on youtube. Making my list now
As a game designer I really like UE, it gives me possibility to make game on my own without programmers and without necessary to learn any programming language. This the huge pro of UE.
Tools helps to make game faster/easier/better - there is no real competition between UE and other engines.
The unreal slackers discord helps me a lot for the bad documentation there are so many experienced helpful people. I don't know how people leran UE without a support discord